Morphine's Profile
-
Whenever I put the line of code for the LED’s in, the virtual controller freezes and does not move any axis. Only the non-led profile works and I haven’t found a way to make the LEDs work. ANy ideas?
-
I sometimes made a bit complex Warthog programming, using the LEDs as indicators for a number of things. Those scripts ended up causing problems with the Warthog programming and drivers. I discussed it with Thrustmaster Support, and they dug it out all the way. They provided me with some new internal files to their TARGET unit.
They did not provide any exact information, but when overriding the older TARGET file in their own directories, it fixed these LED and freezing problems. Even when looking inside the file, it is not self explanatory even by programmer eyes.The fixed file obviously was overriding something in their own setup, but I think they did not re-version their TARGET software because of this. It may or may not be fixed in their distribution, and you can always try to reload the TARGET software, and see if it is newer, even without newer version number.
OR you could try inserting the file I received. You can find it in my profile, here: https://www.benchmarksims.org/forum/showthread.php?5857-Is-there-a-TM-Warthog-profile-that-mimics-F16-hotas-setup&p=71632&viewfull=1#post71632 Remember to backup the old one.
I never had any problems after I replaced the old one, and since then my profile has been working perfect.Of course my profile may be a borderline case, along with the author. But hey, if it fixes something internal, it might fix it for you too!
Greetings to a fellow Finn!
-
Whenever I put the line of code for the LED’s in, the virtual controller freezes and does not move any axis. Only the non-led profile works and I haven’t found a way to make the LEDs work. ANy ideas?
As TKorho says, there seems to be some bugs in the LED handling as I’ve also had problems and removed the LED code (I also decided to use the physical AB detent so I didn’t need the LEDs). You could try using the newer tmh file that he provided to see if that fixes the problem as well.
@TKorho, thanks for providing the new tmh file.
-
As TKorho says, there seems to be some bugs in the LED handling as I’ve also had problems and removed the LED code (I also decided to use the physical AB detent so I didn’t need the LEDs). You could try using the newer tmh file that he provided to see if that fixes the problem as well.
Yeah the only LED coding I have is for the Maser Arm and Master Lighting Switch for FENCE purposes but I always physically verify the positions of the switches anywho so it is redundant. However I have never had a problem with those two LEDs. The only peculiarity I have found is it doesn’t check the switch positions when you spin up your profile and (for me at least) I would have to cycle those two toggles to get the throttle/TARGET to get it’s act together. Other than that all normal. However I’m also not running Morph’s profile other than the engine start/stop coding.
-
I’m having some trouble with this. I have a fresh install of 4.32 v7, and fresh install and updated firmware of the HOTAS Warthog. I ran the script in target script editor and launched BMS, and loaded the warthog_dx key file and configured everything as per the .png files. It seemed to work ok once, though none of the buttons on the stick worked. Buttons on the throttle worked though. But after exiting the sim all the settings for the flight and avionics controls tabs reset, and I can’t get them to stay set now… I’ll set them and all will appear well, but I launch a TE and the controls don’t work, and when I exit the sim everything is reset in the menus again.
Also, when the profile is loaded, a lot of the buttons (like TMS and DMS for example) show up as unmapped in the in-BMS keyfile viewer on the controller config page. Is that normal because they are sent as DX keystrokes?
-
I’m having some trouble with this. I have a fresh install of 4.32 v7, and fresh install and updated firmware of the HOTAS Warthog. I ran the script in target script editor and launched BMS, and loaded the warthog_dx key file and configured everything as per the .png files. It seemed to work ok once, though none of the buttons on the stick worked. Buttons on the throttle worked though. But after exiting the sim all the settings for the flight and avionics controls tabs reset, and I can’t get them to stay set now… I’ll set them and all will appear well, but I launch a TE and the controls don’t work, and when I exit the sim everything is reset in the menus again.
Also, when the profile is loaded, a lot of the buttons (like TMS and DMS for example) show up as unmapped in the in-BMS keyfile viewer on the controller config page. Is that normal because they are sent as DX keystrokes?
Upon further review of the middle portion of this thread, it looks like I am suffering from the wrong dx controller number issue. I’m going to try to get that sorted today. Probably need to lock the two config files as well.
-
Hey Gearbox, I think you’ve identified the problem (device numbering) and how to fix it. Good luck and let us know if you have any questions.
-
Hey Gearbox, I think you’ve identified the problem (device numbering) and how to fix it. Good luck and let us know if you have any questions.
It was indeed the numbering. Had to use JoyIDs to make it work, replugging and reboots wouldn’t move the assignments. Seems to be working perfectly now. Thanks!
-
Hey guys - I’m a first time Warthog user - and I have a few questions:
First of all a few questions regarding the material things in my hands:
My Y axis Deadzone works nice, it stands on the 32768 when I leave it.
But my X axis deadzone only works when I come from the right back to the middle. Coming from the left it can stay also on ~31900 (extrema, average I’d say ~32300).
If I want to reach X 65535, I MUST go on Y > 41000, on Y = 0 I can reach X 64300. Going to the left there is no problem up and down.If I calibrate my throttle, my Right throttle gets scaled down becoming unsymetric to the left throttle. I have to delete the calibration in order to use it correctly. Is that normal?
I only flew one time yesterday, taking off and landing a few feets behind a C17 in the windy Ramp Start TE was feeling faqing good (I guess sometimes it would be better not to be able to see numbers).
Will I note something later on perhaps?Above the chinese and boat hat, there is that fat flat grey thing. Is it normal that it stucks forward, but not backward?
So now about the Profile and all the things giving the thing a sense:
I started the Target Script Editor, loaded the TMC file, compiled it, and pressed run.
Is this the procedure I have to do after every OS reboot if I want to play falcon? Can I close Target Script editer after pressing run? Or does it have to be active while playing?Edit: Can I make a button press Ctrl+Shift+home / Scroll lock too?
Last I want to say big thanks 1000 times for the profile, everything is easier when you can take a look at how others handle it!
-
The slider that sticks forwards does so on purpose, it’s for closing the speed brakes.
Dunno about your zeroing, sounds like something might be wrong with it. Might want to contact TM support.
Yes you have to launch the target script every time you want to use it in falcon, and leave it open.
-
Now I have one more question:
in Kolbes Falcon BMS Keyfile there is written:
CODE Modifier(s) key(s) 0 None 1 Ctrl 2 Shift 3 Alt 4 Ctrl Shift 5 Ctrl Alt 6 Alt Shift 7 Ctrl Shift Alt
In the tmc there is written:
MapKey(&Throttle, PSF, PULSE+L_SHIFT+L_CTL+'t'); // 0x14 4 MapKey(&Throttle, PSM, PULSE+L_CTL+'t'); // 0x14 1 MapKey(&Throttle, PSB, PULSE+L_SHIFT+L_ALT+'l'); // 0x26 6 MapKeyR(&Throttle, PSB, PULSE+'l'); // 0x26 0
this means in Warthog_dx.key
0x14 4 = inexistent
0x14 1 = Line 525 SimOpenChatBox -1 0 0X14 1 0 0 1 “Sim-Chat”
0x26 6 = Line 179 SimLandingLightToggle 1142 0 0X26 6 0 0 1 “LG Panel-Lights Landing Switch”
0x26 0 = Line 103 SimExtlMasterNorm 1084 0 0X26 0 0 0 1 “EXT LIGHTNING-Master Norm”But I have seen that it works.
My question is, why does it work?btw wtf is KevinsFistofGod? Edit: https://www.benchmarksims.org/forum/showthread.php?11733-what-is-quot-Fist-of-God-quot&highlight=KevinsFistofGod
Edit: Jeah the Kolbes Falcon BMS Keyfile documents table seems to be wrong, but his Keyfile generator 1.6.xls does the job correct I guess:
CODE MODIFIER 0 none 2 ctrl 1 shft 4 alt 3 ctrl shft 6 ctrl alt 5 alt shft 7 ctrl shft alt ```so in fact they are masks for:
SHIFT 1 (bin)0001
CTRL 2 (bin)0010
ALT 4 (bin)0100 -
For some reason this didn’t work for me. Throttle was set as rudder, china hat controlled the throttle and slew controls simply didn’t work.
-
For some reason this didn’t work for me. Throttle was set as rudder, china hat controlled the throttle and slew controls simply didn’t work.
Sounds like you didn’t do all the axis assignments in the flight controls and avionics tabs correctly.
-
I can understand for the rudder and slew controls but how do you explain the china hat acting as the throttle?
-
I can understand for the rudder and slew controls but how do you explain the china hat acting as the throttle?
The script makes the china hat act like an axis. Do you have the devices with the correct directx ids? I posted this in another thread for someone who was having similar problems:
You have to use the Warthog_DX.key file or whatever it is called that comes with Morphine’s profile, or adjust your own keyfile to match its assignments.
You have to verify your DX assignments. The stick has to be device 1 and the throttle has to be device 2. Pedals can be whatever but I have them as device 3.
You can use the JoyIDs utility to view dx number assignments and re-assign them. I have the utility in a stack of icons on my desktop that serve as my falcon launch checklist.
So to get working:
-
Use JoyIDs to fix your assignments first. Stick 1, Throttle 2, Pedals 3.
-
Run the target script in the target script editor. You should hear some usb device plugging and unplugging sounds, and in JoyIDs the stick and throttle will vanish and Thrustmaster Combined should appear as #1
-
Launch falcon and go the controls section. Set it to use the warthog_dx keyfile.
-
Go to the avionics and flight controls pages and set them to match the screen shots supplied with the profile
-
Test everything. If it’s all working to your satisfaction, there are a couple of files in the config folder that should be set to read-only to prevent the axis assignments from getting busted if you open falcon without having run the target script. They are /Falcon BMS 4.32/User/Config/axismapping.dat and joystick.cal. Remember to uncheck read-only on them if you want to make changes in the future.
You can download JoyIDs here: http://theairtacticalassaultgroup.co…ad.php?t=13009
-
-
I can’t get this to behave realistically at all. The pinky switch only zooms, there is dogfight mode on the hats, and throw in an air brake there too.
What am I doing wrong? I’m running the target program and warthog_dx.key file in game.
-
I’m sorry, it was my bad for not doing proper research before saying it didn’t work. I jumped to conclusions too fast and I apologize for that.
-
Ok, I don’t know what I did, but it fixed itself. I wonder if I had a brainfart and didn’t run TARGET or something.
Anyways, is there a command to narrow the radar scan for AA? Also, is there a HOTAS command for selecting A-A mode, instead of having to hit the ICP?
-
Ok, I don’t know what I did, but it fixed itself. I wonder if I had a brainfart and didn’t run TARGET or something.
Anyways, is there a command to narrow the radar scan for AA? Also, is there a HOTAS command for selecting A-A mode, instead of having to hit the ICP?
You can bump the radar cursor off the left or right edge and it will narrow the scan. Do it again to go back to normal full-width scan. You can also bump off the top and bottom to increase and decrease range.
I always just use MRM override, it has pretty much everything you’d want from AA mode in it.
-
I can’t get this to behave realistically at all. The pinky switch only zooms, there is dogfight mode on the hats, and throw in an air brake there too.
What am I doing wrong? I’m running the target program and warthog_dx.key file in game.
This has to be either a wrong direct x device number issue or you didn’t set up the flight controls and avionics tabs correctly.