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

×
Windows 7 64-bit
After the first run of the game the executable file has become a folder.
Additionally a steam_appid.txt has appeared in the game folder.
Attachments:
folder-1.png (39 Kb)
folder-2.png (14 Kb)
Post edited January 20, 2016 by SKARDAVNELNATE
Still totally buggy and now this; I have read enough not to want the game at all. Interdimensional Games... Written down on list of producers to avoid.
avatar
Themken: Still totally buggy and now this; I have read enough not to want the game at all. Interdimensional Games... Written down on list of producers to avoid.
The game is made in Source, which is Steam's engine so some Steam artifacts such as the text file mentioned in the OP are to be expected.

We've updated the game to version 1.25 and before we released the updated version we've verified that Steam is not required at all in order to play the game.
Post edited January 20, 2016 by JudasIscariot
avatar
Themken: Still totally buggy and now this; I have read enough not to want the game at all. Interdimensional Games... Written down on list of producers to avoid.
avatar
JudasIscariot: The game is made in Source, which is Steam's engine so some Steam artifacts such as the text file mentioned in the OP are to be expected.

We've updated the game to version 1.25 and before we released the updated version we've verified that Steam is not required at all in order to play the game.
Alright, I remove that then from my list of negatives.
That explanation is all well and good but the executable is still a folder. This prevents me from running the game again after I've exited once. Being made in Source explains this as well since I recall Portal 2 doing the same for a while until some update stopped it.
And to think, contrary to what I strongly believed three weeks ago, I now have this game... Guess one should never say never. Now I can see for myself how it works and better judge it.
avatar
JudasIscariot: The game is made in Source, which is Steam's engine so some Steam artifacts such as the text file mentioned in the OP are to be expected.

We've updated the game to version 1.25 and before we released the updated version we've verified that Steam is not required at all in order to play the game.
But the text file in question is INSIDE the folder that was previously the game executable, suggesting that there is an issue here as the executable shouldn't just unpack itself so that it cannot be run again. I think I'll wait to see if a fix is released for this before I give the game a try.
avatar
JudasIscariot: The game is made in Source, which is Steam's engine so some Steam artifacts such as the text file mentioned in the OP are to be expected.

We've updated the game to version 1.25 and before we released the updated version we've verified that Steam is not required at all in order to play the game.
avatar
korell: But the text file in question is INSIDE the folder that was previously the game executable, suggesting that there is an issue here as the executable shouldn't just unpack itself so that it cannot be run again. I think I'll wait to see if a fix is released for this before I give the game a try.
Uninstall the game, reinstall it.

Before playing the GOG version, exit Steam completely. The reason that executable is getting turned into a folder is because if you have Steam running in the background, the game sees it, and since you more than likely have the Steam version from the free giveaway, the steam_api file latches onto Steam, the game gets synced with the Steam version and that's why your executable file gets turned into a folder.

So short version:

The GOG version will run fine without Steam in background or even installed. So play either the Steam version OR the GOG version without Steam installed/running in the background.
avatar
korell: But the text file in question is INSIDE the folder that was previously the game executable, suggesting that there is an issue here as the executable shouldn't just unpack itself so that it cannot be run again. I think I'll wait to see if a fix is released for this before I give the game a try.
The text file is in the main folder from the start. When the executable unpacked itself it left 2 VDF files as shown in my attachments.
avatar
JudasIscariot: Before playing the GOG version, exit Steam completely. The reason that executable is getting turned into a folder is because if you have Steam running in the background.
I have steam installed in a Symantec Workspace Virtualization layer so when it's deactivated Windows doesn't even see it as installed. Though maybe the SWV itself is to blame. I've seen Brutal Legend and Overlord become problematic because of it.
avatar
SKARDAVNELNATE: I've seen Brutal Legend and Overlord become problematic because of Symantec Workspace Virtualization.
SWV can't harm games if they are drm-free. It's the drm the problem, not the games nor SWV. Buy on GOG, and completly remove Steam from your system so this drm can't hack your games.
Post edited March 17, 2016 by ERISS