Rybo's Profile - Never disappearing, No shifted layer, Easily customized
-
Thank you for this amazing profile.
I have a problem when I use the script with Target software. This is the error I get:
Running script: E:\Users\David\Documents\Sim Modern\Falcon BMS downloads\Warthog\Rybo’s Profile V3.tmc
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
2: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
Installing filter driver to VID_044F&PID_0404. Please Wait…Done!
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\5&1BF0BA15&0&3) selected
Installing filter driver to VID_044F&PID_0402. Please Wait…Done!
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\5&1BF0BA15&0&9) selected
USB HID device with hardware id “VID_044F&PID_0403” cannot be found
USB HID device with hardware id “VID_044F&PID_B10B” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device with hardware id “VID_044F&PID_B68F” cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
I installed the drivers from Thrustmaster website and I got these four errors (2 error before installing the drivers).
Thank you!
-
Hi. When I run the new profile, Falcon resolution is 1024x768. I can not change the graphics settings. How can I solve the problem? Thank you.
Sorry mate, I have never experienced that and have no clue what would cause or what a potential solution would be.
-
Thank you for this amazing profile.
I have a problem when I use the script with Target software.
I appreciate the kind words, but I’m afraid I have never seen that error before. It appears that the device ID’s are different. You could possibly solve it by replacing the device ID’s in my code with the ones shown for your particular hardware. I wish you the best of luck.
-
Thanks for the help
What version number of Target software and Warthog drivers do you use?I reinstalled drivers and the Target software. My Warthog set works fine but the messages are very annoying :
“VID_044F&PID_0403” JoystickF18
“VID_044F&PID_B10B” T16000L
“VID_044F&PID_B687” TWCSThrottle
“VID_044F&PID_B68F” TFRPHARudderI don’t have any of these devices, I wonder why I get these errors.
So, the Script is running good? A window emerges requesting to load a profile again.
With another script profile for my T16000 I get similar errors “USB HID device with hardware id “XXX” cannot be found”
Perhaps they are normal, but the “Open” pop up window I don’t think so.Sorry for the trouble, I’m very confused…
-
I am using Target Script Editor v 3.0.16.615, but I’m not sure which drivers I have, although I’m sure they’re old. It looks like updates have been released to account for the F-18 stick and their new rudder pedals.
As for the new window, that can often be a result of a switch in a certain position on the throttle, as those simply emulate a keyboard command. It is nothing of concern, you should be able to simply close that window and run the profile without any issues.
-
Thanks Rybo. Its was the ACMI “On” that opened the window.
The profile works perfect, I love it. I found the HAT Pov for antenna elevation very unresponsive (I tried up/down and right/left). I changed it for the 4 key hat switch on my thumb. Now I’m much more quick to find my targets
I’m enjoying BMS x10 times more with the Warthog compared to the T16000 I had before.
-
Thanks for the kind words, glad you’re enjoying it. As far as the antenna elevation goes, I wanted a more fine control for certain scenarios and found it to be the most suitable to my tastes. I’m glad you found a way to modify it to your needs.
-
I wish this thread were sticky so that I could have found it earlier. This profile suits me very well, simple, intuitive n efficient, with some well thought bindings that I particularly appreciate like steerpoints, fov, antenna elevation, emergency jettison,… I feel no need for now to add/change any feature, but I’m very new to flight sims, may be later
-
Thanks for the nice words, Jetsun.
-
Just a heads up, I’m working on an update for my profile for proper 4.34 compatibility. Pending no issues in testing (and assuming my wife doesn’t add more to the to-do list!) I should be able to get it out by the end of the weekend.
-
If any of you using this or thinking of using this profile have any requests let me know! No guarantees that I accommodate them, but I’ll take suggestions under consideration while I’m editing. Cheers!
-
I’m just glad you’re updating it for 4.34 Rybo! This has been my go-to profile ever since I got a Warthog and it works really well. Big thanks for your effort!
-
First post updated with a 4.34 compatible profile. Quick recap of changes:
- CMS Z axis is now set to the Slap Switch (CMS Program 5)
- Minor update to the external lights pinky switch on the throttle
- Increased cursor sensitivity slightly
- Full 4.34 compatibility. The new profile was built on the BMS - Full keyfile that shipped with 4.34.
Cheers!
-
Rybo thanks for the new update. This is my favourite profile by far.
Now Its time to enjoy the new 4.34
Enviado desde mi SM-G950F mediante Tapatalk
-
So has anybody gotten this working with with Saitek Combat Rudder pedals? I look at the manual axis assignments in the config screen, and I can’t reassign the toe brakes or rudder axis.
-
Rybo thanks for the new update. This is my favourite profile by far.
Glad you’re enjoying it. Take the fight North!
-
So has anybody gotten this working with with Saitek Combat Rudder pedals? I look at the manual axis assignments in the config screen, and I can’t reassign the toe brakes or rudder axis.
That’s unfortunate, and even worse I don’t really have any idea why that would be the case. Maybe you’ve already tried these, but here are a few of my ideas to troubleshoot:
- Verify the code for the pedals in DeviceDefaults.txt (seems an unlikely culprit)
- Verify the pedals are present in DeviceSorting.txt (I keep my pedals directly underneath Thrustmaster Combined)
- Double check that the pedal axis assignments can be changed when not running my profile to exonerate potential hardware issues.
Let me know if any of that is helpful… :-?
-
Following this ^
My profile is based on Rybo’s, and works fine with my Saitek pedals.
-
That’s unfortunate, and even worse I don’t really have any idea why that would be the case. Maybe you’ve already tried these, but here are a few of my ideas to troubleshoot:
- Verify the code for the pedals in DeviceDefaults.txt (seems an unlikely culprit)
- Verify the pedals are present in DeviceSorting.txt (I keep my pedals directly underneath Thrustmaster Combined)
- Double check that the pedal axis assignments can be changed when not running my profile to exonerate potential hardware issues.
Let me know if any of that is helpful… :-?
I had my pedals just below my MFD’s in DeviceSorting.txt, but I figured that’d be important to have in general?
I won’t be back in front of my computer before the weekend, but I’ll try the rest then, and report back.
Thanks!
-
I, too, have my pedals in devicesorting.txt - no MFD’s yet!