The program shortly opens a blank window that closes again after a couple of seconds. No error message or indication what is at fault. Win-64 version.
Hi, I am unsure if you have followed the thread however this is an updated build now that fixes a crash on start. If you are still interested, you may want to give the 1.1.7 build a try.
> Assuming you have the right build for your system (x64 is if you are using 64bit windows),
> ran oalinst.exe (it is in the zip file alongside game.exe)
> and didn't accidentally delete/or move the files relative to game.exe it should be fine.
> I haven't not tested it on a huge variety of systems though, so it is possible there is something I didn't consider.
Windows 10 Pro x64 on Ryzen5 2600X, 16GB RAM, Radeon GX580 graphics
> Are you executing it from a command prompt?
Yes. It opens a window that closes after a few second without message
Hmm. This appears to be something specific w/ the file on itch.io. When I try the zip that I uploaded it runs fine, but when I download the zip from itch.io and try it gets that problem you describe. This is very unusual, but I'll see if I can sort it out for you.
Have you tried running it from windows explorer?
Windows 10 will block unsigned executables that are downloaded from the internet. From command line it does nothing, but from windows explorer it will give you a prompt (which if you ask for more info will have a Run anyway).
Hmm, I haven't been able to think of anything that could be the culprit. I could potentially create a special build for you that generates a log and maybe that would give some insight. It will take a few days to get it ready (my time is very short right now), and I totally understand if you aren't interested or can't (I don't like having a player essentially debugging for me)
Do it when you have time. I'm curious about it but I'm not desperate to play the game RIGHT NOW.
Ok, there should be a new build available named 'Walking Tourist x64 Logged'
It will generate a file named <number>.log when run (<number> will change every time it is run). Its contents won't be terribly useful to you, but may help me pinpoint what is failing. You can either post the last handful of lines in the file here, or email the whole file to firstname.lastname@example.org.
Also it will run super slow so it may take longer to hit the crash. E.g. it normally starts instantly, but now takes a good 5 - 10 seconds to hit the splash screen for me. There is also a slim, but unlikely chance I fixed the issue (this build includes an engine update; however no fixes should be related to the issue you are seeing).