Which .ini can I edit that Vortex won't redo?

[Pickysaurus]

Vortex does reverse ini files every time I edit it.

 

 

I have to make copy of all ini's before i startup vortex

 

Vortex does reshuffle the INI on deployment but it won't actually lose your value changes, it just re-orders them.

[Guest deleted34304850]

 

Vortex does reverse ini files every time I edit it.

 

 

I have to make copy of all ini's before i startup vortex

 

Vortex does reshuffle the INI on deployment but it won't actually lose your value changes, it just re-orders them.

 

why would it reshuffle them if its not changing values? afaik the placement of the parameters and their values in the .ini is not going to impact the game. is my understanding incorrect?

[Pickysaurus]

 

 

Vortex does reverse ini files every time I edit it.

 

 

I have to make copy of all ini's before i startup vortex

 

Vortex does reshuffle the INI on deployment but it won't actually lose your value changes, it just re-orders them.

 

why would it reshuffle them if its not changing values? afaik the placement of the parameters and their values in the .ini is not going to impact the game. is my understanding incorrect?

 

 

Tannin may be able to confirm but I believe it always parses the INI, checks the values it needs for saves etc and then writes it back to disk. The library the does that is opinionated about the order of the values.

[AugustaCalidia]

Now I'm very confused. Normally I configure .ini files at the start of a game, and then they remain constant for the remainder of the game, unless I introduce further changes. What then is this "reshuffling" all about? As 1ae0bfb8 has already asked, why reshuffle if no values have changed? Or is reshuffling a normal part of the parsing process? Also, is "reshuffle" a technical term?

 

Finally, an "opinionated" software library? Is that a technical expression as well? Anyway, I love it. That confirms my suspicion that some computers can be very hard headed at times! :smile:

[rmm200]

Now I'm very confused. Normally I configure .ini files at the start of a game, and then they remain constant for the remainder of the game, unless I introduce further changes. What then is this "reshuffling" all about? As 1ae0bfb8 has already asked, why reshuffle if no values have changed? Or is reshuffling a normal part of the parsing process? Also, is "reshuffle" a technical term?

 

Finally, an "opinionated" software library? Is that a technical expression as well? Anyway, I love it. That confirms my suspicion that some computers can be very hard headed at times! :smile:

 

Speaking as a computer programmer - computers are quite agnostic.

"Opinionated" comes from us. Much of our world view winds up in code...

[showler]

Since placement doesn't matter, Vortex might have set it up to be:

 

A

B

C

D

E

 

and BethINI or another program might have set it up to be

 

A

E

C

B

D

 

and both programs just do it their way since it makes no difference either way. Which means that if Vortex updates the file to alter the order to the way it was programmed to order things it really doesn't matter at all.

[Guest deleted34304850]

Since placement doesn't matter, Vortex might have set it up to be:

 

A

B

C

D

E

 

and BethINI or another program might have set it up to be

 

A

E

C

B

D

 

and both programs just do it their way since it makes no difference either way. Which means that if Vortex updates the file to alter the order to the way it was programmed to order things it really doesn't matter at all.

its still unnecessary and a waste of processing power and it adds to confusion because while i am adamant that my ini values are not changed at all by Vortex, I can see how people would make that assumption.

unnecessary processing like this is not good practice.

[showler]

Perhaps. But it might also be easier to have Vortex brute-force things to the way it prefers than to dynamically adapt to whatever another INI editor, or the user themself, might decide to do.

[Tannin42]

I have reviewed a similar report today but was not able to reproduce.

If you edit anything in the main .ini file and deploy, vortex will transfer your manual change to .ini.base, then regenerate .ini.baked and .ini from that information.

 

For the curious, this is the mechanism at play here:

 

Some Vortex settings require Vortex to change certain ini settings (e.g. to facilitate profile-local save files) but most it doesn't touch.

.ini.base is the reference file, containing your custom ini settings with none of the Vortex changes.

.ini.baked is .ini.base with the vortex settings applied.

.ini starts out as a 1:1 copy of .ini.baked

Early during deployment, Vortex compares the .ini file to .ini.baked, any changes it will assume you did manually (in a text editor, inside the game or bethini, doesn't matter) so it transfers these changed settings (and only those) to .ini.base, then regenerates the other two files.

 

Now regarding the shuffling:

First thing to note is: .ini is not a standardized file format, different tools use similar but different formats and call them .ini, they may be 95% compatible but never 100%.

 

That's relevant because Vortex, to retain perfect compatibility, uses the same interface (windows api) as the game to read and set ini settings.

And this interface does not allow me to look at the file as a whole, I only ever read or set individual values, like I can say "windows api, please tell me the value of [General] -> iSomeValue" or "windows api please set the value [General] -> iFoobar to 42" and then windows changes the value and writes the file in whatever way it sees fit. The api doesn't usually change the order of the ini but it also doesn't let me dictate it. To take that control I would have to use a different interface which is then not fully compatible.

 

But also: because I transfer only the values that changed from .ini to .ini.base and then re-create .ini.baked and .ini from it, any changes to the order will be lost. Again: Vortex doesn't _see_ the order of entries, only the values. It will always fall back to the order in .ini.base which was created the first time you started managing the game.

[Flipocles]

For New Vegas at least, I had to copy the FalloutCustom.ini into the profile folders before it would switch them when changing profiles.

By default only FalloutPrefs.ini and Fallout.ini are profile dependent with Vortex.

Profiles are in C:\Users\*YourUserName\AppData\Roaming\Vortex\*GameFolder\profiles

These are the default locations I am pretty sure, so if you installed them elsewhere you're probably just looking for ...\Vortex\*GameFolder\profiles

It does not does?(it's weird, just update it in the profile folder when the profile isn't active) update them like the other ini files when changing them in C:\Users\*YourUserName\Documents\my games\*GameFolder  (If it updates others at all. I didn't test other ini files)