312_JS

Sorry to resurrect this thread, but it's infuriating that something this clear and easy to implement is overlooked just because @Yo-Yo doesn't understand the problem. Perhaps it's a language barrier. Sorry to put it this way, but @Yo-Yo just refuses to understand that trimming should only move your trim tabs, regardless of your curvature settings. His solution of not using curves and using 50% saturation instead is completely wrong, as flying a Spitfire with only half the maximum elevator deflection range obviously puts you in a huge disadvantage. Like @ViFF mentioned above: If you make curvature to pitch, it will also effect the trim tab, requiring much more nose down trim input, and the trim indicator will show incorrect actual physical trim of the elevator. That is definitely not good and obviously incorrect simulation of trim tab. The trim tab should have nothing to do with the curvature.

5 years later, still no F1M..

Another interesting thing is that it only happens in a cockpit view. At least to me.

I also found out that if I use external post process sharpening (using ReShade) set to a too high a setting (the ingame sharpening is also a post process sharpening), the flickering starts again.

I have just found the issue. Setting the ingame Sharpening over 0.91 causes the flickering for me. Setting it to anything from 0 to 0.91 is fine. The Low / Medium / High presets don't touch the previous Sharpening setting, so it was on 1 even when I changed the preset to Low while testing.

I believe it does have something to do with the fog because it started with the patch which introduced it and it flickers between more and less saturated image, as if the fog is turning on an off.

Here's a video. (used a phone camera because it shows up much better than a straight recording for some reason) And a DCS.log dcs.log

That was the first thing I tried before uninstalling it. Made no difference. Flickering still there after today's update. Attaching a track. flickering.trk

Any update, please?

No, 2D only.

Mine was already off. Still flickers.

I do, but uninstalling Reshade didn't solve the issue.

Same here. Extremely annoying. Somebody at ED Discord said it has to do with fog being set to low altitude and that it's being looked at. EDIT: Added a Discord screenshot.

Hello @Bailey, parts of the F1EE lua stopped working since the recent large F1 patch. For example the functions in the DCS ID 80xx range - exporting speed, waypoint distance and bearing, RPM, etc. They don't even show up in the DCS Comms list in the Stream Deck app. Any idea what might have gone wrong? The basic DCS IDs with which these functions work with seem to export as expected.

I have the same issue in 2D. I can have almost everything maxed out and have around 100 FPS unless I am on deck. Then I get 27 FPS. Found out it's the Terrain Texture set to HIGH that's causing it for me. When I set it to LOW, with otherwise the same settings, I'm at 90 FPS on deck.