Jump to content

Kisi

Members
  • Posts

    36
  • Joined

  • Last visited

1 Follower

About Kisi

  • Birthday 01/01/1980

Recent Profile Visitors

1560 profile views
  1. I'm using a DirectX profile from CTS for a F-4. If you need any help with setting it up, PM me and I'll help if I can.
  2. Hi. Is there a video / videos planned to showcase upcoming features? Thanks!
  3. I think the problem here is, that T.A. wrongly associates LAU with the warhead of the weapon. LAU is only the rail that enables a connection between an aircraft and a weapon. If you choose AGM-65D on LAU-117 it will be the exact same Maverick as if you load it up on LAU-88. So it is your choice to either use one LAU over another. It does not affect the weapon's warhead. Hope my explaining is clear as English is not my first language.
  4. I was asking my self the same questions. I hope he's ok and it is just a lack of time on his side.
  5. I'm sorry, but I'll hold on to my money for now. All the things that happened this year in DCS left me very disappointed.
  6. This behavior started for me after september update. It's so frustrating. Also not correcting for the wind. It all makes George gun use pointless.
  7. Does anyone know how much torque can it generate?
  8. Hello HomeFries. Basic will do for me I was trying to use DirectX, but I have trouble with correlating what every button and switch on TM is actually sending to computer. When I try to bind something in DCS it only registers some modifier but not the key and sometimes it registers key with one modifier and I have to add the combination with two modifiers by hand. Is there some kind of chart with TM Warthog and corresponding button / keys combinations used by DirectX profile?
  9. I have the same issue. While testing, I came to conclusion that my stick input is converted to nose action with a little delay, thus my initial tendency to PIO. Don't know if this delay is correct as is, or a bug, but I have to relearn all the close formation flying and tanker operations.
  10. Hey! As TF-51 is a free module and P-51 shares all the settings with it, it is not listed to be enabled. It’s in the script by default. Happy flying Max.
  11. Yeah, I feel you. I would be lost like a child in the mist without these profiles. I only changed my base to Virpil because I knew I could still use my beloved script.
  12. Hello Jalava. I had similar problem with alternated defines.tmh file. I have my joystick base changed to Virpil WarBRD, and to have it fully functional with TM TARGET software I had originally modified "c:\Program Files (x86)\Thrustmaster\TARGET\scripts\defines.tmh". Somehow the installer of new TARGET software didn't replace this file with a new version (maybe it has seen that it was altered). When I deleted all of the previous version of TARGET and reinstalled the new one, the aforementioned file was the right one (which I could alter, just like the old one). Now everything is working properly at my side. The new version of defines.tmh file is bigger then the previous one, but could be altered the same way by finding the same lines as in the older one.
  13. Yes. I did.Couple of times. I also tried to "touch" the settings in CTS but it didn't do anything for this problem. For now I rolled back to 3.0.18 and I commented out the lines you mentioned. It works. There's also another problem that occured with, I think, version 2.70. When I put P-51 profile on, I have it playing coolant.wav. It also plays it whenever I release MSD button (radio transmit button). Thanks for all your help. Edit: Found the changes introduced in 2.69 for the coolant switch in P-51. Disregard my problem there.
  14. Hello @Home Fries I've updated CTS to 2.71 and TARGET to 3.0.21.910. Now when I try to start the script I get this error: Compile Error: Symbol not found: QT_BTN1 in target.tmh at line 869 What am I doing wrong? Thanks!
×
×
  • Create New...