Sure, there's nothing changed in that regard.

However, future WED version will allow to adjust the mouse sensitivity. Maybe this helps in your case.

This bug still exists in A775 pro beta!
I tried adjusting the mouse speed and this doesn't help.

For me to upgrade my developement version, I need to buy a new computer !!!

I don't understand why only I am having problems. (Only in A770 or higher WED on my Laptop)

It has only happened since the slice wire and slice plane tools were added to WED, could this be a clue?

Jethro.

It could be anything, but is probably unrelated to the slice tools. The WED mouse functions were not changed in ages. Only in the last version, the mouse sensitivity setting was added due to your problem. But this apparently did not affect the problem. So the only conclusion that I have now is that it's some very strange mouse driver bug that for some reason only happens on that one PC and nowhere else, and only in combination with WED.

Some mouse drivers allow to activate different mouse settings depending on certain applications - is it possible that you have activated such a setting for the application "WED.EXE"?

Otherwise, the only suggestion I have is that you install some different, generic mouse drivers, such as the Logitech mouse driver. Or buy a new mouse. Buying a new computer, I guess, would be sort of overkill.

This bug is now fixed in Beta V 7.76. I don't know what you did, but its now fixed, thanks.


Jethro.

We did nothing, but it's good to hear that it works now. If the bug occurs again, the next thing would be trying a different driver as suggested above.

Have the same bug before. At V7.77 it works fine if the Properties Window is close, but if the Properties Window is open, then the Entity is rotate like a helicopter. Have a Laptop and a Desktop PC, at both System the same problem...

yeah strange thins happen if you dont dock the properties window to one of the sides.

@Quadraxas: I dock now the Properties window and all works fine. Thanks.

But it should work also with undock window....

I confirm this bug. This will be fixed.

Thanks to jcl