NightMan

I already sent literally half a dozen of automatic reports after each time I experience this crash.

I would prefer everything off as it was before. I used to enjoy going through all the steps. How about introducing an option in the settings allowing the user to choose wether to have those switches on or off by default when jumping into the plane?

The problem is the new "Historical list of units" button. I had it checked somehow, altough I wasn't aware of its introduction. What it does is limit the planes to the ones available in the year defined in "Date, time and weather" settings. No need to repair; "If it ain't broken, don't try to fix it.". Case closed.

Hi! I have FC3 and I use several of the planes frequently. However, today I noticed that the A-10A is missing. Where did the plane go? Is this a temporary bug? Is this a definitive change? Thank you

I just noticed what I think is the same problem reported; The HOTAS CMD Left/Right, which used to change the program in the CMD, now starts dispensing flares and chaffs like crazy. Is this a bug?

Gentlemen; The Autopilot mode switch is not clickable, as well as several switches nearby. Thank you NightMan

Ok. Thanks. Let's then wait a few months until they correct it.

Gentlemen; Since the previous update that the behaviour of the navigation lights in the F-15C has changed. Turning the navigation lights appears to also control the strobe and vice-versa. It’s really confusing. I would like to know how do they work now. Thank you NightMan

Gentlemen; This last update appears to have broken several things in the F-15C, more precisely the lighting and definition of the HUD, VSD, TEWS and MPCD. I see no point in trying to explain the problem, as the pictures are more than self-explanatory. With the HUD there is the possibility to increase or decrease the brightness, but with the other systems there is no such thing. This problem is extremely detrimental because it makes it completely impossible to read anything on the affected systems. Thank you NightMan

Gentlemen; This last update appears to have broken the Ka-50 combat system. When a target is locked the reticle should drop and the pilot would only need to point the nose sideways to place the reticle over the target. Now, the reticle doesn’t drop, even if the Shkval racks are pointing downwards. This forces the pilot to drop the nose, which always affects the stability of the helicopter, even if it is hovering on autopilot. Thank you

Gentlemen; This last update appears to have broken the Ka-50 combat system. When a target is locked the reticle should drop and the pilot would only need to point the nose sideways to place the reticle over the target. Now, the reticle doesn’t drop, even if the Shkval racks are pointing downwards. This forces the pilot to drop the nose, which always affects the stability of the helicopter, even if it is hovering on autopilot. Thank you

Gentlemen; Since the previous update that the behaviour of the navigation lights in the F-15C has changed. Turning the navigation lights appears to also control the strobe and vice-versa. It’s really confusing. I would like to know how do they work now. Thank you NightMan

Gentlemen; This last update appears to have broken several things in the F-15C, more precisely the lighting and definition of the HUD, VSD, TEWS and MPCD. I see no point in trying to explain the problem, as the pictures are more than self-explanatory. With the HUD there is the possibility to increase or decrease the brightness, but with the other systems there is no such thing. This problem is extremely detrimental because it makes it completely impossible to read anything on the affected systems. Thank you NightMan

Gentlemen; This last update appears to have broken the Ka-50 combat system. When a target is locked the reticle should drop and the pilot would only need to point the nose sideways to place the reticle over the target. Now, the reticle doesn’t drop, even if the Shkval racks are pointing downwards. This forces the pilot to drop the nose, which always affects the stability of the helicopter, even if it is hovering on autopilot. Thank you

Gentlemen; In prior versions of DCS, when the user selected a vehicle (air/ground) on the map (F10) that vehicle remained selected, even after the user changed view into the cockpit and back onto the map. This was extremely helpful because it allowed the user to track a vehicle without having to look for it and select it each time he wanted to see it. That also allowed keeping track of a vehicle in cluttered areas. With this last update that feature was broken. Now, the user has to look for the vehicle he wants to track and select it each time he looks at the map. In intense situations this is a huge problem. Thank you NightMan

Hi! I had already seen your patches, but I didn't see anything specific to the problems I was experiencing. So I chose to edit the missions (6 and 7 for now) and changed the ROE of the Moskva from Weapon Free to Return Fire. That did the job. However, I downloaded your patch and I will take a look at it. Thank you very much. Best regards

Hi! Yesterday I tried 4 times to complete the 6th mission (Two If By Sea) of the “Su-33 – Sea Dragon” campaign. In fact, I was able to destroy the ships and a few planes each of the 4 times I tried, but while I was returning to the carrier, I must have gotten impatient, and to finish as fast as possible I set the autopilot and accelerated time. Maybe because due to accelerating time, each time I did that, the game crashed. But I digress. This is not what I would like to report – we’ve become used to these crashes. Today I was planning to repeat the mission without accelerating time. However, when I started the game, I noticed there was an update. I allowed the update. When I tried the mission again I noticed that the AIs of our own ships had gotten too intelligent and started firing missiles (SS-N-12 Sandbox) at the coastal ships and eventually sunk them both. I took off and flew for a while, but before I could even get close to the ships the mission was over and there was nothing for us to do. Do you guys have a replacement for the affected campaigns/missions? I understand it is difficult and even impossible to test every mission after each update and even more difficult to predict everything that may go wrong, but these latest updates have been ruining the experience in the campaigns. Thank you NightMan

Interesting video describing the state of the art regarding DCS World

Lights/indicators at the "Targeting mode control panel" are not working properly. The lights/indicators at the "Targeting mode control panel" are not working properly. During the day these lights can barely be seen and appear lit when they are off and appear off when they are lit. So, they are showing the opposite state they are really in, if they can be seen at all. During the night they are not visible at all, which is even worse.

Landing gear indicators are not visible at night I understand ED is working on a new cockpit for the Kamov. I would like to call your attention to the fact that some lights in the cockpit are not visible at night. An example are the landing gear indicators. When the landing gear is retracted, the red lights are not seen.

DCS World is scoring all vehicles as just vehicles, regardless of their category or type. For example: a Tunguska or a Chaparral, when destroyed, are scored as "Vehicles" and not as "Air Defenses" as they should be and used to be.

+1

+1

But we are not getting younger, and by the time the full list of RWR symbols is published in the manual we will be dead, so, why don't you just tell us what the file is. The manual that comes with version 2.5.3 is still from 2013; ED clearly is not kean on documentating, or they are simply lazy or maybe sloppy.

This is just a huge rip-off. If a customer pays for a product, which in this case are the modules, then he has the right to use it whenever and wherever he wants. This is illegal according to E.U. laws.