[OLD BUG REPORTS] Cleaning and Organization of old posts

[Snappy]

Hello,

 

 

since the latest update(27/11) even the Close Combat modes of the radar have issues locking onto targets at close range (<5nm) AND within the actual HUD frame, so really directly in front of the aircraft.

 

 

Sometimes it takes a long time while I was chasing a target in its 6 o clock position at 2-3 miles until it finally locked on.All that time the target was straight ahead.

 

 

I don't consider this realistic. I get that an 80's technology radar is limited in its longer range and TWS detection, but here the radar is only sweeping a very narrow area in front the aircraft with a high frequency.

At these distances it really should have no issues locking a target within this small area dead ahead.

 

Razbam/Decoy please check into this.

 

Kind regards,

 

Snappy

[some1]

I confirm, something's not right.

[ThorBrasil]

All engine sounds are being remade

 

Sent from my SM-G960F using Tapatalk

 

Thank you! Merry Christmas and A Happy New Year! :thumbup:

[viper2097]

The new PCN Panel is missing the ENC button for automatic waypoint switching.

Is this a bug, or intended?

[viper2097]

To use the NVG now, we have to

- Equip it to the aircraft

- unstow it

- mount it to the helmet

- finaly use it

 

Thats one setting and three key bindings where one keybind (shift+home) is alreadey used to start engines (how is that even possible?).

 

Could you please simplify it as it is in all other modules? Thank you, that would be very helpful...

[viper2097]

Reported half a year ago, still not even a comment. Any news on that issue?

[Rayak]

IIRC this function is not realistic for our mirage based on AdA feedback

[baltic_dragon]

Yep. Intended. No such thing in M-2KC currently.

[viper2097]

Ok, thx for the info :thumbup:.

Too bad, was a useful function....

[Mr_sukebe]

Two thoughts:

- Clearly this isn't a bug, no idea why you've opened it in this section

- Whilst you might not like it, some clearly do, me included. So if you'd like it changed, then how about putting forward a suggestion that they make it a checkbox option as to whether we'd like to use it in "simple" form, or in "cool" form.

[jojo]

Yep, intended behaviour.

2 clicks to put on your helmet (one on the case, one on the rack), then standard key/ keyboard shortcut to toggle on/ off. :smilewink:

[jojo]

You get something else realistic instead. Explanation here:

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

[jojo]

This is actually important because it highlights how radio is supposed to work. I was looking for some info on that but everyone seemed to actually completely ignore the issue and assume that the rocker on the throttle acts as radio PTT. That's how SRS and I think VAICOM treat it, even though it's been mentioned in many places that rocker is used for radio SELECTION. Well, this debacle seems to accidentally explain what is going on - the rocker indeed only selects the radio, and button number 8 on stick is PTT. At least that's how I understand it and it would mean that the closest HOTAS mapping would be to map whatever stick button was used for STT/TWS switch to Communications instead (or SRS PTT), and map STT/TWS to TDC press instead. Can any of the devs weigh in on this?

 

The HOTAS description by Baltic Dragon in official Razbam manual is correct description of Mirage 2000C RDI HOTAS.

The rocker on the back of throttle is a 2 ways push to talk indeed.

In game you open dedicated radio menu, but this is a game function.

 

So with SRS you would be right to map 2 push to talk and that’s the end of it.

 

HOTAS functions changed from Mirage 2000C RDM to Mirage 2000C RDI.

[viper2097]

Just read it, good information, did not see those buttons before.

Thx :thumbup:

[viper2097]

The description in the manual can't be correct, because it contradicts itself.

Just read through the whole first page of this thread.

[frosen]

Second that!

[viper2097]

https://forums.eagle.ru/showthread.php?t=255091

[baltic_dragon]

Another workaround for the time being is to assign keys to dim these ligths to 0, works very well.

[SpeedyE420]

Bug still exists. Ive been able to reproduce several times.

[Nooch]

I don't want to have simplified NVG's. It's perfect the way it is.

[Nooch]

That is awesome! So glad they are re-doing the engine sounds.

[viper2097]

Yeah, you're correct, the bug section maight not be the right one.

 

Ok, I just have seen that everything(except the use itself) is also clickable and you don't need the keybinds.

Well, thats a gamechanger and that way its really done quite good.

[paco2002]

Same here, i had a situation we're i had an enemy in front of me with the ACM modes and it just didn't lock

[Chapa]

As a workaround, you can map the three keybinds and build a macro with a tool like Voice Attacks. It can be useful for so much things that it is worth to be annoyed one time with it and never again by the NVG feature you don’t like.

 

Not as easy for sure but pragmatic.

[Harlikwin]

Well its realistic at least. Fumbling around with NVG's that is.