Skip to content

Request: Stop overriding gta_sa.set file. #4171

Open
@blonter

Description

@blonter

Is your feature request related to a problem? Please describe.

Hello.

I recently noticed that MTA uses the singleplayer's settings file despite it has its own.
The gta_sa.set file which is located in your Documents folder will be overriden each time you launch MTA.

This is bad if you use different settings for singleplayer and MTA. I don't know what settings are being overridden, the screen resolution is one of them but it could be more.

I personally use a 4:3 screen resolution (1400x1050) in singleplayer because this game doesn't really have a widescreen support. The toggleable option in settings is broken, it'll make things worse. Widescreen fix mod could be an option but if you are a speedrunner you can't really install all fixing mods like silentpatch etc. Or if you just dislike having such mods at all.

So you either stick with FHD in singleplayer as well and live with the streched vehicles/peds/hud or you set up a 4:3 screen resolution.

If you first install MTA, it should still read the contents of gta_sa.set so all your binds will be there, but after having the coreconfig.xml I think that the game should not touch gta_sa.set file anymore.

Installing the game twice for singleplayer and for MTA separatedly is not an option, since the settings file will be the same for every instance of installation.

Describe the solution you'd like

If MTA needs to keep using the settings file, then somehow make it to not to override the screen resolution as well. Most settings will stay unchanged, even if you use different keybindings in MTA, they won't be synced back to singleplayer only the screen resolution (based on my experiences)

Totally getting rid of the usage of the settings file would be preferrable. However it should still use it once (for reading only) when coreconfing.xml is absent.

Describe alternatives you've considered

No response

Additional context

No response

Security Policy

  • I have read and understood the Security Policy and this issue is not about a cheat or security vulnerability.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions