You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Launching DOOM BFA with the +set fs_basepath command line parameter causes the game to show string variable placeholders in the settings menu.
To Reproduce
Steps to reproduce the behavior:
Run DOOM BFA with the +set fs_basepath command line parameter, eg. C:\Games\Doom 3 Source Ports\DOOM BFA\DoomBFA.exe" +set fs_basepath "C:\Games\Steam\steamapps\common\DOOM 3 BFG Edition"
Click on settings in the main menu
Expected behavior
Show normal settings.
Screenshots
Desktop (please complete the following information):
OS: Windows 11
Graphics card: GeForce GTX 1080 Ti
Graphics driver: NVIDIA 536.67
DOOM BFA version: DOOM_BFA_1.3.0-win_x64 and DOOM_BFA_Nigthly_2023-09-23-17-14-1695489243
Additional context
So far have not noticed any other bugs. Single player and multiplayer appears to launch successfully.
As for why one would do this: keeping source ports and game data separate and/or if Steam updates or overwrites files.
The text was updated successfully, but these errors were encountered:
Hi, the issue here is that it expects to find it's own asset files either in fs_basepath or in fs_savepath. Since the port is not in any of those paths it can't find it's own assets. If you want to keep the game clean I would recommend to all the base_* folders on the save folder
Describe the bug
Launching DOOM BFA with the +set fs_basepath command line parameter causes the game to show string variable placeholders in the settings menu.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Show normal settings.
Screenshots
![string_variable_placeholders1](https://private-user-images.githubusercontent.com/58829078/270125261-4bff09f6-d283-4537-b84a-6ab633591603.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzA1MjgsIm5iZiI6MTczOTI3MDIyOCwicGF0aCI6Ii81ODgyOTA3OC8yNzAxMjUyNjEtNGJmZjA5ZjYtZDI4My00NTM3LWI4NGEtNmFiNjMzNTkxNjAzLmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDEwMzcwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk1YzAzNzBjM2VkZDMzNWRjZGM0Y2E3ZTQwMTc1MGQ3NjQ5YTZkMGM0MjExNmZiM2M1ODJjZGJjMGUxMjMzNTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.aoqhLkCR9iuhJPpdwXtVdr9PhQVU6UT619WJreQQriY)
![string_variable_placeholders2](https://private-user-images.githubusercontent.com/58829078/270125273-f64f6a25-f885-473b-a452-dd5ecaeda809.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzA1MjgsIm5iZiI6MTczOTI3MDIyOCwicGF0aCI6Ii81ODgyOTA3OC8yNzAxMjUyNzMtZjY0ZjZhMjUtZjg4NS00NzNiLWE0NTItZGQ1ZWNhZWRhODA5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDEwMzcwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA2MTc5NTRlMWY5ZTgyZTRkY2ZiODBlMTk0MGQ5NTI3OWFlYmNmZDdiMDBhYmE5MTRmOGVkNzQ1NWJkMDk2NjYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.CuxXPTP6Irkult2_3cvX8GOFG-gYlpdIm7EzI8F6X4o)
Desktop (please complete the following information):
Additional context
So far have not noticed any other bugs. Single player and multiplayer appears to launch successfully.
As for why one would do this: keeping source ports and game data separate and/or if Steam updates or overwrites files.
The text was updated successfully, but these errors were encountered: