Post by karjala on May 5, 2023 3:32:19 GMT
There are problems with TFE not detecting Game Install locations.
Problem 1:
Most people use Steam and if the launcher is installed on C but if the game library was moved to E it doesn't always detect it.
The way the alternate install detection should work is to ...
1. Get the Steam install location from registry \Software\Wow6432Node\Valve\Steam and get the InstallPath
2. Check if the app manifest exists in that drive. Do this by seeing if Installpath\steamapps\appmanifest_32400.acf exists.
3. If it exists - then you know that DF is installed on that drive (typically C:) inside InstallPath\steamapps\common\Dark Forces\GAME
4. If it does NOT exist (Ex: installed on another drive) - open InstallPath\steamapps\libraryfolders.vdf file
5. There it will list the drives in numerical order 0, 1, 2... N and for each drive it will show the "apps" installed on each drive. (Typically 0 drive is the C: drive. )
6. Look through each drive index's app stanza and see if app 32400 is present. If it is present, then load the path variable to find the Steam library root path on that drive.
7. Based on the drive path you will know that the game is installed i in path\steamapps\common\Dark Forces\GAME folder
The above worked in my powershell DF launcher and WDFUSE 2.6+.
Problem 2
If the user finds the location of DARK.GOB and presses ok the message about missing game data is still present confusing them. They can still start the mission by returning to the main menu but they don't know about it and keep trying to fix a problem that doesn't exist.
Example clip is here --> clips.twitch.tv/EsteemedEvilSnakeRitzMitz-XTanSJfUHzXW6uj0
Problem 1:
Most people use Steam and if the launcher is installed on C but if the game library was moved to E it doesn't always detect it.
The way the alternate install detection should work is to ...
1. Get the Steam install location from registry \Software\Wow6432Node\Valve\Steam and get the InstallPath
2. Check if the app manifest exists in that drive. Do this by seeing if Installpath\steamapps\appmanifest_32400.acf exists.
3. If it exists - then you know that DF is installed on that drive (typically C:) inside InstallPath\steamapps\common\Dark Forces\GAME
4. If it does NOT exist (Ex: installed on another drive) - open InstallPath\steamapps\libraryfolders.vdf file
5. There it will list the drives in numerical order 0, 1, 2... N and for each drive it will show the "apps" installed on each drive. (Typically 0 drive is the C: drive. )
6. Look through each drive index's app stanza and see if app 32400 is present. If it is present, then load the path variable to find the Steam library root path on that drive.
7. Based on the drive path you will know that the game is installed i in path\steamapps\common\Dark Forces\GAME folder
The above worked in my powershell DF launcher and WDFUSE 2.6+.
Problem 2
If the user finds the location of DARK.GOB and presses ok the message about missing game data is still present confusing them. They can still start the mission by returning to the main menu but they don't know about it and keep trying to fix a problem that doesn't exist.
Example clip is here --> clips.twitch.tv/EsteemedEvilSnakeRitzMitz-XTanSJfUHzXW6uj0