Celestia has worked well for me in the past but with the last few updates I have had some problems with mouse movement. When I click and hold both mouse buttons to quickly move in and out on an object and then let go of both buttons simultaneously the object I'm veiwing snaps eraticly, usually off the screen. I'm not sure if this is a bug in the program or a problem with my mouse driver but this is the only program I experence a problem like this in. I'm running Windows XP. If anyone is having a simaler problem and knows how to correct it please let me know.
Thanks,
Nick
Erratic snap motion when moving with mouse
Which version of Celestia is showing thie problem?
I do not see that problem under WinXP sp1, Nvidia GF4 Ti4200, Celestia 1.2.5pre6, when doing two-button movement using either a USB mouse that includes a wheel (Microsoft Optical Intellimouse) or a PS2 mouse with three buttons (DEC labelled) running on my system at home.
However, I *have* had the problem you describe under WinNT4 sp6, ATI Rage Pro, Celestia 1.2.5pre4. When releasing both buttons, the viewpoint jumped to a different (nearby) location. Shortly afterward I replaced the mouse by one with a wheel and upgraded Celestia, too. I haven't actually tried to use two-button movement on that system since then, so I don't know if the problem still exists. (That system's at work and I'm not, so I can't check it right now.)
I do not see that problem under WinXP sp1, Nvidia GF4 Ti4200, Celestia 1.2.5pre6, when doing two-button movement using either a USB mouse that includes a wheel (Microsoft Optical Intellimouse) or a PS2 mouse with three buttons (DEC labelled) running on my system at home.
However, I *have* had the problem you describe under WinNT4 sp6, ATI Rage Pro, Celestia 1.2.5pre4. When releasing both buttons, the viewpoint jumped to a different (nearby) location. Shortly afterward I replaced the mouse by one with a wheel and upgraded Celestia, too. I haven't actually tried to use two-button movement on that system since then, so I don't know if the problem still exists. (That system's at work and I'm not, so I can't check it right now.)
Selden