COLTROGUE

Is there anything I can help investigate regarding expected behavior, or is it a back end-investigation about possible cause of sim-behavior?

Further, this behavior has appeared for me regardless of ground hot/cold or air start, and regardless of stores load/configuration.

f5_engine_behavior_bug.miz f5_engine_bug.trk Edit: I realized the track attachment was INOP Engine thrust, FF, ITT, nozzle are all affected by most recent minimum or maximum stabilized throttle position. This issue has been present since DCS:W 1.5 and first became apparent during formation rejoin. Pulling IDLE after a MAX take-off to prevent overshoot on rejoin, then resetting Ng to match lead would yield reduced thrust vs the lead aircraft who pulled from MAX to cruise power (i.e. 90% Ng). In many circumstances, the wingman could not catch up using MIL power, while the flight lead was still set to ~90% Ng. In my view of the submitted track, the engines start at either parameter, with similar NG but different FF, ITT and Nozzle Position on the left vs. right engine. These photos are not from the test track, but show identical behavior at higher altitude and I believe the Dec 2018 version of DCS Open Beta. IDLE power Resumed cruise from IDLE MAX power Resumed cruise from MAX

Use the same filepath, except within the 2.1 (DCSopenalpha) installation

I'll go ahead and make the next version with the gray panel - I prefer the way the black looks, but I haven't found any videos or pictures of eagles with a black panel.

Detox, I'm working on adding in those lines and their lights right now - I'll test the ADI buttons and see, I'm guessing it's as you suspected, and if so, I'll turn them back up!

Thanks! Alcon, I'm in the process of going through and customizing the instrumentaiton and lighting a bit (customizing relative to the original mod) trying to get it a bit closer to an eagle pit, with exception of the gray front panel (Because I still prefer the black one)

Ron, it was a change to the brightness of the alpha channel. Coxy, it does pass IC.

Alcon, I took the liberty of converting this mod to a livery IOT attain IC compliance. I returned the HSI needles, and fixed the ADI/HSI bug, as well as reduced the intensity of cockpit lighting. It should work if properly installed in 1.5 or 2.1. Thanks c@sper! Edit: Please reply here if you encounter any bugs (besides the distance counter on the HSI). Feedback is appreciated. https://www.digitalcombatsimulator.com/en/files/2829090/

- Team Fishbed will win 40-18 - Team Fishbed will win 18-10

From the times I was working as C2 (or just trying to monitor 264 while some wingmen and I worked our own plans as well), thank you so much for not announcing every missile, turn, startup, etc. If everyone would ask themselves (before they speak), "Does anyone on this frequency even care at all what I'm about to announce to the world?" life would be much better for C2/GCI, and all who are monitoring. For example, Hogs and Eagles can't talk in SR except via 264 (or equivalent) so it would be good if the CAP were engaging w/n 15nm, that they announce as such so the hogs are aware. Once they've made the announcement, the Hogs can reduce their SA in that direction and focus on the strike, and they don't need to know about every missile launch, where you're turning, etc. Let C2 elements coordinate that when available, rather than tell everyone "He's banking left!" Thank goodness for SR "forcing" the use of a whisper-equilavent, and thank you to all who tried (and mostly succeeded) in using it properly. There are still plenty of people who love to tell stories on any and all freqs, but it is getting much, much better. (Thanks Ciribob!) TL|DR - keep it to 8 seconds or less, and only if there is someone on the freq who needs to know, and there's no other freq you can tell them on. Listen, instead, and focus on building SA, and all will be right with the Blues.

Yes. Absolutely. I think an installation troubleshooting video would help. The common errors being failure to unzip prior to install, and failure to check export file. *Edit: I'm <really> looking forward to the multichannel audio stutter fix, and thanks again for making this awesome tool*

This please! Octuplefire mentioned something about you folks talking about including it, and I'm looking forward to it. Edit: 1st post of 104th page...:vertag:

Outstanding! Used 1.0.6 on TAW#1 last night and it sounded great, but the functionality wasn't there from the aircraft side, just CA. A video showing everyone how to properly install, and then showing the process of connecting, will go a long way (I think) to getting more people on board. Additionally, I may have been confused in trying, but I was not able to get someone to connect to a server I attempted to host on 1.0.7; what is the process for setting one up? My attempt was to "run" the server, and then provide my public IP to my buddy, (same as my DCS server IP). He couldn't connect, nor could my client connect to my own, unless I used my local IP. I have put the listed ports through the firewall. Are there other ports to forward to use the server-side tool? Thanks for your efforts and extremely fast corrections here, Ciribob! Can't say enough how awesome this is.

+1 :)