[NO BUG]A10C and A10CII inventory load failure on Syria map

[Eviscerador]

Hello everyone.

 

I found this bug that might be related to the Syria map or to the A10C and A10CII module. I don't really know which is the issue but the bug is as follows:

 

- Map: Syria. I tested it in several airbases: Beirut, Ramat David.

- Module: A10C and A10CII

- Issue: Fresh mission. Cold start without any weapons, you ask reload, the crew reload whatever you asked and when you load the inventory into de DSMS the inventory is still empty and everything is lined red. Even if you try to load manually each station it won't allow you to do so.

 

I tested it on every other map (except Normandy and the Channel) and it works fine in every place but Syria.

 

I'm attaching the track for reference.

 

I will post this bug in the Syria bug subforum as well.

 

Thank you.

Inventory failure Ramat David.trk

[Ziptie]

Hello everyone.

 

I found this bug that might be related to the Syria map or to the A10C and A10CII module. I don't really know which is the issue but the bug is as follows:

 

- Map: Syria. I tested it in several airbases: Incirclik, Beirut, Ramat David.

- Module: A10C and A10CII

- Issue: Fresh mission. Cold start without any weapons, you ask reload, the crew reload whatever you asked and when you load the inventory into de DSMS the inventory is still empty and everything is lined red. Even if you try to load manually each station it won't allow you to do so.

 

I tested it on every other map (except Normandy and the Channel) and it works fine in every place but Syria.

 

I'm attaching the track for reference.

 

I will post this bug in the Syria bug subforum as well.

 

Thank you.

 

Via MFD, did you select the LOAD OSB and then select the LOAD DSMS OSB after the aircraft has been completely armed? Works fine for me.

 

 

Cheers,

 

Ziptie

[SJBMX]

I ran into this issue, and it was determined that the problem was that the mission creator had, at one point, used the "Prepare Mission" function.

[Eviscerador]

 

Via MFD, did you select the LOAD OSB and then select the LOAD DSMS OSB after the aircraft has been completely armed? Works fine for me.

 

 

Cheers,

 

Ziptie

 

Yes I did. I even tried to load them manually via the inventory page on the dsms but to no avail. It happens only on some airbases. Ramat David or Beirut. In Damascus it works fine.

[Eviscerador]

I ran into this issue, and it was determined that the problem was that the mission creator had, at one point, used the "Prepare Mission" function.

 

That's what I thought but then I made a fresh mission, just placed one a10c on ramat ramp, and it also happened.

 

It also happens if you preload weapons on the plane. At least 3 more people on my virtual squadron have the same issue so it is not just me.

[Yurgon]

- Issue: Fresh mission. Cold start without any weapons, you ask reload, the crew reload whatever you asked and when you load the inventory into de DSMS the inventory is still empty and everything is lined red.

 

Works perfectly fine for me.

 

However, in your track you never loaded the DSMS or anything else.

 

You did click the "Load ALL" OSB, but it wasn't ready yet.

 

Wait for the asterisks to appear, then click "Load ALL". Once the asterisks re-appear, you're good to go.

 

On a side note, it's absolutely okay not to know every tiny detail about a module as complex as the A-10C. But I would caution against calling something a bug, and filing it in the Bugs subforum, when there's a chance the game is actually working as intended. Maybe phrase it as a question next time?

 

I will post this bug in the Syria bug subforum as well.

 

You should remove it or update it there.

 

I ran into this issue, and it was determined that the problem was that the mission creator had, at one point, used the "Prepare Mission" function.

 

Very good point, that was my first guess as well, but the track file doesn't include the "DSMS" folder that would typically show up after "Prepare Mission" and then cause all DSMS reloads to fail, and OP's track shows very clearly that he's just rushing through the DTC-load procedure prematurely (admittedly I had to watch the track twice, though; didn't catch it the first time ;)).

[Stuka]

Yup, like Yurgon said: you never loaded the DSMS. You pressed the LOAD ALL button when it was not available yet.

It only came available a split second before you went to the DSMS page.

[Eviscerador]

 

Works perfectly fine for me.

 

However, in your track you never loaded the DSMS or anything else.

 

You did click the "Load ALL" OSB, but it wasn't ready yet.

 

Wait for the asterisks to appear, then click "Load ALL". Once the asterisks re-appear, you're good to go.

 

On a side note, it's absolutely okay not to know every tiny detail about a module as complex as the A-10C. But I would caution against calling something a bug, and filing it in the Bugs subforum, when there's a chance the game is actually working as intended. Maybe phrase it as a question next time?

 

 

 

You should remove it or update it there.

 

 

 

Very good point, that was my first guess as well, but the track file doesn't include the "DSMS" folder that would typically show up after "Prepare Mission" and then cause all DSMS reloads to fail, and OP's track shows very clearly that he's just rushing through the DTC-load procedure prematurely (admittedly I had to watch the track twice, though; didn't catch it the first time ;)).

 

With all due respect, I've been flying the A10C since 2012 and I know the module. I tried to load the inventory MANUALLY, station by station, which should work even if you don't load the cartridge. And it didn't work.

 

It works in every map but in Syria in some of the airbases. Damascus work, Beirut doesn't neither does in Ramat David. I repaired and removed all mods before posting the bug report. It keeps failing. And I'm not the only one in my virtual squadron. We all have the same issue every time.

 

That kind of condescending speech makes me sick. Don't worry, the issue will surface sooner or later.

[Yurgon]

With all due respect, I've been flying the A10C since 2012 and I know the module.

 

Before posting, I ran and watched your track at least twice and could clearly observe that you were pressing the LOAD ALL OSB too early. The asterisks weren't there yet.

 

I then renamed the track to "Inventory failure Ramat David.trk.miz" and ran it from the game's Mission menu, loaded weapons and the DSMS, and all was fine.

 

I also ran your track a third time, took control immediately, loaded one of the predefined loadouts, then loaded the DTC like I always do, and it worked fine, the DSMS had properly recognized all weapons. Just to be sure, I loaded a completely different loadout, reloaded the DSMS, and again the DSMS showed all weapons/stations properly loaded and recognized.

 

I also placed an A-10C and an A-10C II at Ramat David in a fresh mission in the ME, loaded both with weapons, then loaded the DTC, and the DSMS was perfectly fine.

 

I dare say I probably took more time examining your track than it took you to post it.

 

If you think it's condescending to point out you made a mistake, suit yourself.

 

If you think the mistake you made is not related to the problem at hand, a new track could shed some light on it. You might also want to indicate the exact DCS version number the track was recorded in. I tested it in 2.5.6.57264 OpenBeta, so maybe it's a problem that's already been fixed?

 

In any case, I can't replicate what happened to you, as long as I follow the proper steps.

[Eviscerador]

 

Before posting, I ran and watched your track at least twice and could clearly observe that you were pressing the LOAD ALL OSB too early. The asterisks weren't there yet.

 

I then renamed the track to "Inventory failure Ramat David.trk.miz" and ran it from the game's Mission menu, loaded weapons and the DSMS, and all was fine.

 

I also ran your track a third time, took control immediately, loaded one of the predefined loadouts, then loaded the DTC like I always do, and it worked fine, the DSMS had properly recognized all weapons. Just to be sure, I loaded a completely different loadout, reloaded the DSMS, and again the DSMS showed all weapons/stations properly loaded and recognized.

 

I also placed an A-10C and an A-10C II at Ramat David in a fresh mission in the ME, loaded both with weapons, then loaded the DTC, and the DSMS was perfectly fine.

 

I dare say I probably took more time examining your track than it took you to post it.

 

If you think it's condescending to point out you made a mistake, suit yourself.

 

If you think the mistake you made is not related to the problem at hand, a new track could shed some light on it. You might also want to indicate the exact DCS version number the track was recorded in. I tested it in 2.5.6.57264 OpenBeta, so maybe it's a problem that's already been fixed?

 

In any case, I can't replicate what happened to you, as long as I follow the proper steps.

 

Let's for one moment think I'm doing it bad as you say. Then why the DSMS loads fine in every other map, mission or base but those? Consistently. In fact I even tested with a hot start, loaded, empty, waiting for a fully aligned CDU before loading everything. It just doesn't load, not with the LOAD page or manually. Believe me, I fiddled with the issue more time than it took you to test it before posting it here.

 

OB version is 2.5.6.57264

 

But don't worry. Tomorrow I will make an ingame video. You will see it is a clean installation with no mods, I will create a fresh Syria mission. I'll place an a10C on Ramat David, I will do a cold start step by step and you will see the result by yourself. Then with the video feel free to tell me I've messed up with the cold start.

[Chunk]

You have a pretty condescending attitude towards people trying to help you. I’ve no doubt that you know what you’re doing, and that you have tons of hours in this aircraft. However, like Yurgon said, you erred in this instance. Maybe something is amiss in your install, have you run a repair to your install and tried the same scenario again? Like Yurgon stated, I have no issues either. I look forward to your video!

[Yurgon]

Then why the DSMS loads fine in every other map, mission or base but those?

 

That's a circular argument.

 

I believe it's what you witness, but doesn't get us any closer to the underlying root cause.

 

In fact I even tested with a hot start, loaded, empty, waiting for a fully aligned CDU before loading everything. It just doesn't load, not with the LOAD page or manually. Believe me, I fiddled with the issue more time than it took you to test it before posting it here.

 

I'm looking forward to it.

 

Just to be sure, I ran a couple more tests with a cold start A-10C II at Ramat David.

 

I need to properly load the DSMS via the DTS page once. After that, reloading the DSMS consistently updates it to everything I put on the jet. I can then also manually update the DSMS via the DSMS INV page just fine. Even updating via DSMS INV first, and then loading new ammunition afterward clears the red marks in the DSMS as soon as the rearming is completed by the ground crew.

 

I noticed you seem to load ammo via the radio menu (F8. Ground Crew...; F1. Rearm and Refuel...). I usually do it with the "Rearming and Refueling Window" shortcut (LALT + ' by default), but trying it both ways didn't change the outcome in my tests.

 

Also clicking the OSBs with the mouse didn't change anything for me (I usually use the TM Cougar MFDs).

 

Not knowing how you start the aircraft in any mission other than the above track, I can only note that you made a mistake in that track that directly ties to the observed behavior, and explains it perfectly, and would do exactly the same in any mission on any map.

 

I'm looking forward to a video recording to clear things up. Ideally, you should do two videos so we can see a direct comparison between how it's working okay in one and not okay in another. If it turns out that you're right and there's something wrong with the DTS DSMS loading on some airports in the Syria map under some conditions, hunting this down is probably going to be a royal pain in the behind for ED. ;)

 

Edit: And some more tests.

 

I found that in some cases, manually updating the DSMS via the DSMS INV page didn't work for me, regardless if I did it before or after the actual rearming.

 

However, loading or reloading the DSMS via the DTS page worked all the time.

 

And I ran some of the latest tests in Nellis, where the observed behavior matched that from Ramat David for me.

Edited November 9, 2020 by Yurgon

[Chain_1]

Can confirm this is operator error, with a root cause of a lack of checklist discipline. You hit "Load All" before it was available, i.e. there was no asterisk by it. That's because the asterisk does not appear until the CDU is powered on and has completed its BITs. You, as is documented in your replay, pressed "Load All" before even turning the CDU on.

[Eviscerador]

 

I'm looking forward to a video recording to clear things up. Ideally, you should do two videos so we can see a direct comparison between how it's working okay in one and not okay in another. If it turns out that you're right and there's something wrong with the DTS DSMS loading on some airports in the Syria map under some conditions, hunting this down is probably going to be a royal pain in the behind for ED. ;)

 

 

That's my idea, I will record a full uncut video with the following steps:

- Checking that my install is clean (you can trust me I repaired it twice yesterday) and without mods.

- Going to mission editor and placing two A10C 2, one in Ramat David, one in Damascus in a fresh mission. I won't touch anything else. It will be a fresh template mission.

- Going through the cold start in Ramat David. Fiddle with the inventory page and try to load it manually.

- Going through the cold start in Damascus. Check that everything loads fine.

 

I have at least two more people in my virtual squadron having the same issues, so it is not only me.

 

I hope I will have it ready today.

[Eviscerador]

OK guys, I confirm it is actually not a bug. One of the missions we play in the squadron has some scripting. It seems after this patch something changed and it messed up with the "prepared mission folders" and it gave you the same error again and again even after you load another fresh mission. You need to delete all temporary folders on the mission and restart the program to get it working again.

 

Today everything went fine except that mission, after flying it, it happened again, so we focused on the mission folders and we found the issue.

 

So in the end the first guy was right. It was something to do with the prepare mission. But since it happened also on fresh starts, I discarded that.