Jump to content

Home Fries

Members
  • Posts

    3507
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. Version 2.66a (hotfix 1) is released. Change Log: Fixed profile crash using HOTAS Cougar with modules using DMS for SnapViews. AH-64D: Added Trim Reset to S3+H4U/H4P. JF-17: Mapped altimeter setting to S3+LGAIN and remapped flood light to MFD3 S3+SYM Mosquito: Set radios to mimic F-14 (2 radios and intercom) with SRS and Warthog Throttle. M-2000C: Added radar mode commands back to Warthog throttle base. Added Aux Gunsight Elevation to MFD3 S3+GAIN Updated bindings since 2.66: AH-64, JF-17, M2000C Updated SnapViews since 2.66: none Updated Custom Luas since 2.66: AV-8B, F-14, UH-1H
  2. It's in. I just need to test a mosquito fix and it's ready to go.
  3. Let me review the T-45 code and get back to you. EDIT: found the issue. It will be fixed in the next patch.
  4. Working on the USAAF 653rd Bombardment Squadron. This is a weather recon bird, based heavily on NS521 at the USAF Museum at Wright-Patterson AFB. This does, however, have dynamic borts to allow for a fleet. EDIT: This contest entry is now a skinpack of the 25th Bombardment Group (Reconnaissance), with three similar skins with varying degrees of invasion stripes, all based on historical aircraft. Mosquito FB Mk.VI Skin Pack: USAAF 25th Bombardment Group (Reconnaissance) (digitalcombatsimulator.com) Here's the original at WPAFB: and here's the work in progress (Edit: updated base color and weathering): And a custom pilot livery with USAAF browns and A-6 boots. And the new aircraft in the skin pack:
  5. Purple in this case equals to "George AI." Normally italics are long press.
  6. The two "issues" are related. First, the MMCB is nominally the VR Zoom in VR, and the shifted functionality is what is listed on the control scheme. This isn't universal yet, but I try to make it as consistent as possible. I'll be sure to add this substitution to the HTML guide. Second, S3+S1 Long should put you in AI control mode with H3 doing WASD, and S3+S1 Short should put H3 back to the Symbology switch.
  7. Ok thanks. I use Win10 and American English as well, so that at least kills the theory.
  8. That's exactly what's happening. Somehow the EXE is missing the section that it's supposed to populate to. The order matters. I have no idea why this is happening. Someone had this happen earlier. The best we could determine was a language option with Windows 11, but we were never able to resolve the issue for sure. Now that we know this is the issue, what OS are you running, and what native language are you using? EDIT: In other news, the server is back up. I think I solved the long term problems as well.
  9. I keep mine on a separate drive and it works fine. As long as TARGET is installed to the default folder, you should be good to go.
  10. Until the server is back up, I've posted the files on my Google Drive. Just extract the zip files to your CTS folder and they're nested properly to go to the folders they should be in. The version.txt will let you compare existing files with the updated files to see what needs to change (if you don't want to do a complete install). I didn't realize there's a trim reset. I'll make it happen for the next version.
  11. Sorry folks, the server is down right now. I'm trying to find a more reliable solution. @Zomalk, regarding your questions, I'll see if I can answer them for you, though Kisi and Tomeye already did an admirable job. First, so you're clear, this is a TARGET profile. This means that TARGET (the Thrustmaster programming environment) suppresses the individual controllers (e.g. Warthog Stick and Warthog Throttle) and in lieu of that you should see either "Thrustmaster Combined" or "Thrustmaster Virtual Game Controller" (if you have admin privileges). The diff.lua files are designed for use with these virtual controllers and the keyboard, and in some cases the extra (third or fourth) MFD. Regarding the value you discuss, "Custom Controller LUA for F-14," this does default to 0 because I don't want to have any mods (custom files) tied to default settings. If you don't have the Tomcat, you shouldn't have any need or want to change this. The error you're getting may be due to something else. If you are still getting it, please post the DCS_World.tmc file you compiled with the CTS software. Finally, TARGET script editing is not necessary to enjoy the profile. The whole reason for the front end and the database is to allow you to customize your settings without having to edit a line of code. That said, if you do know your way around C, it probably woulldn't hurt. If you find a bug, please let me know what you found and I'll look into it. I can't promise a quick reply in the near future (I'm extremely busy until March, and then only very busy until May), but I try to be as responsive as my schedule allows.
  12. It's under the throttle control for individual helicopters or Russian helos. Set it to -1. If you look at the HTML change log, it's hyperlinked to the right values and shows you a table of mappings and which helos are supported.
  13. Version 2.66 is released. Excepting hotfixes, this will probably be my last update for a few months. If the F-15E or F-4 are released before April, I'll see what I can do, but it won't likely be a quick turnaround. Change log: Mosquito: Added Rocket functionality. Changed individual magnetos to dual-magneto macros on LMFD to make room Added Bomb Bay controls to Cougar TQS JF-17: Fixed diff.luas Added MFD3 overlay Helicopters: Added option for Warthog Pinky Switch to actuate external lighting instead of throttle axis control Ka-50: Fixed pinky switch not commanding non-discrete throttle Known Issues: None Updated bindings since 2.65: Mosquito, AH-64, Mi-8, Mi-24, UH-1, JF-17 Updated SnapViews since 2.65: both (BS3, Mosquito) Updated Custom Luas since 2.65: none
  14. Ben Sorry it took so long to get to this, but I finally got to look at the profile. The 2MFD variants were way out of whack. I just fixed them and they'll be in the next release in the very near future. I've added your feature request into the next build, and also incorporated it into the AH-64, Mi-8 and Mi-24. For each of the helos, set the discrete throttle option to -1. The new build should be out shortly.
  15. Possible write error. You may want to rename your existing folder to something else and then reinstall. Unfortunately, my server is down for a day so it will have to wait.
  16. Version 2.65 is released for DCS 2.8.1! Change Log: Ka-50: Updated for DCS 2.8.1/Black Shark 3 M2000C: Updated for DCS 2.8.1 Added discrete state to FBW Spin switch Added TDC Mode to LOSB19 (Cougar) Known Issues: None Updated bindings since 2.64d: Ka-50, M2000C Updated SnapViews since 2.64: 2.65 (BS3) Updated Custom Luas since 2.64: AV-8B
  17. Glad to have you onboard, Diz! For everyone else, we're recruiting for all of our airframes, and not just the F-14.
  18. FYI, today's patch breaks a good number of switch toggles in Black Shark 2 in favor of discrete switch settings. I will get to work on updating the Ka-50 profile for both BS2 and BS3, but in the meantime you may need to use the mouse if a toggle function is not working. My goal is to get this taken care of this weekend and have a new release next week, but no promises.
  19. 1) You can't, and 2) no it's not possible. It's a possibility for version 3, but when I started this I had originally envisioned the use of MFDs for shortcuts and the rockers as backups. I recognize that VR changes things quite a bit...
  20. Even with the Microsoft Store fix, I still get this on occasion. Just stop the profile, unplug/replug your stick, and try again. Lather rinse repeat until it works.
  21. Version 2.64d is released. Change log: Updated CTS database to add Switch TEMPO value @tomeye if you don't want to do a full download, go to your CTS/DB/version.txt file, find the following line: http://<ip>/TARGET/CTS/CTSscript.zip 2.644 and change the number to 2.643 (or anything smaller than 2.644). That will force re-downloading the modified TTM file without going through the full download.
  22. After investigation, I remember what I was doing. I was adding SwTempo as another tempo for switches with a TEMPO Long On, TEMPO Short Off button mechanism, where DefTempo seemed to take too long. This was mainly for the hardpoint select on the Mirage F1, but I backfitted it to the DX macros without adding the variable to the database (it's still manually input on my dev build). I'll add SwTempo to the database and upload a hotfix.
  23. Thank you both for the report and the fix. I'll put it on the bug tracker and investigate.
  24. Version 2.64c is uploaded for DCS 2.8.0.32937. Incorporates 2.64b and updates the AV-8B custom lua for the latest patch.
×
×
  • Create New...