Braid got an update today:
Changes since original build:
- Added support for systems without S3TC support.
- Added support for PowerPC and 64-bit Intel Macs.
- Added support for amd64 Linux systems.
- Possibly fixed never-ending black screen that some Mac players experienced.
- Now attempts to choose correct language at startup, if a translation is available, on both Mac and Linux.
- Added notes on useful command line options to Linux README.
working fine under fedora 14 64bit!
New builds of Braid and Cortex Command address (almost) all the complaints so far (S3TC, installer error, intel64, readme). "Ultrapolling" mouse is still broken in Cortex Command, but the workaround is easy so no biggie for now. Good job on the new build Svartalf! Good improvement on the documentation icculus (can't say more unfortunately as the new build introduces a fatal bug).
Update to my last post: the fatal bug in Braid is related to the shipped version of libstdc++.so.6 in the amd64 build. Game works fine if I let it link to my system's libstdc++.so.6. So good job icculus as well!![]()
I have CC segfaulting on start. All that appears in the terminal is
xxxx@Blackline:~/CortexCommand$ ./CortexCommand
Attempting to start PulseAudio sound driver
AL lib: pulseaudio.c:485: Context did not connect: Connection refused
[Error] Failed to Create OpenAL Device.
[Error] OpenAL Error: (null).
PulseAudio unavailable, attempting next sound driver...
Attempting to start ALSA sound driver
Initialized sound against ALSA sound driver.
Shutting down Allegro due to signal #11
Segmentation fault
System is Ubuntu 10.04 32 bit Nvidia AMD CPU
How about deleting the libopenal.so.1 and using the system wide one?
Moved libopenal.so.1 out of my CortexCommand/libs directory and onto the Desktop. Same results as before:
Attempting to start PulseAudio sound driver
AL lib: pulseaudio.c:485: Context did not connect: Connection refused
[Error] Failed to Create OpenAL Device.
[Error] OpenAL Error: (null).
PulseAudio unavailable, attempting next sound driver...
Attempting to start ALSA sound driver
Initialized sound against ALSA sound driver.
Shutting down Allegro due to signal #11
Segmentation fault
ALSA seems to be starting, (I don't have any issues with it anywhere else that I'm aware of). Is there any way we can see what Allegro is choking on?