Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

settings not saved #37

Closed
atomGit opened this issue Mar 8, 2024 · 4 comments
Closed

settings not saved #37

atomGit opened this issue Mar 8, 2024 · 4 comments

Comments

@atomGit
Copy link

atomGit commented Mar 8, 2024

i believe i have all the latest files from FreeHL, FreeCS and FTEQW as of today

starting game with: ./fteqw64 -game cstrike

in the configuration menu, none of the settings are saved when exiting the game (key binds for ex.)

(the same is true for ./fteqw64 -game valve)

@eukara
Copy link
Owner

eukara commented Mar 8, 2024

Looks like cfg_save_auto being set to 1 by the menu is no longer being respected by the engine? I do force it to 1 upon menu init:
https://github.com/VeraVisions/nuclide/blob/master/src/menu-fn/entry.qc#L119

@atomGit
Copy link
Author

atomGit commented Mar 8, 2024

hmmm ... according to fteqw.org the last build was 10/23 and i'm pretty certain that settings were saved prior to the latest builds of FreeCS/HL

another thing i noticed is that a config.cfg is not created if it's missing (maybe that's intentional?)

@atomGit
Copy link
Author

atomGit commented Mar 9, 2024

cstrike/config.cfg is read by FTE, but if i cfg_save the settings are written to fte.cfg

dunno if that helps sort things out or not

autoexec.cfg is read as expected but some settings are not applied, such as con_textsize - i tried adding that to different files in different directories but i couldn't get it to work

@atomGit
Copy link
Author

atomGit commented Mar 24, 2024

looks like this is fixed

@atomGit atomGit closed this as completed Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants