on the new MacBook Pro 2016 moi3d is almost unusable, when you move the objects with the mouse its jumping and when you move the app windows, series graphic glitches happen... :-(


cheers

torsten

Hi torsten, that might have something to do with the retina type display, where the OS tells some apps (like MoI) that the screen is actually 1/2 of its actual width and height, and then draws a stretched image. The libraries that MoI v3 and earlier are built with have some problems with that. That's another area that should get cleared up with MoI v4 as well.

For the app window movement glitches, do they go away once you actually finish moving the window?

- Michael

yes michael they do... :-)

Hi torsten, if the window movement glitches go away after you've finished moving, that should not really cause any difficulty itself in using the program. I know it looks gross but that's going to fall into the "cosmetic" category and it should be resolved with v4.

Can you describe a bit more about the jumpy mouse problem though? I haven't heard about that one before and that sounds like it could impact work.

- Michael

when you orbit with the mouse and make small movements it kind of jumps more than you actually move...

Hi torsten, does it only happen during view orbiting? What about other mouse things like drawing?

Does the jump look like the mouse cursor gets larger for a moment? Maybe you're running into this new OS feature: https://www.tekrevue.com/tip/cursor-bigger-shake-to-locate-el-capitan/

Try going to your Mac system settings under System Preferences > Accessibility > Display and turn off "Shake mouse pointer to locate", does it go away after that?

- Michael

hi michael,

no I turned that feature off already, as far as I see its only while orbiting the mouse...


cheers


t.

Hi torsten, that's too bad I was hoping that was it.

Unfortunately right now I have no idea what you're running into with that - I have not been able to observe any differences in mouse orbiting behavior while running on Sierra over here, nor heard anything about it from any other users as of yet. Maybe if more people run into it I'll be able to find a common element and narrow down the cause.

Hopefully it's another glitch caused by using X11/Wineskin and will be solved by v4's native Mac build.

- Michael