Jump to content

SGT Coyle

Members
  • Posts

    1388
  • Joined

  • Last visited

Everything posted by SGT Coyle

  1. I'll give printing one a try. If it comes out I'll post file here.
  2. Thanks for the backup. I've been going through all my .ttm files looking for duplicates. In a few cases I had already started editing out USB scancodes all together.
  3. Right out of the box, the Warthog Stick and Throttle have DirectX (DX)buttons assigned to it. You'll have to assigned those available buttons to controls in game. Since I haven't relied on those basic settings in years, I'm more than just rusty on the particulars of where the config files reside in the game folders. I use TARGET Script Editor to map my controls. I'd be happy to offer my script, but it would be way to complicated for a TARGET beginner, but I'd be happy to help you get started.
  4. Sure. This is an example of an SE script that worked fine a couple months ago. Viggen.7z
  5. Well I might have posted too soon. It seems that any .tmc command that calls a macro defined with a USB scancode throws a compiler error. This is getting frustrating.
  6. Lange_666, I recently found my macro generator was assigning defines of WIN key modifiers to default USB scan codes as "L_WIN". Deleting all WIN key references in macro file got rid of "Define Stack Error".
  7. Don't know what it was, but redoing it seemed to work. Found that automated Macro File Generator was placing "L_WIN + " as a modifier. That was breaking any USB[0x] commands.
  8. Contact Thrustmaster about getting a replacement main board. It'll probably cost a bit. Check to see if electronics are covered on your home owners policy. Check this out: http://ts.thrustmaster.com/faqs/eng/thr_eng_00140.pdf
  9. How many waypoints can the Harrier take in a mission?
  10. Anyone know what causes a Define stack full error in the compiler? I got this "Compile Error define stack full in TD_Functions.tmh at line 255", and I have no idea why. [color=#1e90ff][b]int[/b][/color] Cat_Hookup() { [color=#1e90ff][b]if[/b][/color] (Bar_Down >[color=#ffffff]0[/color]) { ActKey[color=#ffffff]([/color]PULSE + KEYON + Catapult_Hook_Up); <- [u][b][i]This is line 255[/i][/b][/u] Bar_Down = [color=#ffffff]0[/color]; } [color=#1e90ff][b]else[/b][/color] [color=#1e90ff][b]if[/b][/color] (Bar_Down < [color=#ffffff]1[/color]) { ActKey[color=#ffffff]([/color]PULSE + KEYON + [color=#ffffff]0[/color]); }
  11. It could be a Keyboard Rate issue. The encoders are pressing and releasing the keys to fast. I've seen that with some button presses on the Hornet a few updates back, but it's fixed now. Are you using any Virpil software to program keys or buttons. I use TARGET with my Warthog and I can set a custom "KB Rate". I had to do that to fix the a fore mentioned Hornet issue.
  12. Can we get the ability to hide warning lights on either side of the UFC? This request falls along the lines of hiding the stick, throttle, and pilot when we get that.
  13. looks awesome.
  14. Anyone done a progressive output on a button press? I want a key press sent on a held button press that gets progressively faster the longer it’s held. Like adjusting the time on an old digital clock. I like this for flipping through kneeboard pages
  15. Steady progress is always welcome.
  16. Yes, I disabled mouse and hand controllers in DCS Settings. Comms is navigated by looking at selection and left clicking. I don't want to use the mouse in VR. I wanted a way to make interaction with cockpit as seamless as possible, and trying to manipulate a thing on a thing, was not really going to make life easier. On the WartHog you can easily turn the mini stick into a 4-way hat that will do the same thing, but I like that for TDC and such. Thanks, If anyone wants more info send me a PM.
  17. Check this Not exactly pretty, but it works.
  18. Make "De-coupling" an option. I like love the coupled mouse cursor. I made a little, four button control pad I attached to my throttle. Right, Left, and scroll Forward/Back mouse buttons. Works like a charm, and I can't play VR without it. "Quality of Life" changes should include more options for the player.
  19. How about bridges? Seems it can see a river. It should be able to see a bridge.
  20. What controller are you using?
  21. Can Scratch-Pad capture BRA calls and JTAC transmissions directly? Or can the player copy and paste those messages( or any part) into Scratch-Pad? I've had this loaded in OB since pg 8 but haven't had time to play around with it till now. So I'm late to the party, but better late than never. This is simply brilliant and free beer for the author.:thumbup: and all those contributors. You guys should get together and organize this into one mod github. Brilliant! Just freaking awesome.
  22. Ipad compatible?
  23. Anyone got a image resolution that works best for VR?
  24. I don't have a view directory or any "view.lua" or any view anything, but I do get intermittently this zoomed in all the way, on spawning in. I think only in 2D, not VR. But VR your moving your head around prior to spawning in, I can expect to recenter immediately. It's the 2D thing I don't get. Next time I'll save logs and a track file.
  25. So what's Reload Tables in the controls settings under Assist heading?
×
×
  • Create New...