Xoho

To clarify, the primary issue being raised is the combination of a lack of lineup assistance and simultaneous raising of the JBD and hold back blocks. Lighting would be beneficial, but it would not fix the issue. A possible solution, as suggested above, would be to raise the holdback blocks upon takeoff request, and then to raise the JBD once the player is in position, or once the player hits a separate key (e.g. Carl Vinson catapult controls)

Tested in singleplayer: Observed while testing a mission run in the mission editor. Only AI are present, and this behavior occurred consistently to one group of AI. No track file available (none saved). See video description, same issue prior to "fix"

When spawning a "player" aircraft in the air, parameters such as the aircraft heading, speed, and torque all default to 0. AI aircraft appear unaffected. Heading: When the mission first begins, the aircraft will be facing the correct direction (towards the first waypoint); however, the instant the mission begins to play (time begins to increase) the aircraft will snap to true North. Speed: The aircraft spawns in the mission with a ground speed of 0 regardless of what is set in the mission editor (in this case, the default 90 knots at 500ft altitude). Torque: The aircraft spawns with rotor torque at the minimum value regardless of what would be necessary to maintain flight. This results in a sudden loss of altitude immediately upon spawning in. I have attached a short track that displays all of these issues. Steps to reproduce: 1. Enter Mission Editor 2. Place SA-342 (any variant) 3. Set to "Player" 4. Set altitude + airspeed to > 0. 5. Create waypoint with airspeed > 0. 6. Enter mission (Note where the aircraft is facing (not the compass heading which reads 0 regardless of actual heading) before clicking "Fly") 7. Click "Fly" or unpause. 8. Note the new aircraft heading (0 degrees), airspeed (0 km/h), and torque setting (minimum). In the following images, note the terrain in front of the helicopter. The two images were taken a split second apart. Before the mission begins to play the aircraft is facing the correct heading (which is not the heading displayed in the compass). The instant the mission begins to play, the aircraft snaps to North. SA342L Airborne Spawn State Bug #001.trk

Thanks for the tip. Unfortunately this issue still occurs for me despite clearing those every update (and even with a full reinstallation).

This can actually be done with a relatively simple lua edit that doesn't break the integrity check and can be used by anyone (just gives the mission creator the option to spawn aircraft there). I don't have it on me, but it should be one of the first few results when you google "DCS spawn on ground mod". Unfortunately, it will be undone every single update, and does not work with survey sim (FC3 level) aircraft, which just explode. All study sim (full fidelity) modules work almost flawlessly with it however. I do hope that's something they add in the future.

The causes appear to be all the korry push buttons. Switches work as intended, at least so far.

The following C-101 training missions are impossible to complete, as when they ask for a user action (pressing a button), the trigger does not fire and the mission will not progress, even after holding the button for a prolonged period, or depressing and holding the spacebar. Lessons confirmed not working: 1.2 Basic Visual Flight (Stuck trying to activate pitot heat) 2.2 IFR Flight (Stuck trying to activate pitot heat) 4.1 Ground attack with guns and rockets (Stuck trying to select pylons 2 & 5) 4.2 Ground attack with bombs (Stuck trying to select pylons 2 & 5) 4.3 Anti-ship strike with Sea Eagle missile (Stuck trying to select pylons 2 & 5) 5 Misiles (typo in mission name) and cannon employment in air combat (Stuck trying to select pylons 1 & 6) Lessons 1.1, 2.1, and 3 are also likely not working; however, I do not have time to go through them at the moment. If others could confirm that would be fantastic. Screenshots showing where some of the missions break are included. Tracks can be found on the Eagle Dynamics discord here (unable to upload to forums due to file size restrictions): https://discordapp.com/channels/542985647502393346/543358251694292992/754212767006720111

If that occurred in multiplayer, it's entirely possible they weren't damaged on their screen. Damage is not always synced between clients unfortunately. This has been a pretty serious issue in the Korea1952 server, where you'll be bounced by dozens of sabres only to find out that you were smoking or leaking fuel for everyone else, but not yourself. Perhaps that plays into the issue at hand here?

VREST page nozzle rotation values are placeholders, and not functional. They do not adjust with weight, or altitude. See this thread: https://forums.eagle.ru/showthread.php?t=285533

Strange. I was only able to increase the temperature to 38C during June in the Syria map. I also tried the "Summer Heat" preset which defaulted to 38C and would go no higher. How were you able to input a higher temperature?

Many of the parking spots at this airfield appear to be unusable, despite aircraft of appropriate size (fixed and rotary wing) fitting without issue when placed as statics. For example, parking spots 41 to 52.

Shadows from objects such as hangars or bunkers appear through the terrain, including entire hills. Some objects (such as some of the walls at Bassel Al-Assad) don't cast shadows at all, and many shadows move along the ground when the camera rotates around them at a constant distance. MGRS BT 411102: MGRS BS 481931: Bassel Al-Assad:

The maximum value for air temperature in the mission editor is 38C. With temperatures that can reach over 48C in areas such as Syria, Nevada, and the Persian Gulf, we cannot replicate these conditions with the current limitations of DCS World. Raising this limit to 50C would rectify this issue. EDIT: Syria, Nevada, and the PG have different maximum temperatures as per Flappie's tests below. Syria's max temperature appears to be 38C, and the Persian Gulf's 41.3C. Other maps such as the Caucuses can reach up to 50C, so it would be nice to see this raised.

Prior to the 2.5.1 update, the shaking was significantly less noticeable/intense than it is now. As of the 2.5.1 update (for which I created a bug report), the intensity of the shaking became extreme, and it stopped being a bumpy ride similar to the A-10, in favor of the shaking.

F-102/F-106 would be incredible. F-106 especially would be awesome.