SGT Coyle

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.

Will this be part of the next update?

Awesome! Thanks for that explanation. I cold never find what the "/xa" was for.

+1 on that

TARGET 3-Way Sitch You can assign the OFF position of any switch on the TMWH by use of the MapKeyR(Release); function. I'll use the example given above and achieve a desirable result by use of the TMWH Auto Pilot 3-way Switch: //Autopilot Select Switch -- Physical switch as RDR Altimeter 3-way Switch MapKey(&Throttle[color=#ffffff],[/color]APPAT, PULSE + [i]Altitude_Switch_Baro[/i]); // Baro [b]MapKeyR[/b](&Throttle[color=#ffffff],[/color]APPAT, PULSE +[i]Altitude_Switch_Baro[/i]);// [b]Baro/RDR[/b] [b]MapKeyR[/b](&Throttle[color=#ffffff],[/color]APALT, PULSE +[i]Altitude_Switch_RDR[/i]);// [b]Baro/RDR[/b] MapKey(&Throttle[color=#ffffff],[/color]APALT, PULSE + [i]Altitude_Switch_RDR[/i]); // RDR This is how I map a three way toggle switch with the MapKeyR function. By just mapping the on/off positions of the physical switch, I get a three way switch working in the game.

I haven't had TARGET crash in a long time. I found it wasn't TARGET crashing, but windows USB power settings bugging it to death. What Module you flying?

Here's my axis mapping, from my AV8B script with an F18 grip: //AXIS init [b]MapAxis(&JoystickF18, JOYX, DX_X_AXIS);[/b]//initial default joy stick "X" [b]SetSCurve(&JoystickF18, JOYX, 0, 0, 0, 0, 2);[/b] [b]MapAxis(&JoystickF18, JOYY, DX_Y_AXIS)[/b];//initialize default joy stick "Y" [b]SetSCurve(&JoystickF18, JOYY, 0, 0, 0, 0, 2);[/b] //MapAxis(&Throttle, THR_LEFT, DX_ZROT_AXIS); [b]MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS);[/b] //*********Slew Stick acting as Mouse // MapAxis(&Throttle, SCX, MOUSE_X_AXIS, AXIS_NORMAL, MAP_RELATIVE); // SetSCurve(&Throttle, SCX, 0, 10, 0, 0, -4); // MapAxis(&Throttle, SCY, MOUSE_Y_AXIS, AXIS_REVERSED, MAP_RELATIVE); // SetSCurve(&Throttle, SCY, 0, 10, 0, 0, -4); //*********Slew Stick acting as independent AXIS. NOT Mouse!!! Used to setup control of A/C TDC MapAxis(&Throttle, SCX, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Throttle, SCX, 0, 5, 0, 3, 0); MapAxis(&Throttle, SCY, DX_YROT_AXIS, AXIS_REVERSED, MAP_ABSOLUTE); SetSCurve(&Throttle, SCY, 0, 5, 0, 3, 0); //TDC Slew Control on Throttle Mini Stick //KeyAxis(&Throttle, SCX, 0, AXMAP2(3, ,0, )); //KeyAxis(&Throttle, SCY, 0, AXMAP2(3, ,0, )); [b] MapAxis(&Throttle, THR_FC, DX_SLIDER_AXIS); [/b] // Assigned in game as Nozzle Control Lever There's only one slider on the Throttle, I don't know where you seeing joy_slider_1 / 2 reported.

My experience when I get errors concerning Macro Files is either a call in the .tmc for a macro that has no definition or duplicate defined macro name in the .ttm'

Target.tmh Is included in the TARGET software.

OP = Original Post If you have questions or comments about what is presented please PM me. I'd like to keep the thread from bulging from individual one to one conversations. If something needs further explanation or clarification, I will edit appropriate post. Thanks

Hey Guy and Gals, I started this thread with the hope that we could get some news as to what to expect in the Beta Updates for the Harrier. Zues67 has graciously obliged. Lets refrain from peppering him and others with questions, expectations, disappointments and the like. Let the Devs talk without comment. There are plenty of threads covering almost every system, feature, bug, and complaint under the sun. Lets not repeat those here.