norman99

Interestingly, when you export MFS to external screens, they be come substantially more readable. No more constant fiddling with brightness/contrast/auto or manual gain etc. It just works perfectly 95% of the time. Because of this, I’ve come to the conclusion that the raw MFD/FLIR displays are actually recreated rather realistically, but once they are placed into the 3D environment, and all the environmental lighting effects/shaders are applied on top of the raw MFD/FLIR image, readability drops considerably. I don’t have my export displays currently available to provide an example, but I’m sure someone else could create an example.

Disregard, I’ve found an explanation. It was due a texture mod applied to the carrier.

Well spotted. Change your ATT switch (second row below the UFC) from STBY to AUTO. That should fix it for you.

Thanks Minsky, I appreciate the explanation, I had a feeing this was going to be the answer. Unfortunately, a selectable livery means these textures won't be available on multiplayer servers. As I'm happy with the look of them during the day, I guess I'll just have to enable/disable the textures based on my planned recovery time each mission.

I did a clean & repair of my DCS installation, and it fixed the problem. I guess somewhere along the line, some of the data in the .lua files that control MFD/HUD rendering had been changed.

Introduced in May, but basically broken on arrival. (Obviously no more than 5 min of testing was completed before release.) 7 months later, not even a mention of a fix in the works. And the community managers wonder why, occasionally, customers appear to loose patience with ED....

Thanks for your work @Minsky, I too suffer from struggling to see the deck in certain scenarios. Unfortunately, it seems your mod also affects the deck lighting at night. It drastically lowers the brightness/intensity, to the point where night landings become impossible, as the deck is only visible ay 0.1nm. One note though, I'm installing the mod the same way as Marlan is, as a mod in the root DCS folder (so I can use it during multiplayer, regardless of the server livery), so whether this is the cause, I'm not sure. Deck lighting with this mod: Deck lighting without this mod (default):

The large AUTOPILOT caution on the left DDI means: “Autopilot did not engage or A/P disengaged after it was selected for any reason except pilot actuation of the paddle switch. The caution is re-moved after 10 seconds or when the paddle switch is actuated. The auto-pilot can be commanded out of the BALT or RALT hold mode by CSS.” In DCS, this is almost always due to a control stick input being applied whilst simultaneously trying to engage the autopilot. Creating or slightly enlarging a null zone at the centre of both pitch and roll axis solves this problem.

I get most of these with a cold start too. The simple answer is that the BIT system is still substantially incomplete. Given these do not affect any operational capability, I understand why BIT completion is probably a very low priority. (Personally, a doubt it’ll ever be fully implemented). Which is a shame, as it drives the OCD in me crazy.

I guess the lack of responses means it’s only me experiencing this issue. That should be a good thing, as it means hopefully I can fix it. Does anyone have any suggestions where I should start looking?

Anyone else having this problem? I literally can’t see the landing area deck lights till 0.1nm. I guess ACLS is barely still usable (when it works), but any manual landing is impossible. No shaders or changes to DCS lighting made, so it's all default settings. P.S. The standard ACLS "---: (EGIW)" grade too....

Still broken when other aircraft, either AI or multiplayer, are present and inbound to the carrier. At the moment, ACLS is only useful for training in solo missions, nothing more. Unfortunately it seems this is so far down ED's priority list, I wouldn't hold your breath for a fix any time soon. Honestly, it probably shouldn't have made it to release with such an obvious bug present, but that's just my 2 cents.

Anyone else having this problem? I literally cant see the landing area deck lights till 0.1nm. I guess ACLS is barely still usable (when it works), but any manual landing is impossible. No shaders or changes to DCS lighting made, so it's all default settings. P.S. The standard ACLS "---: (EGIW)" grade too....

Or take a couple LGBs and kill them F-15E style! https://theaviationgeekclub.com/that-time-an-f-15e-shot-down-an-iraqi-mi-24-attack-helicopter-with-a-2000lb-laser-guided-bomb/ Though to be fair, 2000lbs is completely overkill haha.

Basically everything in this package! https://www.turbosquid.com/3d-models/sa-3-goa-battalion-3ds/684172

@BIGNEWY Despite merging of similar posts over the last 18 months, it seems little progress has been made on fixing the issue. Any chance we could see some improvements soon?

I would have thought including a somewhat realistic, individual unit based "max detection range", especially for AI, would be a core fundamental concept in any modern warfare simulator? Even if these aren't dynamic and/or situation dependant, something as simple as "F/A-18 Max Detection Range=80nm" etc, would prevent the ridiculous examples above.

Well, it seems my suspicions were right. Using this app simultaneously with my WinWing MIP, disables the WinWing UFC/HUD panels completely, both switches and displays. Obviously this is a deal breaker for me, so until there's a way to make them compatible, I'll have to avoid using the UFC Android app entirely. It's such a shame, as my phone would have made the perfect IFEI panel for use with the rest of the WinWing hardware.

Looks similar to this issue, reported 18 months ago….

Yep, priority seems reversed. Currently, it will XMIT and therefore turn off the radar, even if you have a contact designated L&S, or even more frustratingly, a missile in the air. I thought radar priority was designed to prevent this from happening. Seems we have jammer priority implemented instead.

Thanks for the explanation, I thought it would be something like this. There’s no rush to make any official changes to this campaign, I’m more than happy to make some changes to my version and see what results I get.

A question about the Hornet Crisis in the PG campaign. I noticed I was always assigned loadouts with 3 external tanks, regardless of how short the mission flightplan was. So, I went looking in the Init>db_loadout.lua, and found ALOT of loadouts have been commented out, leaving only 3 tank loadouts active and available for DCE. Was this done for a reason? Can I simply remove the comment marks to enable all the other loadouts, or will this break the campaign in some way?

@[SWISS]Maverick A clean & repair of DCS fixed it for me. I guess there are a number of lua’s that control MFD/HUD/HMD rendering, and some values must have changed.

2 kts from starboard.

Also, before I purchase, can anyone confirm this app is compatible with SimAppPro from WinWing?