I have started to experience this issue as well with build 67342. It never happened before. I see the following in stdout when it happens : The program 'CoherentUI_Host' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 127994 error_code 10 request_code 130 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) It seems to be a different bug than #2617 ... Should I open a new one ? I'm running linux 3.14.0 with mesa 10.2.1 with the gallium driver.
The error code may be a platform integration difference. Does it match the pattern that you have ~14 CoherentUI_host processes normally, and none when the error occurs?
Yes it does. That's most probably because CoherentUI crashes on any Xwindow error tho. I'm still not sure it's the same issue as BadAccess is a clearly different issue.
I've been having the same problem, consistently, in all my games. For the record I've only been playing on the stable version on my MacBook Pro . To resolve it I force quit the game and then reconnect and its all good.
The clicking getting stuck hasn't happened today. However, I rarely have a full UI. I'm frequently missing the build bar and/or the command menu off on the side. I've never had the economy bar missing though.
I never had this issue before the latest update. Had to force quit my last game because i could not select anything. I hit escape multiple times. I could still rotate the camera and the game was still going but I just lost the ability to click or select anything with the mouse. Im using Windows 7 64bit.
Now I encountered my eco bar not showing up. The majority of the matches have some part of my UI gone. :-(
Looks like every single match I play has some form of the UI broken. Be it clicking, chrono cam, build bar, command bar, or eco bar, one of them won't work every single match.
I just had this too on Win 7. I was playing a skirmish with one other AI on my team against a single AI opponent. I was using the keyboard to alter my build queues (building bots) and after that my mouse clicks didn't register. The only mouse control I could do was move the cursor and zoom in and out with the wheel.
I have the exact same problem as brian, Every single game I have, i have some kind of problem with the UI, not being able to select my commander at the start, or even there not being a start annihilation button in the beginning and don't get me started on how many times I crash per game.
The game is not playable anymore since the last update. Is there a way to revert to 66830 ? I'd like to play PA !!!!
Just purchased this game yesterday through Steam and encountered this bug (amongst many others) on both my old Vista laptop and newer MacBook Pro. Both run the game fine (sort of..) but clicking stops responding mid-way through games every game I play. This is a show-stopping bug.
Nope. As soon as an update is pushed, the servers are updated, and everyone has to play on the new game version.
I'm experiencing this technical difficulty as well. This is literally a game stopper. This is a great game, I get it's not done, but I still want to at least play it. Now with the price reduction their are many new people playing this game. This sort of thing will turn people away. PA is going to start with a smaller fan base then they potentially could have if this game stopping bug is not squashed pronto. It would be most appreciated if a dev could post here giving us an eta of a fix or next update.
Agreed. It's a little concerning that this wasn't an issue, and now it is an issue, and it hasn't been fixed. While there have been several hotfixes released dealing with (in my opinion, less common and pressing bugs). Please! I want to play PA again! It's been a really frustrating... what, week and a half now?
