It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi
Linux Mint 17.3 64-bit
When I try to start the last version (0.24.0.3), a browser's window appears , with "NW.JS" written inside, and nothing else happens.
If I try to start the game (the script or the main executable) in a terminal, I get this error message: "Running The Curious Expedition [5765:0205/181413:ERROR:browser_main_loop.cc(170)] Running without the SUID sandbox!"

The previous version worked.
Same on somewhat-outdated Arch.
Sorry about the issue. We'll investigate what the problem is and will upload a new version.
avatar
siever: Hi
Linux Mint 17.3 64-bit
When I try to start the last version (0.24.0.3), a browser's window appears , with "NW.JS" written inside, and nothing else happens.
If I try to start the game (the script or the main executable) in a terminal, I get this error message: "Running The Curious Expedition [5765:0205/181413:ERROR:browser_main_loop.cc(170)] Running without the SUID sandbox!"

The previous version worked.
We uploaded a newer version of the game today, can you please check and see if works for you?
avatar
siever: Hi
Linux Mint 17.3 64-bit
When I try to start the last version (0.24.0.3), a browser's window appears , with "NW.JS" written inside, and nothing else happens.
If I try to start the game (the script or the main executable) in a terminal, I get this error message: "Running The Curious Expedition [5765:0205/181413:ERROR:browser_main_loop.cc(170)] Running without the SUID sandbox!"

The previous version worked.
avatar
JudasIscariot: We uploaded a newer version of the game today, can you please check and see if works for you?
OK. The new one works.
Thanks
Thanks, the new version at least runs (on my Debian 8 Jessie system). It's lots of fun, but so far I've only made it past one expedition without the game locking-up. I get back and trade-in and/or keep my goods, but then the Continue button doesn't do anything.

This is the error message from the console when I click the Continue button:

[edit: apparently I can't post links, so I'm editing out the two slashes after file:]

[2378:0208/202043:INFO:CONSOLE(896)] ""You must specify your applicationId using Parse.initialize."", source: file:/tmp/.org.chromium.Chromium.Zq595C/min-cegame.js (896)
[2378:0208/202043:ERROR:nw_shell.cc(335)] You must specify your applicationId using Parse.initialize.
[2378:0208/202043:INFO:CONSOLE(1)] "Uncaught You must specify your applicationId using Parse.initialize.", source: file:/tmp/.org.chromium.Chromium.Zq595C/lib/parse-1.5.0.min.js (1)


I'm looking forward to your finished game, it's a lot of fun.
avatar
VojZaru: Thanks, the new version at least runs (on my Debian 8 Jessie system). It's lots of fun, but so far I've only made it past one expedition without the game locking-up. I get back and trade-in and/or keep my goods, but then the Continue button doesn't do anything.

This is the error message from the console when I click the Continue button:

[edit: apparently I can't post links, so I'm editing out the two slashes after file:]

[2378:0208/202043:INFO:CONSOLE(896)] ""You must specify your applicationId using Parse.initialize."", source: file:/tmp/.org.chromium.Chromium.Zq595C/min-cegame.js (896)
[2378:0208/202043:ERROR:nw_shell.cc(335)] You must specify your applicationId using Parse.initialize.
[2378:0208/202043:INFO:CONSOLE(1)] "Uncaught You must specify your applicationId using Parse.initialize.", source: file:/tmp/.org.chromium.Chromium.Zq595C/lib/parse-1.5.0.min.js (1)

I'm looking forward to your finished game, it's a lot of fun.
Thanks! If you enable "send stats" through the settings screen, these issues will be automatically uploaded into our bug tracker together with all the game data we need for debugging. I'll try to fix the issue asap.

Thanks! If you enable "send stats" through the settings screen, these issues will be automatically uploaded into our bug tracker together with all the game data we need for debugging. I'll try to fix the issue asap.
Already enabled. I'll just trust it to let you know any future problems. Thanks for the quick reply.
The game starts now, but first it displays 40 seconds of white fullscreen window with no activity.
I usually encounter this with games that don't understand that a computer can have no Internet access (is that the case?).

There's some log message right after the game unfreezes:

[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.

Hope that helps.
avatar
rhn: The game starts now, but first it displays 40 seconds of white fullscreen window with no activity.
I usually encounter this with games that don't understand that a computer can have no Internet access (is that the case?).

There's some log message right after the game unfreezes:

[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.

Hope that helps.
Sorry to hear that. We just pushed a new version. Are you still encountering this problem?