icecold951

It may...may be fixed in the update. In a mission last night a solo plane in a mission escorting a tanker. It refueled twice without incident. I think it was more of a one time glitch.

This is an actual video of my issue with the full afterburner climbing. It is from Raven one DF campaign, mission 1. Note, this isn't normal behavior with older missions pre update, and new missions.

This is a video capture of the glitch I have mentioned. It is again not limited to Raven One DF, but affects it. I am seeking if anyone can look to see if they to get this glitch. It is also posted at the DCS bugs section.

This is a video of the glitch, describing exactly what is happening. Using Raven One DF M01

I have created a video of the glitch, shown on Raven One DF M01 You can easily find it on You Tube with the keyword search DCS Afterburner Takeoff Glitch or ths link

Try watching in the dominant fury mission 1. Directly launch the mission and just F2 to the tomcats and Cajun I did this on two computers and got the same results.

Nope. The lead is an AI. If memory serves, 4 hornets on the deck. First flight is pure AI. Also I tried restricted afterburner. It doesn't apply during takeoff. It is still in takeoff until they call rejoin. Again and again I'm seeing the same results. If you watch carefully, they climb to 10k feet every time. They don't report "rejoining" until then. I first noticed this glitch when I turned onto WP1 in a mission and my wingman kept burning into the sky until 10k. I even see the glitch on Raven One DF mission 1. The tomcats do it, and Cajun. It sounds like you saw exactly what I saw, and misinterpreted it. But if you watch the F2 status bar, afterburner to 10k every time before they say rejoin. Edit, calling rejoin only applies to a plane within your flight. You don't hear it regarding another flight. After that, they hard chase the flight lead.

Unfortunately, there seems to be a lack of response by anyone regarding bugs. I can confirm the issue exists. I'll try and reproduce it myself tomorrow. I've had AI refuelings since the update, and this didn't happen. It is especially important to me, as I have a bug above. If you by any chance have any older carrier missions or Raven One DF, could you examine the AI aircraft on takeoff, in the Raven One, mission one, just wait and watch the tomcats. See if they do to you, what they do to me on two computers. All AI planes afterburner climb to 10k feet on takeoff. Older missions I have seem to do the exact same thing. I'll attach a mission file with an easy test. Just watch the AI planes taking off first. Upload your miz file, and can examine that for a mission edit issue. Does it happen a lot, or just this mission? Recreating the flight might fix it. DS20.miz

To be clear, this is not a DF bug directly. It affects other missions. I am trying to find out, and it shows in DF01 and probably more after that, if anyone else is getting AI aircraft going full afterburners to 10k feet after takeoff. The F14s, Cajun, and pretty much every AI plane taking off from a carrier. The primary problem with this bug is it is a real gas guzzler. And AI are already horrible about being fuel efficient. And any chasing wingman will use even more fuel to catch up. I'm getting this bug on two different computers. Fresh installs on both of them. It seems unlikely if it is a me problem, if two computers are getting it. And yet in a couple of bug places no one can seem to tell me if they get it or not. It seems to affect any mission made pre update. I've seen it a couple of times on after, but usually they behave.

Okay, new update. I am getting this same glitch on two different computers.

New update: I have now reproduced this on two separate computers. I can't be the only one getting this. So it is getting missed or ignored?

If you could maybe test it without lua? Save the mission and then try creating a flight without that that takes off immediately. I do that too, with in game WPs. It ignores them until it reaches altitude. It may or may not reproduce in a new mission. I saw it reproduce once. I've tried recreating the flight, resaving on a new mission file, and still..... I just did a clean install, completely removed everything and didn't touch a setting. It still produced this result in Rave One, the new campaign that just released.

New update. Even new missions are producing this glitch. I would dearly love to know if it is just me, as I am not seeing any mention of it. Experimenting on possible causes, including a possible reinstall.

New update. Even new missions are producing this glitch.

Somehow saying solved and isn't. Major bug, not simply with this campaign. So far all missions created before the recent update now have aircraft going full burner to 10k feet. My missions were the first I saw this. then I decided to start this campaign waiting for any word on this and a fix. Cajun in mission 1 did exactly this. Not solved move. Full burners climbing to angles 10. Baltic Dragon, recommend someone press Eagle Dynamics about a fix. It seriously breaks missions, as the planes use a literal ton of fuel to do this, and any chasing planes use even more. As posted elsewhere in a bug report, these are my personal fun projects. 1 is the start of a mission created months ago. 2 is a basic mission only to test mission editor after the update, and the planes behave normally. Can anyone confirm if this is a just me issue, or a general issue? 1.trk 2.trk

On pre-existing missions from before the update, my AI carrier planes, don't know about land based, all go max burner to 10k feet before rejoining. This is seriously wasteful of fuel, not to mention can break some mission aspects. I'm concerned that making complex missions is going to be impossible if updates break older missions so completely. Tomorrow I am trying to resave it as an new file entirely, rather than save over the existing one. See if that helps. New missions do not do this. Edit: These are two tracks showing the issue. track 1 is before the update, and no efforts of creating a new flight or resaving the mission have fixed it. Track 2 is a new created mission, very basic, demonstrating proper takoff behavior. 1.trk 2.trk

Wingmen now go full burners to 10k before rejoining. That has to use a ton, literally, of fuel. Extremely wasteful. So far, still testing, this happens in existing missions. Even if you recreate the flight. So far, in one freshly made mission, they rejoin as normal. It is the wing man tagged Test-1 Regular release of DCS, not a beta. Update: This includes all AI aircraft, not just wingmen. Resaving the mission as a new file doesn't fix it. Creating a new flight doesn't fix it. It does not seem to happen to new missions, only old ones. Track 1 is an older mission, of about six months. Track 2 is a new basic mission. Takeoff is more normal. FYI, a similar post is in the mission editor section, seeing if I alone and experiencing this. No response so far. New Edit: This but even affects aircraft in the Raven One DF campaign. Mission 1, just starting this after update, and Cajun is full burners to Angels 10. 1.trk 2.trk

I don't know why, but the open composite tool was the problem. When I downloaded the .dll file and put it into the DCS folder, it works fine as of late last night. So if anyone else has trouble with the open composite tool....this helped.

Downloaded the .dll directly, rather than using the open composite. That works. For some reason the open composite tool is messed up in this. This is despite the sim being properly installed.

Complete uninstall, delete, reinstall, and same issue.

Sounds like I might have to do a reinstall then....Anyone else?

Reboot, used the cleaning tool, redownloaded open composite, the works. Works in Steam VR, but it goes desktop under Open Composite. Are you getting it to work?

Help? I just got the DCS update and OpenVR doesn't work, Open Composite. First, was this a me issue and is it still working for others? Or is it broken?

Open Composite doesn't appear to be working as of the current update.

Anyone else having issues as of the current DCS update? It won't open in OpenXR using Open Composite