Fix for Linux CoherentUI issued!

Coherent emailed me last night saying "we will let you know when we finish testing the fix", and this very morning with the actual "fix" posted here (it's more of a slight improvement while they investigate the issue). This is not something we've been sitting on for weeks, this is a bleeding edge fix hot off the presses. We're not trying to withhold fixes -- we're aware of the problems, which is why we've been talking to Coherent about it.

I've been swamped in very urgent work today, and I have not even had time to consider what the risk of integrating their update this late would be. Don't worry, we'll ship it soon, and once Coherent has a more thorough fix, we'll ship that too.

Slight Improvement? I was able to play a 5-hour GW game vs Metrarch the Machinist wherein which I produced about 22,000 units. UI worked all the way thru. Seems pretty "fixed" to me. Of course, it may not be perfect from a programmer perspective, but it certainly works from the player end.

So it looks like you should have your fix within 24 hours Linux lovers!

*Czechs Calendar* Right on time for 1.0 release too.

Your welcome.

Yes. @jorgenpt has confirmed my guess about what changed. Actual problem is some crash within view renderer process (or even one of it's threads). Unfortunately as result there happen failure with shared memory access which trigger error in X11 library that cause shutdown in previous version of Coherent.

Now problem is still here (at least on game window resize), but Coherent devs add code to handle X11 error properly so it's no longer cause shutdown of whole "host" if occur. Though you still might see "X error received" in log which likely mean that one of views has crashed.

PS: Also just to be sure are you talking about playing with "--software-ui" or not?

Nope, --software-ui breaks my cursor. Completely unusable.

Also, the bug everyone was complaining about was, at its core, about the fact that the Host UI shut down instead of handling the error correctly and continuing. Its like a rock concert ending because the bassist missed a single note halfway thru the first set. This has been fixed, which is what we wanted. The fact that the UI errors still occur is not the critical issue here, and is tolerable.

This is in fact the most encouraging news from Uber or Coherent about the state of Linux. Really shows they are in fact aware and active on issues that come up with this new software. Because I know it is important for us and them that it work correctly crossplatform as intended.

I am real excited about this little ray of sunshine, this means Linux has a fix for functionality come release day? That makes it slightly north of the Starbound public access.

Linux, Uber, Coherent, and the people hoping for the most well-recieved launch, all just got real lucky with this solution come to surface.

Problem is: if view that handle hotkeys going to crash it's will break the game and without hotkeys you can no longer reload UI. So it's still serious issue and have to be fixed.

Hotkey's being broken is still an issue of lesser priority and seriousness though. We will have to advise Linux users to not use them for the time being.

You can't open menu without hotkeys.
Anyway I pretty sure it's will be addressed soon because Uber will release stable version and will be able to work on unstable stuff again.

Yea, but generally the crash is a probalistic thing, and if you limit yourself to using esc, the likelyhood of running into the problem falls to negligible. Much better odds than before still.

Personally I doubt that crashes actually related to usage of those certain views features, but who knows...

And patch with fix is live folks, let's play some games.

It should be possible to work around that by using the UI debugger. You an also always reload a scene by F5 in the debugger.

I'm going to test it, but I'm mostly sure there won't be any "scene" anymore if renderer crashed.

Well sure you can't reload a dead scene, but you should be able to open the main menu, if not that exact scene has died.

Some weird things happen to Coherent when such crash occur. I not even sure that debugger remain usable at all...
I just tested it and first I get scene list, but scene screen was blank and after some point debugger fail to retrieve list.

So It's doesn't looks like you can keep ability to reload parent view.

Is the rendering for the PiP broken for anyone else?

Some screenshot to show what did you mean exactly?

@Brokenshakles and @SXX,

I was just playing and when I opened the PiP it was completely black except for showing icons correctly. I turned on the back facing option (as that's what I opened it up for) and switch to another planet and back the it lighting faded in. I've had this once before at the beginning of a match (not n PiP) but it cleared up after a few seconds by itself that time.

Edit: I loaded up a couple of replays to see if I could reproduce the PiP issue and grab a screenshot and had the delayed fade at the start of one of them:

Don't see same thing with open source drivers, but didn't tried replay screen yet.
I feel this is what happen when one of view crash so interesting if you guys can check your Coherent logs.

Only annoying glitch I have with open source drivers is this one: when I choose unit build bar and unit list only partially appear on screen until I move cursor over them. What interesting unit health and stats panel also appear glitched in first place but then fixes itself.