Furiz

Hey @PlaceboC6, I have to correct myself, I don't do auto start but when I tried it I noticed it now confirms coordinates, anyways please read he manual first when you have issues cause it can help a lot. You didn't do the alignment properly, you have to wait till ALIGN on the HUD starts flashing and RDY on the DED flashes as well. Then you have proper alignment, all described in the manual. I did the same mission with auto start and waited till it was flashing, all is good. Cant believe in 2 years flying this sim you still have issues with alignment. Here is my track: F16 do proper alignment.trk

Hey @PlaceboC6 I saw your track, didn't notice you re enter the coordinates in first 2 min of the alignment which is necessary when doing Normal alignment which is being done when auto starting the jet cause the auto sequence wont do that on its own. So it needs to be done to get a proper alignment, after that the HUD will function just fine. Page 172 and 173 of DCS F-16C Early Access Guide describes that process.

This is what I want

Already been discussed and the dead horse died gazillion times already.

No problem, if you have any other questions just ask many people here like to help

Hey, F-16 doesn't have similar function like F-18 where you store coordinates in each bomb, but instead you can create mark points with TGP for example or make steerpoints in mission editor or in the jet, then when dropping the bombs you need to switch those points.

That would indeed be useful, and really not something hard to add.

Hey, Perform proper alignment of the aircraft, then set MIDS LVT knob to ON, on the ICP press LIST > ENTER to get to Data Link NET STATUS page and press 1 on the ICP - NET STATUS page to turn GPS TIME - ON. And that's it. If you still have problems please post a short track showing the issue so we can see what is going on.

This would be great to have, currently we can not reference the laser code we used on our bombs when loading weapons.

Yes, slewing your sensors will create offset from the STPT, so that offset has to be zeroized to show proper data and that is done by pressing CZ or cursor zero.

Great to see all those issues reported, a step in the right direction

Current known SAM locations are pre set on your HSD, you can discover additional SAM sites if they were hidden previously with HTS or they may surprise you.

@DmitriKozlowsky Hey, I saw your track and that dot inside the flight path marker says your HUD has TDC assigned, if Mav was selected there should be an asterisk in the upper right cornet of the Mav display but there isn't one, also Mav did not lock that building, screenshot from your track: You need to assign TDC to your left DDI (Sensor Control Switch LEFT) and Mav will attempt to lock the target if I remember correctly.

@Lookiss Hey, yeah as they have said above Alignment should be done while the jet is not moving or shaking. Alignment also comes after EPU and SEC tests IRL, here is a good video of a real procedure done by Viper crew chief:

I believe that simulating all those as some say worthless features is not worthless at all, without them the aircraft is naked, bare boned... I buy modern airframes cause I love to fiddle with their systems and I love to explore those systems, test how to use them best vs which enemy, but in the F-16 there is really nothing to explore, just bare bones... I mean dropping bombs or shooting missiles is not everything you can do in an aircraft, if I wanted only that I could have gotten a much cheaper deal.

@WHOGX5 Very well written and to the point, I think ED should have quality standards when it comes to releasing modules, so that differences in completion are not this big, I know all aircraft can't be at the same level due to documentation issues but they can't be this far away. F-16 feels naked with all the missing features on it like error messages, test page, radar functionality, ECM functionality etc etc, don't need to list more as you said it all. Well people are concerned cause it seems ED is lowering its standards, something we really don't want to see happening.

Off course you can't make it 100% copy of the real deal, and that is completely understandable. However I'm sure no one was expecting completely unusable pages like the ones shown above, and I'm sure you gonna point out to the roadmap but since you have changed it so many times the roadmap gives the wrong impression. Our F-16C really needs more systems done, that TEST page would be great to have working.

There are other items on the roadmap not nearly complete like. You can easily see that when you try to access some control pages, GBU-24 Paweway III missing some stuff, HTS some buttons don't do anything etc. FCR not fully complete, AGM-154A control page is not even accessible. CBU-105 we can only change BA in the control page. or TEST page in the Viper, non of the buttons work on this screenshot: DTE - none of the buttons work: Labeling stuff complete on the roadmap is really not fair. And in my opinion F-16C is more than just SNIPER XR away from leaving EA state. This is just my uneducated point of view, imagine how someone that worked on Viper feels when he sits is this digital cockpit.

Guys you are over complicating this, he just wanted to know how to get out of this mode:)

That is medium ranged missile AA mode, you need to go back to Nav mode. To do that press the AA button on the ICP just below the HUD, or if you used DGFT Switch then DOGFIGHT Missile Override Switch - MISSILE/OVERRIDE CENTER, or DOGFIGHT Missile Override Switch - CENTER

That bug has been reported on this very forum.

Cause there is lots of stuff going on on MP server, and it probably has scripts that we don't have locally etc etc ... Best to try and reproduce in single mission with no scripts and mods.

Sensors remain SOI even after they are no longer displayed the MFD, so if MFD display is switched with DMS left (if on left MFD) from for example TGP, which is currently SOI, to HAD then HAD will not become SOI but instead TGP will remain SOI and is slewable in the background. For me it makes no sense to have some other sensor not displayed remain SOI, it should switch automatically to other displayed sensor or if not able to make the page displayed SOI (SMS for example) SOI should go to HUD. Here is a track to show what I mean with this: F16 able to slew sensors while not on MFD.trk This was already discussed here: I think this is worth investigating. Thank you.

There is new INS logic at hand with some recent update, that might be the cause.

Those are minor issues that can be fleshed out later