JCofDI

Hat in hand - this issue appears to have been a result of me running a mod to "increase cloud quality" that I forgot I had even enabled. (The graphics files have an unselectable quality one step higher, the mod just re-enables that as part of increasing view distance.) I stepped back to the default highest cloud quality and the issue is gone. Thanks again for the mod, and sorry for the false report!

A few Hornet shots I've taken lately.

Not dismissing that other people aren't seeing it, just sharing screens to help show it. Two visible "seams" to the cloud layer looking different directions. Information bar included in shots to help narrow down location/direction to look. Also included a screenshot of the Mission Editor setup for any further setup parameters that might be needed. As mentioned, it's far less apparent than the shot I originally quoted, so if this lesser example is expected or normal that's okay with me too, just appeared at first blush like the sort of thing that was being requested. Edit: also meant to add, I run zero motion blur inside of DCS.

I was using Cirrocumulus 3 on a sunrise Kola flight and saw the same sort of issue in the top layer there, but not nearly as severe as that photo. Didn't think to grab a screenshot when I was on but can get it next session if needed. Fantastic mod by the way - thank you! Looking forward to those 2.1 cirrus clouds!

Thanks for the reply. Are you able to share a screenshot of what you're entering at the left? Also, could you confirm if you're using the local spreadsheet or the Google Sheets version? If able to try the other method, do you get the same results in each? At this point the only thing I can think is that it's an older Excel version causing issues with one of the formulas, but if you're using the Google Sheets version that wouldn't be it either. Sorry for the frustration! If nothing else, feel free to give me your exact detent location and I can share the correct user curve.

@i_am_lugnuts Glad to hear you got it to work out! Sorry for the delay in getting a new version out, but I actually just finalized the newest version tonight to include the F-15E and have updated the download page and first post accordingly. With a Thrustmaster Warthog you may be able to just use the Special Options, but otherwise using your proper Detent Location should get you all sorted out. Thanks for the interest! @WinOrLose Interesting results. If you're still having issues, would you be able to share what your User Curve looked like with the Mig-21? My Warthog throttle has a detent location of 31 which seems similar to yours and my numbers were as shown below. With this user curve my A/B kicks in just over the detent and the remaining post-detent range just controls how hard the afterburner runs. With a Warthog, be sure you *don't* have the inverted checkbox marked with an x, and you should only be adjusting the X Saturation and Deadzone settings on the spreadsheet from their defaults (100 and 0 respectively) if you also adjust those settings inside DCS (which I don't believe a Warthog should need).

Thank you for the compliments, Bucic! This is starting to get a bit out of my wheelhouse as I'm no hardware guy, but it ultimately depends on how the hardware is designed to report the range. I can at least describe how DCS interacts with the hardware I am familiar with and go from there. To compare it to throttles on the market, you can set it up the "Warthog" way, or set it up the "Virpil" way (credit to Virpil, newer software lets you customize even this, but for sake of discussion we'll stick with it). The Warthog has a fixed idle detent that reports at 0% once you're resting against it, and as you lift up over that detent and travel backwards to the OFF range (which reports as a button when fully in the OFF position), the axis simply remains at 0%. I believe this is the ideal way to manage a detent since in-game "0%" typically just translates to "Idle, waiting for cutoff command". The downside is that this is less customizable so if a module were to show that OFF range accurately, you wouldn't be able to model it appropriately. The "Virpil" method, prior to software allowing you to set axis-buttons based on hardware position, meant that you had to use a range of the throttle as an axis button to fire the DCS OFF command. You don't want to be pressing toward idle and accidentally fire the command to shut down engines, so the typical setup for a Virpil throttle with an idle detent that rests at 5% of the range would be to set a virtual button in the 0-3% range, then in-game set a deadzone to match your idle detent location of 5%. This method certainly allows for more customization, but it's just more complicated as there's more items needing to be adjusted to make it all work properly - particularly with a split throttle arrangement. Once you get the hang of it though, it's perfectly suitable. Now, for the DCS calculator portion. With the "Warthog" method, you have no in-game deadzone to adjust as 0% on the hardware is 0% in-game, and you just have cosmetic travel range in the real world - for the calculator you wouldn't need to touch the deadzone from the default. With the "Virpil" method, you would enter the deadzone in DCS as 18 (as 18% is where you are at 16 degrees and idle, so it's your new "zero") and the DCS calculator would need that 18 deadzone that matches your axis-tune window. Cool project, and good luck with it! (As an aside, the new Virpil method which I use allows for it to mimic that Warthog style - where you can make the idle-detent your actual 0% of the throttle range and still assign virtual buttons at axis ranges below the detent using the hardware reporting values. Makes swapping to something like MSFS which doesn't easily handle the deadzone method much easier.)

Thanks for the kind words @GK61! As Trigati notes, the spreadsheet has some updated values with the most recent release. Every time I've dabbled in computer code I end up as confused and broken as the results I make The app version won't be wrong per se; it has the initial values I used which were when the engine actually was in afterburner. However, there was some confusion that this location was sometimes visually past a detent in-game despite not being in afterburner, so the newest version in the spreadsheets align the calculated detent location with the in-game detents.

Hello all. I recognize that the overall behavior for the paddle switch with our model of Tomcat is correct (that paddle depress moves the SAS Pitch/Roll switches to OFF), but from reading the manual it notes that on the AFCS panel all switches are held by a solenoid, and springloaded to return to the OFF position otherwise. The current behavior in DCS is that the STAB AUG Pitch, Roll, and Yaw as well as the AP Engage switch can all be placed to ON while cold and dark. Also while cold and dark, pressing the Emergency Disconnect Paddle still switches the Pitch, Roll, and AP Engage to OFF. See the below GIF, taken in a cold and dark jet with no power source, with switches remaining ON from initial click and then flipping OFF when paddle is pressed. From this I have two questions: 1) Is it accurate that these switches are able to remain ON when the jet is unpowered? 2) If (1) is accurate, is it also accurate that the disconnect paddle is linked to these switches in a way that allows them to be flipped OFF when in an unpowered state? This may ultimately not be a bug, but after someone brought it to my attention I've been very curious what the actual switch mechanisms are that would permit that behavior. Any insight provided would be fantastic. Thank you!

Wags' videos on the GBU-24 advertised an increased standoff range for both the Hornet and the Viper. From the May 28, 2022 Viper GBU-24 video: `the GBU-24 also uses a 2,000 lbs. class warhead, but it has a much more advanced autopilot and larger control surfaces that allow a greater standoff range of greater than 11 miles.` If the DCS laser range limitation is ~8 miles - how should we best go about achieving this greater standoff range - or has the standoff range understanding changed since these videos? Also, I know it's unlikely but I feel the need to ask - are you able to provide a public reference which suggests the GBU-24 needs a laser track at the point of launch? Lastly, the only thing I could find in the patch notes around this report indicates it might be related to this line: `Fixed: Code for the GBU-24 is incorrect.` Could you clarify any specifics around what this correction was if it does relate to this topic?

Hello all! This has now been updated to v1017. v1.017 – Updates in this release only apply to the Excel and Google Sheets version. When Software is updated, will post a new version. ReadMe updated to reflect new axis tune page in DCS 2.8. Added: AH-64 Lockout Detent Added: Mirage F1-CE (The Idle/cutoff behavior was requested, but was not consistent enough for me to work out how to best make a curve for it, so this is only MIL & AB values.) Updated: <Aircraft/Old AB Value/New AB Value> Updated: AJS37 Viggen 18->20 Updated: F-16 Viper 20->24 Updated: F/A-18 Hornet 23->25 Updated: JF-17 Thunder 8->16 To download, visit the User Files link. Thank you all! https://www.digitalcombatsimulator.com/en/files/3315617/

If you check your DCS.log file after said black screen, you'll see that once the textures load in that it is in fact getting flagged by IC which is why it doesn't load. Barthek himself confirmed it no longer passes IC unfortunately. It's a fantastic addition though, and OVGME at least makes it easy to use it when flying single-player.

I'm having the same issue. No other texture mods, tried adjusting some settings, no dice. I get a bright white flash that shows the UI at the bottom, then it's a fully black screen with no sound.

I'll be happy to add the Mossie! For right now, from some quick testing, you can use the Su-27/33 page to get pretty close to where the RCtrl+Enter overlay shows the second stage starting, and it "audibly" lines up with my WH detent in practice. The automatic finger lifts of the module currently have me questioning how far you could really get on the throttle without pressing them at all though - as they start to lift about 10-15% before the visible "gate" portion of the axis - so I may hold off on updating the release until those function. Alternatively, if someone can find documentation that would otherwise show where it should be I'd be happy to use that as confirmation of the placement as well. Thanks!

Adding a vouch for DiCE to edit countermeasure programs, the F-5 RWR Fix, Vaicom Pro for adding a more natural control option for radio interactions, Helios for view export customization, and the Mirage 2000 serval lua file to edit the RWR display as suggested by the developers. Hopefully some avenues to enable these in some fashion are opened up soon.

V1015 is now on the User Files site which has options for Inverted axes, X Saturation, and Deadzone changes on the spreadsheet version (still learning to code so that I can update the software version as well - Coming Soon). I've also added a Google Sheets link to the download so spreadsheet software is no longer required to use that version and also ensure the new options are available to all. Do note that a Google account is required and you will need to use the "Make a Copy" feature in order to customize the calculator to find your custom User Curves. Please feel free to reach out with any issues or feedback. Thank you all - enjoy the flights!

Thanks a bunch - haven't had a chance to catch up on all the posts since release so apologies for the repetition. Too busy flying the Goshawk I guess

Loving this mod! Fantastic work by the VNAO team. Hoping to use it to get more folks in to try it out - is there a way to bind throttle increase/decrease to buttons or keyboard keys? I didn't see them in the bindings by default, but it's how I usually set up planes with an Xbox controller if I'm trying to map it for someone with no Hotas access.

@LanceCriminal86understandable! It's a good line of reasoning but the way DCS auto-smoothes its curves (put one at 100 and the next at 50 and see how it overshoots then corrects), it can end up making situations strange to adjust only one point when we're talking about only one or two percent differences. Also worth noting that with the detent at 26 it's kind of in the no-man's-land between the 20 and 30 sliders, so if just doing singular adjustments to the sliders I'd recommend alternating movements between the two instead of just sticking to one. Hope that's good to set you towards finding your sweet spot!

@zildacGlad to hear it's back to being bang-on for you! Could not have done it without your help on how inverted and idle detent things were set up, so thank you again! Any other issues please let me know! @LanceCriminal86 Thanks for the kind words and detailed post! Strange issue - I've tested it with the newest patch and the A/B location for the F-14 hasn't changed, so the curves should be accurate if your detent location is in fact 26. Is this detent set up for both left and right throttles, and do both throttles equally touch off burners in this way? If there's a lot of "travel" through the detent you may want to set it later rather than right up against the "start" point of it. Another way to think of the detent location number is that it should be the last position right before A/B lights off. Jostles shouldn't be causing it, but if it's a big enough bump to travel another percent then that indeed would be doing it. For that reason in the initial testing, some folks did find it preferable to add some cushion to their detent location. Usually subtracting 2 from their calculation was enough to work out for them. From the FAQ portion of the ReadMe: Reducing the detent like that as you suggested won't change the entire line much, but it may smooth it out enough to match up with the detent and still not be as touchy. Please let me know how it goes.

@zildac Took a bit longer than I intended, but here's the latest rework! Absolutely no rush but if you have a chance to test it out feel free. I believe the idle deadzone issue will still exist based on how the Virpil deadzone exist - I can only unfortunately work with what DCS gives me on that front . The latest version has a Saturation and a Deadzone input. Short explanation is that deadzone will always remove from the left side of the graph, while saturation will always affect the right side of the graph. One thing to try may be finding your "DCS" value of the idle detent the same way that the MIL Detent location is found, then inputting that value as a Deadzone. Anyone is free to give it a try. Made some "UI" updates as much as Excel can but previous warnings about working copy still applies . IMPORTANT NOTE: The previous "Detented" column is now just used to build the graph. Please use the "User Values" section below the graph to input the curves and it should be a 1:1 input.

@zildacGlad to hear it! I'll keep fine tuning now that I know I'm back on track and hopefully get you right on-lock for that detent again. Hopefully by this time tomorrow I'll have a new version of the sheet to break horribly test. I think the last thing I need to know would just be making sure I understand the idle/off detent. It's set up in the VPC software to use a "range" of the axis to fire the "off" button, right? Do you set that range in the software using a percentage of the throttle axis? (For example: 0-5% range = Hold "End" or a similar setup?) Or are there already physical buttons past the detent like on the Warthog?