Steph21

Ok, nice to know, thanks Zeus

Thanks Zeus Now i'm confused about Magic+Radar lock HUD symbology :) In your first 2 examples, you have Radar lock and Magic lock. But you get Circle+Square with 530D selected and Triangle with CAN selected. When having both Radar lock and Magic lock on the same target, is Triangle only displayed with CAN or MAG selected ? and Square+Circle if 530D selected ?

From M2000 footage, seems AOA is not displayed on the HUD in MAG on CAN master modes. So it seems they forgot to list it in display changes indeed.

Thx zeus, very clear now.

Thx

How do we switch between search modes? With MAG on PCA ?

This is correct behaviour. Box is radar lock, circle for Magic lock. When you get radar lock and magic lock , box and circle are replaced by triangle. There are bugs around radar system but not on related Hud symbology. You might just don't know anymore what to look for

+1

3 way switch option is available for AP roll but not for AP Pitch unfortunately. Way more useful for AP pitch IMO. Wait and see as it should be included later on.

Designating target by moving a TD box in the HUD is done in DTOS mode, which is not available yet in Early Access. You can only designate with TGP in CCRP or bomb on a steerpoint. In CCIP, you fly the piper on the target, you're not designating a target with the HUD with a TD box (TGP or no TGP makes no difference, as it's slaved to the CCIP piper). CCIP works fine, CCIP delayed release too. Maybe you were flying the Hornet 3 months ago :thumbup:

Most of switch positions at cold start are on par with shutdown checklist. But you still have to set some switch to the correct position during preflight check like iff, external/internal light, altimeter setting, hud display...and of course all switches synchronized with hotas if relevant.

LSS is implemented in the F16 and works fine on stable version (might be in WIP though). Haven't tried in latest Open Beta. Set LSS code and click Uncage on Throttle while having POD on SOI. You'll see SA Cue moving around during the search pattern. Of course, efficiency depends on position of the aircraft vs Laser Spot position. But if laser spot is on top of a building for example and that you're high enough, you shouldn't have an issue to find it with LSS (if LSS code matches laser code of course).

Thanks :thumbup:

Great news !

ED, could you please clarify if FCR automatic range scale decrease not working on STT from TWS is a bug/wip (whereas it works on STT from SAM) ? And also if FCR automatic range scale decrease not working for bugged target in SAM and TWS is also a bug/wip Thanks

You have to set Radio 1 and Radio 2 input in SRS Also make sure you load the correct profile in SRS

Tested it yesterday on latest Open Beta, and it works fine now, thanks Baltic Dragon :thumbup:

Great news ! Thank Tim

Would be great, the new Ulmer mask is so nice :matrix:

It's a defensive spiral, used when low on energy and bogey on rear hemisphere closing for a gun shot. He managed to keep his acceleration lower than the MIG 29 in the downward spiral. MIG 29 pulled up first an tried to extend, bad call against fighter equipped with missile (and bad call to have followed him in the spiral depending of his initial energy state). And AIM9X+JHMCS = no fun :joystick:

Thanks Baltic, i'll wait then and thanks Tim for the Alsace patch then, and the new VR Pilot in general. It's awesome. The only reason i'm not starting the campaign on the Stable branch, is to be able to play it with the new pilot :thumbup:

Hi, just started the campaign on the latest open beta. I've reached the AO, and reported Firefight in Kahasab and description of Crash Site. Then i get the option to report a truck leaving the crash site, but i just can't see any truck doing so. My wingman then report it, but still not truck moving. Is it supposed to be one of the truck parked initially near the crashed plane ? Tried it several times, but still no truck moving in the area. i've circled around but nothing is moving in the area, just AAA shooting at me. Anyone had the issue ? Note: Having the Alsace patch on the new VR pilot is a nice touch ;) Very nice Baltic !

INS Update in PI mode is also broken, it should update position of IP when doing INS update without clicking on VAL (Target Cross should be set to where you did the update) but it doesn't. Workaround is to click on VAL to validate the update before passing over IP. Other workaround is to disable INS Drift in game options (if not enforced in the mission). BAD do not illuminate indeed and i'm not sure it should be. Keep in mind that ruler in F10 (or mission editor) doesn't provide tenth of degrees precision for BAD True heading input (theta). This added to INS Update issue added to release when trigger is pulled makes PI bombing not accurate unless using GBU. If you want to fly the Mirage currently, you have to know all workarounds for bugs around Radar, INS, WSC,.... And it's becoming a long list ;)

1- place target between top of diamond and dot at center of diamond for target designation 2- dont level off after designation when armed with mk82 (you can do it with gbu), but stay in a 25-30° dive until solution cue appear then pull up at 4.5 G max. You should get better results

Played a bit with SAM/TWS/STT mode to check how automatic range Scale was handled on latest Open Beta: SAM: no automatic range scale decrease occurs when having a bugged target STT from SAM: automatic range scale decrease occurs when having a STT target TWS: no automatic range scale decrease occurs when having a bugged target STT from TWS: no automatic range scale decrease occurs when having a STT target I think having automatic range scale decrease occuring for STT Target only when coming from SAM Mode, and not from TWS Mode is a bug (or WIP for TWS implementation) Not having automatic range scale decrease occuring for bugged Target on SAM/TWS Mode, i'm not sure if it's a bug or not. Should happen based on some documentation on F16 Block 50, but not sure it applies to F16 CM Block 50 circa 2007 It might be in WIP Maybe ED could clarify the subject Haven't played with automatic range increase yet. remark: this is not the same topic as Manual Range increase/decrease with acquisition cursor for which another thread already exists. Please do not move it to this thread this time :smilewink: