• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 Sticky textures when injecting a simobject with SimConnect

G

gpxe0

Messages
48
Country
france
Hello

I was working on creating matching rules for Vatsim for MSFS.

I have an AI simobject with multiple textures for the A320 for Easyjet. (MSFS compatible of course).
- one mdl file
- multiple texture sets (texture.1, texture.2, texture.3 folders)
- and in aircraft.cfg
- multiple [fltsim.xx] sections ([fltsim.0], [fltsim.1],[fltsim.2])
- for each [fltsim.xx] section, a different title (title="EZY1", title="EZY2", title="EZ3")

The matching rule is set so that for an A320 from Easyjet, vPilot (the Vatsim client, connecting to the sim with SimConnect) can pick either EZ1, EZ2 or EZ3, totally randomly.

When I make connect/disconnect from the Vatsim network with vPilot, all aircrafts nearby are injected in the sim as simobjects with teh application of the matching rules and teh random selection as explained above, when applicable. I can see that vPilot picks a differnte title (texture) each time for the Easyjet A320, but strangely, the A320 in teh sim always shows the same livery (ie teh one that has been loaded at the first launch of vPilot). I tried to stop vPilot and relaunch (instead of connecting/disconnecting from the network) but with no change. So the texture seems to be "sticky".

Is anyone aware of this kind of a similar problem ?

Thanks
 
I don't know if this helps, but I had a similar issue when making Jetway simobjects with different numbers on the signs. Despite 36 different textures, they'd all read as number 1.
The way I got around it was creating a new unique model folder for each one (model.1, model.2, etc) with each containing only a model.CFG file that links back to the original model, like this:

[models]
normal=../[name of model folder containing original model]/[modelname].xml

and then for each [fltsim.xx] entry just change to model=1, model=2, etc.
I assume you'd want to put something like model=EZY1, model=EZY2, etc. if you name each new model folder as model.EZY1, model.EZY2, etc.
That way each plane spawns with the same model (since their model files all link back to the original model), but as a new instance of that model so that the textures aren't the same between all of them.
 
Well, if that works, that is certainly a workaround I could use for some time, but, man, that is very heavy on resources as you have to copy the mdl files in so many folders !!

Anyone having direct contacts at Asobo could maybe raise the point directly to them as this is a major bug in Simconnect !!
 
gpxe0 said:
Well, if that works, that is certainly a workaround I could use for some time, but, man, that is very heavy on resources as you have to copy the mdl files in so many folders !!

Anyone having direct contacts at Asobo could maybe raise the point directly to them as this is a major bug in Simconnect !!
Click to expand...
Actually you don't have to copy the mdl files. Just put a simple model.CFG with the text I wrote earlier in each new folder. Keep the original model where it is, don't worry about copying it! The model.cfg just points to the original so you don't have to copy+paste.
 
It's probably not a SimConnect bug, but it IS a bug... and the "work around" is clanky and chews through disk space for no legitimate reason.
 
You must log in or register to reply here.
Back
Top