Morphine's Profile
-
I am having trouble with this…
This is what I did:
-Made sure stick and throttle where in the right USB ID order
-Used target script to combine them to a single controller (Device name set to Thrustmaster Combined) EDIT: Used FalconBMS-Warthog.tmc
-Loaded up FalconBMS, setup axes like here (https://sites.google.com/a/hodderweb.com/warthog/falcon-bms/home/bms-setup) - only difference for me is that my device is called Thrustmaster Virtual Game Controller (root)
-Loaded up the key file (Warthog_DX-4_33_2.key)
What happens in game that all my axes work - but key bindings are all wrong - ie trigger is “OSB1 button push”What am I doing wrong?
-
Direktor go to the hogging Reddit site. There is a fix for your issue there… I don’t have a link right now but I remember seeing it there.
-
Direktor go to the hogging Reddit site. There is a fix for your issue there… I don’t have a link right now but I remember seeing it there.
Sorry, this does not help me. I did not find the thread you are referring to.
-
Sorry, this does not help me. I did not find the thread you are referring to.
I think he wants you to Google it. It does not sound like a site on this Forum.
-
Stupid autocorrect got me. Hoggit, this is the link not sure if this is your issue but a couple posts down looks like it might be. https://www.reddit.com/r/hoggit/comments/3r0bhm/morphines_bms_profile_for_warthog_updated_for_433/?sort=new
-
Well, while I’m here I might as well ask my own question… I prefer to use the slider on the throttle as my zoom, and don’t need view controls on the coolie hat… I remapped those two things in the game but they don’t seem to be recognized. So I guess that means I need to change something in the script… Problem is when I look at code it looks like the green stuff from the matrix and I don’t want to mess it up. Do I just delete lines with the word slider and coolie in them or is it more complicated then that?
Thanks
-
I spent a few hours on this the last few days and made some updates. I cleaned up the file a lot and added some sounds to buttons which were missing.
I have also created a profile which uses the Paddle for the shift state instead of the Pinky button for those of you who prefer that.
Both profiles have been tested.
Updated Original Profile: https://www.dropbox.com/s/eb8393zfy1ll9bg/Warthog_DX-4_33_2.key?dl=0
Paddle Shift Profile (Target Script & Keyfile): https://www.dropbox.com/s/vzn0gl4kd4l3s6y/Warthog_DX-Paddle-Shift-State.zip?dl=0
Please keep reporting any bugs you might find.
Thanks for your second edition of the profile HOTAS, works better, but it is incomplete.
Why do not you take as an example the pattern of Morphine edited for version 4.32?
The last one you posted, does not have the keys to radio communications, it does not have the DMS switch to the next or previous steeropoint, the slew control moves on the wrong axis, flaps not working …
If you could create a profile equal to that of Morphine I would be really grateful! -
Thanks for your second edition of the profile HOTAS, works better, but it is incomplete.
Why do not you take as an example the pattern of Morphine edited for version 4.32?
The last one you posted, does not have the keys to radio communications, it does not have the DMS switch to the next or previous steeropoint, the slew control moves on the wrong axis, flaps not working …
If you could create a profile equal to that of Morphine I would be really grateful!All of these things all work properly for me. Sorry, I work a lot, I have been working on it whenever I have time.
Mine works flawlessly though, and I use that exact same one. Decalre, Picture, nearest threat, changing waypoints, etc… every mapping on the PDF document works fine for me. My friends are using it too and they are not having issues with it. I just messaged them to check. I would not have shared this with the community if these things did not work.
The flaps switch is mapped to Autopilot systems. The flaps are automated on the F16, and all the new planes as well as far as I know, I know the F-18 has automated flaps for sure.
Though aside from all that, i’ll be happy to try and help you get it working.
From what I read it sounds like your Target script is not running. What you are describing is exactly what would happen if that were the case. Those are all shift state commands, plus the Radio calls are short macros (which could actually be mapped out with the 4.33 update), and the Target script is needed for that. The Flaps switch is not a shift state command, but if you were thinking that is in fact for the flaps then we already got to the bottom of that.
However, if you are running the target script then we have some detective work to do.
Morphine’s 4.32 is exactly what this is/was.
-
Stupid autocorrect got me. Hoggit, this is the link not sure if this is your issue but a couple posts down looks like it might be. https://www.reddit.com/r/hoggit/comments/3r0bhm/morphines_bms_profile_for_warthog_updated_for_433/?sort=new
Tnx Sage!
In the meantime i figured out that it has to do with the controller order in the windows game controllers panel.
I did unplug all the devices and plugged them in in the correct order, but every time I restart my machine they get messed up.
Is there a (known) way around this? -
Tnx Sage!
In the meantime i figured out that it has to do with the controller order in the windows game controllers panel.
I did unplug all the devices and plugged them in in the correct order, but every time I restart my machine they get messed up.
Is there a (known) way around this?Do you run the script from the TARGET GUI or the Script Editor?
I always use the Script Editor and it is listed as Combined.
n/m, I just ran it with the GUI and it is still Combined, same as the script editor. Let me just list some ideas you can try if you want.
Try one at a time:
1) Do this first: Disable USB selective suspend setting This is what could be reassigning your controllers.
–-------Make sure your Target script is running so it creates the Thrustmaster Devices in DM
---------Go to Device manager
---------Expand “Thrustmaster Devices”
---------Right click on each one (3) and choose the “Power Management” Tab / Uncheck “Allow the computer to turn this device off…”
---------Finally, Go to Control Panel / Power Options / Disable it in your profile2) Try running the script with the opposite application of what you usually use.
3) –-Unplug all other devices except for your mouse and keyboard. Remove everything, Mic, Headset, Rudder Pedals, Game pad, ETC…, even TrackIR if you use that.
------Unplug your stick and throttle.
------Reboot
------Plug in ONLY your Stick and Throttle
–----Start the target script and go in to Falcon and see if it works.
------After confirming if it works or not go ahead and plug everything back in. (If controller IDs get messed up again after you plug everything in then we will deal with that then)
4) Uninstall Warthog drivers / Reboot / Reinstall Drivers
5) Try this last: Go to device manager / Go to the top menu bar and choose - “View”, “Show Hidden Devices” / Go through your “Human Interface Devices” tree and remove all the devices that are light grey (Ghosted) - Reboot
-
Boxin, thanks for your effort. I am using the key file you provided and everything appears to work as it should except my zoom. I gave up trying to move it so under the view panel I selected mouse wheel. Applied it and went in game. No zoom scroll… Does it have something to do with this key file or do you think I eff’d something up elsewhere? Edit: I am 99% positive I as mapping it to fFOV not Zoom which seems to be the correct way so I don’t Thai k that is the reason.
-
Do you run the script from the TARGET GUI or the Script Editor?
I always use the Script Editor and it is listed as Combined.
n/m, I just ran it with the GUI and it is still Combined, same as the script editor. Let me just list some ideas you can try if you want.
Try one at a time:
1) Do this first: Disable USB selective suspend setting This is what could be reassigning your controllers.
–-------Make sure your Target script is running so it creates the Thrustmaster Devices in DM
---------Go to Device manager
---------Expand “Thrustmaster Devices”
---------Right click on each one (3) and choose the “Power Management” Tab / Uncheck “Allow the computer to turn this device off…”
---------Finally, Go to Control Panel / Power Options / Disable it in your profile2) Try running the script with the opposite application of what you usually use.
3) –-Unplug all other devices except for your mouse and keyboard. Remove everything, Mic, Headset, Rudder Pedals, Game pad, ETC…, even TrackIR if you use that.
------Unplug your stick and throttle.
------Reboot
------Plug in ONLY your Stick and Throttle
–----Start the target script and go in to Falcon and see if it works.
------After confirming if it works or not go ahead and plug everything back in. (If controller IDs get messed up again after you plug everything in then we will deal with that then)
4) Uninstall Warthog drivers / Reboot / Reinstall Drivers
5) Try this last: Go to device manager / Go to the top menu bar and choose - “View”, “Show Hidden Devices” / Go through your “Human Interface Devices” tree and remove all the devices that are light grey (Ghosted) - Reboot
Thank you Boxin, appreciate the effort. I will test using your suggestions, and report back with the results/more info!
-
Boxin, thanks for your effort. I am using the key file you provided and everything appears to work as it should except my zoom. I gave up trying to move it so under the view panel I selected mouse wheel. Applied it and went in game. No zoom scroll… Does it have something to do with this key file or do you think I eff’d something up elsewhere? Edit: I am 99% positive I as mapping it to fFOV not Zoom which seems to be the correct way so I don’t Thai k that is the reason.
I haven’t tried to do this as I use Trackir, but I will take a look at it and get back to you
-
I haven’t tried to do this as I use Trackir, but I will take a look at it and get back to you
Bah! I am an idiot. I did remap it under the zoom not FOV. I use trackIR too. Just prefer the z axis to move forward back in the cockpit and zoom with the slider. I -think- I might have tried to put the slider in zoom instead of FOV earlier which could have been why I had trouble getting it to work. I will try later. So only issue now is figuring out how to turn on the jammer. I hit j and all my misses fell off so I don’t think it is j in this profile.
-
Bah! I am an idiot. I did remap it under the zoom not FOV. I use trackIR too. Just prefer the z axis to move forward back in the cockpit and zoom with the slider. I -think- I might have tried to put the slider in zoom instead of FOV earlier which could have been why I had trouble getting it to work. I will try later. So only issue now is figuring out how to turn on the jammer. I hit j and all my misses fell off so I don’t think it is j in this profile.
Right on. What do you use for the radar antena?
Yea if you want to see what the profile does just look at the original PDF docs. I have not changed a thing, only updated.
-
Right on. What do you use for the radar antena?
Yea if you want to see what the profile does just look at the original PDF docs. I have not changed a thing, only updated.
Not sure yet. My hope was to use keys for the radar. Preferably the coolie hat as I don’t need views mapped to it.
-
Do you run the script from the TARGET GUI or the Script Editor?
I always use the Script Editor and it is listed as Combined.
n/m, I just ran it with the GUI and it is still Combined, same as the script editor. Let me just list some ideas you can try if you want.
Try one at a time:
1) Do this first: Disable USB selective suspend setting This is what could be reassigning your controllers.
–-------Make sure your Target script is running so it creates the Thrustmaster Devices in DM
---------Go to Device manager
---------Expand “Thrustmaster Devices”
---------Right click on each one (3) and choose the “Power Management” Tab / Uncheck “Allow the computer to turn this device off…”
---------Finally, Go to Control Panel / Power Options / Disable it in your profile2) Try running the script with the opposite application of what you usually use.
3) –-Unplug all other devices except for your mouse and keyboard. Remove everything, Mic, Headset, Rudder Pedals, Game pad, ETC…, even TrackIR if you use that.
------Unplug your stick and throttle.
------Reboot
------Plug in ONLY your Stick and Throttle
–----Start the target script and go in to Falcon and see if it works.
------After confirming if it works or not go ahead and plug everything back in. (If controller IDs get messed up again after you plug everything in then we will deal with that then)
4) Uninstall Warthog drivers / Reboot / Reinstall Drivers
5) Try this last: Go to device manager / Go to the top menu bar and choose - “View”, “Show Hidden Devices” / Go through your “Human Interface Devices” tree and remove all the devices that are light grey (Ghosted) - Reboot
OK - this is how it is:
If everything is unplugged, computer rebooted, and then plugged in correctly (order wise), after binding the controllers and loading the keyfile/configuring axes - everything works fine.
So I know what needs to be done before starting FaconBMS.
The problem seems to be the USB hub that I use (not enough ports in my MOBO, and cable length issues) because after OS restart, the USB devices order gets messed up.
For now I just keep the HOTAS/pedals unplugged until I plan on playing, upon which I just connect them in the correct order and taaadaaaa problem solvedAnyway, thank you for the great profile, hope to see you over the virtual battlefields (preferably same sides )
-
OK - this is how it is:
If everything is unplugged, computer rebooted, and then plugged in correctly (order wise), after binding the controllers and loading the keyfile/configuring axes - everything works fine.
So I know what needs to be done before starting FaconBMS.
The problem seems to be the USB hub that I use (not enough ports in my MOBO, and cable length issues) because after OS restart, the USB devices order gets messed up.
For now I just keep the HOTAS/pedals unplugged until I plan on playing, upon which I just connect them in the correct order and taaadaaaa problem solvedAnyway, thank you for the great profile, hope to see you over the virtual battlefields (preferably same sides )
That’s great. Glad to see you got it sorted out.
Sounds good. I have been looking at Base Ops and looking for servers lately.
-
This is going to be a stupid question, I know, but I am trying to get my radios working and using the Comms switch on my warthog. How does it work? I have to press via the keyboard to call up the relevant radio menu? T for tower…W for wingman…F for flight etc? There is no button mapped to do this? I must use the keyboard? Ok, assuming info have to first call up the appropriate radio menu, then how does it interact with my Comms switch on the WH throttle? Say, for example, the Comms switch up, which operated the UHF radio, and when I press it, gives a nice bit of squelch to show I have pressed it. I want to communicate with the tower: I call up the tower menu with T, then cycle through a page or two with subsequent presses of the T key on the keyboard, then select the cammand I want (for the purposes of this hypothetical, I want clearance to land, which is say 4). I do this, and the command is sent. There is nothing for the WH Comms UHF switch to do; all done via the keyboard, right? What’s the point of having a Comms switch at all if I can do it all via keyboard? Right, or have I got it very wrong? Grateful advice…
Apoll
-
Hi all!
Is there any 4.33 profile updated? If so, where could I take It?
Greetings.