Thank you, I bought your game without hesitation now.

What an awesome way to start the week. Thank you, truly.
I've bought the whole bundle (Game, as intended, and the extras, that I usually would wait on).
I'm also mentoring a couple of new Linux users, and I hope to convince them to buy (or maybe I'll just gift them a copy - I'm feeling charitable thanks to you :) ).

Thank you and your team for your hard work, your commitment to Linux (and thus, cross-platform support), and for designing games as unique and enjoyable as this one.

And thank you to GOG for publishing the Linux build so quickly.



I hope GOG explores a kind of blank "shim" (for lack of a better term) as was suggested in this forum for games until Galaxy for Linux is complete - hopefully easing the pain for developers, customers, and GOG while development continues.

That was unexpected and very fast. Purchased.

Is there some official combination to toggle fullscreen mode for the game? I didn't find such option in UI, and ended up using my combination in KDE / KWin (Meta + PgUp). That was somewhat confusing, and not all might have such combination set up.

Based on our testing, it works when Galaxy is not installed on Windows and Mac. If someone has repro steps for this, we may be able to fix it, or we may need to wait for an update to Galaxy itself.
Thank you very much! :D
There is no in-game toggle, you'd have to restart the game.

You can also force it to start in a specific mode via a command line parameter. Pass 0 for windowed, 1 for full screen.

I see. Well, at least in KDE global shortcut for that works fine, so it's not a major issue for me :)

The game crashes though when I reach the first slime monster (after picking up a dagger, opening that door and trying to throw it through). Where should I better report such bugs and do you need any logs for it?

In the terminal I see this:

Running Crypt of the NecroDancer
Running Crypt of the NecroDancer
NecroDancer version v1.12 loading...
OnCreate: Initializing Steam
DRM free initialization
DRM free initialization complete
OnCreate: Updating screen size
Updating screen size: 960x540
OnCreate: Starting FMOD
Initializing FMOD values
OnCreate: Setting update rate
GLOBAL_SCALE_FACTOR: 2.0
Loading ControllerMainMenu...
LoadPlayerDataXML(), cloudTimestamp=0
Monkey Runtime Error : Memory access violation

{{~~(null)~~}}

Hm, does it crash if you don't throw the dagger and instead just walk into the slime? That is odd.

Thanks for the reply! So the game should work standalone without needing any access to the internet, right? I don't need the "achievements/leaderboard" part; I just want to make sure the game will work without needing a client.

Same thing happens if I just walk straight when I reach that slime.

I'll just run a small test to exclude any potential XFS issues.

By the way, the loading time at startup (when it says "loading") is really long for such a game. What is it doing exactly there?

Yep, another XFS issue confirmed ;))

I just made a 1.7 GB file, formatted it with XFS and mounted it as a loop device, copied the game inside and run from there. It doesn't crash anymore.

So the crash is caused by my large XFS partition which is 1.9TB. Since the game is 32 bit, did you compile it with -D_FILE_OFFSET_BITS=64?

See similar issues reported here:

http://forum.unity3d.com/threads/there-is-no-data-folder-failure-in-clarc-unity-3d-on-large-xfs-partition-on-linux.277828/
https://www.gog.com/forum/grim_fandango_remastered/grim_fandango_remastered_fails_to_run_on_linux
http://www.doublefine.com/forums/viewthread/16251/
http://www.doublefine.com/forums/viewthread/16523/
http://www.frozenbyte.com/board/viewtopic.php?f=17&t=27349

This XFS issue comes up fairly often for 32 bit releases. Do you need to keep the game 32 bit though? It's already pretty obsolete, and releasing 64 bit only isn't a bad idea.

Thank you! I appreciate the extra effort it must have taken. Happily bought and enjoying it thoroughly.

I've installed it on my Win 7 laptop which doesn't have Galaxy. I disabled internet connectivity during install, and during play, and it worked just fine.

Many thanks for your efforts <3

I'm also experiencing longer load times than I was expecting.

I would assume that a relatively high percentage of the target audience for retro-style games still hasn't switched to 64 bit.
Keeping it 32 bit "only" might therefore still be a better idea than keeping it 64 bit only. ;)