-
Posts
37 -
Joined
-
Last visited
-
Hey~ Somehow i have encountered this error while tried to get the TQS led working: TMHotasLEDSync v1.0.8 Physical USB HID devices managed by script! Currently plugged USB HID devices[7]: 1: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200" 2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 3: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110" 4: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" 5: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 6: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 7: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" USB HID device with hardware id "VID_044F&PID_0404" cannot be found USB HID device "Viper TQS"(USB\VID_044F&PID_0412\3655327C3530) selected USB HID device with hardware id "VID_044F&PID_0413" cannot be found USB HID device with hardware id "VID_044F&PID_0416" cannot be found USB HID device with hardware id "VID_044F&PID_0417" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Script stopped! Done Device name set to Thrustmaster Combined Runtime Error: STOP request received while running main on line 65 in "C:\Users\Jarrod\Saved Games\DCS\ViperTQSLight\TMHotasLEDSync\TMHotasLEDSync.tmc" Error:Script run timed out! =========== I can confirm TARGET software and TQS firmware are all newest. Is there anything I could do to slove this? Many thanks!
-
Hello Folks, Currently I've been using the page indecate waypoint information in MFD (not CDU) to select waypoint. But everytime I hit 'DIR' for the selected waypoint the system will automatically create a new 'turn point' at my current position. This completely mess up my waypoint list after serval times of slingloading/transporting back and forth, especially when it comes to more than 3 preplanned points. I won't be able to tell which point is which....not in a short time at least. Is there anyway I could avoid this (automatically creating new turnpoints everytime I menually switch from waypoints), or have I done something wrong? Many Thanks!
- 1 reply
-
- navigation
- turnpoint
-
(and 1 more)
Tagged with:
-
JarrodR5 changed their profile photo
-
Hi, I did cold start and inserted waypoint into the navigation system using Lat/Lon format. I realized that when I create the first way point the Lat Lon defult position sould be at PP (current start up position) when I switch the format the coordinate will appeared. However, dispite how this position diplayed in the MFD is correct, it is not. When I click the Lon button it will suddently change to different digits (sometimes it won't), and if I store this way point without altering, the initial waypoint (1W) I create for current position will be significantly drifted to 213nm away. Pretty sure this should be a bug, Many thanks! -------------------------------- UPDATE I've been trying to record a track, but everytime I quit mission or try to change slot after inputing waypoints DCS crashed....
-
Hi, I have noticed that Polychops have been developing AI for Kiowa. Is there any chance the AI could be used in the SA342 as well and help doing air to ground in the future, like sopt target and help launching HOT3s? Currently it is really painful to do it by switching from seats while try to stablize the aircraft at the same time... please let me know. Many thanks!
-
Thanks mate, ticking the box 'using DCS resolution' makes it work properly!
-
Hello! I am currently using HTC vive pro vr headset. Jester menu is blocked from option 2 to option 4, I can not see these options when i am playing in vr. My friend who is using Quset3 said he has no such trouble. I think it is about compatability for the menu on HTC. Hope this could be fixed. Many thanks!
-
known issue Multiplayer datalink share of detected air targets.
JarrodR5 replied to Yaga's topic in Bugs and Problems
Same seems to happening to me and my friend, the current update did not fixed it. Inputing assigned STN into DED seemingly not working for MP cold start F16. Even follow the new GPS allignment procedure. I would try to add track when me and my friend have time. But that could take a while. -
Just checked, the recent update did not fix this issue. The needle on hsi is still pointing randomly to wrong direction.
-
reported TGP not powering up after April 10th update
JarrodR5 replied to Swamp Fox Loader's topic in Bugs and Problems
Hi, The issue is: if we switch the POWER for TGP on before equiping the TGP, TGP will never turn on after the equip is done. If you rearm which refresh the loadout (including the TGP), TGP will turn off and never be on again unless you toggle the power switch on and off. in other words, TGP now need to restart and re-align after every rearm. Same situation happens to TGP on A10CII. Please have a look into this, Attached trk file is an cold F16 originally equiped with tgp before start up and how it beheaves after rearming. Thanks! TGP Power F16.trk -
reported TGP not powering up after April 10th update
JarrodR5 replied to Swamp Fox Loader's topic in Bugs and Problems
Hi, I know this is an investigating issue. just a heads up, The same situation for TGP is happennig to A10CII as well. If TGP power is set to on before equiping the TGP, It will not turn on. I assume this will happens when another rearming is done, although there is already an aligned TGP equiped in previous sorties like F16 does. Thank you! TGP A10CII.trk -
Hi, Thank you for replying. I've double tested just now and seems 105 can destroy T90 again. Last time I tested after update it was only 70% damage can be delt to T90s group, which was very strange. I guess i have no more question for now. Anyway, thanks for helping Cheers!
-
For now T90s are still not killable with a cbu-105/97 drop. It could be a lot to ask in such a short time. Sorry in advance, but just bringing updated situation on the table. Many Thanks.
-
Ahh Ok...Wasted an whole afternoon to try figure out this funtion lol.
-
Hi, At current stage can we use tpod to search for laser (that is pointed by JTAC or wingman)? If we can, how do we change the search code? Thanks!