Upgrades and numbering issue.

Navigator

Navigator

Registered
Hi guys,

Starting to love this game again, I bought the DW18 and tried to install my own sound that I made "back in the day" when my hobby was the modding. The sound actually was pretty good if I do say so myself.

So, this car is from the developer and I can't go into the files really. I can add-on with upgrades.
The problem is this: when I upgrade and want to alter the file again, it doesn't take the number.
For instance: there is already (dev) version 1.69 and I added 1.70
Even if I uninstall 1.70, take it out of the packages folder: the mas program wil not make an rfcmp version 1.70 again. I have to have 1.70 in there and make a 1.71

At this rate, when I'm done fine-tuning, I'm at version 8.99 :)
I just want to remake 1.70 and install it al over: is there a way to do so?

(I never worked with upgrades, just repacked the whole file back than, but thats no option here)
 
Hello, for example if you install 1.05XX upgrade from 1.04 you need to remove the rfcmp of 1.05 version in Packages folder and not install it in your server.
I also had troubles before understanding that ...
On server you can't install 1.04, 1.05 and then 1.05XX ... it will have some weird effects.
On client part you can.
1.05 must not be viewed by the Mod Manager and only yours 1.05XX.

You must upgrade from an even version 1.0, 1.02, 1.6 ... and never an odd one 1.01, 1.3 ...
 
Last edited:
Thanks for your response mate.
Sorry if I sound a bit stupid in this, but its hard stuff for me: server is when you go online, right?
I dont do that, just play online.
Also, I havent worked with the XX extension: just getting up in numbers here.
So I had uninstalled the 1.70 and removed it from the packages folder too. The mas program however, didn't want to make a second 1.70....... when I click "package" it just doesn't do anything. Even not when I try to put it in a completely different folder: it seems to remember it made this particular file already?
 
Never redo an existing 'offcial' or Workshop package ...
By XX i mean whatever you want.
In your case in version use 1.70Nav for example. It shows the "root" of your version but it's another one.
By server i mean "dedicated server" since it's the only way to make an online game.
 
Ah, I get it!
Also: I didn't explain it properly: the car from the developer is version 1.68 an they themselves have an upgrade in there also: version 1.69
Now I started with upgrades on 1.70 and its just that one, I can't seem to redo: it won't make the package......
 
My example :

Capture.JPG

You must use 1.69XX upgrade from 1.68 ... and maybe also include 1.69 content or only yours.
 
Here is another complete example, adding 2 skins (last 2 mas files) and keeping the car_upgrade.mas from cars used from 1.05 :

Capture.JPG
 
Last edited:
@DanRZ if I understand the issue correctly, the question is: are you able to make some further changes, and repackage that 1.05C22 upgrade again? That's what Navigator isn't able to do.
 
Ah, it's starting to come at me now........I'm going to test some with that.
I didn't use the XX.

While writing this, I see Lazza's post and indeed; thats the thing.
 
Lazza said:
@DanRZ if I understand the issue correctly, the question is: are you able to make some further changes, and repackage that 1.05C22 upgrade again? That's what Navigator isn't able to do.
Click to expand...

I don't do 1.06 .... i just remake 1.05C22 if needed ...
I still can do 1.05C23 and so on but 1.05C22 will need to be completely uninstalled, removed and deleted from server.

You can't make an upgrade from an already upgraded version.
 
Last edited:
DanRZ said:
...You can't make an upgrade from an already upgraded version.
Click to expand...
In the Past that was right, but now you can.
I have made one for the Formula Pro 2021 for Example, that has the Version 1.20 and the Update 1.21 and i've made my Update to 1.21 as "Update from".
You can find it HERE.
 
1.20 to 1.21 is not an upgrade from upgrade since 1.20 is an "even" version ...
1.22 from 1.21 would be one.
You just "remade" the original 1.21 and i think people who had the original 1.21 may have issues.

I never achieved upgrade from upgrade on the many cars i tried, still have to get back to "even" version "from", and it was only a month back. I was able to make the rfcmp but i couldn't install it on dedicated.

Some cars like Glickenhaus, i think, have only one and an even version by the way so there is no upgrade existing before someone add a skin or modify upgrades.ini for example ...

There is some obscure rules for upgrading content i think, kind of wizardry :D
 
Last edited:
DanRZ said:
1.20 to 1.21 is not an upgrade from upgrade since 1.20 is an "even" version ...
1.22 from 1.21 would be one.
You just "remade" the original 1.21 and i think people who had the original 1.21 may have issues.

I never achieved upgrade from upgrade on the many cars i tried, still have to get back to "even" version "from", and it was only a month back. I was able to make the rfcmp but i couldn't install it on dedicated.

Some cars like Glickenhaus, i think, have only one and an even version by the way so there is no upgrade existing before someone add a skin or modify upgrades.ini for example ...

There is some obscure rules for upgrading content i think, kind of wizardry :D
Click to expand...
No, i didn't remade/repackaged the 1.21.
1.21 is the original Update for the 1.20 and my 1.21noHalo, that only contains the Upgrades.ini, is an Update from the original 1.21 (set in that Way in the MAS Tool).
To update in that Way was not possible in the Past, but, as said, now it is.
BTW even or uneven Version Numbers don't matter.
It's just the Scheme that S397 uses, that the uneven Version is the Update.
 
Ehh, still playing around with it.....it did work when adding something and so I can go on I think.
Thanks for all the useful info guys!!
 
Just an observation, modders usually tend to choose a version # that is somewhat separated from the current version #. For example, if the current version is v1.21, then modders often select a number like 150. Just to get it clear of any small updates from S397.
 
There should be some kind of explicit rule to avoid that kind of problems.

I noticed they will never or rarely simply add a version on the last version and last digit ...

First version may be 1.04 upgraded to 1.05.
The next one is often 1.16 upgraded to 1.17 for example.

So in theory modders who want to make another upgrade can use any version 1.05+ and then 1.17+ without any issues which is clever but not "explicit" since nobody clearly described this rule in any tutorial.

Using 1.20 or 1.50 may cause some issues in future but maybe S397 never use 0 as last digit, again another unwritten rule ...

The rule "last upgrade + text" always work : 1.05XX will never be used by S397 or any content creator because they use only pure numerics.
 
Last edited:
DanRZ said:
There should be some kind of explicit rule to avoid that kind of problems.

I noticed they will never or rarely simply add a version on the last version and last digit ...

First version may be 1.04 upgraded to 1.05.
The next one is often 1.16 upgraded to 1.17 for example.

So in theory modders who want to make another upgrade can use any version 1.05+ and then 1.17+ without any issues which is clever but not "explicit" since nobody clearly described this rule in any tutorial.

Using 1.20 or 1.50 may cause some issues in future but maybe S397 never use 0 as last digit, again another unwritten rule ...

The rule "last upgrade + text" always work : 1.05XX will never be used by S397 or any content creator because they use only pure numerics.
Click to expand...
It is stated, well sort of..in the tutorial on how to to create an update rfcmp it says to use the base as the "update from" field. Version number can whatever you want, but makes sense that if you are updating content to have some sort of reference to what version you are updating.

upload_2022-12-29_19-6-23.png

https://docs.studio-397.com/users-guide/custom-liveries-how-to-make-an-update-rfcmp-for-league-use
 
redapg said:
No, i didn't remade/repackaged the 1.21.
1.21 is the original Update for the 1.20 and my 1.21noHalo, that only contains the Upgrades.ini, is an Update from the original 1.21 (set in that Way in the MAS Tool).
To update in that Way was not possible in the Past, but, as said, now it is.
BTW even or uneven Version Numbers don't matter.
It's just the Scheme that S397 uses, that the uneven Version is the Update.
Click to expand...
If you update on v1.21, it works fine in single player, but when you install it on a server it doesn't work (it installs it but the new folder doesn't appear). On the other hand, if you do it on v1.20 when installing it on a server, it works.
Have you tried yours on a server? 1.21noHalo
 
Flipo said:
If you update on v1.21, it works fine in single player, but when you install it on a server it doesn't work (it installs it but the new folder doesn't appear). On the other hand, if you do it on v1.20 when installing it on a server, it works.
Have you tried yours on a server? 1.21noHalo
Click to expand...
Thank you for Testing.
We've had a Discussion about it in another Thread already, that i can not find anymore.
As i've said, my Update only contains the modified Upgrades ini.
And that was something, that couldn't be done in this Way in the Past.
You couldn't update the Update.
Now, that there was something changed in the Code, you can do it.
The Advantage is, that you can use a small File, like in this Case, that only contains the edited Upgrades ini, instead of a huge File with all veh, icons ..... included.
In my Opinion, it also should be doable from Code Side, that such kind of Updates also work on a Server.
 
You must log in or register to reply here.
Back
Top