[OLD BUG REPORTS] Cleaning and Organization of old posts

When trying to push the ignition switch in the NTTR training mission ("Startup from cold and dark") nothing happens: no sound (I would expect something similar to a clicking sound), no animation (button does not go down) and engine does not start either.

(Of course Ignition switch orange cover is open; Using Cheat -> Start Procedure starts the engine properly)

2.5.6 known bugs lists for Bf-109: engine start doesn't work - maybe there is a similar issue with the M-2000C?

Any ideas?

I often bump the throttle which places it forward of the idle-cutoff detent thereby making a successful start impossible. Ensuring the throttle is at idle and clicking the idle-cutoff release button prior to start resolves it. That may be stating the obvious and not a solution to your bug and if so, sorry.

Your 3rd ballpoint references a current non-functional feature per the manual. All that is required to display a synthetic runway is that the runway lat/long be properly set up in the editor as the destination waypoint. PCA App Mode and the proper ILS frequency complete the process. Since we cannot currently place a synthetic runway ourselves with the PCN, it probably makes no difference whether or not there is a CP/PD entry.

Me too.

With best regards.

The radar elevation display is not corresponding to the antenna real elevation most of the time, ou have to reset it with the target unlock button.

Also for the air-to-ground modes, it seems that the radar modes are not reset correctly after CNM neutral. For instance going to CAS and using CNM forward after using guns in air-to-air and a boresight radar mode will result in the HUD (and I guess radar) not in a2g but still a2a.

Thanks Smokin Hole!

There is no bug: I had the volume turned down so I could'nt hear the engine and must have been too impatient to wait for the engine to spool up :-)

But it would be great if the ignition switch would be animated to get a visual feedback when the button is pressed...thanks!

With last two patches there is pilot visor bug - visor animation slides down and visor overlay disappears.

Mirage Pilot Body initial state doesn't correspond with game pilot body option. When enabled, Mirage is always without pilot body and you need to enable it by key.

This problem definitely exists in 2.5.5 as well, with the added complication of it seeming to be unable to lock scanned targets until within 20nm as often as not.

do you mean, you have to use the key binding to add the pilot in game ?

Sorry not sure what you mean

Yes, with the mirage, even with the « show pilot when available » checkbox enabled in the options, it doesn’t appears at the mission start and must be displayed by the key binding. Other planes start with the pilot shown at the start.

With last two patches there is pilot visor bug - visor animation slides down and visor overlay disappears.

I have noticed the same bug. Quite annoying because I like to use the sun visor for immersion.

This is probably why when I sometimes lose lock on someone with in 20nm it all of a sudden can't be reacquired... I think my scan is centered but it really isn't? Will have to try that unlock magic button

This is probably why when I sometimes lose lock on someone with in 20nm it all of a sudden can't be reacquired... I think my scan is centered but it really isn't? Will have to try that unlock magic button

It's 'target unlock' to break radar lock on target, not 'magic unlock' (which also exist to break Magic Lock)

ever since the update to the Mirage,,, has it been a year? 6 months? anyways, it has never been as easy as it was... I have beaten my brains out trying to fly and work it like before the last big shakeup with new cockpit and such. I think something is screwy, but I can't be sure if it my body or the plane. I know for sure it worked a lot easier a while back...

I've been flying this a bit since 2.5.6 and I noticed that my log book total hours were way higher than expected since I reinstalled a few months back. I've flown the Mirage probably about 40-50 minutes since I reinstalled and the log book indicates 48+ hours. I looked at other DCS modules and their values are were I would expect. Look I'm all for rounding up, but this seems a bit excessive.

B

Your 3rd ballpoint references a current non-functional feature per the manual. All that is required to display a synthetic runway is that the runway lat/long be properly set up in the editor as the destination waypoint. PCA App Mode and the proper ILS frequency complete the process. Since we cannot currently place a synthetic runway ourselves with the PCN, it probably makes no difference whether or not there is a CP/PD entry.

Also apparently the glideslope an heading are inversely placed in the INS even when properly setup. In the ILS tut, when I'm checking airfield waypt in the tutorial, it shows 3 and 310. Presumably 3 is the glideslope (as per aerodrome chart also) and 310 is the heading (?), but when modifying, it treats the left value as heading and right value as glideslope (left value allows for 3.1 digits, right value 2.1).

Like the synthetic runway, the localiser should be tied to the landing waypoint and use the runway's course. It should not float about the HUD like a wayward Azimuth Steering Line.

Similar Airbus system.

Bug report : https://forums.eagle.ru/showthread.php?p=3183828#post3183828

Hi .

I was taxiing in dubai internationnal airport when the plane jumped and crashed on the ground.

You can see the scene in the track attached.

Regards

Hello,

when i choose the peru skin, the cockpit suit have the sand color.

In the external view the suit is green. I think this is easy to fix.

regards

Josh

This problem definitely exists in 2.5.5 as well, with the added complication of it seeming to be unable to lock scanned targets until within 20nm as often as not.

There is another bug. Use B-scope instead of PPI.

When you are in PPI, you have to place radar cursor on B-scope target's position to be able to lock.

So directly in front it's the same, but when you try to lock off axis, there is a huge difference.

It shouldn't be like that, it's a bug.

ENC button still present in manual 1.1.0 and M02 training missions

The current manual version 1.1.0 still has some references to the "ENC" button at the INS panel (which in the current OpenBeta 2.5.6 isn`t visible any more), e.g. at:

1. pages 160, 161 and 162 (pictures/screenshots)

2. "...If the ENC button on the INS Panel is lit..." at page 96

3. "...The ENC button will blink ..." at page 160

Also there are still references in the training missions "...M02. Introduction to the INS" for both Caucasus and NTTR versions.

Thank you!

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

Hello,

You have lots of "MODS" on your installation, so it's impossible to see your track on a vanilla installation.

So, it should be a reason : try without them, it should solve the problem.