I've been able to reproduce this problem both on a laptop and a desktop machine, on two separate installs of Windows 7 x64 RTM
Can someone else confirm that this is not an isolated incident?
Same problem here. ATI 4870 1GB memory.
Adobe, no further responses on this one?
[Frames below may be incorrect and/or missing, no symbols loaded for AcXtrnal.dll]
I have exactly the same problem here (crashes and guide line is not visible).
ATI Radeon 4350 with 512MB
Windows 7 RTM
I have submitted all everything that they have asked me to, and worked with some of the support people, but so far have not found a solution as of yet.
I have just installed ACR 5.5 RC and the guide line is shown.
It might be due to the fact that I connect remotely to the box with CS4.
I shall verify in the evening and let you know.
The guideline isn't visible to me with ACR 5.5 on win7 RTM ultimate x64. I have a Dell Studio laptop with the Intel 4 series chipset.
People with the exact same issue should post their system info exactly as requested by Adriana, AND email it to her.
She didn't ask anyone to post the info and only one person to email her. If people feel the need to post their system info they should at least delete the serial number line.
My apologies for a false positive. When I tried ACR 5.5 RC from a remote desktop
(which is totally different graphics-wise) I saw the guide line.
But when tried from actual display the line was gone.
I just tried it through Remote Desktop, and you are absolutely right - I can see the guideline! I don't like doing my PS'ing through RDP though
I agree, it is impossible to use RDP.
The workaround for getting back straighten tools guide line is disabling Windows 7 Desktop composition feature.
You can do it once and for all by going to: Computer -> Properties -> Advanced system settings -> tab Advanced -> button Settings under Performance part:
Second approach is to disable Desktop composition only when you are running Bridge.
Right click on Bridge shortcut, tab Compatibility, and tick “Disable desktop composition”.
Hopefully Adobe will fix this issue, so we can stop making workarounds.