Pavlin_33

To be honest with you, I don't think it makes any sense doing BFM in DCS in anything else except same aircraft. There are way too many discrepancies. The other day I got out-turned and out-climbed in a Flanker by a low-energy Mirage 2000 and ever since then I just enter a fight knowing I will lose and just practice handling and SA and not caring too much about the outcome.

RL SPO-15 (Soviet RWR) will detect radiation at a minimum of 150% of the range of the illuminating radar.

Your results mean that M-200C has higher thrust-to-drag ratio than the MiG-29A. Aircraft settle into certain sustained turn rate once the drag from high Angle-of-Attack equals the thrust produced. I was under the impression that the delta-wing of the Mirage should be very draggy under high AoA, but what do I know? I am no expert.

+1

I have 1080 screen and I can't see squat beyond 3-5km.

Unless something changed in the meanwhile there are only 3 states in DCS: - engine off - engine on - A/B on

I am very glad to hear that I am not the only one with this problem. For me WVR is somewhere around 3-4km. Beyond that I am blind as a bat.

Or remove ECM completely until it's done better. Personally I would love to see some randomness in ECM effects as well as ECM affecting AWACS/EWR and SAMs. At the moment it does nothing more but deny you range information, but this can be easily worked around using DL or GCI.

I am no expert on black 'n' white CRT screens, but Shkval is there to help better see targets that are far away. Now I understnad that in certain conditions it might be unreadable, but at the moment it's useless most of the time. I use zoom to look out and find targets instead the screen that was designed to do just that. Again, I don't think there is any problem with the image contrast, but a weird sun glare that is being rendered in the middle of the screen.

So could it be the fact that I don't have shadows turned on, is causing the Shkval to be unreadable? My track does not depict the issue 100%, but in the screenshots from MP you can see that it's useless from distance of 5km when the Sun is nowhere near shining directly. Also, the glare does not seem to move at all when you move your head around. 29's HDD is readable in direct sunlight IRL.

Thanks for sharing your settings. Even in your screenshot it's quite difficult to tell of there is a target there or not - I believe there should be one avanger. What I did find out is that it depends on the position of the Sun. Unless the Sun is in your front hemisphere, the Shkval gets more or less washed out. Now I do realize that in some extreeme positions the Sun can cause issues, but in DCS it's a bit exagerated.

Here's the track. Basically the Shkval's protective glare shield offers no protection from sunlight. It's as if the screen is just exposed directly to the sun. Also the glare seems to be static no mater the head position. 25t-glare.trk

I will definitely do this. Where can I find the `dcs.log` file? My screenshots are all taken in MP in single-threaded DCS.

Not to open a can of worms here, but full fidelity modules also suffer from many "FC3" simplifications: - auto-start sequence option - perfect RWR (not all, but many) - simplified A2A radar (can discriminate between targets at any range; I think all) Just to name a few.

Hi @Flappie, is there any chance for someone to have a look at this? The issue comes Sun reflecting of the CRT screen. It basically renders the Shkval useless under most situations. In the screenshot you can see that the target is practically not visible form a distance of less than 2km.

Because there are no other alternatives for flying Soviet jets.

Jeff - you love it and you hate it. It's like a screaming toddler that getts puppy eyes at the end of the day. It has TWS but not helmet mounted sight. It has fox3, but fox2 sucks. It has array of weponry, but short legs. It has missile warning system, but it's slow... Things I really like about it, is that it seems to be very well modeled and feels like a real aicraft. And oh, yes, it has PROPER IFF modeled! Not this DCS - toy IFF.

I guess beeping would go higher in frequency only when you use narrow search field, but in full-wide mode it should be exactly the same as in RWS, no?

Here's the track file. jf-17-fpm.trk

Here are the tracks. I've tried to re-create the video with the following parameters: alt ~ 14.000' speed ~ 400kts 1.3-1.6G in the turn after bomb release In my SP tracks the pod never looses the lock, in both "area" and "point" tracking and you can clearly seem the bomb impact. jf-17-tpod-area.trk jf-17-tpod-point.trk

Same thing happens even if I am in area track and manually slew the target designator, but I will double check this.

But exaclty the same maneuver works perfectly in single player. Also the pod seems sto snap off exaclty at the moment of impact and does this consistently. I will post a track from SP a bit latter.

In some aspects FC3 planes have also limited functionality compared to their RL counterparts. It's already a difficult adversary in capable hands. Try flying online against "EvilKipper" and see how it feels like

Engines need to be less than 10% N1.

Why no RWR warning when launched via STT? 120 is receiving M-Link data (before pitbull) and this combined with STT should trigger a launch warning. Same happens for R-27, for example. Does Aim-7 have mid-course guidance?