Havner Posted April 17, 2014 Posted April 17, 2014 Has anyone noticed any incorrect/poor behavior of the TARGET software when the MFDs are connected? I have Warthog + 2MFD, so that's 4 TM devices in total connected. I recently bought the MFDs and some completely valid constructions cause all the TM inputs to hang. E.g.: MapKey( &Joystick, S3, TEMPO( EXEC( [color=#a52a2a]"f1();"[/color] ), EXEC( [color=#a52a2a]"f2();"[/color] ), 300 ) ); If there are 2 EXECs in TEMPO hitting the key hangs all 4 TM devices. If I disconnect 2 MFDs or put just one EXEC in TEMPO it works properly. [sIGPIC][/sIGPIC]
Havner Posted April 17, 2014 Author Posted April 17, 2014 (edited) Mine is ok. Warthog+2MFDs In general mine is as well. They do work. I'm asking about some fancy TARGET constructs. Have you tried the above for example? EDIT: the above is not enough, I have pretty big profiles. Will try to prepare some use case. Edited April 17, 2014 by Havner [sIGPIC][/sIGPIC]
Havner Posted April 17, 2014 Author Posted April 17, 2014 (edited) I think I found a reason. You can't change both MFD leds at the same time, or even with little time in between. Could somebody try this? After 2-3 presses of GAINU/GAIND the MFD should hang or even restart. MapKey( &RMFD, GAINU, LED( &RMFD, LED_ONOFF, LED_CURRENT^LED1^LED2 ) ); MapKey( &RMFD, GAIND, LED( &RMFD, LED_ONOFF, LED_CURRENT^LED1^LED2 ) ); Edited April 18, 2014 by Havner [sIGPIC][/sIGPIC]
Home Fries Posted April 18, 2014 Posted April 18, 2014 Havner, I've found that most of my crashes are LED related, and I try to do dual LEDs as little as possible. Once in a blue moon is fine, but it does tend to saturate things when you do it often. I'm not sure why that is, I just stay away from doing it whenever practical. -Home Fries My DCS Files and Skins My DCS TARGET Profile for Cougar or Warthog and MFDs F-14B LANTIRN Guide
Rogue Trooper Posted April 18, 2014 Posted April 18, 2014 Havner, For how long have you seen this problem? Mine was working perfectly until around 3 weeks ago. I started getting USB drop out which stopped the target software from running. Before that I never got USB dropout, but now it is occurring on a regular basis. I use 3 MFDs and the Warthog hotas (Target GUI user). I have always used the LEDS to confirm the position of the throttles U/M/D switch and I never had problems before. I am not sure but this seemed to start after a few major software updates: Windows, NVidia and DCS 1.28. My setup seems to be a lot more reliable after I turned off the Throttles back lights and lowered the brightness of the MFDs button lights (still using LEDS). So "all of a sudden" my USBs can't seem to power this setup. Perhaps a new usb driver/energy saving software in windows is causing the problem? HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled. DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!. Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.
Havner Posted April 18, 2014 Author Posted April 18, 2014 Since I bought them, which is 2 days ago ;-) I seem to have this problem now sometimes even when changing one LED. I use GAINU/GAIND to switch "pages" on the MFDs and the LEDs tell me which page I'm on. I will investigate this further anyway. I need to get to a working setup anyway. EDIT: Warthog throttle leds seem to be resistant to the issue. [sIGPIC][/sIGPIC]
Rogue Trooper Posted April 18, 2014 Posted April 18, 2014 I never used the throttle LEDS so I am not sure about these. HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled. DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!. Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.
Berndt Mangler Posted April 18, 2014 Posted April 18, 2014 I'm not sure what the goal is sorry for that. Perhaps you know this already, but the LEDs on the MFCD can be dim'ed and all turned off using the Devices and Printers? Select the MFCD and edit its properties. I've never been able to set these from Target. Your code is one I've not yet tried, but I will when I can. I set them to dim as well as turn off those eye burners from the game controller properties. If I'm off the chart here sorry and never mind. [sIGPIC][/sIGPIC] MoBo: SaberTooth P67 B3 CPU: i7 2600K OC'd 4.434 Cooling: H100, Nine Asorted Fans GPU: EVGA Drvr344.75 GTX 780 and 580 w/physX MEM: Patriot Viper Xtrm 16GB Power: Antec HGC-900 HRD: Samsung SSD 256GB, WD 2TB wPageFile OS: Win7pro 64b Display: AcerHN274H-nVidia3D 27", Qty2 BenQ GW2750HM 27", Asus VS208 24", Qty2 Lilliput U80/c Input: G13, G110, G700s, TM WortHog, Saitek Cmbt Rudder, TM MFCDs, TrackIR5 Sound: Z906, G930w/IR5/Pwr. Pack Chair: See Album
Havner Posted April 18, 2014 Author Posted April 18, 2014 I'm not sure what the goal is sorry for that. Perhaps you know this already, but the LEDs on the MFCD can be dim'ed and all turned off using the Devices and Printers? Select the MFCD and edit its properties. I've never been able to set these from Target. Your code is one I've not yet tried, but I will when I can. I set them to dim as well as turn off those eye burners from the game controller properties. If I'm off the chart here sorry and never mind. The point is exactly the opposite. It is to use them and make them display meaningful information that you need :-) I have no problem to learn how to use them, I know this pretty well. I have a problem with a hardware (or drivers for that matter) that blow up under certain conditions. [sIGPIC][/sIGPIC]
Berndt Mangler Posted April 18, 2014 Posted April 18, 2014 Don't mind me then. I never made them work and gave up on that long time ago. I'll keep and eye on the post, perhaps some one will have that little clue, I too would like to implement them, I want to make them flash when I left my flaps down or brakes open. (yes.. I still screw that up from time to time:) Perhaps just letting it crashing it would learn me...hahahaha I'm working on other things but I'll try your code as soon as I can, perhaps I can still help.. [sIGPIC][/sIGPIC] MoBo: SaberTooth P67 B3 CPU: i7 2600K OC'd 4.434 Cooling: H100, Nine Asorted Fans GPU: EVGA Drvr344.75 GTX 780 and 580 w/physX MEM: Patriot Viper Xtrm 16GB Power: Antec HGC-900 HRD: Samsung SSD 256GB, WD 2TB wPageFile OS: Win7pro 64b Display: AcerHN274H-nVidia3D 27", Qty2 BenQ GW2750HM 27", Asus VS208 24", Qty2 Lilliput U80/c Input: G13, G110, G700s, TM WortHog, Saitek Cmbt Rudder, TM MFCDs, TrackIR5 Sound: Z906, G930w/IR5/Pwr. Pack Chair: See Album
Havner Posted April 18, 2014 Author Posted April 18, 2014 I too would like to implement them, I want to make them flash when I left my flaps down or brakes open. (yes.. I still screw that up from time to time:) Perhaps just letting it crashing it would learn me...hahahaha It's described in the TARGET manual :-) [sIGPIC][/sIGPIC]
Home Fries Posted April 18, 2014 Posted April 18, 2014 ivanwfr started a TARGET programming thread, and Post 24 details other "lower level" commands to use LEDs. I like using these because they seem to cause fewer profile crashes (yet another reason I think this is due to FAST service saturation). I used and tweaked his LED routines heavily in my own profiles; just take a look at MFD_lights.tmc in the profile in my signature. -Home Fries My DCS Files and Skins My DCS TARGET Profile for Cougar or Warthog and MFDs F-14B LANTIRN Guide
Havner Posted April 18, 2014 Author Posted April 18, 2014 (edited) Thanks. Looks promising. Will try using GameOutput() and see if it makes a difference for me. EDIT: just take a look at MFD_lights.tmc in the profile in my signature. Funny thing, what did seem to help me was your modified target.tmh. Edited April 18, 2014 by Havner [sIGPIC][/sIGPIC]
Berndt Mangler Posted April 18, 2014 Posted April 18, 2014 I used and tweaked his LED routines heavily in my own profiles; just take a look at MFD_lights.tmc in the profile in my signature. Thank you both for this thread, I'd like to revisit this. It's described in the TARGET manual :-)[/quote Yes, RTFB. learned that already too.. where so many have yet to do so. I'll admit though, I can forget it's in there. Thanks [sIGPIC][/sIGPIC] MoBo: SaberTooth P67 B3 CPU: i7 2600K OC'd 4.434 Cooling: H100, Nine Asorted Fans GPU: EVGA Drvr344.75 GTX 780 and 580 w/physX MEM: Patriot Viper Xtrm 16GB Power: Antec HGC-900 HRD: Samsung SSD 256GB, WD 2TB wPageFile OS: Win7pro 64b Display: AcerHN274H-nVidia3D 27", Qty2 BenQ GW2750HM 27", Asus VS208 24", Qty2 Lilliput U80/c Input: G13, G110, G700s, TM WortHog, Saitek Cmbt Rudder, TM MFCDs, TrackIR5 Sound: Z906, G930w/IR5/Pwr. Pack Chair: See Album
ElGringo Posted August 26, 2015 Posted August 26, 2015 (edited) Hello, I revive this thread because I found no other related to my problem. I started recently using functions and EXEC in my profiles, and all was doing well. My F-86 profile for example was working a week ago. It doesn' t anymore. My controls lock-up when some buttons are pressed in a certain order. Tried on another computer, with no luck. Did a firmware update, tried on other USB ports. The only last two remaining reasons I see are: _Software limitation (so why was it working before?) _Hardware problem (Had an earlier problem with some cables inside the stick and had to resolder some stuff. I checked again today and all looks fine) Here is one of the profiles that makes my HOTAS hang: [color=#1e90ff][b]include[/b][/color] [color=#a52a2a]"target.tmh"[/color] [color=#1e90ff][b]int[/b][/color] main() { Configure(&HCougar, MODE_EXCLUDED); Configure(&T16000, MODE_EXCLUDED); Configure(&LMFD, MODE_EXCLUDED); Configure(&RMFD, MODE_EXCLUDED); [color=#1e90ff][b]if[/b][/color][color=#ffffff]([/color]Init(&EventHandle)) [color=#1e90ff][b]return[/b][/color] [color=#ffffff]1[/color]; SetKBRate[color=#ffffff]([/color][color=#ffffff]50[/color], [color=#ffffff]50[/color]); SetKBLayout[color=#ffffff]([/color]KB_FR); SetShiftButton(&Throttle, RDRNRM, &Throttle, APPAT, APALT); [color=#1e90ff][b]int[/b][/color] MasterArmOn = CHAIN[color=#ffffff]([/color]DX24, D[color=#ffffff]([/color][color=#ffffff]50[/color]), EXEC([color=#a52a2a]"MapKeyIOUMD(&Joystick, H4P, 0, 0, 0,SEQ(DOWN+DX1, UP+DX1), 0, 0);"[/color] [color=#a52a2a]"MapKey(&Joystick, H4U, SEQ(PULSE+L_SHIFT+USB[0x5F], PULSE+L_SHIFT+USB[0x5C]));"[/color] [color=#a52a2a]"MapKey(&Joystick, H4D, SEQ(PULSE+L_SHIFT+USB[0x59], PULSE+L_SHIFT+USB[0x5C]));"[/color] [color=#a52a2a]"MapKeyIOUMD(&Joystick, H4L, 0, PULSE+R_CTL+USB[0x19], SEQ(PULSE+R_SHIFT+USB[0x05], PULSE+L_ALT+USB[0x05]), SEQ(PULSE+L_SHIFT+USB[0x1B], PULSE+USB[0x1B]), 0, PULSE+R_CTL+USB[0x19]);"[/color] [color=#a52a2a]"MapKeyIOUMD(&Joystick, H4R, 0, PULSE+R_SHIFT+USB[0x19], SEQ(PULSE+R_CTL+USB[0x05], PULSE+L_ALT+USB[0x05]), SEQ(PULSE+L_CTL+USB[0x1B], PULSE+USB[0x1B]), 0, PULSE+R_SHIFT+USB[0x19]);"[/color])); [color=#1e90ff][b]int[/b][/color] MasterArmOff = CHAIN[color=#ffffff]([/color][color=#ffffff]0[/color], D[color=#ffffff]([/color][color=#ffffff]50[/color]), UP[color=#ffffff]+[/color]DX1, D[color=#ffffff]([/color][color=#ffffff]50[/color]), EXEC([color=#a52a2a]"MapKey(&Joystick, H4P, 0);"[/color] [color=#a52a2a]"MapKey(&Joystick, H4U, 0);"[/color] [color=#a52a2a]"MapKey(&Joystick, H4D, 0);"[/color] [color=#a52a2a]"MapKey(&Joystick, H4L, 0);"[/color] [color=#a52a2a]"MapKey(&Joystick, H4R, 0);"[/color])); MapKey(&Joystick, TG1, USB[color=#ffffff][[/color][color=#ffffff]0x2C[/color]]); MapKey(&Joystick, TG2, [color=#ffffff]0[/color]); MapKey(&Joystick, S1, TEMPO[color=#ffffff]([/color]SEQ[color=#ffffff]([/color]L_SHIFT[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x06[/color]], L_CTL[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x06[/color]], R_SHIFT[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x06[/color]]), PULSE[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x06[/color]], [color=#ffffff]500[/color])); [color=#32cd32]//Guns Selector[/color] MapKey(&Joystick, S2, USB[color=#ffffff][[/color][color=#ffffff]0x05[/color]]); [color=#32cd32]//Weapon Release [/color] MapKey(&Joystick, S3, USB[color=#ffffff][[/color][color=#ffffff]0x07[/color]]); [color=#32cd32]//Steer (D) [/color] MapKey(&Joystick, S4, USB[color=#ffffff][[/color][color=#ffffff]0x16[/color]]); [color=#32cd32]//Wheel Brake[/color] MapKey(&Joystick, H1U, USB[color=#ffffff][[/color][color=#ffffff]0x52[/color]]); [color=#32cd32]//Trim Pitch Down[/color] MapKey(&Joystick, H1D, USB[color=#ffffff][[/color][color=#ffffff]0x51[/color]]); [color=#32cd32]//Trim Pitch Up[/color] MapKey(&Joystick, H1L, USB[color=#ffffff][[/color][color=#ffffff]0x50[/color]]); [color=#32cd32]//Trim Roll Left[/color] MapKey(&Joystick, H1R, USB[color=#ffffff][[/color][color=#ffffff]0x4F[/color]]); [color=#32cd32]//Trim Roll Right[/color] MapKey(&Joystick, H2U, [color=#ffffff]0[/color]); MapKey(&Joystick, H2D, [color=#ffffff]0[/color]); MapKey(&Joystick, H2L, [color=#ffffff]0[/color]); MapKey(&Joystick, H2R, [color=#ffffff]0[/color]); MapKey(&Joystick, H3U, [color=#ffffff]0[/color]); MapKey(&Joystick, H3D, [color=#ffffff]0[/color]); MapKey(&Joystick, H3L, DXHATUPLEFT); [color=#32cd32]//Trim Yaw Left [/color] MapKey(&Joystick, H3R, DXHATUPRIGHT); [color=#32cd32]//Trim Yaw right[/color] MapKey(&Joystick, H4P, [color=#ffffff]0[/color]); [color=#32cd32]//GAR-8 Missiles EXEC [/color] MapKey(&Joystick, H4U, [color=#ffffff]0[/color]); [color=#32cd32]//Gunsight Rocket Mode Toggle (Guns by default) EXEC[/color] MapKey(&Joystick, H4D, [color=#ffffff]0[/color]); [color=#32cd32]//Gunsight Bomb Mode Toggle (Guns by default) EXEC[/color] MapKey(&Joystick, H4L, [color=#ffffff]0[/color]); [color=#32cd32]//Missile Salvo OR Bomb Station Left OR Rockets Angle EXEC[/color] MapKey(&Joystick, H4R, [color=#ffffff]0[/color]); [color=#32cd32]//Missile Salvo OR Bomb Station Right OR Rockets Angle EXEC[/color] MapAxis(&Joystick, JOYX, DX_X_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Joystick, JOYX, [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color]); MapAxis(&Joystick, JOYY, DX_Y_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Joystick, JOYY, [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color]); MapKey(&Throttle, SC, TEMPO[color=#ffffff]([/color]F13, PULSE[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x64[/color]], [color=#ffffff]500[/color])); [color=#32cd32]//Reset View & TrackIR[/color] MapKey(&Throttle, MSP, DX2); [color=#32cd32]//Gunsight Electrical Cage[/color] MapKey(&Throttle, MSU, DX3); MapKey(&Throttle, MSD, DX5); [color=#32cd32]//Gunsight Target Selector button[/color] MapKey(&Throttle, MSL, DX6); MapKey(&Throttle, MSR, DX4); MapKey(&Throttle, SPDF, DX7); [color=#32cd32]//Airbrakes [/color] MapKey(&Throttle, SPDM, [color=#ffffff]0[/color]); MapKey(&Throttle, SPDB, DX8); MapKey(&Throttle, BSF, DX9); MapKey(&Throttle, BSB, DX10); MapKey(&Throttle, CHF, DX11); MapKey(&Throttle, CHB, DX12); MapKey(&Throttle, PSF, DX13); [color=#32cd32]//Position Lights[/color] MapKey(&Throttle, PSB, DX14); MapKey(&Throttle, LTB, DX15); [color=#32cd32]//Teamspeak[/color] MapKey(&Throttle, EFLNORM, DX16); MapKey(&Throttle, EFRNORM, DX17); MapKey(&Throttle, APUON, DX20); MapKey(&Throttle, APUOFF, [color=#ffffff]0[/color]); MapKey(&Throttle, LDGH, TEMPO[color=#ffffff]([/color]DX21, PULSE[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x11[/color]], [color=#ffffff]500[/color])); [color=#32cd32]//Short:Jettison Fuel Tanks, Long:Jettison Weapons [/color] MapKey(&Throttle, FLAPU, DX22); [color=#32cd32]//Flaps[/color] MapKey(&Throttle, FLAPD, DX23); MapKey(&Throttle, FLAPM, [color=#ffffff]0[/color]); MapKey(&Throttle, EACON, MasterArmOn); [color=#32cd32]//Master Arm +DX1[/color] MapKey(&Throttle, EACOFF, MasterArmOff); MapKey(&Throttle, RDRNRM, DX25); [color=#32cd32]//Bombs Arm [/color] MapKey(&Throttle, RDRDIS, [color=#ffffff]0[/color]); MapKeyIOUMD(&Throttle, APENG, [color=#ffffff]0[/color], SEQ[color=#ffffff]([/color]PULSE[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x19[/color]], PULSE[color=#ffffff]+[/color]L_SHIFT[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x19[/color]], PULSE[color=#ffffff]+[/color]L_CTL[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x19[/color]]), TEMPO[color=#ffffff]([/color]SEQ[color=#ffffff]([/color]PULSE[color=#ffffff]+[/color]L_CTL[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x05[/color]], PULSE[color=#ffffff]+[/color]L_SHIFT[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x05[/color]]), PULSE[color=#ffffff]+[/color]DX26, [color=#ffffff]500[/color]), [color=#ffffff]0[/color], [color=#ffffff]0[/color], SEQ[color=#ffffff]([/color]PULSE[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x19[/color]], PULSE[color=#ffffff]+[/color]L_SHIFT[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x19[/color]], PULSE[color=#ffffff]+[/color]L_CTL[color=#ffffff]+[/color]USB[color=#ffffff][[/color][color=#ffffff]0x19[/color]])); [color=#32cd32]//Rocket Fuze Selector[/color] MapKey(&Throttle, APPAT, CHAIN[color=#ffffff]([/color]PULSE[color=#ffffff]+[/color]DX30, D[color=#ffffff]([/color][color=#ffffff]100[/color]), DX27)); [color=#32cd32]//Rocket Selector +DX30[/color] MapKeyR(&Throttle, APPAT, CHAIN[color=#ffffff]([/color]D[color=#ffffff]([/color][color=#ffffff]100[/color]), PULSE[color=#ffffff]+[/color]DX30)); MapKey(&Throttle, APALT, CHAIN[color=#ffffff]([/color]PULSE[color=#ffffff]+[/color]DX30, D[color=#ffffff]([/color][color=#ffffff]100[/color]), DX28)); MapKeyR(&Throttle, APALT, CHAIN[color=#ffffff]([/color]D[color=#ffffff]([/color][color=#ffffff]100[/color]), PULSE[color=#ffffff]+[/color]DX30)); MapKey(&Throttle, EOLMOTOR, DX18); MapKey(&Throttle, EOLIGN, DX31); MapKey(&Throttle, EORMOTOR, DX19); MapKey(&Throttle, EORIGN, DX32); MapKey(&Throttle, IDLELON, [color=#ffffff]0[/color]); MapKey(&Throttle, IDLELOFF, [color=#ffffff]0[/color]); MapKey(&Throttle, IDLERON, CHAIN[color=#ffffff]([/color]PULSE[color=#ffffff]+[/color]DX29, D[color=#ffffff]([/color][color=#ffffff]50[/color]), DX29)); [color=#32cd32]//Throttle Idle/Start[/color] MapKey(&Throttle, IDLEROFF, [color=#ffffff]0[/color]); MapKey(&Throttle, CSU, DXHATUP); [color=#32cd32]//Radar Range Decrease [/color] MapKey(&Throttle, CSD, DXHATDOWN); [color=#32cd32]//Radar Range Increase [/color] MapKey(&Throttle, CSL, DXHATLEFT); MapKey(&Throttle, CSR, DXHATRIGHT); KeyAxis(&Throttle, SCY, [color=#ffffff]0[/color], AXMAP2( LIST( [color=#ffffff]0[/color], [color=#ffffff]10[/color], [color=#ffffff]90[/color] ), USB[color=#ffffff][[/color][color=#ffffff]84[/color]], [color=#ffffff]0[/color], USB[color=#ffffff][[/color][color=#ffffff]85[/color]])); [color=#32cd32]//Zoom[/color] KeyAxis(&Throttle, THR_FC, [color=#ffffff]0[/color], AXMAP2( LIST( [color=#ffffff]0[/color], [color=#ffffff]10[/color], [color=#ffffff]90[/color] ), PULSE[color=#ffffff]+[/color]DXHATDOWNLEFT, [color=#ffffff]0[/color], PULSE[color=#ffffff]+[/color]DXHATDOWNRIGHT)); [color=#32cd32]//Gear[/color] SetSCurve(&Throttle, SCX, [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color]); MapAxis(&Throttle, SCY, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Throttle, SCY, [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color]); MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Throttle, THR_RIGHT, [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color]); MapAxis(&Throttle, THR_LEFT, DX_ZROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Throttle, THR_LEFT, [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color]); MapAxis(&Throttle, THR_FC, DX_SLIDER_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetSCurve(&Throttle, THR_FC, [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color], [color=#ffffff]0[/color]); } [color=#1e90ff][b]int[/b][/color] EventHandle[color=#ffffff]([/color][color=#1e90ff][b]int[/b][/color] type, [color=#1e90ff][b]alias[/b][/color] o, [color=#1e90ff][b]int[/b][/color] x) { DefaultMapping(&o, x); } And here is a button press order that lock it up 100% of the time with this profile: 1_EAC to ON 2_S2 Long press or S1 long press (TEMPO commands) 3_EAC to OFF 4_H4P press 5_EAC to ON Could anyone please try it at home and see if he gets the same results? :joystick::mad::joystick::mad::joystick: ...:pilotfly: Edited August 26, 2015 by ElGringo I7 4790k, Asus Z97 Deluxe, 16GB Kingston Hyper X DDR3, Gainward GTX 980 Phantom, 2x SDDs Samsung 850 pro & Sandisk Extreme Pro, 1 HDD Samsung, Hotas Warthog with Sahaj' s 10 cm extension, MFG Crosswind Pedals, Track IR 5, Wheelstand Pro, CH MFP, Logitech G13.
Havner Posted August 26, 2015 Author Posted August 26, 2015 (edited) Funny thing, what did seem to help me was your modified target.tmh. Hello, I revive this thread because I found no other related to my problem. I started recently using functions and EXEC in my profiles, and all was doing well. My F-86 profile for example was working a week ago. It doesn' t anymore. My controls lock-up when some buttons are pressed in a certain order. I have no means of testing this ATM but I do remember that a modified target.tmh posted here helped me with all locking issues. I use it since and don't have those kind of problems anymore. // modified by Home Fries via inputs from Nicu to fix crashes during nested routines. Please try this. File attached for your convenience. Just rename to .tmh And this is the diff: --- target.bak 2013-09-07 21:20:51.255866800 +0200 +++ target.tmh 2014-04-18 19:42:00.474635500 +0200 @@ -1,5 +1,6 @@ // TARGET definitions // Copyright (c) Thrustmaster +// modified by Home Fries via inputs from Nicu to fix crashes during nested routines. include "hid.tmh" include "defines.tmh" @@ -297,7 +298,7 @@ } int MapKey(alias dev, int btnidx, int key=0, int layer=0) { - if(dev[btnidx]){ dev[btnidx] = 0; _evh(EV_HID_INPUT_DATA, &dev, btnidx); } + if(dev[btnidx]){ dev[btnidx] = 0; _evh(EV_HID_INPUT_DATA, &dev, btnidx); dev[btnidx] = 1;} layer = GetLayerBits(layer); GetDeviceData(&dev); Map(&btnidx, &&devdata.keymap+btnidx*KDATASIZE*4 + 24*!!(layer & 0x40)); Dim(&btnidx, 6); @@ -365,36 +366,37 @@ { int v, x; // if(alloc_locked) return 0 & printf("WARNING: you can declare compound key statements (SEQ, CHAIN, EXEC, TEMPO, AXIS) only inside main() call, and not during an event.\xa"); - v = elements(&keyalloc) - kpos - 3; + v = elements(&keyalloc) - kpos - 4; if(v < np | !np) return 0; // not enough allocation space or no parameters Map(&v, p); Dim(&v, np); // v = params array - keyalloc[kpos] = &proc; // function - keyalloc[kpos+1] = kpos + 1 + np; // parameters index + keyalloc[kpos] = np + 4; // size + keyalloc[kpos+1] = &proc; // function + keyalloc[kpos+2] = kpos + 2 + np; // parameters index while(x < np) { - keyalloc[kpos+2+x] = v[x]; + keyalloc[kpos+3+x] = v[x]; x = x+1; } - keyalloc[kpos+2+np] = kpos + 2 | JUMP; + keyalloc[kpos+3+np] = kpos + 3 | JUMP; x = ASMFind(kpos); - if(x == kpos) kpos = kpos + np + 3; - return x | PROC; + if(x == kpos) kpos = kpos + np + 4; + return x + 1 | PROC; // skip block size } int ASMFind(int x) { int i, j, k; while(i < x) { - k = keyalloc[i+1]; - if(keyalloc[i] == keyalloc[x]) - if(k-i == keyalloc[x+1]-x) + k = i + keyalloc[i]; // next + if(keyalloc[i] == keyalloc[x]) // size + if(keyalloc[i+1] == keyalloc[x+1]) // proc { j = x-i; - i = i+2; - while(keyalloc[i] == keyalloc[j+i]) i = i+1; + i = i+3; + while(keyalloc[i] == keyalloc[j+i]) i = i+1; // param if((keyalloc[i] & 0xffff0000) == JUMP) return x-j; } - i = k+2; + i = k; } return x; } @@ -807,4 +809,4 @@ MapKey(&dev, list[i], list[i+1]); i = i+2; } -} +} \ No newline at end of file target.txt Edited August 26, 2015 by Havner [sIGPIC][/sIGPIC]
ElGringo Posted August 26, 2015 Posted August 26, 2015 (edited) EDIT: Thank You! I'm going to try it right away and report back. Edited August 26, 2015 by ElGringo I7 4790k, Asus Z97 Deluxe, 16GB Kingston Hyper X DDR3, Gainward GTX 980 Phantom, 2x SDDs Samsung 850 pro & Sandisk Extreme Pro, 1 HDD Samsung, Hotas Warthog with Sahaj' s 10 cm extension, MFG Crosswind Pedals, Track IR 5, Wheelstand Pro, CH MFP, Logitech G13.
Havner Posted August 26, 2015 Author Posted August 26, 2015 I edited my previous post. See the info there. It was in Home Fries profile zip file but I attached it here. Let us know if it helped. 1 [sIGPIC][/sIGPIC]
ElGringo Posted August 26, 2015 Posted August 26, 2015 (edited) And my controls don' t lock up anymore... So thanks alot to you Sir Havner who kindly helped me, and thanks alot to Home Fries, Savior of Mankind, that made this. to the community. By the way the modified Target.tmh file should get its own sticky. It would save a lot of time to a lot of people. Edited August 26, 2015 by ElGringo I7 4790k, Asus Z97 Deluxe, 16GB Kingston Hyper X DDR3, Gainward GTX 980 Phantom, 2x SDDs Samsung 850 pro & Sandisk Extreme Pro, 1 HDD Samsung, Hotas Warthog with Sahaj' s 10 cm extension, MFG Crosswind Pedals, Track IR 5, Wheelstand Pro, CH MFP, Logitech G13.
Havner Posted August 26, 2015 Author Posted August 26, 2015 By the way the modified Target.tmh file should get its own sticky. It would save a lot of time to a lot of people. It should be included in the TM software package ;) [sIGPIC][/sIGPIC]
Recommended Posts