reported GBU-12 Wrong Lasercodes.

[TheGhostOfDefi]

I found inconsitencys with the Lasercodes using the GBU-12:

1. If you use the BRU-42 the Lasercode shown in Cockpit is always 1688.

2. If you set a Lasercode by the armament page in Editor for the GBU-12 w/o the 42 Rack (Not tested from Rearm menu) the Lasercode is shown in cockpit as set. But the actual code is sporadic still 1688. Track Attached.

P.s. It just dawned on me that i should´ve done that track on Caucasus instead of Sinai for accessibility reasons.

A10Lasercodes.trk

[Yurgon]

I don't currently have the Sinai map installed and can't watch the track. Can you record a new one on the Caucasus map? Or several short tracks that show precisely one issue each?

Also be aware that tracks don't show the Rearming and Refueling window (as far as I'm aware), so anything you set in that window will be invisible to anyone watching the track.

For issue number 1, was that setting the laser code in the Mission Editor or in the Rearming and Refueling window? If it's the latter, the DSMS doesn't know anything about it and you'll have to update the DSMS via the INV page to let it know which laser code your bombs are set to. I think reloading the DSMS, or rearming first and then LOAD ALL, should also tell the jet the proper laser code.

Issue 2 sounds hard to recreate without a track and a detailed description.

[TheGhostOfDefi]

I´ll hope that i can deliver more tracks the coming weekend.

[TheGhostOfDefi]

I have additional Infos that i could not yet comprehend:

 

1. Pretty much is the case all the Time (Given: Not testet with x3).

 

2. Station 4 in my most recent tests did not divert from Code 1688 at all. (All tests are conducted Hot Spawned in Air with Loadout set in editor)

Further i have the feeling that i get more problems if i use the lasercode 1567 than 1686. 

 

As i used copy to all stations in editor all entered lasercodes are ignored and 1688 is used.

 

I couldnt verify more today. I try tomorrow.

 

## Update ##

It seems to have to do with saved Loadouts. If i select the weapons manually onto the Aircraft the Lasercode mostly works. BUT if i select a saved Loadout and change the lasercode then there. It wont be taken over. 

Even problem 1. i could eliminate in this very limited Testing-Run i did. (By changing weapons manually)

2.  I guess that certain stations are problematic can be traced back to my testing behavior. 

 

Now the only interesting thing is, if my saved Loadouts are corrupted (And if more aircraft are affected) or this could be a problem with other users too.

Edited March 28 by TheGhostOfDefi
More Testing

[TheGhostOfDefi]

@YurgonCould you maybe verify that the FMU-152 is the reason for the fault? With the FMU-139 the Lasercodes work. When selected together with the FMU-152 they go back to 1688.

[Yurgon]

1 hour ago, TheGhostOfDefi said:

Could you maybe verify that the FMU-152 is the reason for the fault?

Yup, seeing that consistently. When I select either the FMU-143 or the FMU-152 fuze, the laser codes don't load into DSMS (doesn't matter if the fuze setting is applied in the ME or in the rearming and refueling window, or if the aircraft is a hot start, or if the DSMS is loaded manually through the DTS UPLOAD page).

With the FMU-139, I see no problem at all.

I couldn't find any difference between loading a GBU-12 directly onto a pylon or using the BRU-42 TER; to me it looks like the fuze is the common denominator, not the pylon/rack.

I've reported this internally.

Note, I think I've read somewhere that FMU-143 and FMU-152 aren't even used for Paveway II series bombs, so maybe that's why it doesn't work. But then it wouldn't make much sense to offer these fuzes for these weapons.

[graveyard4DCS]