Thrustmaster Warthog Profiles for Current WW2 AC

[WWDarkdiz]

Like I said, Requiem indicated his throttle fried due to plugging it into a USB 3 port.  I just write the scripts, and plug mine into USB 2 ports (admittedly I USED to plug them into a powered USB 3 hub, but since I got my new computer the plug directly into a motherboard fed USB2 port).  Clearly in his case, there was a power bump with his, or a pin got bent, or corroded, or there was a short, no one will ever know.  I think he got it fixed though.  Aslo clearly, the TM stuff works with either USB 2 or 3.

At the end of the day, if you want to plug yours into a USB 3 port, knock yourself out. I'm going to continue to use my USB 2 ports.  Thanks for the pin-out diagram, but for me, as long as I get the biddity-bop that the device connects when plugged in, I'm happy.

[WWDarkdiz]

Update for Deltasim modified Warthog for 4.602.

V06012021 added provision for Typhoon gunsight vertical adjustment, moved some lesser-used functions to make room

Enjoy, as always, thoughtful feedback welcomed

Darkdiz-TM_BOS.zip

[VilsonFarias]

@WWDarkdiz: thanks for the information regarding the USB2/3. In theory, it should work on USB3 ports without any trouble but sometimes a bad implementations may lead to unexpected issues. I prefer to not take any risks, so I'll be using my TM on a low-powered port.

[WWDarkdiz]

I really think that USB 2 and 3 are 99.99999% backwards compatible (nothing is ever 100%, 100% of the time), so putting any USB 2 device on a USB 3 plug SHOULD not be an issue.  However, since I have several USB2 ports specially allocated for my TM and Track IR devices, I may as well use them, as doing that frees up my other USB 3 and 3.2 etc etc etc ports for devices that can benefit from the higher speed.

On another note, I'm so glad I seem to have gotten the Windows store cache issue solved for some of the other folks on this thread, my TARGET is just SCREAMING along right now, no issues at all, all devices seen first time, haven't had to unplug the joy in several days now, fingers crossed...

S!

[Max-Q]

@WWDarkdiz  Firstly thanks for sharing your target profiles wwdarkdiz, it looks like you’ve put a lot of hard work into it.

 

FYI - I have the Deltasim mod so I’m using your modded version of the profile.

 

Mate I’m wondering if you can help me as some of the controls aren’t responding in-game like they should and it’s driving me nuts.

 

Ok so following your ‘read me first’ pdf...

I’ve replaced the game default MAP file with your supplied map file (renaming it as current.map).

I’ve loaded your profile into TARGET, then tested all buttons/hats etc in both device analyser and event tester, they all appear to work as intended cross checking your specific keybinds/macros on your supplied reference files. 

I’ve mapped all other axises etc in-game as stipulated.

All seems good to this point.

…BUT then in-game some buttons don’t work as intended or they trigger something else. 

 

For example:

 

BSF

/O LSHF g Tailwheel Unlock

Pushing the hat switch forward unlocks the tail wheel but moving it back to centre position retracts the landing gear. 

Image attached from event tester

 

SCL/R

/I RCTL/RSHF \ Oil Rad Close/Open 

Oil open/close using the Deltasim mod plus S3 shift does not work. Water open/close does work.   

/I RCTL/RSHF seems to work fine in event tester and analyser? 

SHIFT S3 works with some other functions in-game. 

Image attached from event tester.

 

I haven’t discovered any other problems as yet as I’m new to the game and I’m just trying to get a plane off the ground for the first time so these little gremlins have halted any progress.

 

Any ideas what could be the cause? 

 

 

Edited August 17, 2021 by Max-Q

[Hoss]

On 11/10/2020 at 7:46 PM, paul_leonard said:

Darkdiz:

How come no one is responding to your post?  I've been looking for something like this for months and months and months.  Started with Sublogic's Jet.  Have had nearly every exotic controller since including original VR Forte VFX1 (think it is in the crawlspace somewhere).  Lots of games and hardware in between.  But never any good, never enough time.  Twins.  Thank you for investing the time and your knowledge.  Your work brings logic and consistency to the relationship between the game and the interface.  It will still take an investment in time, but I've gone through your remarks, and it makes total sense.  Looking forward to the investment instead of the frustration. 

Paul

PS - not surprised your Canadian.

 

On 5/25/2021 at 5:27 AM, unlikely_spider said:

This still doesn't make sense to me though. My understanding is that the old USB 2.0 connector pins on a USB 3.0 port are still present, in addition to the new pins. A USB 2 plug won't even contact the USB 3 connectors. I'm just trying to understand because I've used a USB 3 port on my Warthog because that's the easiest one to connect to on the front of my PC. Here are the motherboard header pins for USB 3.0 on the left and 2.0 on the right. From this page: 

 

What was it in Deadpool 2 that Ryan Reynolds said about Canada? Saw it last night so it's still rattling around in the void between the ears........

 

Did you get TARGET figured out? or are you using some other keyboard emulation to run your profiles?.   I ask because you did not use the print function in TARGET to generate your Photo/jpeg showing key assignments.  I use both TARGET and Joytokey for two different types of controllers.  If I were going to build a second profile for IL2 it would probably be for TC, and I'd use Joytokey to program my Crosswinds for directional controls on my tank... As it stands now I have only one profile for IL2 (which I can control all planes in game) and several for DCS, because they could find no commonality of assignments for most WWII planes, and early jets.  Now, modern Jets are another animal entirely.............. Helo's too.  Good work, thanks for taking the time and sharing your work to help out the community.  If you would like to see my profile PM me. 

 

[WWDarkdiz]

19 hours ago, 352nd_Hoss said:

Now, modern Jets are another animal entirely.

Ya, the modern jets in DCS are seriously more complex, I'm trying to sort out a profile for the F14 RIO, a work in progress...

And yeah, I got TARGET figured out (sort of...).  At least I have a process that works most of the time

@MaxQ

I'll have a close look at the bindings, but from here it looks like the g keybind (default setting for gear retract) may be interfering.  Check the in-game key bindings, make sure the gear retract command is not bound as g.  I have mine bound to the shifted flaps up/down as RSHF or RCTL g for retract/extend respectively.  That will eliminate the game seeing the "g" command when you hit the BSB release (put the boat switch back to the center).  It also sounds like not all of the darkdiz_current_map bindings have been properly setup (you are not the first to report this).  Look on the first tab of the keybindings spreadsheet, all of the necessary keybinds are there.  Simply copying the darkdiz_current_map and renaming it current.map appears to NOT work 100% of the time, so better to manually change the keybindings (PITA I know, but worth it).

In terms of the oil rad not working, the SCL/R position MUST be past the 90% deflection ON THE X axis with the S3 switch pressed for it to work properly.  If you have much Y axis in the deflection, it will likely cause the game to see something else.  I have a homemade guide on the SC hat so I only get either X or Y input, not both.

That being said, I'm not happy with how I have the SCL/R bound anyway, so in the next update (which I will post later tonight) I moved it to another switch, works WAY better.

Edited August 17, 2021 by WWDarkdiz

[WWDarkdiz]

Here is the update for 4.603.

Changed a few spots where I didn't like the way things worked out (SCL/R is now FOV+/-, Oil and Water rads now on Hat 3 as shifted functions, moved some of the TS/SRS channel changes to Hat 3 shifted, optimized change firing position (now MSP shifted), fire wpn group 3 (moved from LTB), changed track IR recenter to shifted S4 (jives with what I use in DCS).  Some of my snap views also optimized so that when you have an overwing Lewis gun mounted on a given WW1 plane, the "up" view modifier puts you right behind the gun, sighted in :).  If used with the change firing position, its VERY easy to shoot across the turning circle with the Lewis.

As always, feedback welcome, copious amounts of cash, bottles of rum also work... (jk)

Darkdiz-IL2BOS_v4_603.zip

[Hoss]

For TIR center I have always used F1, it's the command in almost every flight sim for Player cockpit.  Since I always fly full real/expert, I don't use any of the other view commands except F9/F10, therefore F11 is my PTT. But with F1 there are no conflict with any other commands, and you don't need a shift function to use it.  Cause I use it all the time. 

 

Cheers

Hoss

[WWDarkdiz]

It a personal preference, I find the F1 command usually means cockpit view.

I ended up using LSHF+LCTRL F12, it ended up that way since I'm trying to build some commonality with my DCS profile.  This key combo was something that the CTS installer I tried had as a default, it was easier to change these commands than those ones.  I ended up NOT using the CTS profile, but didn't bother to change the key binds.  Good idea though, the F1, as it defaults to the cockpit center view.

[Max-Q]

@WWDarkdiz 

Thank you kindly for your prompt response and words of advice.

I'll give the updated profile a whirl and yep I'll definitely double check in-game keybindings with the speadsheet if anything seems to be broken. 

Cheers!