Morphine's Profile
-
I got a new Warthog yesterday and this has been a bit of a pain to get it working. Still one thing to go is slew control is not working in either game nor in device analyzer. Weird thing is that it was working yesterday when I had wrong device numbering and other buttons were not working correctly. Now that I fixed that virtual mouse is dead. I tried to recalibrate joystick while script was running but it didnt help.
Any suggestions?
-
@Greg:
I got a new Warthog yesterday and this has been a bit of a pain to get it working. Still one thing to go is slew control is not working in either game nor in device analyzer. Weird thing is that it was working yesterday when I had wrong device numbering and other buttons were not working correctly. Now that I fixed that virtual mouse is dead. I tried to recalibrate joystick while script was running but it didnt help.
Any suggestions?
This turned out to be a hardware problem, and after dealer replaced it with a new hotas problem was solved. Weird though that you can have a switch that works 2 hours in an equipment that costs 350€.
-
Yes, unfortunately “quality control” is a difficult challenge for all of the consumer joystick vendors. Glad to hear you got it sorted out.
-
Hi Morphine,
I’ve been checking the functioning of the sript for HWorthog and there are some commands that are not working inside the sim.
Still not sure if they are not working or I have done something wrong because now I’m starting at F16.
One example I have is that the NWS configured for Master Mode button with two more aggregate functions. When I press the button on the ground NWS does not work. This script that you created for TARGET where more than one command on the same button a shortcut key is required. In the case of the NWS link for its operation is needed or not, because I was using it with soil and the shortcut to invoke attempt however it still fails.Tks.
-
Thanks for the profile Morphine! One quick question though: Do I have to start the TARGET Script Editor and open the script to run it, or can I create a desktop shortcut or something to launch both the script and BMS in one go?
-
My problem is fixed……!!!
-
Thanks for the profile Morphine! One quick question though: Do I have to start the TARGET Script Editor and open the script to run it, or can I create a desktop shortcut or something to launch both the script and BMS in one go?
You need to start TARGET and RUN the script everytime before starting BMS or you will lose your axes settings (and of course it will not work).
I don’t think there is a way to automate it with one click like you can in the TARGET GUI although I suppose there might be a way to add a command at the end of the script to launch BMS. I just haven’t tried.
-
-
I’ve just come back to BMS after 2 months of being at uni, and the game has forgotten your entire profile and key mappings as it always does after a long period for some reason. Usually I fix this myself, but something else has happened this time - the NWS button on the stick that you allocated as SHIFT has changed it’s functionality to be Left MFD OSB3 for some reason, I didn’t touch a setting so it’s done it purely of it’s own accord. How to I assign it back to it’s SHIFT function?
-
Hi Morphine,
Can you point me to where your G13 and G15 Profiles are located?
Thanks!
-
Hi Morphine, in order to have more realism is not better to change how the speed brake button work? the release of speed brake it’s better if depend from pressure on button….sorry if i not explained well
-
Hi Morphine, in order to have more realism is not better to change how the speed brake button work? the release of speed brake it’s better if depend from pressure on button….sorry if i not explained well
I’m not sure I understand exactly what you mean but the speedbrake switch on the Warthog throttle works exactly like the one on the Cougar F-16 throttle. It is my understanding that is the same operation as the real jet. Can you be more specific about what you think is incorrect about how the switch works?
Just to make sure yours is working properly, the speedbrake should not retract unless you move it forward and should stay deployed as long as the switch is in the middle position.
-
But on real f-16 the speed brake extension depend from pressure on switch, right? Or it is an on/off switch like on some business civilian jet?
-
But on real f-16 the speed brake extension depend from pressure on switch, right? Or it is an on/off switch like on some business civilian jet?
There is not a pressure sensing mechanism in the switch but the extension part of the switch is spring-loaded. When moved to the deploy position, the speedbrake will begin extending (and its fairly quick). You can stop it before it reaches full extension by moving the switch back to center and leave it extended in it’s current state. Use the outside view and observe the speedbrake extending as you move the switch and quickly return to center. You should be able to stop it before reaching full extension. Below is the text from page 133 of the BMS Dash-1 describing the speedbrake operation.
1.13.4. Speed brake System
The speed brake system consists of two pairs of clamshell surfaces located on each side of the engine nozzle and inboard of the horizontal tail and is powered by hydraulic system A. The speed brakes open to 60 degrees with the gear not down and locked. With the gear down and locked speed brake opening is limited to 43 degrees to prevent the lower surfaces from striking the runway during landing. This limit can be overridden by holding the SPD BRK switch in the open (aft) position. When the NLG strut compresses on landing the speed brakes can be fully opened and remain fully open without holding the SPD BRK switch.The Speed brake switch
The SPD BRK switch, located on the throttle, is a thumb activated three position slide switch. The open (aft) position is spring loaded to off (centre) and allows the speed brakes to be incrementally opened. The closed (forward) position locks in place, allowing a single motion to close the speed brakes.The speed brake position indicator
A three position indicator is located left of the LG control panel.
Positions are:
• CLOSED
• 9 dots symbol: The speed brakes are not closed (thus open but it is not possible to say how open they are)
• Diagonal lines: Electrical power is removed from the indicator. -
This post is deleted! -
once i realized through trial and error (not having seen post 271 ) that the script needed to be run each time, i got the profile working and its awesome. maybe add that instruction to the OP for first time users? i kept trying to do things like adding the TMC file as a configuration, or dropping into the drag/drop windows, etc.
and IRT the speedbrakes, viper drivers report never using partial boards really. either full open or full closed. i love the way the speedbrake switch works on this hotas
and again, much thanks for the awesome profile sir! at some point i want to dive into the LED thing, and also i want to assign batt/main power to the APU switch, and maybe move some stuff around. We’ll see
-
Challenge Accepted!
This is also something I’ve wanted to do for a while as well. Add the code below to the TARGET Script and the 1st (Top) LED will come on once you are in the deadzone and the remaining lights will come on once you leave the deadzone and activate the AB. In your controller setup screen set the AB detent when the first light is on and you will be good to go.
Add the code below between the following two lines in the TARGET Script:
SetShiftButton(&Joystick, S3);////////////////// AXIS CONTROLS //////////////////////////////
////////////////// LED CONTROLS ////////////////////////////// //initialize LED status all "OFF" ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); //set LED 1 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)); //set LED 2 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3)); //set LED 3 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); //set LED 4 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)); //set LED 5 OFF //LED Throttle Position Indicator; LED 1 - MIL Power; LED 1-5 AB KeyAxis(&Throttle, THR_LEFT, 0, AXMAP2( LIST( 0, 65, 75 ), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED2), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED3), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED5)) ));
If you’ve changed the deadzone to something other than 65 - 75, you will need to adjust the vaules in the text “AXMAP2( LIST( 0, 65, 75 )” accordingly.
Well it has been at least eight months since I’ve played BMS because after I upgraded to Windows 8.1 I didn’t feel like going through setting up all my controls again. However, everything worked pretty much perfectly this time. This new code with the LED’s though is messing up things. If I utilize this code it causes my stick and throttle to become unresponsive once I hit the deadzone. If I don’t go into the deadzone with the throttle then everything continues to work. I copied and pasted the code exactly from here. Is the last long line supposed to be broken up into separate lines or something? Thanks for the help.
-
This post is deleted! -
I stopped using the LEDs and started using the mechanical detent once I was able to anchor my throttle. I’ll see if I can test it later this week.
-
I actually figured it out. I went into the TARGET GUI and enabled the LED’s on the throttle via the checkboxes and then your script worked correctly. With that said, I don’t use the LED’s now. I use a hybrid of your script. I bought the TUSBA for the Cougar throttle so I can use it without the Cougar stick and I use the switches on the Warthog throttle with the FSSB R3 for the Warthog stick plus the MFD’s and your G-13 profile. Then, next week I have the Obutto cockpit coming so that will shuffle it all up. Without your script though, I would be SOL.
Re-ordering controllers in Windows is a huge pain still and there is no fix.