Need help modifying Brennus profile… Pulling my hair out !!!!!
-
If you keep everything plugged in the same all the time then BMS works the same. If something is different I only have problems with joystick axes, my .key file is OK.
For example I forget to plug in my joystick and I start BMS. BMS reconfigures itself a little. I quit BMS, plug in my joystick, and start BMS again. The joystick axes are wrong so I have to set them again: joystick for main controller, X, Y, throttle, brakes left, brakes right, cursor X, cursor Y, rudder, FOV, range, and antenna. Whew, 12 things. Is it a pain in the butt? Yes, but it is fast to fix. Never have I had a problem with .key file which doesn’t change when you start BMS in wrong state so it is safe from harm.
-
The joystick axes are wrong so I have to set them again: joystick for main controller, X, Y, throttle, brakes left, brakes right, cursor X, cursor Y, rudder, FOV, range, and antenna. Whew, 12 things. Is it a pain in the butt? Yes, but it is fast to fix.
Go into your install folder -> user -> config -> devicesdefault.txt and follow the instructions. You will never feel that pain again
Edit : actually, you still will have to reset the AB and idle detent. But its a small step.
-
Go into your install folder -> user -> config -> devicesdefault.txt and follow the instructions. You will never feel that pain again
Edit : actually, you still will have to reset the AB and idle detent. But its a small step.
Looks a bit complicated.
It has about 5 CH devices with the same name. -
@Smasha : this is only for AXIS assignation. So you dont have to reassign them if, once, you launch BMS without your devices plugged in…
But if you have troubles with BUTTONS, this will not help you.
Now if you still want some info on what to do with this file, I can provide.
-
I3crusader, I see it but I can’t get it to work. If I load up with the wrong setup and back again with the correct GUID setup in the DeviceDefaults.txt file it still shows up “keyboard”. I can’t find these GUIDs in my registry. I thought at first you were going to suggest making axismapping.dat a real-only file once configured. I’ve seen that trick before.
# Default Device Axis Mapping File # Syntax: # '#' - this marks a comment line (duh). These lines are not evaluated by this parser. # 'GUID = {...}' - this line marks the beginning of a new device configuration # # Now you may map physical axis to in-game axis.. the format is 'in_game=physical, where # 'physical' may be 'X Y Z RX RY RZ SLIDER0 SLIDER1' and in_game may be # 'AXIS_PITCH, AXIS_ROLL, AXIS_YAW, AXIS_THROTTLE, AXIS_THROTTLE2, AXIS_TRIM_PITCH, AXIS_TRIM_YAW, AXIS_TRIM_ROLL, AXIS_BRAKE_LEFT, # AXIS_BRAKE_RIGHT, AXIS_FOV, AXIS_ANT_ELEV, AXIS_CURSOR_X, AXIS_CURSOR_Y, AXIS_RANGE_KNOB, AXIS_COMM_VOLUME_1, AXIS_COMM_VOLUME_2,' # AXIS_MSL_VOLUME, AXIS_THREAT_VOLUME, AXIS_HUD_BRIGHTNESS, AXIS_RET_DEPR, AXIS_ZOOM, AXIS_INTERCOM_VOLUME' # You can only map one in-game axis to one physical axis # A typical line my look like 'RZ=AXIS_THROTTLE' # # CH Pro Pedals USB GUID = {C0F2068E-0000-0000-0000-504944564944} AXIS_BRAKE_LEFT = X AXIS_BRAKE_RIGHT = Y AXIS_YAW = Z # Joystick - HOTAS Warthog GUID = {0402044F-0000-0000-0000-504944564944} AXIS_PITCH = Y AXIS_ROLL = X # Thrustmaster Combined GUID = {FFFF044F-0000-0000-0000-504944564944} AXIS_THROTTLE = Z AXIS_THROTTLE2 = SLIDER1 AXIS_FOV = Rx AXIS_ANT_ELEV = RZ AXIS_CURSOR_X = X AXIS_CURSOR_Y = Y AXIS_RANGE_KNOB = RX # Saitek X36 USB #GUID = {053F06A3-0000-0000-0000-504944564944} # Saitek X45 Flight Controller USB #GUID = {053C06A3-0000-0000-0000-504944564944} # Saitek X52 Flight Stick (USB) #GUID = {025506A3-0000-0000-0000-504944564944} # Saitek X65F Pro Flight Control System #GUID = {0B6A06A3-0000-0000-0000-504944564944} # Saitek Cyborg Evo #GUID = {046406A3-0000-0000-0000-504944564944} # Saitek Pro Flight Rudder Pedals #GUID = {076306A3-0000-0000-0000-504944564944} # Logitech WingMan Force 3d #GUID = {C283046D-0000-0000-0000-504944564944} # Logitech G940 #GUID = {C287046D-0000-0000-0000-504944564944} # StickWorks SWF22 #GUID = {FF1009F3-0000-0000-0000-504944564944} # Thrustmaster HOTAS Cougar #GUID = {0400044F-0000-0000-0000-504944564944} # Thrustmaster Top Gunョ AfterBurner (USB) #GUID = {B101044F-0000-0000-0000-504944564944} # Thrustmaster F16 MFD 1 #GUID = {B351044F-0000-0000-0000-504944564944} # Thrustmaster F16 MFD 2 #GUID = {B352044F-0000-0000-0000-504944564944} # Controller (XBOX 360 For Windows) #GUID = {028E045E-0000-0000-0000-504944564944} # PLAYSTATION(R)3 Controller #GUID = {0268054C-0000-0000-0000-504944564944} # Logitech Cordless RumblePad 2 USB #GUID = {C219046D-0000-0000-0000-504944564944} # Throttle - HOTAS Warthog #GUID = {0404044F-0000-0000-0000-504944564944}
In other news I was tired of always having to invert my CH Pro Pedals for braking so I decided to invert them in the CH software. Unfortunately I need a deadzone and when you invert the control axis it puts the deadzone on the wrong side! Gaaah. It’s either a script solution or I just miscalibrate them to trick a deadzone.
-
[QUOTE=Frederf;295087
# Thrustmaster Combined GUID = {FFFF044F-0000-0000-0000-504944564944} AXIS_THROTTLE = Z AXIS_THROTTLE2 = SLIDER1 AXIS_FOV [color]= Rx[/color] AXIS_ANT_ELEV = RZ AXIS_CURSOR_X = X AXIS_CURSOR_Y = Y AXIS_RANGE_KNOB = RX Try to change the axis for the FOV, I dont think BMS understands Rx. It should be RX. And since you have RX assigned for the range knob, I would say its the SLIDER0 axis. There is a weird correspondance between TARGET Axis names and names in this file. You have : [b]TARGET [/b]----------------> [b]devicedefault.txt[/b] DX_THROTTLE_AXIS ----->SLIDER0 DX_SLIDER_AXIS -------->SLIDER1 Its possible this screw things up. EDIT : about GUID : you dont have to worry about them. Basically, every time BMS launches and see a device not on this list, it adds 2 commented lines, 1 with the name, one with its GUID. All you have to do is uncomment the GUID line and add axis assignation after.
-
I fixed the lower case Rx to RX.
The TM Combined listed axes names are in device analyzer:
X
Y
Z
Rx
Ry
Rz
Slider0
Throttle
I assume SLIDER0 = Slider0 and SLIDER1 = Throttle.Even if my assignments are wrong functionally they are still valid. TARGET always outputs values for all 8 axes even if they aren’t bound. They just get frozen to 0 value.
But maybe there is an error in that section for Combined. I comment out every line in that block with #. Still doesn’t work.
# CH Pro Pedals USB GUID = {C0F2068E-0000-0000-0000-504944564944} AXIS_BRAKE_LEFT = X AXIS_BRAKE_RIGHT = Y AXIS_YAW = Z # Joystick - HOTAS Warthog GUID = {0402044F-0000-0000-0000-504944564944} AXIS_PITCH = Y AXIS_ROLL = X # Thrustmaster Combined #GUID = {FFFF044F-0000-0000-0000-504944564944} #AXIS_THROTTLE = Z #AXIS_THROTTLE2 = SLIDER1 #AXIS_FOV = RX #AXIS_ANT_ELEV = RZ #AXIS_CURSOR_X = X #AXIS_CURSOR_Y = Y #AXIS_RANGE_KNOB = RX
-
Then…. I dont know.
First things first : you assigned RX twice in your combined section, to FOV and to RangeKnob. Not that it matters for the rest, as you commented it out, but still
All I can tell you is that the rest should work… but thats not exactly helpful, I know
Make sure you save the file before launching BMS, try to launch it without your devices plugged in, then plug them in and try again…
Try to delete the lines corresponding to your devices, then plug them in and launch, to have a “fresh” GUID for each…Otherwise, I’m out of ideas