Lord Vader

Hi @[31st] Spider
What you are experiencing is the adding of deltas in VIS mode. This is correct behaviour.
Pressing TMS aft in VIS mode will revert to pre-designate mode (cursor slaved to the FPV). 
Steerpoints are not "altered", you can return to PRE or CCRP mode and then press CZ to remove the deltas.
 

Hi @Gunslinger52
I watched your track and it appears you are trying to hit the tree trunk at the base and then halfway. I do indeed see the rounds hit beyond the trees once you move up the trunk, but this is expected behaviour.
Not only are we dealing with a limitation of how trees are depicted (not affecting sensors and weapons, something that may one day be reviewed), this is also a perspective illusion. Even though you are aiming "just above", the targeting is actually being performed way back in the terrain. Something that's even more evident because you are aiming at a sloped area. So the weapons will fly further. 
Try to do this on a building or a large object and you'll see how it compensates correctly. 

Alright, looks like you're programing it like I am.
I do see CMWS not recognizing the initial position, but not the others you mention. I will report it internally for the team to have a look. 
Thanks.

Hi again, @Jalava
It's confirmed. Ground Power Switch 3B powers the armament computer. Since the CAGE button is associated with the SMS page it won't operate until that particular system is powered on. This is correct behaviour. Thanks for bringing it up, though.

Thanks for the new images @ring_H₃PO₄, I think we got it.
It's been reported, thanks.

@Pyrocumulous
This is really a weird find. 
It is my belief the next updates may bring a fix to this weird bug. Please report back if after the updates you still have the issue.
Thanks for your patience and support.

Hi, @Voy
If you take a look at the data that is displayed on the HUD when selecting CRUISE/HOME, it's not the bullseye range. This is a different value.
What you are seeing is the estimated fuel above Home point in hundreds of pounds. If you go below bingo, you should also see a "FUEL" warning on the left of it. 

This is correct behaviour and does replace the bullseye information on the HUD.

Hi @Alpiinoo
Previously, when you pressed "remove payload" in ME for those stations, it would wrongly add an empty fuel tank pylon. This was corrected some revisions ago, because the pylon is mounted with the tank itself, that's why when you jettison those stations the pylon is dropped with the tank. 
The current limitation of not having any weapon pylon in those stations in a "empty" configuration, reflects our documented references for weapon pylon usage. If you have other documentation that contradicts this, please feel free to send it to @BIGNEWY.
Currently, the "Remove Pylon" for those stations is redundant to make sure older created missions are still compatible. 

Hi @Atazar SPN
The pilot model for the F/A-18C is being updated. When the new model is released, we'll revisit all stages, including the ejected.

Hi @OldFlyer
I was going to suggest a repair for the Maverick issue. Good thing you did it and solved your problem.
Regarding the snowplow feature, you said it yourself that you haven't flown the F-16 for some time.
The Snowplow logic was updated and improved. Some of the TPOD functions still require some additional system logics that are still being worked on incrementally. But we are confident this is working much closer to the logics of available documentation. 
Take a look at my comment here, it should help you understand how it works now:
 

Hey @D4n
I am sorry but I can't reproduce what you are stating. Took control of your track and it performed as expected.
Like @FusRoPotatosaid, there could be an issue with your joystick inputs.
When flying, use the control input window (RCTRL+Enter) to check the ranges.
Make sure you don't have another stick or gamepad connected. Also make sure you don't have some axis assignments mixed up.
Also make sure you disable mods for testing if you have them.
If you still need help, let us know.
 

Hi @gdotts
Are you referring to the button to reset trim position to default? It's still there.

Hey @Need-To-Know
I've reported this internally. Thanks for letting us know. 

Hi @Rongor
We are aware the manual contains several items that need updating. At this point, treat it as WIP. We apologize for the inconvenience.
The current logic in DCS will be reflected in the manual. 

Hi again, so we reviewed this snowplow logic and concluded the following:
- When in pre-designate state, the Snowplow cursor is at a fixed location in front of the aircraft. The Snowplow cursor needs an elevation component to determine the look-down angle because 50% FCR range only determines the horizontal component. The Snowplow cursor is placed at the elevation of the current steerpoint, which is where the FCR beam and TGP is focused. After designating, then the cursor will move to the altitude of the terrain.
There are some additional refinements coming to Snowplow with the core sighting point/targeting logic, and those refinements is what I mentioned above as being reported.
But the elevation mechanism of Snowplow while in a pre-designate state is already working as intended.

- This, or course, means that the manual needs updating. Like we've mentioned in other posts, the manual is currently being revised to reflect current states. We understand this may lead to confusion but a good rule of thumb is to keep up with changelogs and check for updates/changes. 

Hi @darkman222
The video you used as reference is a bit old and reflects a previous state of the maverick/HMCS logic.
We currently have an accurate representation of the AGM-65 operation using VIS mode for both the HUD and JHMCS operation based on documentation for our F-16C Block 50 CCIP tape. The steps are the following:

Setup:
- AG Master Mode
- AGM-65 Power ON
- VIS mode selected
- WPN format on MFD
Procedure:
- HUD to SOI
- TMS forward long to cage TD box to HMCS
- Designate via HUD or HMCS (TMS long) and ground stabilize
- LOS symbology is shown cued to TD box on HUD and HMCS
- DMS aft to move SOI to WPN page
- Refine target and TMS forward to lock
- Fire within MLE range
- Profit
Hope this helps, happy flights.

Hey @D4n
Just because they are around and are armed, doesn't mean they are a threat. The Su-25s in mission are not set to engage the player. 
This is a "free flight", meaning you can either fly or use the weapons, even engage them if you wish. If not, there really are no threats in mission.

Hi @einarabelc5
I ran that Maverick training mission and there is an intentional wing heavy loadout. The narrator is clear on what to do to counteract it using trim. I saw no odd behaviour, to be honest.
Yes, the F-16 can be quite challenging with asymmetrical loads.
It is advised to use the aileron and rudder trimmers to counteract the plane's behaviour.
It is also wise to avoid very pronounced asymmetries, especially on take-off.  
On your second message, I would clearly avoid abrupt inputs in such conditions. This will make the asymmetry more pronounced, leading to undesired rolls.
There's also an identified issue using Mavericks on moving targets that hopefully will be fixed soon. 

Hey @Cpt. TRIJJ
Regarding the sound, It's possible you might need to adjust your audio settings. I would suggest turning on "Hear Like in Helmet" option and also reduce the "In Cockpit" slider to your liking. This will filter out the engine roar and some cockpit sounds as well. 

As for the tutorial itself, I didn't find any issue with it. You must allow the full narration to finish before pressing any buttons or keys. The instructor mentions the OSB referring to "MAN" on the DDI, then the OSB referring to the "UFC". Then you'll see the "RTCLE" option is then highlighted in the UFC. Pressing the circular button next to it will add the mentioned colons, allowing data input on the keypad. Hope this helps.

Hi again @moggeland repliers.
This situation was reviewed internally and I have to explain the following:

When we originally designed the HAS, the scan times were slightly longer per unit, resulting in a longer search pattern. Matt Wagner's video at the time reflect that original logic.
Since then, the system has been adjusted to be slightly faster, especially if no station is found from the selection. 
As for the timer resetting, it's based on a algorithm, involving the maximum time that can be achieved with targets and if they're detected or not. If not, the cycle is reinitialized. If one is detected, the scanning time may increase accordingly but it doesn't take all the time specified. Again, that should be regarded as "maximum" time, not actual total time.  
Thank you for your time and for understanding. 

Hi @Apache 64nice nickname.
This was reported internally. However, do bear in mind the pilot body is still requiring some tweaks.
Thanks.

Hi @DreamingInfraviolet
I watched your track and must observe several things you need to review.
You try to change coordinates with the INS system in NAV mode. It won't be updated like that. If you want to do this, you need to reset the INS system (off, then one of the align modes) inserting the coordinates in the first two minutes of alignment in NORM mode. 
By design, INS does not know where it is unless you confirm the coordinates. In this case, if you confirm the current ones, you would intentionally have a misalignment. The system will say it's "accurate" because it's assuming your coordinates are correct. 
Remember our model of the F-16 does not include an integrated GPS system, like the A-10C EGI. This is a separate system that generates a position via an algorithm called a Kalman filter. Long story short, GPS is an aid to this equation. 
The Fix feature will only correct INS coords drift if GPS is not available. So it's working correctly in your example.
I was able to take control of your track and do the correct procedures with success. 
Hope this helps.

Hi, @applepiefrost
The mark point you are creating isn't drifting. It's, in fact, floating mid air. Although the altitude registered in the mark point is correct, the actual visual representation in the HUD and HMD is not. Even steerpoints created on ground level seem to be floating. Depending on terrains, it's about 100ft above. 
Without context, It's hard to say what happened to provoke this offset. It could be a previous altimeter setting, set in an older version of DCS or the module itself, for example. 
How long has this mission been created? Did you change any altitude or altimeter parameters for it?

If you open your Miz with a zip unpacker and check the mission.lua using notepad++, you can see that below "failures" you have several of them set up as "enable = true".
What you can do is enable failures in that mission options menu and in this section we talked about disable them all. 
You can also edit the lua file and add "false" to those enabled. This way you needn't redo it. 

Hi @Hippo
The HUD brightness can be adjusted if you need it to be less intense.
Although we can revisit it in the future if required, for now the brightness seems to be correct.