By chance I found that F11 did this on my system. If it's anywhere in the menus, it's not where I'd expect to find it. Very odd.

Ah... no; I see now that F11 has this effect on everything on my system (which is a fairly basic Lubuntu install). Apologies for being misleading. (Unless it does work for you, in which case I'm pleased to have been of service :)

edit: I'm also pretty horrified by some of the comments made in this thread. Insulting the developers is not ok, people (and I really can't fathom how any of you might have thought that it was).

Thanks for the info!

I wouldn't make such assumption. 32 bit only x86 computers aren't manufactured for years already. 32 bit is common only in ARM and MIPS world. And given that 32 bit development is quite messy (example right above), it makes sense for developers to drop 32 bit releases altogether. More and more do just that, regardless whether the target audience is retro oriented or not. For instance Witcher 3 is 64 bit only. Same as upcoming Trine 3.

The Windows version of NecroDancer does not require Galaxy, we're trying to get to the bottom of what's causing that crash.

Can it be an issue with MonkeyX? I can report it to their bug tracker. Do you generally build it yourself with your project from source? I suppose if MonkeyX libs themselves aren't built with -D_FILE_OFFSET_BITS=64, this bug will surface up.

So, what? You are going to have to take a look at the target audience. Maybe a significant number of the potential customers for this specific product have a fairly old computer or a 32 bit Windows license.

Maybe you've misunderstood me. What I wanted to say is that this specific game might be appealing to people who still use a very old computer.
Maybe the number of these people is significant enough to justify offering a 32 bit version.

Of course they are. I don't exactly understand why you give me games like these as an example.
It's obvious why Witcher 3 wouldn't get many additional sales from a 32 bit version and the Trine series always tried to appeal with fancy graphics.

My guess is that a game that doesn't put a lot of strain on your system and is arguably retro-styled may get a relatively high number of sales from people who still can't run 64 bit programmes.

I could be wrong, of course. :)

If developers are concerned about supporting legacy systems, they try to research it. I.e. make a poll or something like that. The general trend that I see - everyone gradually drops 32 bit releases.

I don't think retro styled games are concerned with old computers, unless it's not a styled, but actual retro game (for instance developed for Commodore 64 or anything the like). I.e. I don't see a connection between retro style and need to support legacy systems.

If you are talking about the crash on startup that is caused by the game not being able to access localhost because of a firewall.

Thanks for looking into it!

Many purely retro PC-gamers still have a stand-alone WinXP box, naturally using the 32bits version, because the 64-bits version has scarcely any drivers.
For instance, it's a pain to connect a real Roland MT-32 to a Win7+ box, because the MIDI-mapper is gone from Windows7 upward.
I got it to work on my Win 8.1 64 Bit Laptop with a lot of hacks, but it does work :-D !
Mind you that this only valid for people still running original versions of the games.
Thanks to the tech wizards at GOG, most ported games work perfectly on modern OS'es. Hats off to those guys and gals.

It's probably easier to do in Wine on Linux, than on recent Windows. Wine even can run 16 bit Windows applications on 64 bit system, while actual Windows already can't. For legacy support it's easier to use such environments or even emulators instead of keeping actual hardware. For instance I could run original version of Neverhood using Wine, while it's not going to work on current Windows at all. Of course it's runnable in ScummVM now as well, but that's besides the point.

I didn't work with Roland MT-32, but I assume ALSA can handle it. In general Linux has decent MIDI support.

Wow, I waited months in order to buy the game on GOG, read that there would not be a Linux version in this thread so I finally bit the bullet and bought it on Steam and now a few days latter, here's the GOG version... And I can't get a refund on Steam, as I've already played close to 10 hours.

Oh well! Thanks for the port anyway!

(Amazing game by the way; my favorite of 2015 yet.)

Just downloaded version 2.3.0.5 (1.27). The game still has the same bug. Can you please build it in 64-bit to get rid of this issue?