Ivakhir

In case it works for someone else: I had the same issue and I narrowed it down to the following mod: VSN F/A-18F All other VSN mods work. Removing the Super Hornet from my mods folder allowed me to start DCS again.

Quick noob question: I always wondered what regular/common take-off and the following climbing procedures are. I usually take off and turn towards my waypoint whenever I feel like it without any regards to airspeed, altitude or rate of climb. I'm pretty sure there are regular procedures that fighter pilots follow, right? The ATC always says 'climb 300' but I'm not 100% sure what that means. The F-15C manual has the following information: How do i interpret this? My first guess would be climbing at a speed of 350KIAS until I reach an altitude where that equals 0.9 Mach but that would be pretty high wouldn't it? What if my next waypoint's altitude isn't that high?

I am trying to have a player controlled flight of A10s attack a static building with a GBU31. To this end I have created this waypoint with the advanced waypoint actions, see screenshot. When attempting to use the radio commands e.g. "flight > engage with > ground targets > guided bombs > default" they'll copy but fly over it without doing anything. If there is no player lead, they'll drop their bombs on the target just fine. Is there any way I can work around this and get my wingmen to attack static buildings? Other modules have the "attack primary and rejoin" radio command which seems to work fine in this case. a10aiwontattack.trk

Summary I have encountered the following issues when flying one specific self-created mission: Heading misalignment on the HSI Datalink misalignment on the HMD Waypoint misalignment in the entire system Misalignment of HUD cues when in auto/ccip modes for dropping MK83s I report all these issues in one ticket because I am certain they have the same origin. Description In the mission, the player starts from a moving carrier in the persian gulf, see MissionParameters.jpg & FA18CBandarStrike.miz. The first issue encountered is a heading misalignment on the HSI when performing an INS alignment, see HSIMisaligned.jpg. Then, there is a misalignment between the actual position and the position shown on the HMD for the wingman, same goes for all other aircraft, see HMDMisaligned.jpg. Next, when steering towards waypoint 2, the waypoint is actually passed when the system shows around 3nm left. The heading towards waypoint 2 is then shifted 180 degrees and the distance is increasing again. Then, with a target selected on Bandar-e-Jask airfield, the auto-release cue for dropping a MK83 bomb of it is misaligned, see MK83Auto_1.jpg. I understand that there is wind but that is way too weak to have such influence. Releasing at the point calculated in auto-release mode results in a miss by more than a mile, see MK83Release_1.jpg. After this the CCIP cues are completely messed up and do not correspond to reality anymore, see MK83CCIP_2.jpg. Additional information In a fresh mission in a cold start with same weather parameters, these issues did not occur A short track showing the first two issues is included in the attachments The latter three issues occur only in the later part of the mission, creating a track that is larger than 5 MB FA18CBandarStrike.miz Misalignment_short.trk

When changing an aircraft's payload directly in its personal 'Mission Payload' setting, the weight does not change. Occurs all the time on any map and on any aircraft.

Same here: A-10C with signal light testing on, so all lights are in fact on. Also, HUD is so dim that it's actually unplayable.

I have the same problem, but they're not off, they're just super-dim. Same goes for the HUD. On this picture, i have enabled the signal light test, so all the caution lights are in fact on.

Noticed the same thing. I think it might have something to do with the target though. Tried it with static planes, behavior described above takes place. Tried it with ground vehicles, worked just fine. I heard other people having the same problem with buildings.