Okay, so it's been two hours or so now and I just had my first Maya "crash".RVeldhuyzen wrote: ↑Mon Feb 08, 2021 6:25 amOkay, this is really early, so don't read too much into it, but .... WOOHOO!ngomes wrote: ↑Mon Feb 08, 2021 6:17 am 3Dconnexon has released "beta 14" (revision r3295) of the new driver for macOS. The "beta" builds can be downloaded from the FAQ page linked here. A change history summary is available on the top post.
The issue affecting button support in Blender is resolved (MAC-277). We have also modified the Maya plugin in an attempt to minimize the "flickering" issue (MAC-278).
I've been working from 9am this morning and have had to restart Maya at least 42 times so far because it crashed, and have almost gotten used to the flickering.
I just installed this beta and used Maya for a few minutes, but so far NO MORE FLICKERING!
I expect to do a few more hours of work today, so I'll check back in later to share how it's going. But so far so good
Again, this morning before installing this latest beta I had dozens of crashes (the 42 I mentioned before was an exaggeration, but after thinking about it, I experienced around 20 or so crashes), since the update just a single one, just now! And still no flickering, the flickering seems to have been fixed.
Working for the past two hours made me feel like suddenly relaxing my shoulders after not realising I had been tensing them for hours, you know. Thank you!
But this latest "crash" is a weird one. In the previous beta where you thought you fixed the Maya issues but I reported seeing no change. What I did notice was that the crash where the background would turn black and it would crash a minute later disappeared, that crash didn't happen anymore.
A new crash did occur in the previous beta. Maya would suddenly not respond anymore. When clicking anywhere in a Maya window MacOS would give the error sound like you were clicking in a window that had a pop up active, so your click in the parent window is blocked because the pop-up overrides it. Maya would not respond to clicks, the keyboard or the SpaceMouse Pro, giving the MacOS blip sound when clicking. After a minute or so of this Maya would crash to desktop. The only thing that did respond sort of was the SpaceMouse button I have mapped to "undo". Pressing that would make the command line in Maya display an "undo que is disabled" error (pressing CMD+Z didn't have that effect).
This lates update seems to have fixed a lot. Like I mentioned, just a single crash which was almost the same as what I just described. Maya/MacOS would act like Maya had a pop-up open which would not allow interaction with any other Maya window. I checked, there were no other windows. I could move the Maya windows, but not scale them. I could do anything else in MacOS, just not interact with Maya. Same as before.
The difference was that this time Maya didn't crash. It just sat there, ignoring me
I had to force quit it to restart.With maya still open I opened the demo apps in the system tab, both of which showed the SpaceMouse working just fine.
Turning the SpaceMouse off and on again didn't change anything.
Another small issue, not a mayor thing but a small annoyance is the Lock Horizon thing. With it turend off the camera "roll's". With it turned off it doesn't, which is the way I prefer it. I have "Lock Horizon" mapped to a button since I don't think that is a Maya feature, is it?. When Maya launches the feature is turned off. If I press the mapped button, nothing happens. I press the button again the feature activates and the camera operates like I want.
I seem to remember that in the past there was a 3DConnextion menu option in Maya where I could tick a Lock Horizon option. Am I remembering that, right? I think I set that over a decade ago and it just migrated along through updates of the driver, maya and MacOS and even Macs, but this beta might have lost it.
Having that menu might solve this issue without needing to activate the option every time Maya starts?
