Bridge CC: Strange behavior with Nvidia's desktop manager

  • 1
  • Problem
  • Updated 4 years ago
  • (Edited)
Hi guys,

some month ago I got strange difficulties with Brigde CC: As I wanted to delete, copy, crop, duplicate, etc... some files via rightclick Bridge always maximized to fullsize (all over both monitors). After minimizing back nearly to the size before Brigde always loses it's scalefactor for the contentwindow an stayed maximized displaying only one file. So I had to readjust the scaleslider, too.

For one little operation via rightclick I had to do many more clicks for readjustment.That spoiled my pleasure working with Bridge as my favourite file browser. The german hotline recommended me to switch to a new profile - I did last week. At the beginning Bridge behaved as normal, but since yesterday evening the problem returned.

This morning I could find out one crucial reason!

I'm working with Nvidas Quadro 600 in my PC (two monitors Dell Ultrasharp 2410) and latest driver (340.66-quadro-grid-desktop-notebook-win8-win7-64bit-international-whql, but I tried also with the 320.00 - it's the same). The driver installs with many modules and among other software with the nview desktop manager. If I deactivate the desktop manager Bridge behaves normally, if I activate it back the problem returns: On/off --> it's absolutely reproducable.

But the desktop manager offers many nice features (e.g. the arrangement and behaviour of windows on my desktop, taskbar, etc..) I do not want to live without. Due to the strange behaviour of Bridge I leave it turned off, but hope that the development team could discuss it with nvidia and they will work out a solution comming with further updates.

One additional issue (which possibly could depend on the same bug): Photoshop and Lightroom remember their last position on desktop faultlessly (if they've been on monitor 1 or 2 before closing), but InDesign and Illustrator (always CC 2014) forget them and the main application starts always on 1 although all the opend toolboxes come up on monitor 2 (their latest position).

It seems to me that there might be some interfaceproblems between Adobe's CC and nvidia's displaydrivers.

Hope the development team(s) of Adobe and Nvidia will find a future solution!

Good luck,
Ralf
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Please let NVidia know about this so they can debug their desktop manager software.
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes
Hi Chris,

yes thanks, I would like to do, but who can I contact? NVidia Germany does not respond to my phonecalls and on the web I haven't found any forum on their site dealing with Quadro or software problems - only Geforce...

Do you or Adobes development team have any further contact information.

Thanks,
Ralf
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
We only have internal contact information. NVidia's feedback forums seem like the best place to start: https://forums.geforce.com
Photo of heyix

heyix

  • 10 Posts
  • 0 Reply Likes
Hi Chris,

after 5 months it's me again: Short question - what happens in the case?

As you at the time recommened I reported the problem to Nvidia's Geforce-Forum. Now the displaydriver is on release 347.25, but Bridge behaves as before (so I have to leave the display-manager further turned off). That in consequence does not help me for InDesign CC, that loses it's latest display-position by closing the application ( I reported this bug via the feature request form) - the toolboxes always stay in place, but the main application is forgetful!

Not very satisfactory for me. Could you please try another way to get this problem solved. E.g. there might be a bug in Bridge CC (no other application shows this strange behaviour, no tool has any problems with the display-manager). So it would be very nice if you could carry on this topic to a higher Adobe support level.

Tanks,
Ralf
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
There's not much we can do. NVidia needs to address the bug in their software.
All we could do is try to replicate the issue that you're seeing and report it to NVidia.