A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
It’s good to see someone keeping Morphines going well done….
I have this unusual problem particularry using Mavericks and also boresighting them via the TGP, the TMS up button seems very hit n miss… All other munitions it works fine, locks up great in AA FCR and AG FCR, using LGB’s it fine, I get IR point after ground stabilising… The issue is using Mavs on their own, I am TMS ing up like a loon to get a lock, sometimes the lock only appears at 4-5 miles… I have also tried boresighting them via the TGP, I get all sorts of issues, pages not being SOI when they should, lots of issues getting an IR Point, multiple tries etc… I love the Warthogs but this one area is causing a lot of frustration… Anyone have any ideas? I have been through the sorting .txt and all is as it should be. I am running windows 7 64 bit…
-
Just make sure you have the weapon up on a MFD and it’s SOI. The only other advice I can offer is to zoom the maverick seeker head in, pinkie button and then TMS up. I find the IR mav’s like the the D’s are better at getting a lock from further out than the Optical ones.
-
Thanks I appreciate the quick response… I have used the training mission Cavok as a way of boresighting… I made a short video of my attempts, I’m sure its not me… Have you heard of any glitches that could cause this? Here is a link to the video I made
https://www.dropbox.com/s/5lxf3c07xcah6nn/falcon%20bms.exe%2012.04.2017%20-%2022.27.16.01.mp4?dl=0
-
Thanks I appreciate the quick response… I have used the training mission Cavok as a way of boresighting… I made a short video of my attempts, I’m sure its not me… Have you heard of any glitches that could cause this? Here is a link to the video I made
https://www.dropbox.com/s/5lxf3c07xcah6nn/falcon%20bms.exe%2012.04.2017%20-%2022.27.16.01.mp4?dl=0
It’s you, First at 1:05 you go to slew the the TGP and you press the button on the slew controller. This puts the TGP into laser search mode. This starts messing up the process. Next you should zoom out on the TGP if you want to track the ship. Try to put all of the ship under the gap in the center of the cross hairs. After you finally get it to lock, the hand off starts and fails.
You’re trying to shoot AGM 65G’s in the wide FOV. Which means when you hit TMS up, you’re telling the weapon to force correlate. The mode you’re using bypasses the tracker unit, which is why you don’t get a lock. Try zooming in with the missile (pinkie button) or shooting a missile that doesn’t force correlation’ like a Mav D. This is also why when you TMS up repeatedly the missile switches from Area to HOC. It’s not locking a target because the most of the target is out side the the targeting gate. So it goes into Area target mode (force correlate), It’s discussed in the 34-1-1 on page 162.
At 2:53 the TGP loses it’s point tracking on the ship and switches to area mode. This causes the missile switches out of pre. And even while you’re in VIS, mode you are still trying to force correlate the missile. At 3:02 you put the missile back into pre mode and since the TGP isn’t tracking the ship, the missile’s camera jumps off it. And since you failed to boresight the TGP and missile are now both looking at different areas. By 3:05 the TGP is now SOI, the ship isn’t under the TGP’s cross hairs and you’re hitting TMS up. The system thinks the TGP is trying to lock the water. Even though the ship is under mav crosshairs, it won’t lock or force correlate because the mav is not SOI.
-
I really appreciate the feedback… I am about three quarters through my training for the 185th and this issue is driving me mad. I will reload that mission and follow your advice and report back. Many thanks Aim
-
The slew button seems very sensitive to inwards pressure… I’m guessing thats what is going wrong, my trainer is going to fly the cavok training mission with me tonight and we will go through it.
-
Thanks a lot Gastone for updating the profile. Just got back in to BMS and was worried about Morphine’s profile being outdated for 4.33.
I have one issue though. The autopilot switch seems to be reversed. Like flipping the switch upwards on the designated switch on the throttle flips the switch DOWNWARDS in the simulator. Do I only need to modify the keyfile in BMS itself or do I need to modify the target script as well? Because I have no experience with that.
-
Thanks a lot Gastone for updating the profile. Just got back in to BMS and was worried about Morphine’s profile being outdated for 4.33.
I have one issue though. The autopilot switch seems to be reversed. Like flipping the switch upwards on the designated switch on the throttle flips the switch DOWNWARDS in the simulator. Do I only need to modify the keyfile in BMS itself or do I need to modify the target script as well? Because I have no experience with that.
It was setup by Morphine so that Alt hold on the F-16 matched the label on the Warthog Throttle. This is why the position is inverted relative to F-16. To change it, swap the a and the d on lines 166 and 168 of the target script.
-
For some reason when I use this script if I use the pinky shift everything stops working. For example DMS down swaps SOI fine between left and right MFDs but if I press the pinky button at all (and then release) that stops working completely. What am I doing wrong?
-
For some reason when I use this script if I use the pinky shift everything stops working. For example DMS down swaps SOI fine between left and right MFDs but if I press the pinky button at all (and then release) that stops working completely. What am I doing wrong?
When people have issues with this profile, the two major culprits are not deleting the teamspeak joystick plugin and not using the up to date . Key file. See the first page of this post for further info.
-
I believe there was a conflict with the alternative BMS launcher… I had made some axis binds in there and I don’t believe it worked well with this profile. A clean install and following the steps worked and all is good!
-
Having an issue here, I just reinstalled windows and BMS with it, and now when I run the TARGET script, I’m not seeing “Thrustmaster Combined” in the setup menu or in my windows devices list. I’m only seeing “Thrustmaster Virtual Game Controller (root).” Using the most recent version of TARGET and have never had Teamspreak installed. Any help appreciated, thanks.
-
Having an issue here, I just reinstalled windows and BMS with it, and now when I run the TARGET script, I’m not seeing “Thrustmaster Combined” in the setup menu or in my windows devices list. I’m only seeing “Thrustmaster Virtual Game Controller (root).” Using the most recent version of TARGET and have never had Teamspreak installed. Any help appreciated, thanks.
If you are running Target v3.0.16.615 v2 and the latest version of the profile, available on page 1 of this thread, and are getting root, something is preventing target from creating the combine device. There can be numerous causes for this.
Depending on how you reinstalled windows, there maybe registry errors. Or you haven’t installed the warthog drivers yet. It could be the windows power saving settings. Maybe it’s anti virus software, or Target isn’t pointed at the right directory. It could be some type of windows conflict related to the latest windows update. I really can’t tell based on what info you have provided me. What I can tell is, that the problem is on your end.
As of now the profile works on windows 10 version 1703 OS build 15063.850. The bottom line is that the trouble is on your system. There are to many variables and since I have no knowledge of what is going on with your PC, the only advice I can give you is to follow the steps on page one, and then try and trouble shoot it yourself.
I would start with the Warthog drivers, move onto the power saving, Make sure Target is pointed at it’s install folder, then look at anti virus, and finally windows registry and updates. IE eliminate the easy fixes first.
Hope it helps.
Edit: Just upgraded Win 10 to build 16299.125. Profile and target both work, after a restart.
-
Thanks for those ideas. Will work on this and update with any solution!
-
Sorry guys I have troubles with the profile…when I load it it starts then after a while in the Sim the axis stops working…it happens as I touch the throttle and so it is unusable.
It is not the only script that has the same behavior, but others are for Dcs.
I have win 10 up to the latest updates and the latest drivers and firmware for the warthog.
Can someone point me to a fix?
PS I see only thrustmaster combined in the USB control panel and I tried to uninstall and reinstall both Target and drivers
Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
-
I think I found a workaround……if I comment all the part regarding the throttle led in the profile it works… someone knows why?
I tried this because I tested mud’s profile and it had not the same problem, then analyzed the differences that could be leading to these freezes…that led me to the LEDs…
The problem is that I like the LEDs functionality of morphine profile and I would like to use it…Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
-
I think I found a workaround……if I comment all the part regarding the throttle led in the profile it works… someone knows why?
I tried this because I tested mud’s profile and it had not the same problem, then analyzed the differences that could be leading to these freezes…that led me to the LEDs…
The problem is that I like the LEDs functionality of morphine profile and I would like to use it…Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
Please make sure you have downloaded the most recent version of the profile from the first page of this thread. I have no issues with LED’s. The throttle draws a lot of power, it sounds like your motherboard may not be capable of delivering the amps need to drive it. Your first step in trouble shooting should be to try plugging the throttle into a powered USB hub.
-
I have a USB powered hub and the latest version from this post.
ThanksInviato dal mio ONEPLUS A5010 utilizzando Tapatalk
-
I have a USB powered hub and the latest version from this post.
ThanksInviato dal mio ONEPLUS A5010 utilizzando Tapatalk
If the profile works then stops, check the windows 10 power savings settings. Make sure selective suspend is disabled. Windows has a habit of powering off USB ports if the power savings is in use. You may even have to get into the device manager and disable windows from shutting off power saving. I would also re-download the profile again too if you have been making edits. It’s easy to inadvertently break the profile.
After you trouble shoot windows power saving, if u still have issues Try moving the usb hub to other ports and ot replace your USB hub. The issue sounds like it’s power related on your end. Follow those steps and you’ll eliminate the causality tree for power issues. After, that you’ll have to look at Windows issues.
-
If the profile works then stops, check the windows 10 power savings settings. Make sure selective suspend is disabled. Windows has a habit of powering off USB ports if the power savings is in use. You may even have to get into the device manager and disable windows from shutting off power saving. I would also re-download the profile again too if you have been making edits. It’s easy to inadvertently break the profile.
After you trouble shoot windows power saving, if u still have issues Try moving the usb hub to other ports and ot replace your USB hub. The issue sounds like it’s power related on your end. Follow those steps and you’ll eliminate the causality tree for power issues. After, that you’ll have to look at Windows issues.
Thanks for the heads up….i disabled windows usb powermanagement both in the power profile, and in every singe usb device in the hardware control panel, buth nothing works so far.
The only thing that makes the profile working for now is to comment the parts of the script where there is the led management…so i thing it could be something relating to thrustmaster drivers not managing leds well under windows 10…no one with the same issue?