fat creason

The nozzles are commanded open when throttles are at IDLE and WOW is signal is detected. Pretty sure that if you shut down in the "incorrect" order, both engines will close their nozzles since the WOW circuit is only powered by one side. Can't remember which one at the moment.

We go with SME input whenever possible, there are no plans to change it at this time. There are several videos out there showing that full Zone 5 light-off takes at least 5 seconds, in some situation much more, and the time it takes between engines can vary quite a bit.

We have no plans to change anything about the afterburner on the simulation side. The amount of time each takes to light is dependent on various conditions such as airspeed, altitude and various engine states.

Next major one will be a performance update that will hopefully be one of the last. There will likely be additional handling adjustments after that based on SME feedback, mostly in the landing configuration.

All FM work is being done in another branch that will be merged in all at once when it's complete.

Probably like 2 months, but don't take that as an absolute timeline, it will depend heavily on how much time I can devote to it.

I have no idea on that. We really don't have any control over replays and all that stuff is just linked to standard animation arguments. There's nothing special we do to make replays "work" per se, that's all handled by the DCS engine.

No. Don't expect this to show up anytime soon. I'll post here when it's getting close.

Yep. You can run two instances of DCS on your own machine (one server/one client) and get the same thing. That's how all the big trailer/movie makers do it.

IMO that is a crazy reason to not own the Tomcat, but I'm biased

Ask ED about this one, it comes and goes with no changes in our code.

If you want consistent replays for cinematics, I recommend using server tracks since they just play back physical data instead of the deterministic method used on single player tracks. Ideally the replay system should have an option of which type you want to use. Ask ED for that feature, I can't imagine it would take a lot of time for ED to add since it already exists for servers.

This is correct. You can hear us talking about the replay system here. It might be caused by some type of memory related issue and will likely be extremely difficult to solve, but it's hard to say. We have practically no control or insight over how the replays record and how they play back. Time has already been spent (read: wasted) looking into this, and we effectively made no progress. Based on that experience, the probable large amount of time/resources required to actually fix it effectively pushes it far down the priority list. Otherwise we wouldn't be able to spend our very finite resources on delivering the remainder of the F-14 package and fix more pressing bugs whose resolution takes fewer resources. We won't forget about this one, but we can't commit a large amount of resources into further investigation at this time. This is all assuming that it's something we can fix ourselves and not a DCS bug beyond our control. The jury is still out on that one, as of now we don't see anything we're doing to directly cause the problem.

We've asked ED to make it possible to modify more sound parameters real-time in the code rather than using fixed values set in the sdef files. The current engine whine sound cone angles are sort of a compromise in that regard. There are several things we'd like to do but simply can't for now.

I would generally refrain form testing until you see the patch notes saying that we updated the drag/thrust etc... Only difference right now is the fixed partial deployment of the maneuvering devices. Once drag and thrust are fixed I'll show some plots or videos that prove it, but you don't have to take my word for it if you don't want to.

Like I said, we'll take a look eventually but can make no guarantee on the outcome. A large amount of time was spent on this (not by me) initially to prevent strange deck behavior, but this was early on in DCS carrier ops, pre-Hornet. Things may have changed regarding deck physics that ED has not informed us of.

They also don't operate on carriers. We're limited to a handful of parameters provided by ED that we can adjust.

Will take a look eventually but can't make any guarantees on the outcome. A lot of the current behavior is a compromise for deck handling.

More landing config handling changes are coming too, just after I can get this performance and drag re-do finished.

Crap, I just realized I copy pasted the wrong flight model from FMs.com, it's really a 757! Been fooling you the whole time!

Pitch with power will be increasing. Our SME says there's not enough.

Crap! I took the bait! Was not taking into account the poster when I wrote that.

If you come into this thread armed only feelings, you're not being helpful at all. There are maybe 2 people in this entire thread that have contributed to any type of real discussion.

The MCB and bleed systems are entirely separate and have nothing to do with each other.