Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. Are you trying to use your Virpil ID? That could cause a problem with the TM software.
  2. Madmatt, Sorry to take so long to get back to you on this, but I haven't been able to duplicate the error. Using the DirectX commands works fine when I test. I use TrackIR with hat switch set to trim like you have. Only other thing I can recommend is watching the stick in-game when you try to center trim. let me know if it does two down trims in quick succession instead of a quick down-trim and then center. Also, be sure you're holding down S3 while you double tap down to reset trim (I know this is what you've been doing, but it's worth emphasizing).
  3. They're quite useful with the A-10C, F/A-18, and AV-8B. Additionally, you can program them with TARGET to do other things, which can be especially useful if you also use a TM HOTAS.
  4. This isn't just a VR issue. I use a multimonitor setup with a primary monitor for the in-game display and additional monitors for display exports. Here's what Jester looks like on my system.
  5. Better late than never! :thumbup:
  6. Hi fellas, I've been super busy with real life over the last few months, with any free time I had working on (and playtesting ;) ) the Tomcat profile. Things have eased up a bit, so I can start entertaining requests. I don't yet have the MiG-19, but this is something where if there is the demand and donations I would be happy to purchase the MiG and build a profile. Here's my donation link. I will only use it for what you specifically request, and if the threshold is met or I cannot accomodate your request I will refund the amount. Best, HF
  7. I can confirm this issue with another datapoint: I have a SWFFB2 hooked up for use with the Huey, though I have FFB disabled in DCS since I use my Warthog for all others. I disabled all SWFFB2 axes for the F-14, took off, trimmed into a climb, then switched to the back seat. Iceman started a rolling dive and didn't pick up control until I give him a direct order using the wheel.
  8. Check my sig! It integrates the MFDs as well.
  9. Motivating!
  10. As RIO, you have to manually input the waypoints. They can be transcribed from the kneeboard.
  11. Unfortunately, no. The WAV player I use does not have command line volume control, and I increased the sound by 13db so you could hear the voice over jet noise when in-game. I'll have to look at this next week. I've just been way to busy with RL lately.
  12. Madmatt, I may have a workaround for you. Please try setting the TEMPO DoubleTap value to 400 instead of 350 and let me know the outcome. I'm curious to hear if it works. Here's the logic: you can DoubleTap the TrackIR commands because there is a logic flag on a 350ms timer, and when the flag is active you get a discrete actuation. With the trim centering logic, it's much more primitive in that releasing the hat activates DX32 for 350ms, and you need to press S3+H1D quickly enough again to have DX32 active when the DX30+H1D command is actuated. Since the default keystroke pulse is 50ms, you essentially need to DoubleTap within 300ms. I'll look at replacing the existing routine with a separate logic flag, but this may be why DoubleTap works for TrackIR and not for Trim Reset. Like I said, I'd really like to know if it works for you.
  13. Thanks, Madmatt. That's very helpful indeed!
  14. Thanks, Madmatt. EDIT: I spoke too soon. What I thought was a bug was simply the switch to POV when pausing TrackIR. I can actuate Trim Reset in the Options menu, though I haven't had the opportunity to test in-game. It looks like your controller settings are correct, so I'm not sure. Can you actuate in Options menu but not in-game? If so I may need to lengthen the keystroke.
  15. Issue confirmed here.
  16. I'm trying to duplicate this error, but I'll need some information on your setup. I'm assuming since you have TrackIR that you're using Head Tracking Hardware set to 1. Is this correct? Cougar or Warthog? What is your setting for TEMPO - DoubleTap (in the Timing Values - TEMPO category)? I don't think this is the issue because you can unpause TrackIR, but just covering bases. Do you still get this issue even after pausing/unpausing TrackIR? Do you start the script with the A-10C as default, or do you switch into it from a different profile? If you start with the A-10C, do you still get the issue when you switch to a different profile, load that profile, then switch back to the A-10C? If you do start with a different profile, which profile do you start with by default?
  17. There is some legacy code that wasn't updated since 1.xx that is the culprit. To fix, go to line 1832 in DCS_Global_Subs.tmc and replace CommState_Off(1,2); with CommState_Off(1,prof,1,0,1); That should fix the ejection issue. I'll have to look into the lights. I think all of what you say is by design, but it's been a long time since I coded those and they're intended to convey the scripting state rather than the state of the switches in-game (i.e. making sure the profile and game are in sync).
  18. Saw this as well. While RIO, I was disconnected and rejoined the same cockpit. I was able to mouse-click, but no controller response was allowed. I went to another plane and as pilot was able to actuate controls, but then going back to the original RIO cockpit I was still stuck with mouse clicks only. Didn't realize the controls were tied to the pilot.
  19. Nice catch. When I added the SnapView options I didn't nest the decision tree properly. This is now fixed and 2.32 Hotfix 1 is available for download.
  20. The shift mechanism is global, so there won't be any changes to this. The big reason for using S3 (other than it's legacy roots with the TM FLCS) is that you can use your pinky finger and still use your thumbs for other buttons. Applying the modifier to a thumb halves the amount of shifted commands you can effectively use.
  21. 2.32 is out. Change Log: Fixed compatibility with DCS 2.5.4.29167 Fixed station switching for VR users F-14 Tomcat: Added APU switch engine start (Warthog Throttle) Added Pilot and RIO SnapViews to Hat 3 Pilot RMFD: Switched Steering Control and lighting rows Pilot LMFD: Additional functionality Swapped Chaff and Flare positions on Throttle and MFD Warthog: Swapped TCS FOV and TCS Slave on Throttle Updated diff.luas since 2.31: F-14 Updated custom Lua: none Updated SnapViews: 2.32
  22. Nice catch. I don't use VR, so my testing it is limited. I'm in the process of rebuilding the global process, and I'll have a fix in for 2.32 very shortly. You need to make sure the logical gear state is up for the decouple to work. if gear state is down, it will default to wheelbrakes. LED2 on the LMFD tells you your logical state (on for gear down), but if you're in VR you can set the number of MFDs to 0 and get a WAV file played whenever gear state changes. Later on I'll make this a separate variable or automatically apply it for VR. That's an artifact of being unable to change stations with VR. You should have access to it in 2.32. The switch in the plane is down to actuate. This mirrors the plane even if it is counterintuitive. I may make an option to reverse it at a later time. Concur. Already done for 2.32. You really don't need an analog DLC axis since it is auto-centering IRL, and flaps are normally binary, not analog. I am open to suggestions for VR users though. I'm in agreement on this, and I'd really like to map the tailhook. I normally use the Radar Altimeter switch for the hook, but I felt it was more important to map the SAS switches that are manually disabled in ACM. I could put it on the Left fuel flow, but that switch is very difficult to get to when the throttle is forward, which is why i put it to taxi light (which is normally just set on the ground). I'm open to suggestions, as this profile is a work in progress and I just wanted to get something out for everybody to use. Thanks for the suggestion. I'll see what I can do. Glad to hear it. Thanks for the compliments.
  23. This all works with SRS. VAICOM with SRS PTT Mapping enabled is supposed to cover down on this. I'm not sure what's up, but I set it to work with SRS. For now, just mentally swap TX1 and TX2; hopefully this gets sorted soon. WRT the PTT Common, this is by design for now. It also works with the intercom function in SRS.
  24. You're welcome. You can add it directly, but just so you are aware the updated db_countries.lua will fail integrity check on a multiplayer server. That color scheme is from DCS 1.x.
  25. 2.31 Hotfix 1 is now out. This fixes a minor F-14 issue for Warthog Throttle users with inadvertent pressing of S3 with Flap Lever actuating emergency flaps.
×
×
  • Create New...