Hi Matthias,
Sadly, yes a big problem, but I am trying to identify if its a 3dConnexion driver problem or Capture problem..
I have a SpaceNavigator [I presume they all use the same drivers] with driver v3-4-2. This works fine on my 'old' low spec (P3 M) Laptop with XP.
I have a specific Highend Capture PC which is running Quad Core Extreme Processor, 3GB Ram and Nvidia 8800GTS Graphics.
Using same [3dConnexion] drivers on Vista kills Capture. Moving around a view with the mouse, the processor time spikes up from idle, then drops back. As soon as you start moving the view with 3dConnexion the processor time spikes up, but never recovers. Within a few moves, capture is holding almost 100% of processor time and never recovers this down. This causes the processor and system fans to increase speed to cope with the 'load'. Closing the project in Capture then recovers around 50% of the processor time, and closing Capture fully recovers the processor time.
As Lars from Capture seems to think this is a 3dConnexion driver problem, I have now tried the latest version [3.5.5] but that produces the same results. I obviously now need another Capture and 3dConnexion user to see if its a common problem...
Be really interested to know how you get on....
Thanks,
Paul