Santi871

Emergency jettison removes a SAM designation or breaks STT lock (depending on what the radar was doing when the button was pressed). See attached track. f16emer_jett_breaks_lock.trk

If you use a radar ACM mode to lock a target, and go back to radar CRM mode, then the radar always returns to ACM mode upon return to search (breaking lock, unlocking target, etc.). This means that, for example, if you use dogfight mode, lock someone with ACM radar mode, then go back to regular AA mode and lock someone with RWS/STT, when you break the lock it will return to ACM. See attached track. The only fix right now seems to be to cycle master modes. f16return_to_search_bug.trk

The fact we keep hearing that it's used for IFF from ED is slightly concerning :noexpression:

Oh okay, then it's correct on ME placed ones. The starting position (waypoint 0) that is created when you spawn is also set to 2000m instead of the ramp's elevation now, is that correct too?

Both the initial waypoint 0 (starting position) as well as mission editor waypoints are initialized at 2000 meters elevation, regardless of the true terrain elevation. Track attached. fa18_waypoints_2000m_elev.trk

This is not correct as is, ED should consult with SME.

LTWS in the hornet designates/tracks a position in space correctly, in other words it is INS stabilized, it was fixed a couple months ago. There is no extrapolation after a hit, but that's a separate issue to what's going on in the Viper at the moment and likely also a bug in it too. Also, in the hornet, RWR and HARM aren't INS stabilized still.

I was wrong-ish. It is modeled but it's wonky and it will fail if the radar picture is complex.

It's already reported

Just have them give it a look, please. It's just a suspicion and we all know who are the ones who can check the code and confirm whether it is a bug :) It wouldn't be good if fuel consumption got changed due to an underlying bug affecting throttle input.

Good point. Have you noticed AB doesn't light up until well past the AB mark on the controls indicator? I think the throttle input is shifted in its entire range.

I am running some tests against documentation on fuel flow easy to find on the internet about the blk 50 Viper with F-110-GE-129 engine (the one in DCS Viper). To summarize, the DCS Viper consumes a lot less fuel than the charts state, especially in afterburner (I'm talking a big difference, around 25% of what it should be consuming). Is the fuel consumption still being tweaked? I am sure ED has access to this information.

Thanks wags

Are the brick tails that point towards or away from the bottom of the display depending on cold/hot target a thing we can expect for RWS?

High PRF = Higher range but works best on high closure rate targets, might not detect beaming or cold targets. Medium PRF = Lower range (~30nm or less) but works on all aspect targets.

How can you get in the habit of using something is not modeled?

It was fixed for LTWS in the Hornet (but not HARM or RWR), but this bug is back for SAM in the viper as the thread says. Track attached. Notice the target stays fixed on the radar despite heading and pitch changes, only refreshing when revisited again by the radar (if it is able to find it). f16_sam_no_stabilization.trk

They get launch warning right off the rail. It's a bug or placeholder until TWS is in.

Firing an AMRAAM in LTWS will cause it to switch to TWS to ensure higher update rate and scan centering (when TWS is added). Firing a sparrow in LTWS will cause it to switch to STT so it can guide it.

ALR-56M audio Can anyone shed some light on what kind of audio the ALR-56M produces? So far the only material I've been able to find that maybe contains it is this video: But I'm not 100% sure since it might be one of the older RWRs. If anyone has more info it'd be appreciated. E: to clarify since this got merged into another thread - I'm wondering about new guy tones and other synthetic tones that aren't PRF ones.

Remove code B (or give mission editor option to disable it), it's useless for DCS context.

IMO M6 should be coalition based, such that it's assumed all JF17 in the same coalition share the same code. That way, using M6, friendly will always be friendly, and unknown always unknown. M1 to 3 should be customizable and allow displaying "friendly" regardless of coalition.

AACQ is exactly the same as it was on release: a buggy placeholder that doesn't resemble what it should be. For now it still locks the first thing the radar sees from left to right.

+1

What does simulating physics have to do with writing high quality, reusable code?