[OLD BUG REPORTS] Cleaning and Organization of old posts

is it fixed in beta only?

is it fixed in beta only?

Changes go to Open Beta first and if there no major bugs, ED push the update to the release branch later.

• Open Beta is on 2.5.5.40647, 05 Dec 2019

• Release is on 2.5.5.39384, 15 Nov 2019

Note: recent "release branch" updates have been once per month.

Release history can be found in this thread :

https://forums.eagle.ru/showthread.php?p=2249076#post2249076

Hi there,

When I lock using SVI, the radar display works well with target clearly locked, all associated tracking information and speed vector, however, I do not have the square in the HUD on the target which make things pretty hard!

Funny thing is that I have the small square on the HUD so that I know where to point my nose...

Do you guys have the same problem ? Has this been reported already ?

I'll explain like this:

1. Using autopilot to steer to heading 000 on HUD (and HSI)
   
2. It stops at HUD heading 006
   
3. HSI Shows 000
   
4. Switching to true heading, HSI now shows 006
   
5. HUD has jumped to 012
   
6. F10 Map showed 007
   

Cold start, hot start, air start, they all show this. Latest Open Beta, and this is the Caucasus Freeflight.

Bah shit. Just remembered I was using sedenion's Indication Fix, and thats the cause.

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

Sorry, nothing to see here.

Any chance a moderator can melt this with his above thread?

No comment from the dev´s ?

Its only me ?

Well, anyway, this was indeed my mistake. I published a corrected version of the Mod with HUD and VTB heading tape correctly aligned according true north.

Good evening! I've got a problem with the open beta version of DCS more precisely with the mirage 2000, I just want to precise to you that I already did a complete reinstallation of DCS, two repair process, and I had the same problem with the steam open beta version.

First, when I turn on the red tactical floodlights, I can't turn it off. Then when I switch the night vision switch on the JVN position, the tactical lights are supposed to become green, in my game, it just turns off every light.

The second problem is the RWR, I only have the superior half working, all of the lower half isn't showing anything. It's like the rwr is divided into two parts, one is showing something, and the others don't work, so when a contact is on the delimitation of the two parts, it is cut.

I had a problem with the nvg too : Even with the nvg installed on the helmet I could not use it, but after a reinstallation of dcs and a repair, I can use it anew!

I recorded the two problems that I have, I think it will be easier to understand! (https://youtu.be/tmgnnU8NOHM)

Thanks and good flights!

[...]

The RWR and red light not switching off problems were fixed in last week's thursday update, check that your DCS version is 2.5.5.40647, you can see it in the bottom right corner of the main menu.

For the NVG switch, it is working as intended AFAIK, where did you see that the lights are supposed to turn green ?

I launch DCS today for the first time for 1 or 2 weeks and I did the update. It resolved all of my problems so that's nice!

The floodlights were still red in the previous version, so a friend told me that those lights are supposed to be green. When I was switching the NVG switch on JNV, all of the cockpit lights were turned off. With this new update, floodlights are green and the RWR problem is fixed.

Ok, problems solved then :).

No I have the same. Pimax 5k+. Basically the left side panel lights only appear in the left eye and vice versa. Ditto the torch only seems to appear in one eye depending on the side I'm looking at.

What do you mean by "Self Programmed Landing Point"? It's not going to be displayed unless the landing runway has an ILS and the active waypoint is a database airfield.

I think he mean, by setting the last waypoint to "landing" in the Mission Editor... This is indeed an old request, which I join, with some others old requests.

Fact is that the ILS and TACAN are not (and worse: cannot be) preconfigured for mission start. An automatic ILS and TACAN preset according the "landing" waypoint configured in the Mission Editor would be a nice feature.

No thats not what i mean....

when i set a flightpath in mission edititor with a landingpoint at an airfield with ils i can see the synthetic runway in the hud .

but when i make a flightpath while in flight by setting up the waypoints "in flight" manualy the synthetic runway never appears.

Ok, my mistake...

As per thread title, Landing Lights OFF is correctly mapped in my config (LAlt-LCtrl+T) and gets triggered when I am in config, but in cockpit it just does nothing, both on the switch and on the light itself.

No thats not what i mean....

 

 

when i set a flightpath in mission edititor with a landingpoint at an airfield with ils i can see the synthetic runway in the hud .

 

 

but when i make a flightpath while in flight by setting up the waypoints "in flight" manualy the synthetic runway never appears.

If I'm not mistaken, this has never worked, and I'm not sure if it's supposed to or not.

If I'm not mistaken, this has never worked, and I'm not sure if it's supposed to or not.

Yes, it never did work as intended.

Yes, you should be able to get synthetic runway on airport configured in PCN in flight, provided there is an ILS.

Yes it never worked ! But Razbam promised short after release that they are working on it !

How many years are now gone ?

+1

But Razbam promised short after release that they are working on it !

Source please ?

I don't remember saying that they promised making it available short after release.

For me it's fixed in the latest OB.

Source please ?

 

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