Does it help if you select the now working, no GPU rendering on the GUI, in the launcher?
We are still using CEF as the GUI solution which runs a full chromium browser in the background acting as the UI, and that takes a lot of power as well as there’s communication overhead from getting the pixels to draw from it.
I’ve talked about changing the GUI library for a long time:
But I haven’t found anything suitable, and I haven’t had the time to write my own. To finally fix the low performance and not working on intel we might be looking at another graphics engine change, so there’s a ton of stuff for me to do…
Being able to engulf your own species is an unintended effect of how engulfing is checked (note that shooting toxins at your own species has been blocked forever). I created an issue to track solving it:
How is this an issue? The wobble is made in a shader based on the total elapsed time from the point of view from the graphics engine. There’s no easy way to “pause” that.
Do you have a suggestion for how to do that? It currently has the @ and after that it shows the conditions affecting the process.
The compound concentrations in the environment move very fast due to the way the fluid simulation is. The cursor samples a single point beneath it, from that it is not possible to tell how much the player would get from absorbing the cloud, as the compound distributions vary in it, and the clouds dissipate over time. There’s also the fact that absorbing things only a part of the compounds is absorbed based on a constant ratio, this last part could be tweaked, as well as a multiplier could be applied to the shown amount.
Green is ATP production, red is ATP consumption. I was basically the only one trying to get the features complete before release. I did not have time to separate the bars per organelle type or add tooltips.
That’s interesting. First time I see that. Usually the bsf errors of the form: Cannot create ... mean that graphics drivers are not behaving as they should.
However I do also get occasional crashes when exiting the editor which seems to be related to memory corruption somewhere in the graphics engine: