Jascha

I also have a similar issue. I've recently reinstalled the OS and DCS, so I'm not sure what is to blame here - if it's the patch or something on my side. Settings are maxed out. Clouds on ultra, MSAA x4, no DLSS on these screens: Mission is quick mission F-15E ramp start on Nevada (I edited it so it starts on the runway). No idea if preset or time of day play a role here, but I assume some presets and conditions can make it more visible. Also, did clouds look so bad (pixelated) in mirrors before as well?

Full fidelity Su-25 would be nice though.

Yeah, if 1000 ft or more the numbers for radar altitude on HUD repeater are messed up (they overlap).

I have just noticed it while checking Normandy 2.0 (as I mainly use F11 free camera for that) - it would be way better if the airfields were cycled alphabetically. Right now the order is hard to figure out (seems random). Moreover, is not possible to cycle back, in case I press F11 one time too many. I found a tip that I can also use F10 map to focus on specific airfield. Still, if think it would be nice to have F11 views sorted by airfield name.

That's the key, I guess.

BTW, regarding this mystery why the fix posted above works for some people immediately and others need to try it like 2-3 times, maybe it's important to deselect all Normandy items from the Steam DLC list. So not only Normandy 1944 but Normandy 2.0 and Normandy 2.0 Upgrade as well. That's what I did.

Holy smokes! This actually worked! Thank you! Now I feel bad, because I have accidentally purchased the wrong upgrade (the one for N1 & The Channel owners, and I only had the second one). I'd like to return it and purchase the correct one, but won't it mess up my licenses? Has anyone tried that? I did it only once and it worked.

Lock the doors.

@ThorBrasil Thanks for the quotes.

That's rather disappointing. I think it's a good opportunity to fix the mess caused by weird decision to have two separate maps for (more or less) the same thing (and same period of time). Incorporate the Channel map area into Normandy 2.0 map (as high detailed area that is currently missing). Make the purchase attractive by discounting it to the Channel Map owners (also after the initial special offer there should be *some* discount available). Discontinue sales of the Channel Map. The only difference in comparison to Normandy 1944 map should be - the Channel map stays available to people who buy it before pulling it from store. That's how I see it.

I applaud the decision to introduce discount for The Channel Map owners as well. My questions: - whats the size of this map (on disk)? - the high detail area has rather odd shape - is the part with Dover, Calais and Dunkirk planned to be updated to high detail later as well?

I have provided a video evidence exactly for the scenario you mentioned. Or do you mean by using TGP without markpoints? I works too. Maybe you're not using it correctly?

Weird. I thought that maybe it worked for me because I didn't have Mavericks as my load-out. But I tested it now with D and H variants and it works as well (PRE mode). Maybe the issue here is cold start? Since you mentioned that you had to boresight the missiles? I'd check if this issue is still there when starting a mission airborne.

JDAMs are still dead-on accurate for me. After creating markpoints and setting them as steerpoints, on-board sensors are not slaved to their location. You have to use CZ function (once). If you don't, markpoint (set as current steerpoint) won't act as SPI and therefore JDAMs will miss. I suspect that's causing the issue. I have recorded my test:

I'd try pressing TMS DOWN before you press SP on MFD. TGP must be SOI of course. EDIT: I just checked and SP function works for me as usual. And tbh I don't understand how TGP can slew to a blank steerpoint as you claim (since such steerpoint has no coordinates). One press enters SP mode with TGP in non-ground stabilized mode, facing forward and slightly below HUD FOV. Second press slaves TGP back to steerpoint.

Got it. I misunderstood what is the main issue here. I was referring to some posts above that focus on the accuracy of CCRP itself.

I think some people have a misconception how accurate unguided bombs rally are (or can be). Mk-82 is not a precision-guided munition. There is a reason why the IAMs and LGBs have been developed. Expecting a pinpoint accuracy with a dumb bomb from 14k doesn't sound smart* to me. * Sorry, I couldn't help myself.

I see a Su-25 quick start mission for Syria that resembles your description. It's not the one? Syria - Su-25 - A-G Quick Mission.miz

Is there a way to tweak how long destroyed targets are burning (vehicles and static objects)?

Oh, thanks. I didn't know that. But that doesn't help me as my current tablet case supports landscape mode only. Plus it fits nicely just below the screen that way. My request applies to landscape mode then. ICP panel is too big anyway and for sure there is a place for DED in this orientation as well. I was also hoping maybe split screen on tablet will be a solution, but I think it's impossible to have the same app in both "windows".

Just a friendly suggestion. For F-16C it would be great to combine ICP page with DED. If DED is right on top it will be more convenient to use. Can it be done? BTW any update on these suggestions? 1. This is something I would also like to add, a question of finding some good solution not to change half of the application code 2. I even worked on it, the problem is that each panel and even each OSB button uses a lot of different data (it is not standardized in any way), it would require a huge amount of data checking

Yeah, the small gray slider. I meant it, as a part of Warthog Throttle (device). From Chuck's DCS F-16C guide:

I know it's not the answer to your question, but maybe mapping it as axis to the Warthog Throttle slider is a better idea? It's most common solution, as Warthog Throttle has no rotating knob.

Just use EHSI in NAV mode (or HUD obviously). Why would the visual representation on HSD matter? SPI is a different story, but that has been cleared above.

You mean reducing the zoom range? I cannot find such option. Or do I have to edit some .lua file? Here is the issue with the slider: It's obviously hardware related, but I wonder if it's possible to solve it through settings. Dead-zone would have to be fluid (apply to the position where the slider movement stops, but that would be problematic too, as the slider input is still being registered even after slider is not being moved anymore).