Thanks Olof. I’m not a very technical player when it comes to coding. Can you give me a bit more advanced instructions on how to use this code? In terminal? -force-glcore
never mind figured it out using Steam. Thanks Olof. Great job on this game. I love it.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
Hi everyone, we need some help to troubleshoot this missing text issue. From the Unity forums we might have found a possible culprit and solution. However we have no computer in house with an M1-chip so can’t test it ourselves and want to find a more robust solution than altering the Launch Options.
With the next release (beta 7.1-2) (not the hotfix Olof just pushed), the “fix” will be implemented, and if someone could test it (remember to remove the launch options) that would be greatly appreciated!
Hey ! I’m the one who pushed an issue this afternoon
I have a M1 so I’m ready to test if you want me to test. How ?
Play on to the experimental branch (right click on ACEO in your Steam library => Properties => “Betas”-tab => Select Experimental (no access code needed)). Then make sure you removed (if once entered) the launch option -force-glcore from the application. That’s all, simply report back on if the UI looks like it should or if it’s still bad.
The fix hasn’t yet been deployed, but I’ll let you know when it drops
UPDATE: Fix deployed
Everything was working well (almost well in fact, except some graphics bugs on grass stands for example) with the “-force-glcore” option and beta 7.1-1 yesterday.
With beta 7.1-2, without any options, bug is back. I’m so sorry for you @Alexander
If I set back the “-force-glcore” option with beta 7.1-2, strings are back.
Thanks for testing We will simply need to investigate some more
So we’ve ordered an M1 MacBook in order to deal with this, will be awhile before we get it an can set everything up but do rest assure that we will solve this. Will keep you posted in this thread and hopefully solve it before the 1.0 release.
This just shows these guys dedication… Ordering a new MacBook to get a bug fixed!
Well, Apple will most likely drop the Intel CPU in a not too distant future meaning all Macs will run on the M chips, so if want to be able to continue supporting the macOS platform we do need a machine like this. Plus, it does look like it’s a lot better than the current Intel generation, so I’m not really complaining…
We’ve located the issue and will push a fix either part of tonight or tomorrow’s experimental update.
How’s the new machine?
FAST. The previous one (now in Fredrik’s possession) starts to sweat when you build the project library, emulating the sound of a jet engine. This one didn’t even start its fans… … and that’s even on Rosetta as the Unity editor is not a native M1 application yet.
Incredible improvement almost worth the money, but being able to solve this bug so quickly as we expected is the real treat!
From another M1 user. Really appreciate the effort that is going into solving this issue.
Unfortunately we have found the root cause of this issue to be Unity related and not an error on our part. A shader relating to the heatmap rendering is not handled correctly by the engine and that causes the text labels to disappear, it sees to be some sort of parsing issue when running the game on the specific combination on Apple M1 and Metal and the various exceptions we’ve tried does not solve the issue.
Will reach out to Unity to try and get this fixed but it’ll probably take some time before we can find a solution.