Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. The code for the NWS/Antiskid switch changed in DCS. Apply the 2.35a diff.lua and any difference is transparent.
  2. 2.41 Hotfix 1 is up. This fixes some database entries and Cougar throttle code for IL-2 Tank Crew.
  3. Something simple I'd like to see on the RIO side is a binding to start/stop/reset the stopwatch. This can be very useful for buddy lasing (see the guide linked in my sig), or for timing legs on a CAP circuit. This would be especially nice to map since the button isn't easy to see without performing TrackIR contortions.
  4. "N" is for "Normal" and "R" is for "Reversed." It has to do with how the numeric keypad as UFC/ICP is mapped, with N meaning that what you press on the keypad is what you get in the sim. If you prefer the orientation to match the UFC/ICP (i.e. 1-3 at the top and 7-9 at the bottom), choose "R" and pressing 7 on your keypad will give you "1" on the ICP. If you're not sure, use N.
  5. Press your Area Track button first to ground stabilize, then you can slew.
  6. @MTFDarkEagle, I just updated my curve to better match the in-game detent.
  7. Concur. Even on exports (really, especially on exports) the MFDs are difficult to read.
  8. Looking forward to these updates. The Tomcat is far and away the best module for DCS. Just a couple of questions: 1) The skinner in me wants to know if/when we will get dynamic BORT numbers for the Tomcat and Viggen. 2) You mentioned that the pilot will not be able to control RIO equipment. Is the converse also true (i.e. will the RIO still be able to lean over to click pilot switches and screw with the pilot's ejection seat arming?) :lol: and a completely separate suggestion for skinning: can we get decals for the positions where names would go on the canopy rails? This would be great for virtual squadrons who may need to change pilot/rio combinations from time to time. EDIT: Better yet, tie the pilot/rio decal to the last BORT number like the C-101 so we can have one skin, multiple pilot/rio combos.
  9. I just uploaded a small hotfix that fixes some backlighting issues. Just run the CTS updater to get it.
  10. 2.41 is available for download. It adds the Fw190A8, F-16C, and a couple of surprises! :D There are a couple of things that should be done with 2.41: When you select the Fw190 as a module, it applies to both the A8 and D9. If you only have one or the other, you can disable an individual module on the Fw190 Values page. The WAV files have been moved from DCS to Common. You may safely remove your CTS\DCS\Sound folder. One more thing: I just want to give a huge shout-out to the beta testers who really put in the work for this build. Tackling new binding schemes and documentation was not easy, but their inputs made for a much more polished product than would have otherwise been the case for an initial release.
  11. No problem. In reviewing my docs, the reason I didn't put a gearstate check on the APU switch was to allow cross-bleed airstarts. Just be careful with the APU switch in the future. ;) In other news, the CTS host is back up.
  12. In other news, the Viper was released when 2.40 was being tested as a release candidate. I will be skipping the release of 2.40 and going straight to 2.41. 2.41 will include a basic Viper profile as well as the major changes in 2.40. I was hoping to have it tested and out today, but the ISP that hosts CTS has been down for a while[emoji2959]. Once we get the 2.41 build tested for showstoppers, I’ll release it.
  13. Make sure your APU switch is off and you should have the master mode settings enabled. I suppose I should put a logical gearstate check in the routine so you won’t get the engine crank if the gear is up.
  14. The DC area has Internet issues right now. When the ISP gets it squared away the host will be back up.
  15. Here's my Viper curve (factory detent): 0,7,15,25,35,45,56,67,78,89,100. EDIT: Revised numbers. New values correspond with the throttle actually hitting the detent in-game.
  16. Mark Bulls on your chart, draw cardinal and semicardinal headings with the local MAGVAR (usually just extend your protractor from the nearest TACAN on the chart to reference Mag North), and draw range rings using a drafting compass. From there, it's not too difficult to approximate bulls within SWAG range.
  17. That’s the one. I couldn’t remember the name and I was afk when I wrote the post. Nice thing about it is all you need to do is click on the help icon in the upper right of the script editor and it comes up.
  18. It seems really intimidating, but the structure for a simple profile is not difficult at all. For more complex profiles, more often than not you can Google C++ solutions which really widens the available solutions. Just don’t use the GUI to create a “template” profile. It’s a fool’s errand and it’s better to start with the script editor and read the TM programming guide.
  19. Planes would use blue lenses, which combined with yellow incandescent bulbs would produce a green light. So it appears the bulb is out of spec. :D
  20. All, An update to my last post. We're still on track for a September release, and the build in testing now is essentially a release candidate. However, one of the new sims supported is set to have a major patch released circa September 30. Assuming this is the case, the 2.40 release will be delayed to assess whether anything needs to change in the existing configuration. This is so users won't need to rebuild their bindings within a week for an otherwise inevitable hotfix. Again, the beta testers have been keeping me honest (take a look at the bugtracker to see exactly how honest), and the result is significantly improved over the past couple of builds. You all will be the beneficiaries of this hard work. Best,
  21. An update on 2.40: The beta testers and I have been busy getting things ready to go. The addition of non-DCS sims means creating binding imports for sims that don't support importing with the same ease of use as diff.luas. This has meant creating and testing exhaustive binding configurations, predicting combinations, and putting them all in HTML tables for people who wish to do the manual edits. During this time, I was also able to add the Fw-190A-8 Anton to the list of available DCS modules. Since the Fw-190A-8 shares many of the same parameters as the Fw-190D-9 Dora, I have updated the database so that you select the Fw-190 module if you have either the Anton or the Dora. You can then disable either module from selection in the Fw-190 Values menu (e.g. you can set Fw-190A-8 to 0 if you have the Dora and not the Anton). This deviates from the existing standard, but was necessary to keep the same variables in play while maintaining a one-to-many relationship in the database (relational database users will know what I mean). Finally, in building the Anton profile I went through the other warbirds and changed certain mappings to maintain consistency across the board. You will notice this most in the Dora and the Bf-109K-4. To this end, I also completed the high visibility/printer friendlier MFD inserts for the Bf-109K-4 and Fw-190D-9. With all that has been put into this build, we're still tracking for a September release. While I expect issues with the non-DCS profiles due to differing configurations and the instructions, we're doing our best to smooth out as much as we can to make this release as seamless as possible. Best,
×
×
  • Create New...