The Humble Indie Bundle #2 Has Arrived

[Svartalf]

I know packaging an own Flash version has its pluses but they could also provide *both* executable & an SWF file, that would be the easiest solution IMHO.

That's kind of what I'm going to suggest to them. Think of most of these studios as being a bit of a "newbie" at this sort of thing on Linux, even if they've been using Linux for a while.

[jophos]

This issue has been already addressed in this thread, it's just because Machinarium is bundled with a 32-bit Flash Player, you need to unbundle it creating an *.swf file and run it with a 64-bit Flash Player. Look at previous pages for the solution.

I managed to miss out the middle of the thread. I should know better .

How did you disable/remove PulseAudio?

I'm afraid I cannot remember the exact process, but I did uninstall pulseaudio rather than disabling it. I also uninstalled gstreamer0.10-pulseaudio and ran gstreamer-properties, then changed the defaults to Alsa. I imagine that I should have changed the OpenAL settings before, but I am still slightly surprised that Osmos did not work out to use Alsa by itself.

RE the Cortex Commmand problem; it is the same as that mentioned by Xipeos on page 3. I actually read about this before I installed *facepalm*. I will just have to wait for the next build.

[Xipeos]

RE the Cortex Commmand problem; it is the same as that mentioned by Xipeos on page 3. I actually read about this before I installed *facepalm*. I will just have to wait for the next build.

Svartalf fixed both problems (that I mentioned) in the new build (b24-12162010). Re-download and it'll be fine .

[jophos]

Svartalf fixed both problems (that I mentioned) in the new build (b24-12162010). Re-download and it'll be fine .

Whoops! I assumed that because both my copy and that which is linked to by HIB:2 are named as build 24, that the fix hadn't be released yet.

I ran the uninstall script from my original build and then installed a freshly downloaded version linked to by the Humble Bundle site, yet I still get the same error.

Abortion in file ../System/ContentFile.cpp, line 576, because:
Failed to load datafile object with following path and name:
Base.rte/GUIs/Skins/MainMenu/text

[Svartalf]

I managed to miss out the middle of the thread. I should know better .

Happens...

I'm afraid I cannot remember the exact process, but I did uninstall pulseaudio rather than disabling it. I also uninstalled gstreamer0.10-pulseaudio and ran gstreamer-properties, then changed the defaults to Alsa. I imagine that I should have changed the OpenAL settings before, but I am still slightly surprised that Osmos did not work out to use Alsa by itself.

That's because OpenAL isn't set up to help you there. You've got to explicitly iterate through the list <*waves hand*> OR rely on .alsoftrc to tell you which is the default. Osmos probably uses the latter option as it's a bit clumsy if you're not using an OpenAL sound engine wrapper like I am.

RE the Cortex Commmand problem; it is the same as that mentioned by Xipeos on page 3. I actually read about this before I installed *facepalm*. I will just have to wait for the next build.

"The next build" should be up already. Re-download and if there's a problem there still let me know. Since you discombobulated Pulse the "right" way, it should just roll-over to ALSA properly. If not, report THAT...

[Svartalf]

Whoops! I assumed that because both my copy and that which is linked to by HIB:2 are named as build 24, that the fix hadn't be released yet.

I ran the uninstall script from my original build and then installed a freshly downloaded version linked to by the Humble Bundle site, yet I still get the same error.

Hm... That's the problem with the original code. It only shows it's ugly head when you have Intel on 64-bit and some of the later libc versions- but ONLY on those configurations. AMD, earlier libc, no problem occurs. The uninstall from the old script might've oopsed something since it wasn't working QUITE right (Older version of MojoSetup...) when you put spaces into the install path. Try running the uninstall again, then nuke the directory completely if it still exists, and then try with the b24-12162010 version of the binary.

Let me know if you're still having problems. Be more than happy to help you work through them.

[Kano]

Why is the old b24 linked now?

[Svartalf]

Why is the old b24 linked now?

No earthly idea. Not MY or Daniel's doing, I can assure you.

I'll check into it, gang, and get back with you. (Well, that'd explain the mystery repeat of the issues from the original release...sigh...)

[jophos]

Hm... That's the problem with the original code. It only shows it's ugly head when you have Intel on 64-bit and some of the later libc versions- but ONLY on those configurations. AMD, earlier libc, no problem occurs. The uninstall from the old script might've oopsed something since it wasn't working QUITE right (Older version of MojoSetup...) when you put spaces into the install path. Try running the uninstall again, then nuke the directory completely if it still exists, and then try with the b24-12162010 version of the binary.

Let me know if you're still having problems. Be more than happy to help you work through them.

Thanks for the help. I already tried uninstalling and nuking the directory (just uninstalling leaves the screen "abortscreen.bmp" dump behind). I still have the same error whenever I install though. I have no spaces in my install path "/home/jophos/CortexCommand/". Maybe I am just being dense; The only link to the binary that I have been using is the amd64.bin available through the HIB:2 site. Is there a different source to the updated binaries that you are building, or could it be that the server from which I downloaded the file has not been updated yet?

[jophos]

Thanks for the help. I already tried uninstalling and nuking the directory (just uninstalling leaves the screen "abortscreen.bmp" dump behind). I still have the same error whenever I install though. I have no spaces in my install path "/home/jophos/CortexCommand/". Maybe I am just being dense; The only link to the binary that I have been using is the amd64.bin available through the HIB:2 site. Is there a different source to the updated binaries that you are building, or could it be that the server from which I downloaded the file has not been updated yet?

It seems that the answer has been given while I was fumbling at the keyboard.

ETA: 1 min edit rule is quite harsh.