Cubemen Crashes/Launch Fails - Please Read!

[SeonR]

There are currently 3 crash/launch issues that players are finding:

1. Game randomly crashes on launch (Effects Windows only)

This issue is a Game Engine specific issue and and is being fixed by the Unity game engine folks. As soon as I have an updated engine build, i'll get new versions out.

This issue is currently only effecting a tiny amount of players, but if you are one of those, I am truly sorry, and I am pushing the Unity guys very hard on a quick fix.

2. Game won't run on Linux with with ATI drivers. ( Linux Only )

Fixed in 1.28

3. Game wont start on 64bit Linux installs ( Linux Only )

This is due to Steam not loading all of the 32bit dependancies it should be loading considering it is 32 bit only. Please try installing the ia32 libs and see if that makes Cubemen work.

[SeonR]

For Linux users with ATI cards that are having trouble running Cubemen with the latest 13.1 drivers, a user in the thread below managed to get Cubemen running after doing a removal and clean install of the latest driver.

http://steamcommunity.com/app/207250/discussions/0/828924672576957932/

This might be worth trying in case there is an issue when doing an Upgrade over old drivers, compared with installing clean from scratch.

Anyone that tried this, please post back here about your success or failure. Thanks :-)

[SeonR]

Ok, it seems my latest 1.28 build works around the ATI driver Linux Shader crashes and reports back from the community here is that this issue is fixed *for now* :-)

[Bugs Bunny UA]

I have a problem on Windows 7 x64with nVidia optimus driver, that "get thread context failed", but as I understand it's Unity problem, as I get same problem with Spectraball game.

[SeonR]

Please see this thread.

http://forum.unity3d.com/threads/172759-Unity-4-0-1f2-and-avast-8-0-1482-quot-getThreadContextfailed-quot-error

[Bread Rust]

Usually a "quick fix" doesn't take three months, can you explain what's taking so long on that?

[SeonR]

As posted above, this seems like an AVAST + Windows issue and is fixed by not using Avast. This is the cause from my understanding, as I have been told my the Unity folk. If you are seeing the error and not using Avast, please send me your output_log.txt fel from your Cubemen_data folder and I can pass it along to the Unity devs.

[Bread Rust]

Αναρτήθηκε αρχικά από SeonR:

As posted above, this seems like an AVAST + Windows issue and is fixed by not using Avast. This is the cause from my understanding, as I have been told my the Unity folk. If you are seeing the error and not using Avast, please send me your output_log.txt fel from your Cubemen_data folder and I can pass it along to the Unity devs.

Is there any other way to fix it? I'm not really willing to disable my security program.

[SeonR]

Not that I know of. The Unity engine guys are aware of the issue, but but it's not actually a Unity specific issue, There are lots of apps and games that are suffering from this issue when used with Avast. The Unity developers have not dismissed it, but are at a loss as to how to fix it as it's Avast itself that is causing the memory segment fault due to how it protects memory.