Jump to content

Recommended Posts

Posted (edited)

Hi, 
I am trying to use GBU-10 on the A10C-II module in a custom mission (offline mission editor)
1. try: cold start
After cold starting the aircraft, default(slow) aligning the INS, and using the "load all" button.
When I select GBU-10, it is shown in white on the DSMS page. (master arm on, GBU-31 arm just fine and are shown in green)
2.try: spawn in the air
GBU-10 is still shown in white on DSMS page, but now also only half of my GBU-31s are armed.
This issue seems copletely random to me. Sometimes I boot up the game, launch the same mission, and everything works as intended. Then other times only half of the GBU-10s arm. 
(sorry if I am missing something obvious, but I genuenly couldn't find anyone having the same issue.)

 

 

GBU10.JPG

GBU31-green.JPG

gbu issue1JPG.JPG

Edited by SlavDude
Posted

That looks pretty weird.

Can you upload a track so that we can check if we get the same? Please note which version of DCS you're running (Stable or OpenBeta).

  • Like 2
Posted

As @Yurgon said: A track file would really help, so that we can take a look at what is actually happening.

  • Like 1

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted

As luck would have it, I was unable to reproduce this behaviour after I created this post.
I will play some more, and will update this with a track file, as soon as it happenes again.
Thank you for the assistance.

Posted (edited)

UPDATE: so it happened again.
full cold start, slow align, loadout was set in mission editor so I didn't rearm or anything.
GBU-10s stay white, while GBU-31 arm just fine (after moving the aircraft a little)

track file attached

GBU10_31-A10C-2slowAlign1.trk

 

UPDATE2: I tried the same mission but player set to runway start, and the same issue happened

 

GBU10_31-A10C-2runway1.trk

UPDATE3: after restarting the game seems to fix it, I could load up the same mission with runway start and gbu-10s armed again
 

GBU10_31-A10C-2runwaySuccess1.trk

It seems to me this always happens when I die on the mission and restart it. After the first time my A10 is destroyed, GBU-10s don't arm and GBU-31s arm randomly (if I have 4 equipped sometimes only two of them arm). Backing out to the main menu, or loading up a different mission does not solve the issue, only a full game restart.

I am starting to think this may be an issue with the mission file. I will create a completely new one and check if that still happens.

Edited by SlavDude
Posted
22 hours ago, SlavDude said:

(sorry if I am missing something obvious, but I genuenly couldn't find anyone having the same issue.)

 

Master Arm needs to be in "ARM".

48th_Sig_Pic.png

Posted

Thanks for the tracks! I'll check when I'm back at my PC after Christmas, unless someone beats me to it. 😉

2 hours ago, WizzRD said:

Master Arm needs to be in "ARM".

OP said it was, the screenshots show it to be armed (a bit hard to see depending on the perspective), and if Master Arm was off, no weapon would show with a green status on the DSMS screenshots.

From OP's description and the screenshots, this seems to be something a little more complicated than forgetting a single switch.

  • Like 2
Posted
1 hour ago, Yurgon said:

Thanks for the tracks! I'll check when I'm back at my PC after Christmas, unless someone beats me to it. 😉

 

Thanks, Appreciate it 🙂

Posted (edited)

I was able to reproduce this on my own:

I created a simple mission (see attached), spawning hot on runway, took off and everything worked fine (GBU-10 was green in DSMS). I dropped the GBU-10 and then crashed my aircraft into the ground. I then restarted the mission ("Fly Again") and now the GBU-10 stayed white on the DSMS. I could still drop it though. 🤷‍♂️

Test.miz

Edited by QuiGon
  • Like 1
  • Thanks 1

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted
On 12/24/2022 at 10:34 PM, SlavDude said:

It seems to me this always happens when I die on the mission and restart it.

Excellent observation!

That's indeed what it looks like. I could reliably reproduce the problem by dropping some weapons, dying, running the same mission again and then observing that the previously expended weapon stations were now showing white in the DSMS.

Your runway-start tracks both looked fine for me - I actually had to take control, take off, drop a weapon, die, and then run the same track again in order for the problem to show up.

And like QuiGon said, it looks like weapons can still be dropped from affected stations.

I filed a bug report in the Open Beta Tester part of the forum and I'm sure it'll get fixed eventually, but given the necessary steps to run into this problem, and that it looks to be a cosmetic issue, it may not receive a high priority, so you may need to be a little patient for it to be fixed. 😉

  • Like 1
Posted

I don't think it is cosmetic, because I tried dropping "white" GBU-10s on bunkers and I only saw white smoke. While when droping an armed "green" GBU-10 the bunker also started burning.

In case anyone else is having the same issue, I circumvented it by setting player airplane to "client" and launching mission in multiplayer. (you can launch it in single player, but in that case you need two aircraft set to client, so you can switch role after death, and then switch back. Otherwise you are unable to respawn.)

@QuiGon @YurgonThanks for taking the time and confirming I am not crazy ^^

 

Posted
1 hour ago, SlavDude said:

I don't think it is cosmetic, because I tried dropping "white" GBU-10s on bunkers and I only saw white smoke. While when droping an armed "green" GBU-10 the bunker also started burning.

Oh that's good to know, I amended the bug report.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...