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.
I am deeply sorry about the the delay. I did not notice when your message first came through.
I am uncertain why might not be starting for you. 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.
Are you executing it from a command prompt? If you are not you may want to try that and see if it indicates what is wrong (either obvious to you, or something you can share that might clue me in to what is wrong).
> Assuming you have the right build for your system (x64 is if you are using 64bit windows),
Yes.
> ran oalinst.exe (it is in the zip file alongside game.exe)
Yes.
> and didn't accidentally delete/or move the files relative to game.exe it should be fine.
No.
> 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, 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)
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 ajunkalagames@gmail.com.
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).
There should be a new build available that fixes the issue. All the systems I have are apparently much more lenient about shaders so I didn't spot the issue. I did upload an updated logged build in case something is still wrong, but hopefully that is not the case (it is less aggressive in its logging too).