Jump to content

Recommended Posts

Posted (edited)

I've had the Warthog for a few days but didn't feel like dealing with learning a new programming methodology so I set up the most crucial keys in DCS for F18 and went flying so up until now I haven't played with TARGET. That would be up until a few hours ago actually, I've dug in and found some questions right off the bat...

 

 

 

First: Is there a way to turn off the LEDs permanently? Even the lowest setting is too high for daylight use let alone night flights. I figured how to turn them off in an individual profile but I'd like to never see them again.

 

 

Second: In TARGET I only see a 4 way hat for the POV/trim switch. How do I make that an 8 way as it should be?

 

 

Third: I am using that hat for view and I'd like to slow it down, how is that accomplished?

 

 

Mods, please move over to the thrustmaster section. My bad, I was searching all over and thought I was there when I posted.

 

 

 

I've a few other questions but I'm pretty sure I saw the information somewhere and I'll try to scrounge that up again on my own. Thanks.

Edited by crab
Wrong section
Posted

I am not at home right now so can't remember how to turn the LEDS off off the top of my head. IIRC they are not on by default unless you talking about the standard backlighting. (Don't think you can turn those off)

 

Don't want to steer you on a different course but you can do more than enough for the Hornet without the Target software. You can edit the input default.lua file if you want to do it all in DCS.

 

Sent from my SM-G965F using Tapatalk

Posted

Semi-permanently. They will come back on on reboot or plugging the controller in again. Here's some code that suggests how to turn off lighting:

    MapKey(&Throttle, PSF, PULSE[color=#808080]+[/color]LED(&Throttle, LED_INTENSITY, [color=#ffffff]43[/color]));         [color=#32cd32]//Backlight Dim[/color]
   MapKey(&Throttle, PSM, PULSE[color=#808080]+[/color]LED(&Throttle, LED_INTENSITY, [color=#ffffff]0[/color]));            [color=#32cd32]//Backlight Off[/color]
   MapKey(&Throttle, PSB, PULSE[color=#808080]+[/color]LED(&Throttle, LED_INTENSITY, [color=#ffffff]86[/color]));        [color=#32cd32]//Backlight Max[/color]

You can use ActKey instead which will just run once on "play". The PDF manual has a direct example of this.

 

With some semi-clever scripting you can get 8-way out of the 4-button. Basically you put an EXEC for a primary direction which asks if the neighboring direction is also active. Then it enacts DOWN+ for one of those three options based on if the left, right, or neither neighbor button is also active; if(left else if(right) else center.

 

Then to get the button to release you make any release of the primary direction do a release UP+ action on all three buttons. Then you write similar DOWN and UP commands for the other three directions. Crazy but it works if you really need independent control of the 8 directions.

 

But you don't have to do any of that for POV or trim since the diagonal directions will simply do both actions at the same time. A 4-way hat is sufficient for 8 directions of output without anything crazy.

 

You can flicker the input or make a virtual axis by the key presses (DCS allows axis control of view) and then this axis can be scaled back. REXEC will allow you to have rapid pulses with configurable delay.

Posted

Congratulations on getting the Warthog, I don't understand TARGET handbook, I've programmed my keys using the in game software for each aircraft and I'm sure we all have our own profiles. You can search in the downloads for profiles and add them. But I've generally found the keys that suit, selected what I want them to do in that aircraft, and it's worked fine. I find having a 'picture' of the throttle or stick helps decide which keys/buttons etc helps. I have literally done little diagramsof what key does what, and have to 're-brief' myself every few months as I get back to a particular aircraft. Hope this helps

Posted

You can set LED brightness permanently in TARGET GUI. You can also remove that hardware deadzone that is on the stick.

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Posted

there is no need to use Target, just bind in the game, you can also use a modifier, which is what i did before getting the Virpil system

Custom built W10 Pro 64Bit, Intel Core i9 9900k, Asus ROG Maximus Code XI Z390, 64GB DDR4 3200 RGB, Samsung 1TB NVme M.2 Drive, Gigabyte AORUS 2080TI, 40" Iiyama Display. Wacom Cintiq Pro 24, HOTAS Virpil T50 Stick / FA-18C TM Stick and Virpil T50 Throttle, MFG Crosswind Graphite Pedals. HP Reverb

 

SPECTER



[sIGPIC][/sIGPIC]

 

Lead Terrain Developer / Texture Artist

Posted

Thanks for tips folks. I've got plenty of experience at deciding what I want on the stick/throttle and I've got a handy picture with the real world assignments. The DCS editor has been ok gut I've run into trouble with the base assignments. As examples I cant get a command on center with the flaps switch, the EAC switch will give me button 24 in both positions and the same with the other two position switches although with different DX commands. I also wanted to slow down the view panning and couldn't see any way to do it in the DCS editor.

 

 

 

I only see a way to turn off LEDs in an active profile, with no profile loaded I get the LEDs at the default brightness setting which on mine is two from the left. I don't want them on at any time. Ever. So that's what I was trying to figure out, no LEDs at any time. I'll check out going to axis for view.

Posted

It's a programmable joystick so don't add stress by avoiding its ability to be programmed. Much headache is had by not embracing it. If you really, really, really want to you can go edit custom commands into DCS itself but it's harder than programming the stick and it gets wiped by every update.

 

There is a way in the GUI without running a program. The button is CONTROL LED STATE. No guarantee that it'll be remembered after reboot or replug though.

Posted

Basically, it comes down to this. Target gives you more choices, allows you to use 3 position switches easily.

 

If you map it in DCS directly, you have to play around with LUA files to make the three position switches work. Although I believe ED is trying to make it easier by not having to modify LUA files. The first attempt at keyboard optimization was a, ahem, not too smooth. So we'll have to see what comes of it.

 

You can always get HomeFries EXTENSIVE Target files and just use it. That's another option.

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Posted

I like doing my own. Flying the configuration, modifying it. For me it's a part of flight sims and as strange as it seems, I enjoy the process. At this point I have made all the axis assignments, adjusted them so they work properly, added all the switch gear commands for the throttle/stick, and all work well. The base remains difficult to program correctly, as near as I can determine, impossible with the in game editor. I don't see myself diving into editing DCS files to make it work so I'm setting it aside and going back to TARGET. Again. O_o

 

 

I've not found anything in TARGET that allows me to control LED states until I start a profile, I'll look again the next time I pick it up Frederf.

Posted

Sigh, It's hard on an old man, all this learning. I've got most things working but ran into a couple trouble spots...

 

I was trying to put AA and AG master on the throttle but it doesn't seem to want to work. Works when you press the keyboard but not on the throttle. I've tried mapping it to DX button and to a keypress. Ideally I'd like this to be a pulse when I move the boat switch over and pulse the same again to turn if off when I move it back to center.

 

I had some trouble getting the apu start working but got it going by changing the pulse from the default 32 to 50. The engine cranks on the other hand are not working with the same settings. The command is being sent and the switch visibly does a little twitch but doesn't flop all the way over.

 

Suggestions?

Posted

Ok, lets see; I took the joystick out of the configuration because I needed more axes than I had and that one can be fully programmed in DCS. I got the engine cranks to work by setting the command as a hold to spring loaded side of the eng operate swithc. The master modes started working when I upped their pulse length to 50 milliseconds. What I'm trying to do now is get the boat switch (center switch) to also cancel the mode by going back to center. In other words rock it over to get to air to air and when I'm ready to leave air to air simply center the switch to cancel air to air mode. Any suggestions?

Posted

For others who might have found their way here in a search trying to figure something related out: Skip the basic configuration and go straight to advanced. It's the same thing with a few more options, example follows:

 

So getting that boat switch to work with air to air mode only required me to set a pulse when the switch is rocked over, then as soon as adding that command and while still in the field simply switching to the newly available release option gained when going to advanced and give it a pulse on release. In the right pane you'll now see Air to air with a keyboard command of 1 set to pulse on press and directly below that will be the second command you put in as a release which is another pulse of the keyboard command 1. And problem solved.

 

So, to sum up, go straight to advanced. It's basically the exact same thing with a few more options you can select if you're of a mind. Like a command on release... O_o

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...