antsh

Maybe the line in red from the new features is related? New features for DCS: F-16C Viper include but are not limited to; Complete the Litening targeting pod AGM-65D/G/H/K/L Maverick Flight model and FLCS tuning HARM Targeting System (HTS) AGM-88C HARM POS and HAS modes Complete Air-to-Air Radar: DTT SAM mode, bullseye, intercept steering cue, ACM Slew, Velocity Search with Range, Landing and takeoff handling tuning Integration of the JHMCS with the HARM Targeting System (HTS), Link 16, AG Mode, and AIFF Sniper XR Targeting Pod

Same here. Very evident, and it is a pretty beefy rig: 3900X/2080Super/HP Reverb

They are much better, and the brightness rockers work.

Just wanted to chime in that I noticed this as well with SteamVR. You don't actually have to do anything in the bios, you can set a group policy to force a power plan so that it won't change (even if a program requests a change). You can follow the instructions here but just find the GUID of the ryzen plan you want and set that. https://www.kapilarya.com/how-to-force-windows-10-to-use-custom-power-plan

Have you checked to ensure all mods are turned off? Particularly ones that change the symbology characteristics?

bumpidy bump to maybe have ED take another look. Maybe someone can help convince them like we did for the JHMCS bug :).

I've seen those letters above red datalink tracks (of friendlies) in the instant action PG mission where you bomb the warehouse. No idea what those designations above the track symbols are so here for the answer as well.

Yes, please! I posted about this a while ago as well: https://forums.eagle.ru/showthread.php?t=257472 Also, much easier to DMS down for a second to turn it off than having to move the throttle and use your mouse to spin the knob. It is turned on during auto-start anyway, so wouldn't you think it'd be on for a hot aircraft as well?

Hi there, great work! May I be added to the list please? Thanks!

@BIGNEWY can you take a look at this one as well? I can't believe that the FCR doesn't reduce scale automatically in TWS mode (or that you can't decrease range manually, actually). Otherwise the pilot would have to either exit TWS mode, or take hands off the controls. This also has a knock on effect of having the DLZ scale being really compressed if you start using TWS while a bandit is say in the 80nm scale.

Right, the displacement is happening to exaggerate the upward movement of the bore cross. It would make sense that it would always happen in the up direction of head movement, and should have nothing to do with the horizon. I’d argue it would be even more important this worked while moving your head up and banked to a high degree like in a turning fight.

Apart from using the boresight mode like I described vertical scan and hud scan mode work fine in dogfight mode.

There is an interesting bug/WIP issue with boresite right now. When you TMS up it will slew the radar to where you are looking (and every time you press TMS up it updates to where you are looking). This is how boresite locking works with the helmet display right now. If you TMS down after this it will return to boresight mode looking down the hud as you expect. You can actually watch this happen on the FCR. Look up and to the right for example and press TMS UP, you'll see the radar beam will move up and right (look at the carats on the edges). Once you press TMS down, it will re-center vertically and start to move very quickly around 1-2 degrees horizontally (and now a boresite lock down the hud will work). Hopefully once we get dynamic helmet boresite following implemented like the hornet, this wont be an issue anymore.

Just bumping this because I have been experiencing this as well. Has this been acknowledged as a bug or WIP, and could it be tagged as such if possible?

Can this be changed from correct as is since my other thread was merged into this? @Bignewy said he would investigate, please note my emphasis above, this is different than range bumping.

Good catch, looks like the TLL is pointing to the point on the ground directly below the target.

Yup

Yup I’ve brought it up in the controller bugs and wishlist sections. I just mapped the osb button to the enable button on my Hotas. The sms page does have to be up on the appropriate mfd for this to work though.

Bignewy said he’ll take a look. Mods, can we moved this to bugs?

Just checked and this doesn’t happen in TWS mode. Bugged a target at 60nm with a scale of 80nm. Kept tracking until he was within 10nm, and the scale remained at 80nm. Same experiment with an STT moves the scale down as he approaches as you’d expect. I’m assuming this is a bug or WIP because I can’t imagine a pilot would need to take his hands off the controls just to hit the osb. Note: this is different than bumping the scale which I know doesn’t work in TWS, but I assume scale changes as a toi approaches should still adjust? @Bignewey?

That's where I saw it! So, two questions around: "The range scale will automatically decrement when the TOI is at a range less than 45% of the range scale, and when the ACQ cursor is less than 5% of the range scale." 1. The ACQ cursor is the slewable box when using the TDC? 2. TOI is defined as an STT only, or does it apply to STT, SAM and TWS bugged targets?

Radar Scale - Automatic Change I know this has been discussed somewhere, but I can't find it, so I figure I'd ask. Under what conditions does the radar scale automatically change with respect to the current range of a locked target? I know I have seen this behavior sometimes, and not others. I know it might be different under different situations; can someone confirm or edit the below statements: In STT lock mode: When the target closes to <45% of the current range scale, the range scale automatically decrements. For example: radar scale at 80nm, target is locked in STT and is out at 60nm. When it closes to under 36nm, radar range scale (and HUD Launch Zone scale) decrement to 40nm. I might have read somewhere that the radar cursor must also be in the lower 5% of the FCR, but not sure if that is true. In SAM lock Mode: Does the above take place or is it STT only behavior? In TWS mode with a bugged target: Does the above behavior also take place with a bugged target in TWS, or is it an STT only situation? Also, is the above true for different modes in reverse? When a target is cold and approaching the limits of the current radar scale, will it increment? Thanks!

just a friendly bump to make sure it stays visible :)

Pressing the cursor enable button should do this, but it is not yet implemented. In the meantime you can just assign the appropriate OSB button to that control and it should act similarly until it is implemented.

Just a friendly reminder to hopefully get this implemented after the holiday :). Thanks for all the awesome work! С наступающим!