wernst

. . . still "muh non-calibrated monitor" whining? ED, forget about lighting impovements which have been announced today. ("This will be most evident at night when viewing the cockpits") Not needed, we'll calibrate our monitors and fly happily ever after. Seriously, I’m glad ED comes back to the lighting issues and I’m looking forward to see the results.

Just a word to your detailed „calibrate your monitor right“ story. I have an EIZO monitor, neither a professional one nor a poor man’s version. I always use the predefined RGB settings. Before I started „muh nighthog whining“ here, I have of course tried to play with all non RGB monitor settings available on my monitor. Cranking up and playing with brightness, contrast or gamma didn’t really help: Cockpit displays and outside sceneries were becoming horribly outshined at best, unreadable mostly. Which is logical, as the main problem in my view is the dynamic range of the monitor. (You - and ED devs - obviously have a good one in relation to dynamic range) Let’s assume I didn’t calibration right. But with this „badly calibrated monitor“ I was able to fly the Hog without issues at night, for years – but before the pit upgrade! And with this badly calibrated monitor I still can fly all of my other 11 DCS modules, comfortably at night and day. No monitor calibration needed, that is (was) the charme of ED's 2.5 imaging engine. I hadn’t have any monitor related visualization problems with any of my modules - until the recent Hog update. I think a software modification (as ED already announced) will make any monitor calibrating obsolete. Recalibrating the monitor each time after a mission or module change can’t be a solution. From a muh whining Hog pilot in his freshly serviced A-10C on night mission.

. . . and controls. You don't need any flood light at all to read displays and instruments. They all are backlighted - as well in the old as in the new pit. But what about buttons, switches and turning knobs? How to you find them safely in dark without pawing the panel in order to find the right control? How can you find e.g. the MASTER ARM SW ? Fumbling around? With flood light as it was before one could adjust the flood light level to as little as possible but as much as necessary. I assume that any real (mil or civ) pilot is preferring this solution.

I hadn't any issues with the Hog before the upgrade. All other complex (PFM) modules like Hornet, Viper etc. are still running smoothly and well.

impressive texture specs . . . . . . but stuttering . . . nightly cockpit almost not usable because controls are barely visible spoiling the fun of it.

+1 I'm afraid it will stop working because future updates will probably overwrite "SCRIPTS"

works fine, thanks. That's the one I was looking for after the recent pit update. With the Hog I'm doing night missions with ILS appr in IFR, "nice" textures aren't important here anyway.

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

Don’t get me wrong. Yes, I’m more than sure that ED will soon come up with improvements for the recent "beta" cockpit update. My actual replies are meant for posts here like „. . .buy better hardware . . .“ or „I have no issues because I own an epic monitor“. I’m almost sure that the actual A-10C cockpit issues are not related to poor hardware.

I don't have an "epic" monitor, only a "poor man's" display (EIZO FS2333) yes, gamma to max. = 3.5 -> https://forums.eagle.ru/showthread.php?t=259348 (everything becomes even worse) Not only a few hog pilots have reported issues here, I suppose they do not own an "epic" monitor. Or professional displays as the ED devs have been using for testing the new cockpit update. Should we all throw our displays in the corner and buy an ultimate monitor just to enjoy the cosmetic cockpit update without issues? Issues, which didn't exist before. Better not always becomes best.

Hi ac5, you said earlier: "Only issue is far too dark at dusk / night." High fps but too dark? You probably have already "better hardware" and sure did apply your own "my settings", isn't it? Still some issues? Why? Hmm . . . My plan for 2020: I'll have to buy "better hardware" and will apply "ac5 settings" to run the new cockpit update without issues. But what if . . .? Happy New Year to all Hog and DCS pilots.

Please learn, that obviously all issues with the new cockpit update reported here are not affecting everyone equally. It's maybe related to the different types of hardware they are using. Some users have difficulties with the nightly cockpit while others say: „I’m fine with it“. They might have the same professional type of monitor as the ED devs are using. I only have a semi professional EIZO monitor, obviously a poor man’s monitor. It’s the same with the performance issues. Some users (as you) report „no performance loss“ while not a few here are mentioning noticeable loss of performance. What do you suggest should be done? Listen to the lucky card users or listen to the people who had no problems with the old cockpit - until now?

I have (again) stuttering, an issue which I hadn’t noticed since long and which I have almost forgotten. Since quite some time all modules are more or less stutter free. Fine, but with the new cockpit old problems are here again. Besides performance, the new cockpit is almost not usable at night time. What use is the nice look and appearance of the new cockpit if I can’t see the essential controls at night anymore? Even with floodlight pushed to max. It has been said that the old floodlight was incorrect. But what use is it having a correct floodlight which makes the Hog not flyable at night? Yes, ED please provide an option to roll back the new cockpit to the old one or give us the choice between new and old pit. Don’t get me wrong. I highly appreciate ED’s efforts to continously improving all modules. But it shouldn’t be done at the cost of playability. Function comes before beauty.

Good point. It was also my impression that ED devs are not only using an internal build, but using highly professional monitors where everything shines brightly. It‘s much different to my poor man’s (EIZO) monitor with less dynamic range. And, yes, I don’t have just difficulties with the cockpit readability at nigt but often at daylight too - in general. I can tweak settings of my monitor to some extend but the result then is often unsatisfactory, to say the least. With high gamma, high contrast and brightness the textures are blown out and become blurry and garishly. They do not look nice anymore, even developed with great effort to provide the best.

o.k. Only one last question: How can I roll back my actual A-10C module to the version with the "incorrect" flood light? Just the module only, not world?

Good to hear that there is WIP for the nightly lighting issue with the new cockpit. But there is still one question left to me: Why doesn't the flood light hit the front panel anymore? Is there any reason to cut the flood light beam which illuminates the front panel? The A-10C has two flood lights located on either side of the cockpit. They both are directed to the front panel mainly and provide some light to the side panels. Here is what the DCS A-10C user manual says: 10. Floodlight Dial. Labeled FLOOD, this dial controls thebrightness of the two flood lights located on either side of the cockpit. The dial can be set from OFF (no lighting) to BRT (full brightness). The dial canbe moved past BRT to the TSTORM setting which will shade all flood lights. The images below show that the flood light is functional in the old cockpit but not in the new cockpit anymore. Why? With the flood light control I can easily adjust the level of brightness of this panel and the side panels, suitable to the level of brightness I need - with my monitor. It would solve the problem that different types of user monitors provide different level of acceptable brightness. Leaving the flood light as it was before would be fine to me. It could solve the issues some people (and myself) have with the new cockpit. Better isn't always best.

no mods. I'm using a monitor only. Meanwhile BIGNEW posted that the floodlight of new cockpit doesn't hit the front panel anymore but the side panels only. I can confirm, the floodlight knob controls the brightness of the side panels only. With the old cockpit the floodlight illuminates the front AND side panels, as bright as needed. My question is: Why has the front panel with knobs, switches and pushbuttons been left in the dark?

?? I have started this (my) thread here with screenshots, just 10 steps back, or here: https://forums.eagle.ru/showthread.php?t=259348

What about the knobs, switches and pushbuttons of the front panel? Are they left in the dark?

Hmm, no flood light shining onto the panel? Then it might be the reason of the dark cockpit. But then, what's the point of having a flood light? Where should it shine? What is it for? Without floodlight I still can read the instruments but I can't see the switches, knobs and pushbuttons of the front panel anymore.

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

There is some discussion here about the A-10C cockpit visualization at night. Some people say „I’m fine as it is“ others have issues. I did a comparison between 2 nightly A-10C cockpits: old version vs. new one. (scenery was CAU, Batumi RWY at 23h / 11 p.m.) Left image is a screenshot taken from an old stable version (2.5.3.24984) and the right image was taken from the recent open beta (2.5.5.41372) The following settings were equally applied to both shots: cockpit flood light: to max gamma: max = 3.5 brightness: 50% on my EIZO monitor (FS2333) I hope this comparison helps to understand the issues some users have. A professionell monitor will probably have more possibilities to adjust the brightness levels, but I'm not sure it's hardware only. One (simple) reason for the darker cockpit might be the fact, that the flood light setting in the new cockpit seems to have almost no effect.

My only comment is: Why could I see all controls of the former night cockpit pretty well on my good old non calibrated screen? Why did I see all controls of the former night cockpit pretty well even with B/C "off by ALOT"? My conclusion: Nothing has changed here with my hardware and settings. Only the cockpit design has been updated by software. And, I'm obviously not the only one who has issues with the latest A-10C update. I doesn't help that somebody is reporting "I'm fine with it" while others have bad cards. Somebody might own a highly professional monitor which is needed to enjoy the new cockpit at night. I only have an EIZO FS2333 which is obviously not suited for some DCS updates. I'm working on rolling back the new cockpit update. This update was well meant but not well done. It sure looks nice, but is not perfect in every sense, e.g. functionality.

Your image itself is an example. Without tweaking my monitor parameters I can‘t see any knobs or buttons in this image, but MFCD characters and all other green displays are too bright. As it is with the new cockpit. Without tweaking gammas and brightness on my monitor and in DCS options I can‘t see any knobs and buttons as needed for safe control. After pushing gammas and brightness to extremes knobs and buttons become somehow visible, but all green displays and characters are then outshined, too bright, almost not readable anymore. Please learn: I have tested and compared an "old" A-10C night cockpit from a former stable version with the new one. With the "old" A-10C night cockpit evrything is displayed right as I am used to it. It's also not perfect but at least usable.

With update 2.5.5.41256 the „new high quality A-10Ccockpit" was introduced. The version before was DCS 2.5.5.40647 with the unmodified A-10C cockpit. How can I roll back from latest update to this .40647 update, the one with the "old" but functional cockpit? It would solve (for me) all issues I have experienced so far with the new cockpit until ED releases an update for the "new cockpit update".