Pavlin_33

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?

Yup, I usually use it to stay level in a turn.

Think of the radar beam like a flash light. No matter where you point the light will reach same distance. Expected target range combined with expected target altitude just defines where the center of the search zone will be. In my example (right side) you would miss the enemy 'cause he is below the search zone.

As soon as I get a chance, I will create one.

As you can see from the screenshot, there is a discrepancy between FPV shown on the HUD (correct one) and the B-scope (shows descent when level):

Hi @Mike_Romeo, here's a video. You can see that the pod looses lock just before impact. The curious thing is that the target actually gets destroyed - every time. It's just that I don't get to see the explosion . Happens on MP 100% of the time and almost never in SP.

I am not sure if this is a bug or if I am doing something wrong, but when I fly online my targeting pod seems to loose its lock and reset couple of seconds before bomb impact. This happens even when I do a gentle turn after bomb release. In single-player I am able to consistently hit targets using the pod and there seem to be no issues there. Even if I just fly over a target without banking, the pod's gumball does that snapping movement but stays on target. My engagement is between 12k and 18k feet and doing 300 to 400 KTS. In MP, however, it seems to just snap back to nowhere at some point. The only difference between online and MP attempts is that in MP I start the aircraft manually. Maybe I am missing a step?

This setting is very important and it defines the center point of your search area. According to that and in combination with the expected target altitude it will slew the antenna to search different parts of the sky:

Ah, only now I read it. Ok so probably the issue was the side slew