At apparently random intervals, my Mac (early 2013, i7 quad 2.5ghz, 8gb ram, Radeon 6770m) will lock up as far as camera movement (arrow keys) and mouse moves, but no clicks register with the game. Everything plays on as far as existing orders, but I can't interact any longer after that point. I can press buttons, I can hit escape to pause or quit (but pause seems to allow game to proceed behind pause screen lol), I just have to quit at that point. I'm seriously sad, having just bought the game at Pax (I'm an old TA/TAUIP guy) and was REALLY looking forward to this one. Any thoughts on how to deal with this? System info below for base system and video: Hardware Overview: Model Name:MacBook Pro Model Identifier:MacBookPro8,2 Processor Name:Intel Core i7 Processor Speed:2.5 GHz Number of Processors:1 Total Number of Cores:4 L2 Cache (per Core):256 KB L3 Cache:8 MB Memory:8 GB Boot ROM Version:MBP81.0047.B27 SMC Version (system):1.69f4 State:Enabled AMD Radeon HD 6770M: Chipset Model:AMD Radeon HD 6770M Type:GPU Bus: PCIe PCIe Lane Width:x8 VRAM (Total):1024 MB Vendor:ATI (0x1002) Device ID:0x6740 Revision ID:0x0000 ROM Revision:113-C0170L-573 gMux Version:1.9.23 EFI Driver Version:01.00.573 Oh, display is external ASUS connected via HDMI running 1920 x 1080. Thanks! abenderx
Did you have PIP open and by any chance did the planets look warped like: https://forums.uberent.com/threads/list-of-bugs-in-build-71378.63273/page-4#post-986086 https://forums.uberent.com/threads/list-of-bugs-in-build-71378.63273/page-5#post-986259
Ignoring the warped planets seems like the same selection and zoom freeze issue. Next time try toggling PIP and let me know what you see... then force quit PA and reconnect. In my case it seems to be something that triggers in particular games and keeps recurring in the same game but does not trigger in all games.
OK, it doesn't affect the same place/time each time it happens. Once the mouse won't select and keybd commands stop working, I do notice that the PIP just goes blank. The PIP doesn't seem to cause the issue, because I wasn't using it when it locked up. Once it locks up, I do also notice if I cmd-tab to the desktop, the system resource are just maxed out and nothing the OS is extremely slow until the force-quit of PA, after which the resources get reclaimed and things go back to normal. This is really lame. I love the game, but committing between 15-30 minutes after which the game is unplayable and the current battle lost by default, that's really not good. No crash, so no crash report available. Any ideas?
Might also be related to: PA#3989 Next time it happens see if your system responds again if left for 1-2 minutes. I haven't seen this in the latest PTE builds... although that doesn't mean it's fixed.
I'll try to wait it out and see. Thanks a ton for the attention mikeyh, it's always nice to see interested people on support boards!
Well, no joy on waiting it out or hitting keys until it comes back unfortunately. I have about a 40% chance of having a lockup of mouse clicks and keyboard commands except for escaping to the menu. Once I've clicked on pause (yes, mouse clicks work on the game menu, just not in the game once this occurs) I can wait a while and it's still broken when I return to play. It's extraordinarily frustrating as it only occurs after a while of play, never early in a match. I would really appreciate any ideas from devs or other Mac users, because I'm not finding anyone with similar issues and this game is hard to justify playing when I only have a bit more than a 50-50 chance of even getting to finish a given match!!!
Yep... I can confirm this is still an issue in 71729 on OS X 10.9.5 (13F31)... locked up twice in same game requiring a kill / reconnect. Also seeing regular client crashes after game start.
I should have added it in my initial entry, but my OSX version is OS X 10.9.4 (13E28). I'm playing 71729 as well, although I do think I recall steam updating it within the last day or so, meaning this bug may have been in the previous version as well. Hope this helps the devs to figure this out!
I'm also an exclusive OSX player with roughly the same specs as your MBP (late 2014, 16 GB, Intel Iris Pro), and I've been playing long enough to accumulate some workarounds for the "quirks" on the mac build. 1) Restart the app after every match. 2) As soon as you land, set a camera anchor to your start location. Recall it when the screen goes blank and nothing else works. 3) The sim used to stall and crash, but it's gotten a lot better at recovering. These days the issue you're reporting has been rare for me, but things may have changed in the latest 71729.
This started appearing for me after PTE 71378. Next time it happens I'll take a look with the Coherent debugger.
