Avio

I ran the mission starting hot from runway and all default cockpit settings. I could be that the radar image was captured from too far a distance and full resolution has not been built yet.

Thanks for that. I quoted the above from Grim Reaper who posted many clips on the F15E. Will try at higher speed next time.

Is it correct that there is a speed limit (up to 350 knots) when laser designating a target and using the CCRP Auto mode? There were times when the GBU missed when I flew too fast, though there were times when it hit nicely even at speed above 350. Anyone else observed this?

While there are good Youtube tutorials on radar freezing and storing, for practical use, how does that come in being useful? For pop-up attacks, I could have used the radar to mark a point while still far away, dive low, and when at IP, pop up again to re-acquire and CUE the TPOD to the mark point for a more refined aiming and designating prior to dropping bomb on it. All without storing the image.

Is PVU updating needed? I understand with EGI, PVU is not needed. There was an occasion when I CUE the TPOD to look at where the radar was pointing (a small building), but it pointed a distance to the left of the building instead. Is there an inherent inaccuracy, or perhaps PVU is needed?

Can anyone help confirm, is there a bug in the TACAN morse code sound? At times it didn't sound, even though the volume was tuned up, though there were times I thought I heard it (together with that from the ILS).

Belated thank you, folks. Glad to see the eagle this well modelled. About the max G allowable as shown on the HUD, it always show as 9G. Shouldn't it shows a smaller G number if the plane is loaded up with lots of ordnance? That way pilots would know how much G to pull without exceeding the limit. As for the Flight Control Caution lighting up, I think it could be because I was in Autopilot and had proceeded to move the stick without first turning off the AP. Kind of like the warning one gets in the A10C.

Most videos of the real F15E show them deploying the speed brake during the flare, instead of just after touch-down. Which is better? Opening the brake during flare does tend to distract and even affect the flaring effort somewhat.

I noticed when banking the plane, both rudders seem to flip the wrong way. For instance, when banking to left, both rudders flip outward to right instead of left. Given the adverse yaw, shouldn't the rudders flip to left to counteract like in small aircraft?

Was doing a strike mission when half way Caution lit up about problem with Flight Control, but no control issue as detected at first. Sometime later, during a high-G pull-up from a steep dive, the plane started vibrating and control was mushy and a little sluggish. Managed to land back though. Anyone encountered this before? What could have caused those issues? *Edit* -- I did turn on only one bleed air blower (left or right), to bring down the cockpit noise as someone had suggested. Does that matter? Is avionics cooling simulated?

Real sweeet, folks ! Thanks.

Love the starting splash screen of the top-down view of the speeding eagle a lot. Does anyone know where on the drive directory can that picture be found? Thanks.

That's cool ! I was thinking it be great if there is a spot for community to post up their own screenshots for others to ogle at, that would be nice. Sorry, okay so I found that in another post. Nice !

I noticed coming in on short final at 22 AOA or so, the flight path marker gets very likely to disappear below the HUD (flashing) during the flare. Is this normal and correct in the real jet? Also, in the overhead break landing, the manual says on downwind (at 1600 AGL) keep the runway sight picture between the wing tip and outer rack. Isn't that too close? Wouldn't keeping a small gap between wing tip and runway allow for a less stall-prone break turn through base to final? (I mostly keep to 1500 AGL). Found that the jet needs quite a bit of increased power and tight turn on base turn just to keep it a safe margin from stall.

SO bottom-line, is PFM supposedly more accurate / better than AFM ?

But I remember seeing some posts using only 2K monitors. Just haven't figure out what's the secret sauce, for a long while now.

How about sharing on some cool re-paints and/or screenshots of the Eagle here? Would be nice to see them here, and grab some nice skins too !

Understand that the FM is AFM instead of PFM. Does that make much difference in the flight modelling? How good is that at this early launch stage? Also, what are the major features that are still work-in-progress? Always enjoy A2G, been enjoying the A10C (also the F5E), and this eagle seems to bring on the best of that both.

Indeed this one looks real promising, among the fleet of DCS aircraft I've owned over the past 10+ years. Seems to fly real good, though somewhat twitchy in the pitch. Is it so in the real jet? As for the curve setting for the stick, I put in a 25% for pitch for my WH HOTAS. While I'm quite a "purist" too when it comes to simming, I also know it would be bluffing myself to pretend a non-extended / modded original HOTAS should act and feel the same as the long pole in the actual jet. And 25% seem to work out nicely.

What is most puzzling for me is seeing how so many Youtube clips showing labelling lamps AND MFD / HUD that are super crisp and sharp, that I wonder what they did to their systems, that I am not able to, even though I run a decent high-end system. Anyone knows how they did it?

Thanks YoYo, but I've seen many Youtube videos and they are all sharp and crisp even when zoomed out a distance. Tried 2x MSAA and still the same. (You have to look at those Caution Lights on the caution panel. They are almost illegible, unless zoomed much closer.

Just got this awesome plane ... but really hope someone could point the way to fixing this. Those lamp labels (eg Cautions Lights Labels, Wheel Down lights, etc.) are always looking blurry even though I have almost all settings maxed out (see attached cockpit and settings screens). And this problem is not only present in the F15E, but in ALL other modules, where light-up labels are concerned (eg. Nosewheel Steering light, etc.). Even other labelling / markings in cockpits also look a little blurry, though not as bad. Only when zoomed in real close does the blurriness disappear. I have followed numerous suggestions in trying out all sorts of Nvidia settings, but nothing seems to help. I run a rather high end PC and can get good fps most time. LG 32" Gsync monitor. Any help very much appreciated. See attached screenshots. Thank you.

I have blurry texts / wordings / labels in DCS for a long time now. My system is rather high end with RTX3080 and have most stuff set to highest in DCS. Recently changed to a new 32 inch LG G-Sync, and had followed most recommendations to NVI settings including from this thread, but still same problem. Had that problem too previously in an older system. In the attached image, labels such as "Steering Enabled", gauges, buttons' texts, etc., are all quite blurry, whereas videos on YouTube mostly show texts to be very clear. Any advice appreciated. Note - You need to expand on attached Pic to see clearer.

For example, landing gear lights (Green / Red) is now very hard to see as it appears rather dim. Before 2.8, they show up very clearly under all environment lighting.

Noticed that hotkeys no longer toggle. Take the engine de-ice / dust-protector for example. First toggle works to de-ice, but subsequent toggles did nothing. It was all okay prior to the 2.8 update.