Need help modifying Brennus profile… Pulling my hair out !!!!!
-
When you go in setup and press the trigger, what is the name of the callback ? Is it “First Trigger detent” or “Second Trigger detent”?
Bottom line :
- the first trigger detent will fire the laser when armed,
- the second trigger fires the gun.
-
If I remember right there are two callbacks that fire the gun:
SimTriggerSecondDetent
SimTriggerThey both cause bullets to come out of the gun but there are small differences in behavior and one is more correct than the other. I think SimTrigger is the correct one but double check.
-
Mine says fire guns.
-
I can’t tell by the label in quotes. I take a line out of BMS.key to demonstrate:
SimTMSUp -1 0 0XFFFFFFFF 0 0 0 1 “HOTAS-TMS Up”
The part in red is the callback. This is the exact name of the command to be used. It has to be spelled exactly right. The part in green is the text label for the line. This is what shows up in the right column in setup>controls. You can change it to “Blah blah blah” and it still works.
If you say “fire gun” it’s probably a direct copy of this line from BMS.key
SimTrigger -1 0 0XFFFFFFFF 0 0 0 1 “Wpn-Fire gun”So that would be SimTrigger callback which I think is the more correct one. The other callback in BMS.key is called
SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 1 “HOTAS-Second Trigger Detent” -
I can’t tell by the label in quotes. I take a line out of BMS.key to demonstrate:
SimTMSUp -1 0 0XFFFFFFFF 0 0 0 1 “HOTAS-TMS Up”
The part in red is the callback. This is the exact name of the command to be used. It has to be spelled exactly right. The part in green is the text label for the line. This is what shows up in the right column in setup>controls. You can change it to “Blah blah blah” and it still works.
If you say “fire gun” it’s probably a direct copy of this line from BMS.key
SimTrigger -1 0 0XFFFFFFFF 0 0 0 1 “Wpn-Fire gun”So that would be SimTrigger callback which I think is the more correct one. The other callback in BMS.key is called
SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 1 “HOTAS-Second Trigger Detent”Both detents weren’t assigned in the key map.
I assigned the trigger to first detent in BMS but not too sure about getting the second detent activated.
That was one thing the Cougar had over the CH, the two stage trigger.Does the gun fire or do you have to have it locked over the “eye of death” in the funnel for it to activate?
Maybe I’m doing it wrong?
How do I get the two detents to work with the CH trigger?
Googling again lol.
I know with the Cougar,you hold the trigger half way in way for first detent and then hold it fully to activate the second detent.
But I’m not a programmer so I don’t know how to do this with my CH Fighterstick.
I rely on using profiles.
Put the question up in Ch Hangar.
Can’t do it myself.
My brain will not allow it. -
If I remember right there are two callbacks that fire the gun:
SimTriggerSecondDetent
SimTriggerThey both cause bullets to come out of the gun but there are small differences in behavior and one is more correct than the other. I think SimTrigger is the correct one but double check.
……
So that would be SimTrigger callback which I think is the more correct one. The other callback in BMS.key is called
SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 1 “HOTAS-Second Trigger Detent” -
Thank you.I did put cannon in the search function on this site ,but nothing came up that I was looking for.
P.S I might just keep what I had.
Maybe the gun doesn’t fire at all until it’s safe to do so.Fubar2niner would have had this programmed properly anyway.
S2 doesn’t light up in the controls though.
-
Does the gun fire or do you have to have it locked over the “eye of death” in the funnel for it to activate?
Cannon should fire when master arm is on and in any master mode that isn’t NAV or the jettison modes. This is actually one of the differences between the two callbacks. One shoots in more situations. In no case does the gun ever prevent firing by evaluating how good your aim is.
But I’m not a programmer so I don’t know how to do this with my CH Fighterstick.
To put two functions on one button you’d need some kind of shift function. But the first detent isn’t worth worrying about anyway. You know what first detent does? It starts the AVTR camera rolling early and it does manual laser activation for LGB bombing. Two completely worthless actions. Just put SimTrigger on your joystick trigger and ignore first-detent. I promise you won’t miss it. If you really really really want to put the first detent on your profile I’m sure there’s a way.
-
It starts the AVTR camera rolling early and it does manual laser activation for LGB bombing. Two completely worthless actions. Just put SimTrigger on your joystick trigger and ignore first-detent. I promise you won’t miss it. If you really really really want to put the first detent on your profile I’m sure there’s a way.
I agree on the fact that you can ignore FirstTrigger for now.
BUT (and off-topic) : I completely disagree about overall usefullness of first trigger.
Granted, the AVTR stuff is very circumstancial, but manual laser firing can be very useful, especially when dropping LGBs on moving targets. But its true that for now, its not as useful as it is RL.Anyway, I’ll have a look at what does exactly SimTrigger & SimTriggerSecondDetent, and I’ll see what is the one compensating for yaw.
-
-
@smasha
Sorry I’m late getting back on this, been a helluva week, had no time on BMS myself this week ! Anywho to the question; I have 'fire gun’mapped to “Wpn-Fire Gun” in BMS UI, and first trigger detent mapped to “HOTAS - First Trigger Detent” in BMS UI. I had trouble myself regarding guns until I mapped to “Wpn-Fire Gun”
Try it and see if it works for you. Best way I found to check if first trigger detent is working during early training stages is turn the ACMI to ‘Auto’ ( look in dash 1 manual for AVTR Panel ) then when you hit first trigger detent the ACMI will turn on. Hope this makes sense, still a n00b here myself!
Best regards.
Fubar2Niner
-
-
Just noticed,if you plug in any other usb device like I did with my ps3 eye camera and light for Aerodrums,when you go back into BMS,the controls reset themselves.
My throttle and rudder pedals are greyed out as well as the second detent option I had configured yesterday.
I still had my CH hotas plugged in and use a powered usb hub when plugging in the camera but it seems it resets BMS,controllers.
OK,now the second detent function isn’t working by holding the throttle shift button down + trigger.
Worked beautifully yesterday.
Ok < I had to click the shift box for the throttle before downloading.
Also the WPN fire guns command doesn’t work so I used second detent.
-
This is well known.
Any USB device pluged or unpluged will break your USB id identifier within BMS, so, anytime you launch BMS, check that you have your “standard” config plugged, no more, no less.
-
This is well known.
Any USB device pluged or unpluged will break your USB id identifier withoin BMS, so, anytime you launch BMS, check that you have your “standard” config plugged, no more, no less.
That isn’t good.
I need my Aerodrums.
-
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.