[OLD BUG REPORTS] Cleaning and Organization of old posts

Well it's not a bug: units have changed ! :smilewink:

 

 

 

It would have been nice to include this "little detail" in the changelog.

 

 

RazbamZeus confirmed the change in units on Razbam's discord.

 

 

Offsets for IP are in metrics (also on the HUD) while the rest is in imperial (HSI still in imperial when flying to target).

 

 

It's confusing and we haven't had an "official" word about that :music_whistling:

 

 

 

I know INS bombing is useless with all these JDAM/JSAW etc but still, it is an important change and deserve to be noticed.

Well ok, indeed that's a quite important change !

So on HSI, when flying toward IP, distance will be in Nm, and then when overflying IP, distance to BAD will be in km ? Wonder what they were thinking at Dassault....

Wonder also how TR value will handle that in PCN TR/VS display...

There's still a bug in BAD Delta ALT entry in feet though

Well ok, indeed that's a quite important change !

So on HSI, when flying toward IP, distance will be in Nm, and then when overflying IP, distance to BAD will be in km ? Wonder what they were thinking at Dassault....

Wonder also how TR value will handle that in PCN TR/VS display...

There's still a bug in BAD Delta ALT entry in feet though

Suppose the left windows for delta in feet is buged.

We'll have to use the right field for entering Delta in meters for now.

Suppose the left windows for delta in feet is buged.

 

 

We'll have to use the right field for entering Delta in meters for now.

Indeed.

Can we change distance units on the fly on F10 map for the ruler, like we can for coordinates ? Couldn't find a shortcut for it...

I have made a mission for to hit a ground targhet with GBU 12 and IP mode

1) for altitude and distance use metric sistem in meter for altitude and Kilometer for distance

2) for hit the targhet use JTAG laser beam without JTAG it is impossible to hit the targhet

from previous patch there is an improvement but not enough for hit the targhet without the assistence with JTAG

That's one small step for us , one giant leap for Razbam.

I have made a mission for to hit a ground targhet with GBU 12 and IP mode

 

1) for altitude and distance use metric sistem in meter for altitude and Kilometer for distance

2) for hit the targhet use JTAG laser beam without JTAG it is impossible to hit the targhet

 

from previous patch there is an improvement but not enough for hit the targhet without the assistence with JTAG

 

 

That's one small step for us , one giant leap for Razbam.

We don't get decimal value for Offset heading with ruler on F10 map, so you can't be precise with Unguided Bomb in CCRP INS Bombing. Use CCIP INS bombing if you want to be precise with dumb bombs.

LGB is the way to go for CCRP INS bombing if you want precision.

Guys, if you want to test CCPL + PI (in French), I can’t recommend you enough to run your test on Caucasus map and to use this little piece of software.

You input IP and target coordinates and it will give you the necessary offset accurate data.:thumbup:

https://forums.eagle.ru/showpost.php?p=3481511&postcount=2

New bug in latest Open Beta 2.5.6.45915

INS Bombing: Wrong units of measure for BAD Delta Altitude

 

When entering Delta Altitude for INS bombing on PCN in feet, systems takes it as meters and transforms it as feet before entering the value in the feet windows.

I have to calculate my Delta Alt in meters, to enters meters value in the feet altimeter box to get the correct delta alt in feet

Works fine if entered in meters in right window.

 

Attached a track where i show on F10 map that my target is 4.10 Nm at 066° from IP (IP being where the river goes into the sea) and target is 59ft higher than IP.

In PCN, i enter +00059 in left windonw on BAD Delta Alt, and it transorms it in 18ft (which is 59 meters). So i have to enter 180 in feet windows to get 55 feet displayed (roughly what i need).

Hi Steph

According to me, the value is converted in feet in the "meters" window, but I think it keep meters for computing. It's very accurate when you enter a feet value, despite this weird conversion in the window.

Hi Steph

 

According to me, the value is converted in feet in the "meters" window, but I think it keep meters for computing. It's very accurate when you enter a feet value, despite this weird conversion in the window.

I'm using metrics only now for offset, meters in delta alt (right window) and km for rho, and it works fine.

Might be only a display issue indeed in delta alt left window

Don't forget INS doesn't update using position of cursor or jet, rather resolves error to 0

Also CCRP requires designation using the top of the designation diamond, as opposed to the pipper. Forum user Ramsay confirms this is parrallax issue.

Also, waypoint crosses are not in the right location. They seem to refer to some location below ground.

It happened few times already.

Selective jettison of Mk82 via the PCA panel, crash when pressing the release button. Totally random, cannot reproduce.

Persian gulf, multiplayer, current Open Beta

Hey - thanks, I will update the manual. I removed the reference in M2 - updated training should be available with the next update.

2nd Training mission still has reference to ENC but ton, is it normal ?!

When will the training missions be updated please ?

Thanks beforehand for any information :)))

Regards,

John "Kalon"

sigh

dcs.log-20200405-212638.zip

I can confirm, that happened to me yesterday. I'll try to get the logs.

Had something similar tonight while playing a TTI SP mission. Killed two MiG-31s with 530s. Found a MiG-21, locked him up for a magic shot, then thought it’s too easy, brought up the guns. Had them in continuous fire mode. Squeezed off a few shots and missed. Probably 3-4 bursts, and then shot again. Next thing I know I’m spinning towards the ground. Hit pause and notice that part of my right wing is missing. Eject, watch the MiG fly off. Quit mission, find the only thing mentioned is Right RWR failure.

Glad it’s not just me!

I didn't watch the track, but if you are at gun range, there is a good chance you are passing through wake turbulence of your target. Sometime you can go up to 25G !!! = ED bug.

It isn't specific to M-2000C (Hornet or F-16 too for instance).

I disabled the option in options.

Ok, that makes sense. I recall a very violent pitch up and then tumbling. I’ll turn it off and continue flying and see what happens.

can assure, not working

With latest I am unable to close canopy with clicking on canopy handle. It works to open closed canopy and do nothing when canopy is open.

Never had a problem closing the canopy. I just right click the red handle, then I left click the retention handle (yellow/black square) and left click the red handle to pressurize.

With latest I am unable to close canopy with clicking on canopy handle. It works to open closed canopy and do nothing when canopy is open.

To lower the canopy to half way point, use the canopy handle (move dark red or brown on right side of cockpit back) to lower the rest of the way, click on the canopy support strut. To lock the cockpit downs, move handle forward. To raise the canopy, first unlock the canopy, then click on the hand hold on the right side of the canopy. Its been this way since release.

Here is one example

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