Skip to main content
Wes Duenkel
Inspiring
December 12, 2023
Question

Loupe Movement "Sticky" or "Jerky"

  • December 12, 2023
  • 3 replies
  • 1214 views

Loupe movement in Bridge is "sticky" or "jercky." When using the mouse OR the trackpad, the speed of the curser needs to reach a certain level before the loupe will move. Once it does, it "jumps" too far.
There is some kind of bug or issue with the loupe where it ignores low speed mouse moements or something. This makes the loupe view less useful.

 

This has been an issue for at least a version or two.

 

To test:

1) Select an image (more than one helps to exaggerate the issue).

2) Enable lopue by clicking once in image

3) Try to move loupe slowly.

4) Notice nothing happens until you move cursor faster. Then it jumps too far.

 

Video attached.

 

Please address this.

 

Bridge 14.0.1.137, 2023 Macbook Pro with M2,  Mac OS 14.1.2

3 replies

Wes Duenkel
Inspiring
June 12, 2024

This is STILL an issue with 14.1.1.271 BETA!!! What the hell is going on?

Participant
June 12, 2024

Hi, It's now maybe 2 or 3 years since I have this issue (last version of Bridge that I am using - for this reason - is 2022), so - I don't think Adobe is giving this priority, maybe not even aware of it (it's not very often people complain about it when I did google search...) It would be nice but I don't expect fix anytime soon - they probably need to change the whole "zoom in" engine, as they're not fixing the issue in current one 😕😕 Maybe we (as in - many frustrated people :)) need to contact the support directly

Adobe Employee
January 5, 2024

Hi,

 

Thank you for the feedback.

 

Could you let us know if you are using software or hardware rendering so we can understand this issue better?

Please check this by going to Preferences dialog -> Advance tab -> Use Software Rendering (is it enabled or disabled)?

  

Regards,
Bridge Team

 

Wes Duenkel
Inspiring
January 5, 2024

The behavior is the same regardless of the setting. 

Wes Duenkel
Inspiring
December 19, 2023

This is still an issue with Bridge BETA 14.0.2.150.