Rybo's Profile - Never disappearing, No shifted layer, Easily customized
-
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.
-
@FEIND:
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?
We found our solution to my friend, i will send the solution ASAP.
-
Hi,
C:\Falcon BMS 4.33 U1\User\Config\DeviceSorting.txt
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{B679044F-0000-0000-0000-504944564944} “T-Rudder”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”Rybo’s Profile V2-5.tmc
include “target.tmh”
int main()
{
Configure(&HCougar,MODE_EXCLUDED);
Configure(&T16000, MODE_EXCLUDED);
Configure(&LMFD, MODE_EXCLUDED);
Configure(&RMFD, MODE_EXCLUDED);
Configure(&TFRPRudder,MODE_EXCLUDED);
Configure(&TWCSThrottle,MODE_EXCLUDED); //Enable this line if you use T.Flight Rudder Pedals -
@FEIND:
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?
Last post of bullseye is the solution for TFRP
-
That is all correct. I already got him squared away via PM nearly two weeks ago.
-
possible to add in a shifted state for pinky switch & trim for zoom controll or another solution to zoom? Love the profile and thank you for it
-
It’s certainly possible but have no plans to add a shifted layer. I personally find them quite cumbersome. You are free to modify my TARGET script to your liking, however.
-
Hi there!
Thanks much for sharing your profile. Really enjoying it so far, but only have one quick question. If I wanted to use the throttle slider for a zoom as opposed to FOV Control, would that simply be a process of changing the DeviceDefaults.txt or would I need to also monkey with TARGET black magicks?
Thanks for any input.
-
Just an easy change in DeviceDefaults and then ensuring that you assign the axis properly the next time you start BMS. Your DeviceDefaults should look like this:
Thrustmaster Combined
GUID = {FFFF044F-0000-0000-0000-504944564944}
AXIS_PITCH = Y
AXIS_ROLL = X
AXIS_THROTTLE = RZ
AXIS_ANT_ELEV = SLIDER1
AXIS_RANGE_KNOB = SLIDER0
AXIS_CURSOR_X = RX
AXIS_CURSOR_Y = RY
AXIS_ZOOM = Z -
Hello your profile works for me except the coolie hat. Not sure why it is not bount go anything. Can you help me out?
-
Have you tested it in sim? The coolie hat is used as a set of virtual DX axes that control antenna elevation and the manual range knob. As such it won’t show it when you push it in the BMS Controller Setup UI.
If it doesn’t work in sim, it’s most likely just that the axes are mapped incorrectly in BMS. I’ve seen this happen before when switching profiles. The solution is to simply map them appropriately. In the Controller Setup -> Advanced window set the MAN RANGE KNOB axis to SLIDER0 and set the ANT ELEV to SLIDER1.
If that doesn’t work I won’t be able to help much further without screenshots of your Controller Setup pages.
-
Since U3 update new preset for TM Combined has been added to DeviceDefaults.
If you simply add axes presets to DeviceDefaults there would be 2 codes for TM combined and might cause issues. -
Oh I forgot about that. Thanks chihirobelmo!
Aarenas52 what chihirobelmo described is most likely the issue. Remove the default Thrustmaster Combined and replace it with mine in the first post and you should be all set. If you have issues beyond that feel free to let me know and I’ll do my best to get you sorted.
Cheers!
-
Updated the first post to reflect the correct way to modfiy DeviceDefaults.txt.