Morphine's Profile
-
Boxin already updated it on page 39. It’s port #389, works great.
In the old profile of Morphine it was also the file Falcon BMS-Warthog.tmc.
Before starting the simulator, I started the program Target Script Editor and loads the file .tmc
I downloaded the file put Boxin and once installed, I called in the settings of the BMS.
I started the simulator, I find all the commands unpacked and no longer functioning as before in profile 4.32.
Could you give me some advice?
thanks -
Still having issues here. I had the profile working perfectly in 4.32, but after a windows 10 upgrade, no longer. I assume its because of the way BMS sees joystick ID’s but I’m not having luck figuring out how to control that.
Running the TM Warthog, MFDs, Saitek pedals and TrackIR. In the setup screen all the buttons on the stick that have keys assigned to them (via Target) work as they should, but all the DX buttons (all the buttons on my stick and about half of the throttle assignments) are all muddled and mixed up. This includes most of the shifted functions, is the pinky shift controlled by the game or by Target? Also, I am having issues with one of the MFDs not working at all (it works fine, BMS just doesn’t see the input) and worst of all, BMS doesnt register my stick X and Y axes. I thought that was strange because since it is one combined virtual device, I would have figured it would have been able to see them no problem. The assignable axes show up in the available axes menu when you’re assigning them but they don’t give any input when the stick is moved.
If anyone has had any luck with getting the joystick IDs right, or whatever is causing this problem, please share. This is making me nuts!
This happened to me before. When we run the script it creates 3 devices. Itg seems like it just blows up the keyfile for some reason. I usually fix it by deleting the keyfile and just copying my backup in to the config folder. There have been a few times were I had to complete reinstall BMS too. Matter of fact this just happened to me today lol. I fixed it by reinstalling and using a backup of the keyfile. just delete it, download it again, then copy it in to the config folder. If that doesnt work, reinstall BMS. If that doesnt work, let us know.
So you’re not alone, and you’re not nuts.
Thanks Boxin,
I’m not able to fly right now or have my cockpit set up so there was no way I was going to be able to make changes. Thanks for taking the initiative and making the profile compatible with 4.33.
- Morphine
Anytime man, A lot of us can’t function without your script. Hope you get back in the cockpit soon.
In the old profile of Morphine it was also the file Falcon BMS-Warthog.tmc.
Before starting the simulator, I started the program Target Script Editor and loads the file .tmc
I downloaded the file put Boxin and once installed, I called in the settings of the BMS.
I started the simulator, I find all the commands unpacked and no longer functioning as before in profile 4.32.
Could you give me some advice?
thanksJust a few thoughts…
The keyfile may have been corrupted. It is rare and doesnt happen often, but it does happen. It just happened to me an hour ago. In this case delete the keyfile and copy a fresh one in to your config folder.
I fixed the problem by completely uninstalling Falcon BMS 3.33 properly with the Uninstaller (run setup), then copying a fresh keyfile backup.
Windows freaks out sometimes after starting and stopping Target because there are times it will create another usb device in Windows. for 3 days I kept having to do an automatic repair on the stick and throttle because windows disabled it because it is unable to use USB 3.0??? I have USB 3.0 disabled in BIOS because I cant stand how it puts my controllers to sleep whenever Windows feels like it. In this case I went in to device manager, uninstalled the 3 virtual game controllers Target creates and rebooted.
Go in to device manager, click view in the top menu and Select “Show Hidden Devices”. Expand the “Human Interface Devices” tree and you will see a lot of items that are ghosted. I clean these out every few montths. However, if you dont feel comfortable deleting these please don’t do it. Once or twice when this happened to me - reinstalling didnt work. I deleted all of these things out of device manager and it did the trick, i think.
Let me know how you get on and ill help you get to the bottom of it.
-
Boxin - thank you for taking the time to do this. Much appreciated!
-
Big Ups to Boxin for taking the time to do this. I found a bug or two. The JFS starter toggle (engine Opp left forward on the hotas) left was triggering a UHF radio freq change. This was due to the new keybind for shift+ctlr+J, which is now is now UHF ___._XX Up. I rebound Jet Fuel Start Switch Up in the target profile and keyfile to Shift+alt+ctrl+J to deconflict it. Also, Morphine had left the idle detent set switch to JFS, So I went and set right engine opp forward to alt I for hotas idle detent. To fix it you’ll need a new profile and target script. You can get both here.
https://www.dropbox.com/sh/2r056hw227rt705/AABN6ah4XTs8V_QgtZMEdjVea?dl=0
-
Big Ups to Boxin for taking the time to do this. I found a bug or two. The JFS starter toggle (engine Opp left forward on the hotas) left was triggering a UHF radio freq change. This was due to the new keybind for shift+ctlr+J, which is now is now UHF ___._XX Up. I rebound Jet Fuel Start Switch Up in the target profile and keyfile to Shift+alt+ctrl+J to deconflict it. Also, Morphine had left the idle detent set switch to JFS, So I went and set right engine opp forward to alt I for hotas idle detent. To fix it you’ll need a new profile and target script. You can get both here.
https://www.dropbox.com/sh/2r056hw227rt705/AABN6ah4XTs8V_QgtZMEdjVea?dl=0
Thanks bro, i’ll fix that up. After reading the BMS key file manual I saw that callback was changed, or expanded rather since they added a few things.
It’s awesome the way they designed those functions. Going to give people some good flexibility.
-
Boxin, I tried to change the shift function to the paddle and not the pinky button. I wasn’t able to find all the lines that Morphine recommanded to change in his post. Neverthless, with some experiment i made it working BUT when i hit the paddle, the shift function is ON and STAYS ON, i need the hold the pinky button to deactivate the shift. Any idea why ? I’d like to have a help with it, i’m no expert at all with keyfiles and TARGET ! Thanks.
-
This happened to me before. When we run the script it creates 3 devices. Itg seems like it just blows up the keyfile for some reason. I usually fix it by deleting the keyfile and just copying my backup in to the config folder. There have been a few times were I had to complete reinstall BMS too. Matter of fact this just happened to me today lol. I fixed it by reinstalling and using a backup of the keyfile. just delete it, download it again, then copy it in to the config folder. If that doesnt work, reinstall BMS. If that doesnt work, let us know.
So you’re not alone, and you’re not nuts.
Anytime man, A lot of us can’t function without your script. Hope you get back in the cockpit soon.
Just a few thoughts…
The keyfile may have been corrupted. It is rare and doesnt happen often, but it does happen. It just happened to me an hour ago. In this case delete the keyfile and copy a fresh one in to your config folder.
I fixed the problem by completely uninstalling Falcon BMS 3.33 properly with the Uninstaller (run setup), then copying a fresh keyfile backup.
Windows freaks out sometimes after starting and stopping Target because there are times it will create another usb device in Windows. for 3 days I kept having to do an automatic repair on the stick and throttle because windows disabled it because it is unable to use USB 3.0??? I have USB 3.0 disabled in BIOS because I cant stand how it puts my controllers to sleep whenever Windows feels like it. In this case I went in to device manager, uninstalled the 3 virtual game controllers Target creates and rebooted.
Go in to device manager, click view in the top menu and Select “Show Hidden Devices”. Expand the “Human Interface Devices” tree and you will see a lot of items that are ghosted. I clean these out every few montths. However, if you dont feel comfortable deleting these please don’t do it. Once or twice when this happened to me - reinstalling didnt work. I deleted all of these things out of device manager and it did the trick, i think.
Let me know how you get on and ill help you get to the bottom of it.
I took your advice, I downloaded the file again believing that the previous one was corrupt, but have not solved the problem.
After making this attempt, I also installed the new Falcon 4:33, but without a good result.
The old profile of Morphine on the 4:32 worked very well and I am used to using it. With the new file Warthog_DX.key, you still have all the controls do not work, even I can not make even the MFD SOI or launch a missile.
If the procedure is used with the old files of Morphine, I do not know now how to do … I can not use the software target to create a new profile. -
I took your advice, I downloaded the file again believing that the previous one was corrupt, but have not solved the problem.
After making this attempt, I also installed the new Falcon 4:33, but without a good result.
The old profile of Morphine on the 4:32 worked very well and I am used to using it. With the new file Warthog_DX.key, you still have all the controls do not work, even I can not make even the MFD SOI or launch a missile.
If the procedure is used with the old files of Morphine, I do not know now how to do … I can not use the software target to create a new profile.I’m sorry you’re having trouble. Myself and all of my friends are using it and besides my key file / install going whacky yesterday it all seems to be working alright.
If I were you I would uninstall your Warthog drivers and go in to device manager and delete the 3 devices the script creates, reboot, then reinstall your Warthog Drivers.
The devices are in a node named “Thrustmaster Devices”.
I’ve done it before. It wont screw anything up. After you reinstall your Warthog and run Target, it will just create them again.
So many different variables. Best we can do is make an educated guess.
-
Boxin, I tried to change the shift function to the paddle and not the pinky button. I wasn’t able to find all the lines that Morphine recommanded to change in his post. Neverthless, with some experiment i made it working BUT when i hit the paddle, the shift function is ON and STAYS ON, i need the hold the pinky button to deactivate the shift. Any idea why ? I’d like to have a help with it, i’m no expert at all with keyfiles and TARGET ! Thanks.
I don’t know why. My first run at adapting the key file I had that exact same problem. It is why I ditched the shortcut I was trying to take and instead went through each line.
Whats happening to you with the shift state I could not figure out.
-
I don’t know why. My first run at adapting the key file I had that exact same problem. It is why I ditched the shortcut I was trying to take and instead went through each line.
Whats happening to you with the shift state I could not figure out.
Thanks for the reply anyway ! I’ll investigate.
-
Hi,
there is currently a working profile or working someone in mind?
thanks
-
Boxin, thank you so much!
and Gastone also thx
-
Does this updated profile work yet? I was under the impression it was still having issues. I’m looking forward to getting back into BMS again
-
Does this updated profile work yet? I was under the impression it was still having issues. I’m looking forward to getting back into BMS again
Been using it since day 1 of the update and I have had no issues. It works exactly like it always has, but for all the aircraft. You will still need to bind your new bindings, i.e. the nozzle for the harrier. That Harrier is amazing. The problems I have seen have been problems unrelated to the bindings, but problems with the install or the Hotas, all the problems described have happened to me multiple times in prior versions of BMS, and can be fixed, with the exception of editing the keyfile and Target script to use Paddle instead of the pinky button for shift state, I use pinky button though and have not attempted that edit, it may work fine if done correctly.
I had forgotten to modify the engine bindings because those callbacks were updated, but my JFET squadron mate Gastone caught this and fixed it.
If you have any problems just let the fine gentlemen here know and everyone will be more than happy to help. I check the thread more than once a day.
Here is the link so you don’t have to dig it up. https://www.dropbox.com/s/eb8393zfy1ll9bg/Warthog_DX-4_33_2.key?dl=0
-
Thanks for the update… I’m on it.
-
What do I have to press buttons to activate the framerate ???
-
Alt C then F@bullseye2:
What do I have to press buttons to activate the framerate ???
-
sorry, no….???
-
I believe those are the default keybindings, however yours may differ.
Search your keyfile for the following callback, OTWToggleFrameRate, to see which keys have been assigned.@bullseye2:
sorry, no….???
-
My mistake, it should be ALT C then F@Steve_U:
I believe those are the default keybindings, however yours may differ.
Search your keyfile for the following callback, OTWToggleFrameRate, to see which keys have been assigned.