[OLD BUG REPORTS] Cleaning and Organization of old posts

[Schlomo1933]

It is now partially fixed. But when you switch the taxi or landinglights on the boxes are back!

[Shimmergloom667]

You realy believe that i search now the Forum of the last years for this Statement ? :lol::thumbup:

 

Well... yes. When you make a statement the burden of proof is on you. I don't remember such thing either.

[myHelljumper]

You realy believe that i search now the Forum of the last years for this Statement ? :lol::thumbup:

 

Well, yes.

 

When I say the the dev "promised" or said something, I try to back it up with a link to the post. If not, I add "I could be wrong" or "if I recall correctly", so the reader knows to take what I say with a grain of salt.

 

Most of the time when someone say that the devs have promised something, it's just that they said that they will implement it, with no time-frame or promise.

[Schlomo1933]

Even in their flightmanual the wride that they are working on it!

 

APP MODE AFTER GLIDESCOPE CAPTURE

 

1. ILS GUIDE. Visible only when both localizer and glideslope have been captured. It moves in relation to the FPM showing both glideslope and course deviation. To maintain a perfect approach, you have to place the FPM inside the box. If the deviation from either glideslope or course is too large, a flashing triangle (not shown) will appear indicating that a course/elevation change is required.

 

2. SYNTHETIC RUNWAY. The synthetic runway symbol is an aid for locating the real runway, especially during low visibility conditions. It is only visible when: a. The INS is on. b. The airport is the current fly-to waypoint. c. The runway data (heading and glideslope) were entered .

 

2 d. Both localizer and glideslope have been captured

Not functional at the moment, only possible by placing the “Landing” waypoint in the Mission Editor.

 

(PAGE 99)

 

 

Since when is the Mirage out of beta ? Since April 2017 !!!

Edited December 13, 2019 by Schlomo1933

[DmitriKozlowsky]

Gain control for NVG appears to be missing. Often , even in low light NVG in Mirage are too bright. Controls appear to be missing that feature, which is present in other modules using NVG.

[ShadowFrost]

Just wanted to notify you guys on something, when in TWS (not STT) the Mirage 2000 will lose radar lock of someone that does a roll. If this is correct than leave it, if not, now you know.

 

M2K TWS locks JF-17, JF-17 does two 360s (just straight aileron roll, no other inputs, keeping a straight line) and M2K loses lock. Should be easy enough to try an reproduce. I believe the range was 15-30 nautical miles.

 

 

https://drive.google.com/file/d/1oKOGQyRM6aEifEm38Miw_Wumn5-9mWJU/view?usp=sharing

 

Here is the track file, but unfortunately, its a lot of JF-17 bug testing and I'm also not the mirage pilot. So I don't know how much good it does.

[rinkerbuck]

There is a note in the Chuck's guide that TWS mode in the M2000 will sporadically intentionally unlock to try to not be as obvious to the enemies RWR. Not sure if that's happening in this case or not though.

[mr_mojo97]

Ok, so I updated today and now the radar reticle is flashing half the time, I can’t select the magics only the 530, both the tdc slews and the tws switch work in the options but not on the radar itself and I can’t get he radar to see more than 80. Not flown in a few weeks so I don’t know of there has been a change in procedure.

 

A bit frustrating to say the least.

 

Anybody else having this issue?

[Frederf]

I don't know what a radar reticle or tws is. The Magics are selected by the three-position switch on the throttle handle.

 

The 160, 320 nm ranges are accessible by bumping cursor at the top of the VTB but not by the console range selector switch. I don't know if that's correct.

[dimitri_nikolas]

Hello!

I am quite new to DCS (i.e. I don't have the whole history of former M2000 versions...) but I love the plane as it is now! Thanks for the amazing work, it feels so real...

 

Here are some slight bugs or defaults that might be worth being taken into account in the future if you think it is interesting:

- Preset radio frequencies on V/UHF have a 1 digit offset: CH1 is on 00, CH2 is on 01, etc...

- Radio freq. repeater should show the preset channels when they are in use, instead of the full frequency (i.e. if you are on CH1, it repeats 1, and if you are on 234.5 it repeats 234.5).The only way to check the full preset frequency is to press the READ button on the radio box. On the UHF preset channels can not be checked easily (hard coding).

- There is an important sound missing: when the AP ALT mode is desactivated, there should be a "DONG" sound confirming you that you are no more in that mode (especially if it has been induced by a trim action).

- The IFF "fault" signal is always present (the round circle with black and white sectors) i.e. it says is not working properly. It should be fully black when working properly.

 

Thank you!

[Cine]

Hello

 

I have also the same issue !

Radar is locked and after few seconds the target disapeare from HUD. then impossible to "see" again the target with the radar !

[Moody1204]

Hi,

Found an anoying bug with RWR (again...).

Against JF17, when being spiked and locked the symbol "KL" is centered on the RWR (see attached picture).

Probleme is: I am not at the merge, actually the bandit is on my 11' 20NM away.

 

 

So, it is impossible to know from where the bandit come from and notch properly those PL10...

 

 

Can we have a hotfix on this one please ?

 

 

Cheers

[Zaneboy]

The same issue with the harrier.

 

-> https://forums.eagle.ru/showthread.php?t=258758

[Ramsay]

Can we have a hotfix on this one please ?

 

The same issue with the harrier.

 

It may be a JF-17 regression, as a similar bug was reported as fixed on 7th Dec

 

https://forums.eagle.ru/showthread.php?p=4130643#post4130643

 

Perhaps check with another module i.e. A-10C, etc., and/or report the overly strong RWR signal in the JF-17 forum including a track file.

[myHelljumper]

Are you a real Mirage 2000 Pilot ? Or maybe a mechanic ?:D

 

Preset radio frequencies on V/UHF have a 1 digit offset: CH1 is on 00, CH2 is on 01, etc...

 

IIRC, it's fixed in the open beta vesion, no more CH00.

 

Radio freq. repeater should show the preset channels when they are in use, instead of the full frequency (i.e. if you are on CH1, it repeats 1, and if you are on 234.5 it repeats 234.5).The only way to check the full preset frequency is to press the READ button on the radio box. On the UHF preset channels can not be checked easily (hard coding).

 

Is it like this in the real aircraft ?

 

There is an important sound missing: when the AP ALT mode is desactivated, there should be a "DONG" sound confirming you that you are no more in that mode (especially if it has been induced by a trim action).

 

The dong is present in some cases, even when the auto-pilot is not engaged (pressing the auto-pilot standby when auto-pilot is deactivated) so this functionality might be WIP :).

 

The IFF "fault" signal is always present (the round circle with black and white sectors) i.e. it says is not working properly. It should be fully black when working properly.

 

You seem to know better than me on this :).

[Moody1204]

It may be a JF-17 regression, as a similar bug was reported as fixed on 7th Dec

 

https://forums.eagle.ru/showthread.php?p=4130643#post4130643

 

Perhaps check with another module i.e. A-10C, etc., and/or report the overly strong RWR signal in the JF-17 forum including a track file.

 

 

What do you mean by JF-17 regression ?

 

 

It is bugged, don't know what to described more.

 

 

Edit : Ramsay, can you confirm that your RWR in the Mirage works well with JF17 locking you up ?

Edited December 23, 2019 by Moody1204

[Harlikwin]

On the plus side the JF17 RWR is broken too. So he wont know you are locking him up most of the time.

[jojo]

If you look closely at the picture, the repeater is displaying

 

*********

FF P 010

 

or something like that...

So it's only the green radio on the bottom line.

 

[myHelljumper]

It is bugged, don't know what to described more.

 

The bug was on the JF-17 side, it's radar signal strength parameter was too high.

[aw33com]

When the last missile is the Magic, at least 50% of the time I can not fire it.

Is it me doing something wrong or it's a bug? It has never behaved like that before.

 

Also, the radar being able to keep lock targets through mountains, is that normal?

[jopasaps]

yes, i have the same problem. And i can´t enter correctly numbers in the align system.

[tuflus]

It seems like the TACAN morse code sound plays even if the equipment is set to off. It's really a minor bug, but slightly annoying if you like to set the volumes during preflight and then forget about them.

[tuflus]

I have noticed quite a few times that the relative velocity indication in both HUD and VTH is wrong. It's most obvious when flying formation with another aircraft while the radar displays something like "-100VR"

[tuflus]

Today, while flying mission 10 of the campaign, I tried to enter the waypoint altitudes manually during startup. One of the waypoints required 26000 feet, but if I tried to input that number into the PCN it didn't take. I tried with 25000 and it went throught alright. I then went back to try some other values, even 25001 is rejected, as is the equivalent altitude in meters. So it seems 25000 feet is a hard maximum for PCN altitude inputs. Is this correct?

[jojo]

Today, while flying mission 10 of the campaign, I tried to enter the waypoint altitudes manually during startup. One of the waypoints required 26000 feet, but if I tried to input that number into the PCN it didn't take. I tried with 25000 and it went throught alright. I then went back to try some other values, even 25001 is rejected, as is the equivalent altitude in meters. So it seems 25000 feet is a hard maximum for PCN altitude inputs. Is this correct?

 

Yes, waypoint altitude are supposed to be topographical altitude, not your flight plan altitude. You have to handle that yourself.

In western Europe, no topographical altitude is above 25 000ft.

I wonder though if Indian Mirage 2000H got a custom INS with higher limit ? :D