can not reproduce unable to properly load DSMS config since updating to 2.19.17

[Fox-one-76]

hello,

running in VR with pimax crystal

I9 processor / RTX4070ti / 32gig ram

since updating to  2.19.17 in A10CII (happens in all my missions) when i start cold and dark i can't seem to get the DSMS to load properly

I get red boxes on my stations in the dsms page (or no boxes, only a red bar, on empty pylons) after loading the DSMS config through the "Load all" button.

i tried to rearm and refuel then reload the stores .. same thing

i tried to set the store types/QTY manually... same thing

am i missing something?

thanks

LastMissionTrack.trk

[BIGNEWY]

Hi, 

I was going to try and check your track but it has user mods in it. Are you able to reproduce in a plain mission with no mods? 

thanks

[Fox-one-76]

Hi 

Same thing with a brand new mission, 

no mod, no skin, jus 1 flight of 4 A10CII

Here is the track

LastMissionTrack.trk

[Yurgon]

1 hour ago, Fox-one-76 said:

since updating to  2.19.17 in A10CII (happens in all my missions) when i start cold and dark i can't seem to get the DSMS to load properly

Looking at the second track, you never loaded the DSMS or any other page from the Data Transfer System, and instead you went straight into the DSMS.

At this stage, pylons indicate "I" because of a mismatch between what's loaded on the DSMS (nothing) and what's detected on the pylons (something).

I then saw you load the AGM-65 symmetrically, and the indication correctly went from "I" (inventory mismatch) to "P" (no profile available).

I then took control of the track, simply hit the asterisk at OSB 18 "* LOAD DSMS" on the DTS UPLOAD Page and a few moments later, the DSMS correctly showed everything that was hanging under the wings.

As far as I can tell, nothing changed in DCS, and you are simply missing a step in your startup routine.

[Yurgon]

I just happen to have an old 2.9.16 installation available. In 2.9.16, I observe exactly the same behavior in your track as in 2.9.17.

Aaaaand I see you hit the LOAD ALL OSB about one second before the asterisks * appear on the DTS UPLOAD Page. Seems like you simply don't understand how the DTS UPLOAD works, and are now rushing your startup that, presumably, you didn't rush prior to the latest DCS update.

[Fox-one-76]

Hello,

thanks for the replies...

it is true that after the initial post i quite rushed the startup and that was defenately the cause in this case.

i did some other testing and found out that it happens only in a couple of missions that have built with some mods included ( 479th targets range objects) and / or have a tanker (KC135 mprs) using an anchored orbit. it may or may not be related to the mods or might just be a corrupted file.

i managed to get one of my older templates to work as it should.... so this is defenately not a bug, .

could you please close the thread?

thanks again for the quick and efficient support.

[Yurgon]

7 hours ago, Fox-one-76 said:

i did some other testing and found out that it happens only in a couple of missions that have built with some mods included

Well, there is an odd behavior where DCS sometimes stores additional data to a mission file that prevents the proper loading of the DSMS even when everything is done by the book. It's pretty rare and I think DCS doesn't do it anymore because the internal structure of mission files was updated a while ago. But in case you have old mission files with a "DSMS" folder inside the .miz archive, that could well be the culprit.

If you come across this issue again, report back with a track and/or the mission file. I checked the track file from the first post and it's not affected, there is no extraneous "DSMS" subfolder. I'm just saying such a thing could still be the case in specific mission files.