Mod manager issues with updates

There is a problem how Mod manager handles updates for mods. I've made a skin update for all URD vehicles (version 1.81). I just added a new mas file that contains the skins and the veh files. To avoid collision with existing files I named the skin component "BayroE5_skins.mas" for the Bayro. It works perfect offline with the all cars and tracks mod. This afternoon I tried to join a online server but the car selection screen was empty. Tried the vmod offline with the same result. Uninstalled the updates and voila, the cars are selectable. This is somewhat strange because the original version 1.8 of the mod is installed on my hard disk, the files are not modified by the update but the game looks for the updated components only. All cars have now version 1.81 but the server allows just 1.8.

Another point is that the Mod manager now shows all my updates in the list additional to the full versions of the components.
 
Tosch said:
There is a problem how Mod manager handles updates for mods. I've made a skin update for all URD vehicles (version 1.81). I just added a new mas file that contains the skins and the veh files. To avoid collision with existing files I named the skin component "BayroE5_skins.mas" for the Bayro. It works perfect offline with the all cars and tracks mod. This afternoon I tried to join a online server but the car selection screen was empty. Tried the vmod offline with the same result. Uninstalled the updates and voila, the cars are selectable. This is somewhat strange because the original version 1.8 of the mod is installed on my hard disk, the files are not modified by the update but the game looks for the updated components only. All cars have now version 1.81 but the server allows just 1.8.

Another point is that the Mod manager now shows all my updates in the list additional to the full versions of the components.
Click to expand...

Was vmod created by you or somebody else?
 
The problem was with vehicle updates. No matter if the update is included in the vmod or as an independent component. The only way to properlly install them was using B382 mod manager. O am rraching home now so I'll try it myself and report.

Sorry Ari if I sounded unpleasant. It didnt make any sense with the bug itself that all the vmods and components of previous build worked.
 
I just tried an old component and I can confirm that the bug persists: When using the vmod (online or offline), the car does not appear.

The problem appears when the vmod referencing or containg the update is installed. It splits the vehicle component into two. I have looked at the mft file before and after installing the vmod and, evidently, it has changed. I can confirm that putting back the first mft file that is created everything is OK.
I cannot understand how something as simple as avoiding that a new mft file is created when installing a vmod, has not been addressed in 4 months. It is completely unconceivable...
Look at the mft files before and after installing the vmod. It does not look very difficult to see where the error is:

Before:
[Component]
Name=M2009_car
Version=1.445
Type=2
Author=
Origin=0
Category=0
ID=
URL=
Desc=
Date=0
Flags=8193
RefCount=1
Signature=4c48c73b685c2e04572fbb7497260e397c2cffe169cf840cb0a4a11caef72398
BaseSignature=b1e6be90088bc3ab26f31ec20888c5bc5138374d34cfef01c834302d4d9f8357
MASFile=M2009_1445.mas 18caf78b4f97a95cebc9fe80ae6db7844f66cbbd5c2181e88f6056a37898f9fb

After
[Component]
Name=M2009_car
Version=1.445
Type=2
Author=
Origin=0
Category=0
ID=
URL=
Desc=
Date=1404146993
Flags=2101249
RefCount=2
Signature=4c48c73b685c2e04572fbb7497260e397c2cffe169cf840cb0a4a11caef72398
MASFile=M2009_1445.mas 18caf78b4f97a95cebc9fe80ae6db7844f66cbbd5c2181e88f6056a37898f9fb
 
I just tried changing mft properties to "read only" and it is a simple method to prevent mod manager for splitting the component into two when the vmod is installed. For sure a new problem arises since later mod manager cannot properly uninstall the component since it cannot delete the mft file and the folder with the version number containing it.
 
B769 maintains the bug of mod manager changing original mft files for incorrect ones in updated vehicle components when installing a vmod referencing that updated vehicle.
 
B770 will be out. This bug is important for communities to be solved. 769 didn't fix it so I must guess 770 will be the same.
It is not the first time an unstable, in this case 769 is out for only 24 hours.
This is making goodwilling people lose their time for nothing. No feedback has been possible since 769 was released. What was the purpose of this unstable?

What is the purpose of reporting something if it is not addressed? It is the third time I report this bug. Good job!
 
New build 798. Old mod manager 0.93.g. Old bug where mod manager changes the mft after installing a vmod including or referencing the updated vehicle. I think that the bug is quite clear and well documented...

Should I think it is something personal and assume that ISI does not solve this bug on purpose? Otherwise I do not understand the passivity about this bug...
 
C3PO said:
Maybe other work is deemed more important?
Click to expand...
After 4 months they didn't have time to find the subroutine that MODIFIES an already installed vehicle update when installing a vmod referencing it. Are you suggesting this?
 
Now I have this bug too with build 798 when I am creating GP79 vmod, all was fine with build 770, why is this happening now and not before :confused:

I created GP79_UNRESTRICTED_V0.43 with update GP79_CAR_V0.432 vmod, all seems fine, no error message but there is no cars :mad:
 
What it cannot be understood is that it worked properly in B382. It is not something that never worked.

Regarding Ari's post all I can say that in B770 it was corrupt as well. I don't know exactly how you made it work. Can you confirm it reproducing it? Same vmod and component?
The mod manager is the same version so it shouldn't work.
I do not think it will be something that affects only some updated vehicles and go fine with others.
 
With build 770 and earlier I was using GP79 vmod and it was created with build 382, I used Edit Existing Mod Package and edited only new tracks to existing vmod and all was fine,
Get missing component worked also fine.

Before updating to build 798 I cleaned my package folder and deleted GP79 vmod. and when I am trying to create new vmod GP79_UNRESTRICTED_V0.43 with update GP79_CAR_V0.432 there is only Clio pace car all GP79 cars are missing.

GP79_UNRESTRICTED_V0.43 and GP79_CAR_V0.432 are old components from last summer and the mod manager is same old version also, I find it strange there is bug like that.
 
Ari Antero said:
With build 770 and earlier I was using GP79 vmod and it was created with build 382, I used Edit Existing Mod Package and edited only new tracks to existing vmod and all was fine,
Get missing component worked also fine.

Before updating to build 798 I cleaned my package folder and deleted GP79 vmod. and when I am trying to create new vmod GP79_UNRESTRICTED_V0.43 with update GP79_CAR_V0.432 there is only Clio pace car all GP79 cars are missing.

GP79_UNRESTRICTED_V0.43 and GP79_CAR_V0.432 are old components from last summer and the mod manager is same old version also, I find it strange there is bug like that.
Click to expand...
The problem arises when you install the vmod. If you had the vmod previoulsy installed (from B382) it should have worked. If you jnstalled the vmod with B770 impossible. It is not important how old the base and updated vehicle components are. If you want a temporary solution you can fix it with either each of the following ways:

1. Install the vmod with B382.
2. Make a copy of the mft file in the updated component folder (installed/vehicles...) before updating the vmod and restore it later after updating
3. open the mft file properties in the updated component folder and mark it as "read only: before installing the vmod. If not undone mod manager wil not be able to uninstall it later.
 
You must log in or register to reply here.
Back
Top