Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. That's probably it. If you use VAICOM it forces DirectX because it uses DX20 (the TS3/Discord PTT) for the "auto" channel in VAICOM.
  2. Appendix E in the Setup PDF has been updated with instructions on how to disable the Microsoft Store (which is the likely culprit in Windows 10).
  3. Since you are using a warthog, setting Discord PTT to Keyboard (scroll lock) will assign that to the Mic Switch Press (MSP), and you will have DirectX for MIDS A and B. However, you need to assign it to keyboard either in CTS or in profile selection (RCON Up or H4R), else it will remain as DX20. On the contrary, if the instructions require clarification please let me know.
  4. Version 2.46 is up. Change Log: Added SuperCarrier to selectable modules and added compatibility for F-14 and F/A-18C. Added global option to toggle SimpleRadio Overlay with MFD Hotkeys (may require SRS remapping, see Setup Guide). Improved AWACS Mode (requires SRS remapping, see Adv. Config Guide). JF-17: Fixed button assignment issues, added Air Refueling. UH-1: Fixed LDGH mapping to Master Caution (Warthog). F-14: Added "Tomcat Ball" command to Pilot and RIO HOTAS for SuperCarrier module. Fixed missing pilot commands (including LANTIRN mod). M-2000C: Changed PSM Operation selector orientation to be consistent with PCM Mode selector. Remapped NVG Stow keystroke to deconflict with engine start key. Added LMFD Routine and MFD3 profile for VTB commands. Added "Theta Up" to HOTAS to allow clearing of DO.
  5. I'll look into this, thanks. EDIT: this should be set to the paddle switch on the stick.
  6. And we willingly accept that possibility and responsibility, but what we don't like is when the model itself breaks the skin. In this case, there is apparently no longer a way to have our custom bort texture applied, and even worse, there appears to be no alpha channel so any non-grey tail looks like garbage with no way to fix it.
  7. With the new patch texture format having a single rank insignia repeated on both shoulders, non-symmetric rank insignia (like commander's oak leaves and captain's eagles) are oriented the same way. I would prefer going back to two rank insignia so we could place them in the textures as they should be oriented, but if we are to have just a single insignia, then at least the insignia should be rotated 180 degrees or mirrored for the right shoulder. Mirroring or rotating symmetrical insignia won't matter, so there is no apparent downside to doing this. Also please note that this is exactly the same bug I posted for the Huey in DCS 1.2.7. Here's an example of what I mean: I have a texture for a lieutenant commander. A lieutenant commander wears the gold oak leaves (similar to a major in the Air Force), with the stem facing outboard toward the sleeve. With the orientation the same on the right shoulder, the stem points inboard toward the neck. This is incorrect.
  8. It's legit in the USN as well.
  9. That's a bug. I'll fix it in the upcoming build.
  10. Version 1.20 is up. It applies the new texture format for the patches and helmet in DCS 2.5.6.
  11. Version 1.20 is up. It applies the new texture format for the patches and helmet in DCS 2.5.6.
  12. Version 1.20 is up. It applies the new texture format for the patches and helmet in DCS 2.5.6.
  13. So much plane porn! I love it! Keep up the good work, fellas... Edit: My meager contribution.
  14. Version 2.20 adds RoughMet files for DCS 2.5.
  15. Version 2.45 is up. This is still only supported for 2.5.6 Openbeta. Change Log: Updated SnapViews for new A-10C and Ka-50 cockpits. Added option for VR users with MFDs to force S3+LOSB1 Long for profile change (S3+T9/SPDB for cycling brake type). Added option to play lower volume WAV files (useful for headset users). Fixed blue prop selection algorithm using LSYM. Removed Hawk profile from script. Bf-109/Fw-190: Added landing gear to CH (Warthog) or H3 (Cougar) for VR users and those without MFDs. AV-8B: Added option for Warthog users to use H4P as SSw Press instead of Cannon select. F-14: Added Seat Height adjustment to HOTAS.and RIO MFD. F-16C: Added MFD4 and miscellaneous profile improvements. Combined Arms: Fixed JTAC Mode key assignments. Ka-50: Fixed and improved S2 PTT for use with VAICOM/SRS. Updated Trim Reset to Hover logic. F/A-18C: DCS Scratchpad users can now press S3+S2+ROSB20 on the ground to perform FCS Test. Added MIDS A/B support for SRS (additional configuration required). Removed CommState cycling when using S3+MicSw/CommSw to pull radio knob. Added option for Warthog users to use H4P as SCS Press instead of AIM-9 select. Added Salute and "Hornet Ball" to the HOTAS for the Supercarrier module. MiG-21: Added Radar Power switch to S3+China Hat (Warthog). Reversed orientation of landing light switch to match in-game switch (Warthog). M-2000C: Added and revised HUD functionality for LMFD. Added D2M On/Off to user-selectable countermeasure programs. Added Altitude display (Baro/Radar) select to China Hat (Warthog). Fixed RBRT INS PSM/PCN orientation and made consistent across configurations.
  16. If you set Head Tracking Hardware to 1 in CTS and rebuild the profile, the hat switch should map to trim (i.e. it automatically shifts when TrackIR/VR is enabled).
  17. I didn't put anything in for the Cougar axis (other than Idle) because it's not a hard detent. Even with Idle, I started with earlier profiles but I've been getting away from using that because it's a soft detent and I don't want people to inadvertently shut down their engine when going to idle. :doh: I keep the cougar slider at linear by default, but I would be happy to test and incorporate user curves that you guys provide. If there's support, I may do a cougar axis curve like for the warthog (i.e. using the detent), but right now I need to reduce the profile before I add more complexity.
  18. This should already be taken care of. Put your percent throttle where they meet the afterburner detent into CTS under Throttle Options-Warthog, and then it should all be built in (or at least compatible with the throttle curves included in the luas).
  19. In other news, the latest beta in testing incorporates the F/A-18C MIDS A/B voice channels in SRS. Using MIDS means that assigning a common Push to Talk for SRS across all radios will no longer be possible for the F/A-18. Honestly, this common PTT feature made a lot more sense when the modules were the A-10C, Ka-50, and FC3 and our choices for voice comms were TARS and UniversRadio. Now that SRS can handle everything DCS throws at it, Common PTT is more of a compatibility albatross than anything. I will be removing this feature in a future update and forcing SRS to DirectX buttons only, which should also free up some stacks for additional code. If this beta tests well, I hope to release 2.45 next week once we determine whether there is a DCS patch that requires last minute fixes.
  20. Pressing the button on the MFD is exactly like clicking it with a mouse. The functions are tied to the MFD button, not the TARGET function.
  21. The Warthog layout is fixed based on the A-10C radios (1 is forward, 2 is down, 3 is aft), and 2 radio setups are normally forward and aft. I allowed the offset for 3 radio setups (i.e. A-10C) with the Cougar because its comm switch is offset from the mic switch and I wanted something that would be intuitive for cougar users. I'm not sure what you are asking. Do you mean that pressing a rocker switch will change button assignments within a profile? Generally no, but sometimes buttons and switches will be reassigned based on modes. If you mean using the rockers to select profiles, then yes, it works like selecting profiles with your Cougar TMS.
  22. Great job, Eight Ball! That saved me a lot of time. I wish there was still a way to rep people on this board!
  23. With regard to your specific question, the greyscale portion of the RoughMet you build in the template should be copied to the green channel in the actual RoughMet file you will be using.
  24. Thanks for the detail; that really helps a lot and I'll zero in on the Cougar routines. So does this only occur on the F-18 during GearState transition, or is it also when you press the comm switch to activate the CommState routine?
  25. LEDs are the least stable operations with TARGET. Stuff like what you describe is often fixed with a reboot, but if it is consistent, then for now try setting "Allow Flashing MFD LEDs on Transitions" to 0 (it's under Global - LED/Lighting Options). If that doesn't work, go to -1 to disable all LED indications. I will look into the Hornet in particular since this doesn't appear to happen with other modules.
×
×
  • Create New...