Rybo's Profile - Never disappearing, No shifted layer, Easily customized
-
One question - can the throttle slider be used to zoom view? I don’t think I’ve ever managed to get that working correctly before…
I ran out of axes but I think I have an idea of how it can be done. I’ll post an updated profile if I can get it working satisfactorily.
-
Using DX buttons to handle Range knob then assign friction lever an axis might solve.
Anyway this time FOV AXIS will need to be assigned manually and will disappear when you plug another device to your PC. -
Killer profile, Rybo thank you for putting it together!
-
Using DX buttons to handle Range knob then assign friction lever an axis might solve.
Anyway this time FOV AXIS will need to be assigned manually and will disappear when you plug another device to your PC.That’s definitely something I’ve considered but not my first choice if I can avoid it. I’m going to experiment with a few other concepts I have first
-
I played with zoom control a bit tonight. Unfortunately it isn’t as simple as what I was hoping, although for a totally different reason. The throttle friction lever is dreadfully imprecise (brand new warthog, perhaps it’s a defective pot) and the view just jitters constantly unless I have it in the the little stop in the middle. I figure that eventually I can get it to work to my liking but it will take some time as I learn how to build a custom curve for it.
-
I heard some Warthog has jitter on friction lever when you don’t set LED brightness FULL or OFF.
Mine don’t have the issue and works precisely with middle brightness LED. So I guess they use good pots but some may be defective and some may suffer EMF.
-
Interesting information, I’ll try setting mine to mid tomorrow.
-
Okay, in tweaking the profile a little (just a little!) I’ve come across something that is, more likely than not, my lack of understanding re Target. I want China Hat Forward/Aft to be ICP Next/Previous. The keypresses for these commands are Num+ and Num-, does Target differentiate between number row +/- and the Numpad?
Edit: Nevermind, managed it with USB events. If anyone is wondering, the USB code for Num +/- is 57/56, and the syntax is MapKey(&input device, button name, usb event); or in my case MapKey(&Throttle, CHF, USB[0x57]);
-
@Rybo Thank you for this nice profile. I would like request something from you. We want to change button functions on your profile. I added a photo of throttle and marked the buttons that we wanted to change.
First we want to change Toggle NVG buttons as Next and previous steerpoint, second add external lights flash option to middle position of light button. What should we add to your profile or delete ? Might be hard edit for you… We have no experience about profiles and keyboard layout? Can you help us to do that? Is there any guide to make a profile or create layout ?
-
Hey Rybo, thanks for this awesome profile, it has really helped me get started with BMS. Mentioned earlier about the zoom, I see you’re having troubles with it. What is a solution for zoom control in the interim?
-
Can you help us to do that? Is there any guide to make a profile or create layout ?
The next/previous steerpoint is fairly easy, but if you aren’t familiar with the code structure it can be easy to mess it up. In basic terms, you’ll need to find what the keyboard commands are for next steerpoint (“x” by default) and previous steerpoint (“z” by default).
You will need to open the Thrustmaster script in a text editor (I recommend Notepad++ as it’s free and has fantastic tools). There you will need to find the two lines with the code for that switch and change the keystrokes they perform.
As for the lights, I’m not sure that’s entirely possible but I will think about how to do it.
I’ll send you a PM shortly.
-
Hey Rybo, thanks for this awesome profile, it has really helped me get started with BMS. Mentioned earlier about the zoom, I see you’re having troubles with it. What is a solution for zoom control in the interim?
Thanks for the kind words Nero, it’s nice to see that people are enjoying the profile. I fixed the zoom issue with advice from Chihiro regarding the lights causing some electromagnetic interference. I’ve also cleaned up the code a lot over the past several weeks as I learned more about TARGET so I will probably update the first post sometime this week/weekend with my latest script and BMS keyfile.
The interim solution for zoom is to just keep using the scroll wheel on your mouse
-
Thanks for the kind words Nero, it’s nice to see that people are enjoying the profile. I fixed the zoom issue with advice from Chihiro regarding the lights causing some electromagnetic interference. I’ve also cleaned up the code a lot over the past several weeks as I learned more about TARGET so I will probably update the first post sometime this week/weekend with my latest script and BMS keyfile.
Sounds great, thanks again!
-
dont have to use idle cutoff though right?
-
dont have to use idle cutoff though right?
Are you asking if it’s mandatory that you use idle cutoff with my profile?
If so, the answer is of course not. Simply leave the “Idle Cutoff” selection UN-selected in the config.
I am however curious why you wouldn’t want to use it…
-
The first post has been updated with a new download link and new instructions for the latest version of my profile. It now includes two TARGET scripts, one using the same key layout as before with NVG and Pretty Screenshot on the China Hat, and a second script with Previous and Next Steerpoint on the China Hat due to several requests for it.
If you have any issues feel free to PM me.
Enjoy!
-
Rybo, I cannot use my t flight rudder pedals at all with this script. attached is what I have attempted in the target software. any suggestions?
-
I think they just need the be mode excluded. I’ll send a PM as soon as I can with some instructions for you.
-
Oh in your code…The last line that you wrote looks like it has a | just before the first (. If that isn’t your cursor it will cause big problems.
-
Scratch that. There are a few different issues at play here from what I can see. You’re trying to assign the same DX axes multiple times which won’t work. PM inbound shortly.