RogueSpecterGaming

You should just arm before starting the engine. That will rule that out. But please post a track of your process so we can see what you are doing. Remove any and all mods and run a quick repair. Just flew last night and did not have any issues in singleplayer or multiplayer.

Yes. Wags specifically mentioned it in his recent interview with Deephack where he states it is the next set of things being worked on along with the rest of navigation tools. And you can also see it in the DTC setup "GEO LINES".

Certain stpt ranges are designated for certain functions. 500-699 is for various data one of which is shared coordinate data between wingmen (which creates a L16 markpoint). Whereas, 26-30 is designated for your own created markpoints, and then 21-25 which is used for MGRS entry. And hopefully in the near future 31-55 is for creating GEO Lines. But don't get it wrong, you can still use those for regular stpt data but you should get in the habit of leaving them open in order to use their actual function. Real world, pilots typical just use a few or the first 20 stpts for route planning. The other hundreds of stpts are used for various things like landmarks, other airfields within the area of operation to include divert/emergency airfields, Geo lines and markpoints as mentioned, preplanned threats, IPs, the list goes on and on.

One is closer to the real image (F16) while the other is not (A10). Also, the same reason why the F16 has to boresight and the A10, F18, and anything else that uses the Maverick does not have to boresight. I'm guessing they are using the F16 as a test bed for these things and will eventually model it that way in the other aircraft. But they have to redo some code in the other aircraft to make it happen as far as the boresight goes. The image is something, I would imagine, won't be too difficult it is just on the standard DCS time frame of "soon". I can tell you that real world Maverick imaging is not that clear as you get in the A10. F16 = closer to realism, A10(others) = gamey for ease of use.

And the F16 just got out of EA this year. System failures will come but it will take time. And not all ED modules or third party modules have system failures modelled yet. That was a false statement you made.

A track file would've been nice. Just sounds like you are doing things wrong at this point.

You don't SEQ anymore. That was a very old thing and was not correct. Correct way to select AUTO/MAN is to put the * over MAN/AUTO and press M-SEL (0) on the ICP.

My answer is because I am a real world weapons troop who has 5 years of experience on the F16 and spent loads of time in the cockpit on the SMS page. Master Arm ON = RDY Master Arm SIM = SIM Master Arm OFF = Displays nothing

Track files would be nice to confirm what everyone is doing please.

Sort of kinda. When Master Arm is ON you get the "RDY" above osb 13 on the MFD screen, if in SIM you get "SIM". All that is there in the jet already.

As someone who works on fighters irl and has 5 years on the F16, not once have I ever seen the JHMCS with a clear visor. For night flying they swap to using NVGs which is a completely different helmet (just the basic one). That thread you shared is a Scorpion helmet and does not combine JHMCS with it. The Scorpion is also a different helmet setup than the JHMCS helmet, and I believe that that helmet does have swappable visors, but the JHMCS does not. So, I don't think ED is going to provide a "clear" option just because people want to use JHMCS at night. Take the JHMCS off, use NVGs like real pilots do. You get the same info inside your cockpit. Or just use the JHMCS still at night and deal with the tint. Only the JHMCS II comes with a clear option but that is only when they do night ops and is only currently available on the F-16V.

Are you sure you are putting the correct grid in? If you don't put the correct grid it will revert back to the 31U and whatever else. So, JTAC never tells you the Grid only the square meaning you need to check the F10 prior to see what Grid you are operating in.

And it works very well in modifying threats and which are more important than others. I think that was a problem before was that threat list and what was preceived as more of a threat than something else was thrown off because it was pretty much a blanket list. I've messed with it a lot and it does indeed adjust what is more of a threat based off of where you put that threat in the list.

Did you adjust the altimeter setting appropriately prior to testing? Or did you leave it at 29.92? But yes, please do include a track file.

Again, it is not "dump" it is dumb. And it has nothing to do with how smart the jet is but rather how smart the bomb/munition itself is. Any bomb without GPS/INS, or any other type of guidance kit is considered to be dumb. Which is what Furiz said. Have you tried doing an A-CAL to calibrate the altitude. That could most likely be effected it. But with CCIP the shallower the dive the less accurate it is going to be, plus any wind can effect the accuracy and any slight shift of the jet up/down left/right can effect the accuracy. Best to post a track file so we can see what it is happening. I've never had accuracy issues in terms of "hundreds of meters" off in any direction. Maybe a few meters off, but that is within margin of error using CCIP especially with wind. I will post a track if you don't.