SGT Coyle

This happens to me every once in a while. It used to be every time I went to use it, but it started behaving when I got on of these. All I have are USB3.0 and 3.2 ports on the MB back IO. The MB has two USB 2.0 headers so hook this up and works like a charm. Now every once in a while I have unplug and plug in the stick, but it's worked much better since I made the change. Another thing I do is try to start TARGET first, before DCS, and run the "Device Analyzer" and move the stick to see if it registers. Like I said, dead stick rare these days.

Am I? Seems like a useful feature for missions designers. I didn't know it was out of vogue. I totally forgot it was there until I wanted to see if I could use it on the Harrier to setup the CAS Page. I mean really. I thought I was on to something. LOL!!!

Ok, lets try this again. Can anybody explain how to save cockpit configurations?

Can I script the CAS page entries through the Mission Editor or by way of do-scriptfile?

Why don't you put it in the bug section instead of globbering on about it here. It's bad enough they don't look in these forums anyway, but it sure won't get fixed if you don't put it in the Bug Section. And you're right I completely missed the point because I have those commands mapped to my TMWH as SHIFT + ALT + ?. It quite honestly never dawned on me that they weren't pat of the control settings.

DCS=>Saved Games=>Config=>Input Folder. Delete Joystick Folder. Restart Game . Contents of Input Folder will be rebuilt.

They just redid the radios. WTF!

On the Harrier the "Brightness Knob", as it is now, controls the brightness of the "Symbology" layer. It does nothing for the "Map" or the display as a whole. This is an issue for a "Night Attack" plane.

OK, well my stuff works and yours doesn't. I'll be damned if I going to spend one more second trying to help you with anything.

OK, so what is the controller?

Mine work fine. What's the issue?

If you post on Hoggit I'd be happy to chime in, but I don't understand half this back end code stuff to make a convincing gripe. But I can say the only reason for their success is the incredible community effort to make Multi Player as good as it is. Not supporting that effort is a monumental, short term thinking, mistake. Thanks again for the help.

Play as client and give it a good old 10 count between after hitting Esc did it. Got it working just fine. Thanks everyone for responses.

So fixed the script: local pit_1={"Pit_1"} -- Create a range object. GoldwaterRange=RANGE:New("GoldwaterRange") -- Add strafe pits. -- RANGE.AddStrafePit(Target Names, BoxLength, BoxWidth, Heading, Inverseheading, goodpass, foulline) GoldwaterRange:AddStrafePit(pit_1, 5000, 500, nil, nil, 20, 500) -- Start range. GoldwaterRange:Start() So, I don't know if this is important or not, but I set this up as a SP mission with player skill as "Player" not "Client". So I'm a little confused as to what you mean "Hit escape twice". Is it hit "Fly", "Escape", "Fly", "Escape", then "Fly" or something else. I don't know if this has anything to do with that, but I get an error message popup: DCS: Mission script error: : [string "C:\Users\BIG_DA~1\AppData\Local\Temp\DCS.openbeta\/~mis00007CBA.lua"]:5: attempt to index global 'RANGE' (a nil value) stack traceback: [C]: ? [string "C:\Users\BIG_DA~1\AppData\Local\Temp\DCS.openbeta\/~mis00007CBA.lua"]:5: in main chunk New delay on the triggers are Moose 3 sec and Script 5sec

Does anyone have a simple example mission for the Range module? I've tried repeatedly to get it to work on NTTR with no luck. I've tried it with DCSW 2.5.5 with latest Non-Dev Moose and 2.5.6 with the Moose Dev branch. When I start I don't get any F10 menu. I assumed this feature was default from the reading. This is a SP mission so I don't know if the script starting correctly is the problem. Here's my Range lua: local pit_1={"pit_1"} -- Create a range object. GoldwaterRange=RANGE:New("GoldwaterRange") -- Add strafe pits. -- RANGE.AddStrafePit(Target Names, BoxLength, BoxWidth, Heading, Inverseheading, goodpass, foulline) GoldwaterRange:AddStrafePit(pit_1, 5000, 500, 180, false, 20, 500) -- Start range. GoldwaterRange:Start() BASE:TraceOnOff(true) BASE:TraceLevel(3) BASE:TraceClass("RANGE") RANGE.DebugON(true)Attached my .miz and log. Any help appreciated. TD_BGwRange.miz dcs_log.txt

With some help on FB, I was reminded of where I got a calibration tool for the TMWH. https://deltasimelectronics.com/ They have a forum post here.

What TARGET are you using? GUI or Script Editor? If Script Editor, please post your Script .tmc file. If GUI please post up whatever file it uses for keybinds. Dose Thrustmaster Combined show up in the DCS controller settings page.

Adjustment, not calibration. You can set dead zones and curves. There's a calibration program for a TM steering wheel I remember downloading last year, but it's on an old sys. I'll try to find it. It worked for the WH I've always stayed away from using windows controller to calibrate. It always cased more problems than it solved. Had something to do with registry.

You don't calibrate with TARGET.

It's great to see that some of theses keybindings can be so easily implemented by the customer, but why can't they be implemented by the Developer? It's the easiest way to fill up a change log notice. So much more appreciated than a 3D scanned pilot.

No Shit.

I likey likey!

I'd buy a Naval trainer to go with my Super Carrier, And an A-4 for that matter.

I fly DCS in VR and I can't for the life of me understand. If you're asking for an option to do this, great. Knock yourself out, but if one day I have to walk form the ready room to the plane, just to play in VR, I'm gonna be pissed.

Only if your pilot can be blown off the deck for walking where he/she shouldn't.