Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I discovered that the instruction to set this is in the installscript.vdf in the same folder, but changing it there has no effect as the file is re-generated when you launch the game from steam.
You can however change the compatability mode on the exe and launch it from that EXE directly outside of steam to gain access to a full list of resolutions.
I will report back if I find a way to resolve this issue with steam launching. Sadly the installscript.vdf regenerates and re-runs whenever you try to launch the game directly from Steam.
If the dev/publisher could alter the setting in the install script that would fix it.
Of course they may have set the mode to WIN98 to solve another issue...
No, I never did. If Steam is still configured in their database to set it to the wrong compatibility mode it will keep doing it every time you try to launch it from Steam. There's no way to work around it other than not using Steam to run the game or the data being fixed in the Steam database. The publisher (or developer) would need to fix this. It's a very easy fix though, if they can find where to do it. I'm guessing there's probably a webpage they have access to or they can just update some script file and push it.
The only option we have otherwise is to find a way to stop Steam from having the ability to set the compatibility mode on the EXE or stop Steam from being able to overwrite installscript.vdf and leave it as it is. I'm not actually sure if locking installscript.vdf would really work but the fact it exists implies it could.
Actually I fixed it just now!
After running the game, go to the game's install folder and edit installscript.vdf, change the WIN98 to WINXPSP3. Save and close the file. Right click the file and go to properties. Go to the Security tab. Click Advanced. On the Permissions tab click the Disable inheritance button and select to copy the permissions from the parent. Now edit all permissions by double clicking them and removing Full Control, Modify, and Write.
It is now impossible for anyone to alter the installscript.vdf file. You might actually have issues deleting the file or uninstalling the game without returning to the file's security setting and resetting them. This will prevent Steam from overwriting the install script and will make the change stick around even when run from Steam.
I've followed your direction (to a T[?]) to no avail... :(
*Has this issue ever been fixed/resolved?
-Help?
Thanks.