Britt007

S/N 05681 West Midlands England.

I've used both the cap clip and the pro clip and can honestly say the pro is way better, I also cut off the USB lead and made it wireless and use it with my turtlebeach PX5 headphones. I've attached my profile if you would like to give it a try. Britt007 DCS.xml.zip

Can someone please tell me why the below code when the fire trigger is pressed into its 1st position generates I and O on pressing in, I thought it would only generate the I when pressing in and O when releasing the fire trigger ? The release part works fine. include "target.tmh" //program startup int ZOOMIN=0; int ZOOMOUT=0; int main() { if(Init(&EventHandle)) return 1; // declare the event handler, return on error } //event handler int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); ZOOMIN = CHAIN(DOWN+'i',D(1200),UP+'i'); //Press i, hold for 1.2 secs, release ZOOMOUT = CHAIN(DOWN+'o',D(1200),UP+'o'); //Press o, hold for 1.2 secs, release MapKey(&Joystick, TG1, ZOOMIN); //Trigger stage 1 pressed MapKeyR(&Joystick, TG1, ZOOMOUT); //Trigger stage 1 released }

Thanks for the input, I'm testing in a mission I made, just following a tanker for refuelling practice, and DisableSnapviewSaving is set to false.

I need help setting up custom SnapViews, I’m trying to set a zoomed HUD SnapView on KP5, this is what I’ve tried so far with no luck. I've searched and read everything I've found in this forum and from Google .. I left SnapViewsDefault.lua alone and edited SnapViews.lua, I edited the UseDefaultSnapViews in View.lua and set UseDefaultSnapViews = false I then added the below to SnapViews.lua Snap[11][6] = {} Snap[11][6]["viewAngle"] = 28 Snap[11][6]["x_trans"] = 0.36 Snap[11][6]["hAngle"] = 0 Snap[11][6]["y_trans"] = -0.041336805555555564 Snap[11][6]["rollAngle"] = 0 Snap[11][6]["vAngle"] = -8.5 Snap[11][6]["z_trans"] = 0 Then when in the sim I used RCTRL+NUM0 to use snapviews but when I pressed 5 the HUD is the same I’ve also tried it this way: Adjust some Cockpit FOV Hit LWIN KP# snap view numpad key Hit RALT KP0 to redefine this snap view ...done And this way: 1. If you haven't already done so, set UseDefaultSnapViews=false in your View.lua file. 2. Toggle snap views: RCTL KP0 3. Press the snap view you want to change: KP5 4. Untoggle snap views: RCTL KP0 5. Move/pan/zoom your view to where you want it; for me, simply using zoom in (*) and slightly panning the view up a bit got me a nice zoomed in HUD view. 6. Save cockpit angles: RALT KP0 Press the snap All with no luck, KP5 SnapView stays as default, I’m using Windows 7 Pro, and Notepad++ to edit the files

This is worth a look http://www.youtube.com/watch?v=ak6EgzDwiGs&feature=player_embedded

PhoenixBvo, Thanks for the update, I've got my head around the TARGET script now and it's fun messing around with it. Frostiken, I was using modifiers within DCS A-10 but I want two joystick curves and because I cant see away within DCS A-10 to do it I've gone the TARGET route.

That makes sense now .. thank you.

PhoenixBvo, I've started to learn how to use the TARGET script editor and was messing around with your script file and I've noticed a strange thing happening, when I load and run your script then the device analyser and choose Thrustmaster combined the joystick X and Y axis act strangely. If I just use your 1st joystick setting not using pinky + S1 to move up through the other 5 settings this is what happens, as I move the joystick Y axis up the X axis moves about 4th of the way left, and if I move the joystick Y axis down the X axis moves about 4th of the way right. And if i move the joystick X axis right the Y axis moves about 4th of the way up, and if i move the joystick X axis left the Y axis moves about 4th of the way down, it also happens on the other joystick settings, pinky + S1 but less so as you move through the settings. If I stop your script running and then run the device analyser and select joystick-HOTAS Warthog its fine no movement on the other axis only the one I move. Whats happening, and do you know of this?

This is how I do it .. 1 Put distance between you and the targets 2 Choose Mavericks from DSMS OSB14 3 Put left MFCD into TGP mode and right MFCD into MAV mode 4 Put the Steerpoint switch into Markpoint mode, or press FUNC then 8 MARK on the UFD 5 Turn onto target and SLOW DOWN the aircraft 6 Slew the TGP onto a target 7 Put into laser mode 8 TMS up short twice for point mode 9 TMS right short to make it into a Markpoint 10 Repeat 6 to 9 for each target 11 Choose a Markpoint ether by making HUD SOI and DMS up short or using the STEER rocker switch on the UFC 12 Make right MFCD SOI 13 China hat forward long to slew Maverick to Markpoint target SPI 14 TMS forward short to lock Maverick, keep TMS forward short until Maverick locks 15 Fire Maverick 16 Repeat step 11 for each Markpoint, then 14 and 15 There are other ways to use them, I'm sure someone can tell you how

Hi cichlidfan It's so I can switch curves for when I refuel, I do like the normal curve of the Warthog HOTAS for everything except air to air refuelling, so I wanted to put a S curve in the pitch and roll of the joystick to make it less sensitive for refuelling.

Thank you ..

Pitch and roll

Does anyone have a TARGET file or script for different pitch and roll axis curves on different layers for the Warthog HOTAS please?

Does anyone have a TARGET file or script for different axis curves on different layers for the Warthog HOTAS please?