Cobra847

Please pause CTD reports until the patch with the above fixes hits. Just to clarify; the fix above has not shipped yet.

Soundtrack folder in the module folder.

Here we go; This bug is actually very rare, despite this long thread. E.g.; none of our 30+ internal testers can reproduce it, nor can anyone in the development team. There is an issue with ED's DRM that basically means that we don't get any crashlogs from CTDs (hence why the game just "disappears"). This is an absolutely critical issue and we've raised it with them. Without a crashlog, we don't even have any idea where to begin looking. Predicated on point two, we're trying to nail this down and fix it. We've even asked testers to just focus on this issue and try to get us a crashdump to no avail. We may get in touch with one of you directly soon to try and nail this down using alternate, DRM-free binaries. In summary, we're working on it and we'll be taking drastic measures shortly.

This will be fixed in Wednesday's patch.

Yes- but we first need to drill down and fix the remaining major issues in the F-14B before we unveil and commit to a public completion roadmap :)

We did ask about this before launch. It's something we want as well. Hopefully it'll be feasible down the line.

There were significant AI animation changes in 2.5.5 that cause most of these issues. We're working to solve the issues this created.

"It shouldn't be too difficult..." It's just a SMOP :D Branching the F-14 into something separate that rips out multicrew code and works with a single player is likely unfeasible. It would likely involve significant systemic changes to avoid things breaking and then we must maintain a frankensteined branch of the aircraft too. The correct way to do this would be to change how this works in the base engine, but we have no way of doing this ourselves, and have raised the issue in the past.

There was a significant change to how AI are animated in 2.5.5. We're working to solve all of the issues this created. We patched just last patch (1 week ago!) - and new changes will ship on Wednesday. That'll be a gap of two weeks in total.

Uh, what? You do realize we patched just last patch? :) Here is the changelog from last week: Fixed Jester doing only one action when asked to perform a series of actions of the same type. Fixed negative values (formatted as large positive 32bit integer) showing up for TID contacts' altitude. Fixed bad limiter input on fuel probe yaw moment Fixed Jester radio tune and similar commands Our next changes will ship on Wednesday. FWIW; the AI issues are changes on the DCS side due to changes how AI are animated. We're working to fix all of the issues arising from these changes.

There should not be any changes. We're aiming to ship our changes on Wednesday.

It does. We've reported it to ED.

It's on the list to make this an option.

We have a full battery of FM tests that are run at every build that is made on our buildserver. These are all based on a comprehensive cut of performance charts and data that we feel is representative and allows for us to model the aircraft accurate. Currently, we're not seeing anything out of the ordinary, but we'll make sure to look at this specific issue. Ordnance drag is handled primarily DCS-side, and thus it is somewhat of a black box for us, and this can cause issues. We approach all of our work with the utmost rigor. We don't just magically handwave an FM of this complexity into existence. And we'd rather not waste our time doing it inaccurately as that would be depressing, both on a personal and professional level.

Entire content team is focused on Viggen at present. Main focus is on completion of the full campaign, and other improvements that were delayed due to a lack of resources. The Viggen will exit Early Access soon, far ahead of the F-14, and our resources are aligned accordingly.

ED issue. We've asked them to investigate.

ED issue/renderer change. We're asking them to investigate.

Fixed internally.

An ugly one for sure. There's a fix in progress. I noticed this before release but didn't have time to fix it.

That's a mistake- you should've received two grey ones. Can you e-mail us at support@heatblur.se? Thanks!

In a vacuum, everything is easily caught. In reality, most of these issues were not seen across multiple internal builds. It's possible last minute additions to 2.5.5 had an impact on various items. It sucks. We'll investigate and fix. Big changes can mean big bugs.

Please try a repair and re-report these issues if you see them again.

Is this with today's patch?

The date of the email is not very important, and it's the same e-mail for everyone. Basically, the way they're sent is staggered and mixed, hence why they might trickle in randomly across the globe. The delivery time is also painfully random due to our local post office's throughput and the since we do free shipping, we opt for one of the cheapest (and slowest!) shipping classes. Sorry for the "excuse" heavy post - but rest assured - not much longer for everyone to have received theirs :) Also- today from a hoggit post, I realized I've been somewhat misleading due to being forgetful; the white wolfpack or blue black lions shirts will not be double shipped. We only reprinted all of the grey ones (which is like 95%+ of orders). So if you only ordered one of the aforementioned, expect to only get one of ea.

This will be re-implemented ASAP. Currently the blocking item is volatile VRAM handling in DCS (all dynamic elements get loaded at start, leading to OOM issues). Cockpit labels won't change from cockpit to cockpit. Dynamic texture weathering is impossible in DCS.