Jump to content

minimi66

Members
  • Posts

    268
  • Joined

  • Last visited

Everything posted by minimi66

  1. Er! Blimey, stirred up a bit of a hornets nest there didn't i? Lol!
  2. Perfect!! Job done, thanks very much indeed!
  3. Hi guys, Want to copy my existing TM Warthog config from the Beta to 2.0 Alpha? Can someone tell me which file from where and where it needs to go? Tried what i thought would work but i'm only getting the Default set up in 2.0? I assumed the one i wanted was in Users\Saved Games etc and goes to Mods\aircraft\A-10-C etc? Any help appreciated? Thanks.:megalol:
  4. Tested in Sim too! Tested in FC3 F-15 IA Intercept mission and also in Black Shark IA as well. All perfect!!
  5. UPDATE: Problem solved!! Commodo Firewall was the issue!! Hi, The problem was Commodo Free Internet Firewall!! I was getting fed up with its constant pop up requests to allow this or block that so I uninstalled it and changed to Zone Alarm. I had still been testing the TARGET scripts as recently as the day before (possibly even the same day) and they wouldn’t run, same error message or the script would time out. However it occurred to me this morning that I should try it again now I have ZA instead of Commodo Firewall and BOOM!! It worked!! I had to re-arrange the order of the controller ID’s using the JoyID’s application so that they matched the order in which TARGET was detecting them when running the script but once that was done the script ran perfectly and created the Thrustmaster Combined virtual device (it has never done that before). I opened the Device Analyser (also never been able to open that before either) and all axes and buttons etc are working fine! Thrustmaster Combined is also now showing in Devices and Printers (but it shows as HID-compliant Game Controller). So, I am pretty convinced it was Commodo Firewall? The interesting thing to note is that I had disabled the firewall on numerous occasions when trying to get the scripts to run and had also added EVERY TARGET executable file to the Commodo Allowed Programs list but it was obviously still blocking outwards comms between TARGET and my controllers? I have not changed or altered anything else on my system that could have affected this problem as far as I know. Hope this helps anyone who experiences this problem now or in the future? I can now start using my Warthog HOTAS to its full potential!! Sorted!! PS: VERY happy with Zone Alarm so far too!! Very unobtrusive Firewall.
  6. Hi, Please see my original thread on the problem i was having here: http://forums.eagle.ru/showthread.php?t=142236&highlight=TARGET The problem was Commodo Free Internet Firewall!! I was getting fed up with its constant pop up requests to allow this or block that so I uninstalled it and changed to Zone Alarm. I had still been testing the TARGET scripts as recently as the day before (possibly even the same day) and they wouldn’t run, same error message or the script would time out. However it occurred to me this morning that I should try it again now I have ZA instead of Commodo Firewall and BOOM!! It worked!! I had to re-arrange the order of the controller ID’s using the JoyID’s application so that they matched the order in which TARGET was detecting them when running the script but once that was done the script ran perfectly and created the Thrustmaster Combined virtual device (it has never done that before). I opened the Device Analyser (also never been able to open that before either) and all axes and buttons etc are working fine! Thrustmaster Combined is also now showing in Devices and Printers (but it shows as HID-compliant Game Controller). So, I am pretty convinced it was Commodo Firewall? The interesting thing to note is that I had disabled the firewall on numerous occasions when trying to get the scripts to run and had also added EVERY TARGET executable file to the Commodo Allowed Programs list but it was obviously still blocking outwards comms between TARGET and my controllers? I have not changed or altered anything else on my system that could have affected this problem as far as I know. Hope this helps anyone who experiences this problem now or in the future? I can now start using my Warthog HOTAS to its full potential!! Sorted!! PS: VERY happy with Zone Alarm so far too!! Very unobtrusive Firewall.
  7. No worries, yes its the same with script writer too, tried that this afternoon!! Thanks.
  8. Hi, Unfortunately i did actually try that last night but didn't list it as it was pretty long winded to describe how and what i did. I've tried a few more things today but have had no luck at all? I've emailed Thrustmaster tech support with the full message i posted on here and on some other flight sim forums but to be honest i don't think its fixable? I'm going to move on and just stick to configuring my sims through the in-game controls menu's rather than using something like TARGET. I's wasted nearly 2 days of my life trying to fix something that shouldn't need fixing but that's computers for you i guess? Thanks for the suggestion. Stu
  9. Hi, I am having a major problem with using the Thrustmaster TARGET GUI and loading configuration files for games to my HOTAS Warthog setup. The software detects my TM Warthog HOTAS and 2 x MFD's when in the main TARGET GUI editing environment but upon trying to load ANY config file for use in a game i get the following result after the software attempts to load the file: *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" Physical USB HID devices managed by script! Currently plugged USB HID devices[4]: 1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" 3: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 4: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" Error: (internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0404" Error: (internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0402" Virtual HID devices managed by script! Connecting virtual joystick...Done Device name FAILED (0x00000002) - using default. Connecting virtual keyboard...Done Connecting virtual mouse...Done main returned 0 This happens with every config file i have and that includes the stock ones included with the TM hardware such as DCS Black Shark etc. My system is as follows: ASUS G74SX Gaming Laptop Intel Quad Core i7-2670QM @ 2.2 GHz Turbo Boost to 3.1 GHz. 16 GB RAM GeForce GTX560M with 3 GB VRAM Realtek On-board Sound Card Windows 7 64 Bit TrackIR 5 w/Pro Clip Logitech G602 Gaming Mouse Logitech Wifi Keyboard Creative Rage3D Tactic Gaming Headset Samsung 32 in. TV/Monitor on HDMI TM HOTAS Warthog Stick & Throttle & 2 Cougar MFD's 10 socket USB Hub used to connect some of the peripherals. Solutions tried so far that haven't worked: 1: Uninstall TARGET and re-install. 2: Uninstall HOTAS Warthog Drivers from Control Panel Programs then re-install. 3: Updated TM HOTAs Firmware to latest versions (11 & 23) 4: Disconnect and re-connect all TM and all other devices when prompted to by the above 3 processes. Multiple system reboots and cold starts. 5: Sequential re-connection of key devices only (Mouse, Keyboard and HOTAS Stick & Throttle) whilst monitoring activity in Devices and Printers and Device Manager. 6: Confirmation that the the 2 devices referred to in the above error message are the TM Throttle and Stick ("VID_044F&PID_0404" and "VID_044F&PID_0402"). 7: Enable ALL the executables in Thrustmaster root folders with "Run as Administrator" priveleges. 8: Disable Firewall (Commodo & Windows) before, during and after re-insalls or running TARGET. 9: Connecting TM HOTAS directly to USB Ports on computer rather than through USB Hub. 10: Scattering chicken bones, howling at the moon, rain dances, consulting a soothsayer!!!! Not sure if i've missed or forgotten anything but any assistance or ideas would be appreciated? I understand that most games don't need TARGET to come up up with fairly comprehensive controller setup but my point is that it seems wrong to have purchased a $250 controller setup with its own editing software and find that the 2 DO NOT work together AT ALL based on my experience. Is there a viable alternative to TARGET that can be used? I've never used FSUIPC so am not familiar with its capabilities as opposed to TARGET? Will definitely look into it now though, i'm not optimistic about sorting this out to be honest? Thanks guys. Stu
  10. Hi, I fixed the problem on Friday. In the DCS Options > Controls setup the Communications Menu keystroke "\" was present for the keyboard as well as my Throttle Button 3 which i have set up in VAC to trigger the Comms Menu in game. I cleared the "\" keyboard keystroke and just left Button 3 as the only mapped control for the Comms Menu. Clearly the Comms Menu keystroke was not being triggered in game and when i spoke a VAC command it just generated the F1, F3 etc keystrokes which was why VAC was triggering External View commands and not comms messages. That fixed it and it all now works perfectly! Thanks for all the assistance on both the threads i posted about this problem on. Stu
  11. Hi, I fixed the problem on Friday. In the DCS Options > Controls setup the Communications Menu keystroke "\" was present for the keyboard as well as my Throttle Button 3 which i have set up in VAC to trigger the Comms Menu in game. I cleared the "\" keyboard keystroke and just left Button 3 as the only mapped control for the Comms Menu. Clearly the Comms Menu keystroke was not being triggered in game and when i spoke a VAC command it just generated the F1, F3 etc keystrokes which was why VAC was triggering External View commands and not comms messages. That fixed it and it all now works perfectly! Thanks for all the assistance on both the threads i posted about this problem on. Stu :thumbup:
  12. Hi, Thanks very much for the reply, i am going to work on solving the problem today? I will post my solution if successful.
  13. Hi all, this is a bit off the specific thread topic but since its closely related i decided to see if anyone here could help? Hope that's ok? I've just got back into DCS A-10C and DCS World in general after a couple of years away from it due to being busy with other things. In the process of getting everything set back up again i have hit a problem with getting Fish's VAC A10C profile to work via my TM Warthog Throttle Mic Up button (3) and using thwe AutoHotkey WH_DCS_A-10_VAC_PTA.exe script posted by CubPilot? Basically, when testing in VAC Builder everything works perfectly other than the odd misunderstood phrase here and there. However, in A-10C when i key the PTA button and say a phrase from Fish's accompanying manual of usable phrases (as per his profile) the result is that i get kicked into the F5 Nearest Aircraft View and no radio message gets sent to my Wingman. Not sure whether this is a VAC or VAC Profile issue or an in-game Controls > Options problem. I am pretty mush using all the default HOTAS and Keyboard commands and haven't changed very much at all and nothing to do with Comms or View Commands. Any assistance or ideas would be appreciated? Many thanks. :thumbup:
  14. Hi, I've just got back into DCS A-10C and DCS World in general after a couple of years away from it due to being busy with other things. In the process of getting everything set back up again i have hit a problem with getting Fish's VAC A10C profile to work via my TM Warthog Throttle Mic Up button (3) and using the AutoHotkey WH_DCS_A-10_VAC_PTA.exe script posted by CubPilot? Basically, when testing in VAC Builder everything works perfectly other than the odd misunderstood phrase here and there. However, in A-10C when i key the PTA button and say a phrase from Fish's accompanying manual of usable phrases (as per his profile) the result is that i get kicked into the F5 Nearest Aircraft View and no radio message gets sent to my Wingman. Not sure whether this is a VAC or VAC Profile issue or an in-game Controls > Options problem. I am pretty mush using all the default HOTAS and Keyboard commands and haven't changed very much at all and nothing to do with Comms or View Commands. Any assistance or ideas would be appreciated? Many thanks. :thumbup:
  15. TrackIR ***** Absolutely agree, TrackIR! When you absolutely, positively have to kill every mother****ing tank on the ground! Accept no substitutes!! Once you go TIR you will never go back?
  16. Great news! Thats great news Flim, thanks very much for the update. Will keep saving my $$$ and really looking forward to seeing the A-10C project? Best of luck with it all!
  17. Hi linden! Where can i see pictures of your pit? Hi linden, I must be missing something obvious in the threads? Where can i see some pictures of your pit? It sounds amazing and looks it too from the pictures i have seen? Many thanks.
  18. Happy Days! Awesome! Will wait and see what happens then? Same as you, i was on the site recently and they had recent links to the fully finished and packaged F-16 pits going out to some guys who posted 4 x videos of them being put together complete with the HUD as well. I still have the downloaded copies of the vids. That's what got me interested in the first place. Thanks very much for the update.
  19. Was more interested in the home cockpit kits they were producing, rather than Helios which i was already aware of and not really using at the moment due to lack of touch screens. Was looking to go down a more touchy-feely realism (real panels and buttons etc) with my pit. May have to re-consider now though? Again, thanks for the update though.
  20. Gutted! :( Bugger! Back to the drawing board then! Thanks for the update, was looking forward to seeing their A-10C Cockpit. Self-build i guess. :(
  21. Hi all, I was wondering if anyone can categorically state what the current situation is with SCS Simulations? Their website/forum says the site is unavailable due to expansion but i have seen comments on several DCS forum threads saying that they "are no more" or words to that effect? Their site was still up only a few weeks ago but i went back recently and it seemed to be "under construction" etc. Are they still in business and just updating the site or are they "no more?" Can't find anything official anywhere else on the web either? Cheers.
  22. Original poster progress! Hi all, Thanks for all the interesting posts on both Views and TIR. I decided to persevere with TIR in the end, i downloaded Fish's TIR Profile and tried it out. It was nearly good to go for me as is but needed some minor tweaks here and there due to my own home pit setup and size of monitor etc. Been using it for a week or so now and with a few more tweaks it is really good, i am fully converted now and a definite fan of TIR. I can see however how some people will shy away from it and go down other routes for the viewing system. I also agree with the many posts saying that the keyboard views are probably not meant to be used in-sim, largely anyway. Exception maybe for people editing .trk files etc? I definitely found Fish's YouTube tutorial on TIR setup was VERY useful. I had it playing on my laptop screen whilst setting up and tweaking my TIR profile on my monitor. It definitely cut the time needed to get a workable profile up and running down by a great margin. Took about 1-2 hours in the end. Big thanks to Fish for the profile and the video! So, all good here but thanks to all for the insights provided into your own experiences. Cheers.
  23. Assuming the answer is no then? Er! Guess thats a no then! Lol!
  24. Hi, Anyone using, used or tried to use the VRinsight CDU I or II Panel's with their setup in DCS A10C? Here's the links: http://www.flightstore.co.uk/simulation-c8/vrinsight-cdu-ii-panel-p2462 http://proviationshop.co.uk/shop/article_VRINSIGHTCDUI/VRinsight-CDU-I-Panel.html?pse=coa The info says it works seamlessly with FS2004 and FSX but not sure if there would be problems with DCS titles? Any info appreciated? Cheers guys.
  25. @PeterP, Thanks very much, i will persevere and have a look at creating my own profile after looking at the vid. Thanks.
×
×
  • Create New...