JCofDI

Download the DCS Detent Calculator Spreadsheet by JC of DI on the User Files site: https://www.digitalcombatsimulator.com/en/files/3315617/ Hello all! I created a way for folks with afterburner detents to easily generate custom user curve numbers so that the MIL location of their aircraft perfectly aligns with their throttle detent. My original creation was in the computer language I am most familiar with - Microsoft Excel. Fortunately, one of my first testers was community member Bailey who has made several fantastic apps. Bailey's testing help expanded into a full collaboration, turning my calculator into the standalone program that you see posted above. The utility has been tested with multiple controllers and multiple detents. In the User Files download you'll have both the standalone and the original Excel versions of the calculator that you may choose from, as well as a ReadMe that shows how to find your physical detent location and generate the numbers that you will put into your DCS axis profile. If you would like to check out the code, head over to Bailey's GitHub here: https://github.com/asherao/DCS-Detent-Calculator Also, find more of Bailey’s work on the DCS User Files site. https://www.digitalcombatsimulator.com/en/files/filter/user-is-baileywa/apply/ Feel free to reply in this thread or reach me on Discord, username `@jcofdi`. Thank you very much for your time. Enjoy the flights! – JC 5/22/01 - Thank you so much to everyone who has tried and shared the Detent Calculator so far! The v1015 update now available on the User Files site completes the work done with the help of users in this thread to include options for inverted axes, x saturation, and deadzone changes. These options are currently only available in the Excel file and the new Google Sheets document, created to allow wider access to those without spreadsheet software available. 10/30/22 - Thank you to everyone who have shared and used this tool! My algebra professor would be ecstatic to know that nearly 2,000 people have downloaded something I made using y=mx+b With DCS 2.8 came some changes to the axis tune window which made the detent location much easier to determine. This change spurred me to also release some further requests such as the Mirage-F1, the AH-64D engine lockout range, and some updated values for the AJS37, F-16, F/A-18, and JF-17 to help the MIL location map a little more closely. These changes are only available in the spreadsheet versions of the tool currently. 7/9/23 - Thank you to everyone who reached out and encouraged me to update this for the F-15E. I have taken the opportunity to understand the detent special options supplied by Razbam for the F-15E, M-2000C, and Aerges for the Mirage F1. With these changes I have also made the hard decision to no longer include the software app by Bailey as part of this download. I want to thank Bailey again for the time, knowledge, efforts, and resources provided to me during the previous versions of these releases. With being a code dunce I just can't keep up the software side myself, and so the differences between the two I feel just leads to confusion for new users and offers nothing to users returning to the software for the latest airframes or changes. Thank you also to everyone who continues to support this little spreadsheet nerdery of mine - over 3,000 downloads on the User Files site, a how-to video by OverKill Simulations, and a repurposing of the data into a browser-based tool that reads your throttle position live by Zweihander are just a few of the highlights that I couldn't have imagined when I first made this.

While still something that would be nice to have in-game, I created a spreadsheet to address this issue and Bailey helped convert the original idea into a handy software utility. Takes the "trial-and-error" out of setting up your detents. Hopefully it helps. https://www.digitalcombatsimulator.com/en/files/3315617/

Certainly not the most critical issue, I know. However, I noticed that the Viggen has an automatic EQ effect applied to the tape player while the F-14 does not. Will this automatic EQ effect be added to the Tomcat as well? Or perhaps a special options toggle for those that would like it or not. See the video for a quick comparison using the same audio file (Song1.ogg from the Viggen walkman folder.)

Thanks for the response, BN. I believe that the issue is a full tanker-wide issue however. Here's a KC-130 exhibiting the same results, caused using the same steps. The unpacked mission file again shows the "System" flag set to 4 with this KC-130. Thanks for your time.

Did some further testing inside the mission file of the unpacked .miz today. I noticed that the only notable difference among the "Activate Beacon" section appeared to be the "system" flag. Here's the full portion of that action from "TCNTestED" in the first post. This tanker gives correct range info on the Y mode. Notice that the `system` flag is set as 5. ["id"] = "ActivateBeacon", ["params"] = { ["type"] = 4, ["AA"] = true, ["callsign"] = "TKR", ["modeChannel"] = "X", ["name"] = "Action Created, No Unit Ever Set", ["channel"] = 40, ["system"] = 5, ["bearing"] = true, ["frequency"] = 1127000000, Looking at the section for the tanker on channel 1Y which did not correctly broadcast range, I noticed that the `system` flag was set to 4. With changing no other variables I set this flag to 5 and repackaged the mission, which correctly gave range info on channel 1Y. Conversely, I can put the system flag to 4 on correctly working tankers and they will exhibit the same "Default to X" mode behavior on their respective channels. The attached .miz is of the same mission as the original post, with only the system flags for each tanker set to the "opposite" of what it was in the original mission, and the results are likewise exactly opposite. 1Y is the only correctly behaving tanker in TCNTestEdit, while 37Y and 40Y only show range info on the X TACAN. Hope this helps. TCNTestEdit.miz

TCNTestED.miz I've included a mission featuring three tankers to represent the stages of this issue, and in this case have only adjusted the "Unit" option, but this bug occurs when adjusting Channel, Callsign, or Unit on this panel. Regardless of the Channel Mode setting, changing any one of these options in the TACAN options will force the Channel Mode to X while it visibly remains on Y. Checking the unpacked mission file from the .miz, "modeChannel" appears to remain on Y for all three tankers as well. While the below uses the Unit option, the same trick to re-enable it applies for all options in my testing. - In the mission for Tanker "Aerial 3" I set the Channel to 1Y, then assigned Unit to "Aerial-3-1". When loading the mission, range info will only appear on TACAN 1X despite still showing as 1Y in the panel. - I similarly changed the Unit on "Aerial 4", which was set to Channel 37Y, but after unit selection I toggled the Channel Mode back to X, then re-selected Y. It now broadcasts range correctly on channel 37Y. --- I also further tested 37Y by changing the unit back to the default "Nothing," and it would again only broadcast on 37X until I toggled the Channel Mode again. - Lastly for a control I changed the Channel to 40, then set mode Y for "Aerial 5" and did not set a unit at all. This tanker correctly broadcasts range on 40Y upon load. I'd be happy to provide any further details. Thanks for your time.

Hi all, Likely not urgent, but given that it's an issue that would most likely would affect new users I thought I would share this small bug. In the third Mig-29 training mission which covers BVR missiles, there's a missing trigger action on message 9. At this step the player should use the spacebar to fire a missile at the incoming enemy, but in order to do so the trigger action "Stop Wait User Response" needs to be added. This can be replicated by playing the original training mission, and at the step when the "Fox 3!" message plays the user will be unable to fire using spacebar. By either adding the mentioned trigger action on message 9, or using the included miz file I've made with this change, you will now be able to fire the missile. The "(Start/Stop) Wait User Response" trigger action only affects the spacebar action, so any hotas/controller users won't be affected by this issue. This was tested on 2.5.6.58125 Open Beta and 2.5.6.55960 Stable. Due to size restrictions on the forum I have included the working mission as a Google Drive link below. Thanks. MiG29S_-_3_-_BVR_R-77__R-27ER_-_Missiles-TriggerAdded.miz