[OLD BUG REPORTS] Cleaning and Organization of old posts

Ahh I am idiot! I forgot! Right clicked actual hand handles on opened canopy frame and not red handle at wind shield.

Thanks for help and sorry for false alarm.

Any news on the PID bug it makes the radar really annoying to use in a target rich environment?

Hi.

When you TWS (PID) lock a contact often other contacts will disappear. Whether the contacts other than the locked contact reappear or not depends on the pitch of the aircraft which seems incorrect. Furthermore a contact locked next to another contact which is the same altitude will disappear even when the radar is still locking TWS (PID) locking the original contact.

Steps to reproduce:

1. Create Mission with two aircraft out in front of the mirage that are at the same altitude as each other.

2. TWS (PID) lock one of the contacts.

3. If the other contact disappears then pitch up and down until it can be seen again. If it doesn't disappear then pitch up and down until it disappears to demonstrate the bug.

Workaround:

Fly your plane like a dolphin and bounce up and down to detect contacts other than the one you have TWS (PID) locked.

Please see the attached video for a clearer view on what is happening. Also attached is the track of the same recording.

Thank you.

JNelson

Hi,

when using GBU-12 on M2000C, I can set them but after release, the bomb has disappeared ... I can't see it with F6 key and it never hits something. I release the bomb when climbing a little bit (diamond center is up than 3°).

I use a script so I need to test without.

But when using GBU-16 no problem.

Regards

Here is a track... Even if F6 doesn't work because no bomb. And the mission to test. That works sometimes, sometimes not. No problem with GBU-16.

Same problem without script. No lasering cause no JTAC.

ATME_spotTest.miz

test GBU.trk

Are you sure the bomb is actually released? Do you hear the sound, check with F2 under the wings, check stores in the HDD?

Here is a track...

Unfortunately it looks like the track doesn't play back correctly on my PC as it is very short.

Tacview shows you roll/dive to designate the target area and then release a GBU-12 in level 1g flight (400 CAS / 500 TAS @ 15,600ft).

On weapon release, the bomb appears inside the aircraft (rather than below) and 1 second later, strikes the aircraft.

The track then ends (likely due to DCS recording both bomb and aircraft as destroyed).

IIRC I used to have issues in 1.5.x with Mk-82/GBU-12's when they were mounted on the center rack.

Tested in DCS Open Beta 2.5.6.45915

@Lorthirk : I'm sure, several tests done before opening that thread, and test with another people on its own PC. So it's a real problem

@Ramsay : In my case, no bomb no strike ... but one bomb less on aircraft racks. I can reproduce that easily like in the video(one time on two nearly). I will do another track more longer with external view... But, the problem doesn't exist with GBU16... That is strange.

Test on last OB too.

@Ramsay : In my case, no bomb no strike ... but one bomb less on aircraft racks. I can reproduce that easily like in the video(one time on two nearly).

Unfortunately I can't reproduce using your mission, all 4 bombs released cleanly and were viewable with F6.

As the bombs on the wing roots release first, my speculation on the center line stores was erroneous.

DCS Open Beta 2.5.6.45915

We have the issue regularly in our squadron, but quite randomly. It only happens with 4xGBU-12 load out, not with 2x GBU-12. That's why i guess you don't have it with GBU-16 as you can't load 4 of them. We mainly have it in Multiplayer.

I have the issue with the first GBU-12 released, sometime with the 2nd, but never with the 3rd and 4th GBU-12 that are mounted on dual rack on center station.

When loading 4xGBU-12 you can see on VTB, with PRES function on PPA, that only 3xGBU-12 are displayed as EL1, whereas you get a '---' for the fourth one.

Initially, IRL, only the 2xGBU-12 loadout was valid. The 4xGBU-12 loadout has been validated only in 2015. Not sure how Razbam approached it.

There is clearly an issue with the 4xGBU-12 load out, but hard to reproduce on a constant basis, at least on my part.

Hey guys, good news !

Zeus said on discord that he fixed the radar PPI lock bug, the PID additional contact display bug, and the wrong visualisation of the antenna altitude and elevation.

Only the PPI fix would make it in the next update.

Waiting the the update to test the fixes :)

@Ramsay, it's easy to reproduce

@Steph, yes you've right, the problem I have is with 4 bombs.... I will test with one or 2 only. Your explain seems the right one ;)

So wait and let's see Razbam answer ;).

Hey guys, good news !

 

Zeus said on discord that he fixed the radar PPI lock bug, the PID additional contact display bug, and the wrong visualisation of the antenna altitude and elevation.

Only the PPI fix would make it in the next update.

 

Waiting the the update to test the fixes :)

Great news !

Noticed yesterday that Master Arm switch impacts PCA mode when weapon is selected on PCA. It shouldn't. Will post a track tonight.

So, I did several more tests, 10 tests with 2 GBU12 on central pylon (5) and 10 tests 2 GBU12, one on each pylon (3) and (7).

No problem when GBU-12 are on central pylon (like GBU16), but one problem (on 10 tries) when GBU12 are on pylons (3) and (7).

So I think there's effectively a random problem when GBU12 are on pylons (3) and (7). You've right Steph.

Perhaps that last configuration is not valid for M2000C. I will set GBU12 on the central pylon only for my missions. I will do more tests with 2 GBU12 on pylon (5) to be sure.

Note that those tests have been done with my script active ;)

But I need Razbam confirmation !

Thanks

 

But I need Razbam confirmation !

 

Thanks

Hi,

i have passed this to the testers to look at.

I shall come back asap :)

It happened to me yesterday as well, I thought it came from the buddy lasing as it's a thing IRL to loose the spot but with a 4*GBU12 loadout, 2 of them didn't give me splashes and nowhere to be found??

Yes, that's the issue we get randomly.

This Tuesday, i had no issue dropping my 4 GBU-12, but i had the issue dropping GBU-12 from stations 3 and/or 7 several times.

We'll wait for Razbam feedback.

Hi,

 

i have passed this to the testers to look at.

 

I shall come back asap :)

Ok thank you for your return...

If you need more info, do not hesitate...

So wait for feedback ;)

@Madone : I did my tests without spotting, to be sure there is no link between spot and GBU release.

Sunski

Master Arm changing PCA mode when ground weapon selected:

When selecting a ground weapon or AG Canon on PCA, selecting Attack mode with WSC Fwd and then clicking WSC Aft, it set PCA back into NAV mode. But then when setting Master Arm to ON, PCA mode is set to Attack Mode.

Master Arm shouldn't impact PCA mode.

Track attached

Master Arm affecting PCA mode.trk

Hey guys, good news !

 

Zeus said on discord that he fixed the radar PPI lock bug, the PID additional contact display bug, and the wrong visualisation of the antenna altitude and elevation.

Only the PPI fix would make it in the next update.

 

Waiting the the update to test the fixes :)

Doesn't seem to have made the cut, as i still have issue locking with PPI when target is not in the center on the VTB. Just a made a quick test though.

Do you still have the issue too guys in latest OB?

Doesn't seem to have made the cut, as i still have issue locking with PPI when target is not in the center on the VTB. Just a made a quick test though.

Do you still have the issue too guys in latest OB?

Yes, the bug is not fixed.

Testers have looked at this and cant replicate

Hi Decoy,

that's strange because it's easy to reproduce with the mission I sent. Just climb a little before release it (diamond around 3°).

With 2 ou 4 GBU? More difficult with 2 GBU under wings.... 1/10 but with 4 bombs 1/2 or 1/3 ... I can send a new track without script if necessary. It's a random problem !!

Thanks

@DECOY : As Steph21 said, you can see a problem on VTB when carring 4 GBU12.

Here is pictures extract from the mission I sent. You can see that there's a pb on rack (3) I think, no bomb. But, as you can see in mission configuration and external view, 4 bombs are carried.

In that case two possibility : when the bomb on rack (7) is released, no problem for the first strike but, when the bomb on rack (3) is released problem ... No bomb.

That is for 4 bombs. I will test for 2 bombs on racks (7) and (3).

Sunski

And the problem is exactly the same with 2 GBU on rack (3) and (7). So definitly, VTB visual on rack (3) where no bomb is displayed (--) and the bug are linked.