HiCKS-BB15

Ahh I'm not alone... Same problem on a multi-mission made with MOOSE. Don't understand why, i test 3 times, never ILS worked. I wonder if it necessary to have a flight plan, cause it was free flight with no waypoints.

Excellent ! Merci pour ce partage commémoratif ! Thank you for this commemorative sharing!

If you read 'French', you can also try this post : 'How to calculate easily your bingo' http://www.checksix-forums.com/viewtopic.php?t=145162 Cheers, HiCKS

Rooo, I'm Sad. Too much job to update the missions ? Maybe could you tell us how you create this missions and maybe we can try to follow your way ?

Hello Emolina, I come back after different journeys far away my home, and now the M2000C is a quite good playable so i would like fly your missions : https://forums.eagle.ru/showthread.php?t=174348 But after few tests, every mission i try (Annotated & Interesting) are stuttering. As soon as I'm cockpit, and when i press 'Escape' it's fluid. All missions, every time, are "jerking" . I do not understand why. Baltic_Dragon's campaign is Ok, training missions are ok but your missions are not.

Hello Emolina, I come back after different journeys far away my home, and now the M2000C is a quite good playable so i would like fly your missions : https://www.dropbox.com/sh/mzic1uoxnyofgm3/AACwKPXVgsoXxkuPn4xSUqT6a/Published%20Missions/M-2000C?dl=0 But after few tests, every mission i try (Annotated & Interesting) are stuttering. As soon as I'm cockpit, and when i press 'Escape' it's fluid. All missions, every time, are "jerking" . I do not understand why. Baltic_Dragon's campaign is Ok, training missions are ok but your missions are not.

Hello, any news ? We're a lot to keep a look on your work

So HF, When I load 'TARGET M2000C hc 165.diff.lua' and 'TARGET M2000C kb 165.diff.lua' in command options this is what I see : On Throttle : everything work On HOTAS : All buttons working except the "pinkie lever" do nothing and when I push H3 to left,up(And I also notice that H3 to up = cockpit view) or right then the script going mad and do that : H3 push to down = nothing happen On MFD1 (LEFT) : LOSB 16 to 20 are working but LOSB 1 to 15 don't work LGAIN+LSYM+LCON+LBRT do nothing On MFD2 (RIGHT) LOSB 01 and 16 to 20 are working but LOSB 2 to 10 don't work, LOSB 11 to LOSB15 are mapped for PCN RGAIN+RSYM+RCON do nothing but RBRT is mapped for PCN Like last time I have lot of red lines. I think something going wrong in the script, don't you ? HiCKS.

Hello Home_Fries, I'm damned .. I install your new version and just after launched the script : error ! Any solution ?

Hello Emolina, I can't watch until Wednesday, i will check :)

Hello Emolina, thanks for this amzing job, I like the concept :) By the way, I test few missions and the first thing strange : I always taking off later than possible, we have to wait the engine start-up and INS Alignement, I think the mission should start ten minutes before the time of take off, for the complete startup sequence - taxi and take off. See you, HiCKS

Happy days Home Fries :thumbup: I'm in my family, i come back on wednesday evening in my (poor) room to try your new version. By the way, yesterday i take a look on each file and i understand that my red lines in command options are du to something wrong with DCS and the keyboard files, i will continue to investigate on my return. Have a nice week end, HiCKS

Excellent, no prob, i'm happy to help you :) I set the variable in DCS World.tmc But, I just check the change, and note that the microstick doesn't work on X axis (vertical is ok, but the TDC does not move horizontaly) HiCKS

I also note that the HOTAS loose the profile when i push VHF radio button on the throttle ...

So, i made the change, but another mistake happened : a syntax error. Apparently it's needed a second parenthesis just there : ActKey(KEYON+PULSE+X(AI_PTT_Array,0)[b][size="5"])[/size][/b];"); and now, each time i push the button this appears Is it ok ? HiCKS (cool i'm a debugger :thumbup:)

Hello Home Fries, I was on duty this last days so I only do test this evening with your new version. Unfortunately it's working worse ... so, to continue, i follow your mind : Of course the M-200C profile is loaded (see spoiler) and, as you say, ROSB1 is a keystroke, LOSB19 too (and some others ...). I did the swap, it's working very well. Now MFD1 is on the left and MFD2 is on the right. I did it for each aircraft, but i only fly the M-2000C, and nothing different happen. In game, nothing work for the MFD, and now (after the 1.64 update) i have this error : Compile error in Execute: = expected, in "if(FkeyPress < 1) ActKey{KEYON+PULSE+X(AI_PTT_Array,0);" CommState_On(HC) Compile error in Execute: = expected, in "if(FkeyPress < 1) ActKey{KEYON+PULSE+X(AI_PTT_Array,0);" It's making me crazy, cause i follow scrupulously your setup guide and it doesn't work. :doh: I feel stupid ... Thanks for your help :)

Previously, thanks Home fries for your time and your patience :thumbup: 1.Run the TARGET profile For that, it's ok, i made a shorcut on my desktop by following your instructions. 2.Load the Device Analyzer and the Event Tester (can be done from the Script Editor). no probs 3.In Device Analyzer, you should see the Thrustmaster Combined device with 8 axes and 32 buttons. Start pressing buttons. thats's right : Thrustmaster Combined device with 8 axes and 32 buttons. 3.Pressing S3, you should see DX30 and (depending on the profile loaded) DX3. That's right :) Pressing any LMFD button should give you DX31 + whatever button you selected. Any RMFD should give you DX32+button. Something going wrong my lord, you can see on screenshots (For the Left or Right MFD, it's just their position on my desk ;) ) RMFD : (MFD1) ROSB1=Button 1+Button 30+Button 31 ROSB2 to ROSB14=Button X(the button selected)+Button 31 ROSB15=Button 15+Button 30+Button 31 ROSB16 to ROSB19= just the button on the MFD1 (see the screenshot "Right MFD press button 15.png") GAIN UP=Button 27+Button 30+Button 31 GAIN DOWN=Button 28+Button 30+Button 31 SYM UP=Button 21+Button 31 SYM DOWN=Button 22+Button 31 CON UP=Button 23+Button 31 CON DOWN=Button 24+Button 31 BRT UP=Button 25+Button 31 BRT DOWN=Button 26+Button 31 LMFD : (MFD2) LOSB1+LOSB11=just the button on the MFD2 (see the screenshot "Left MFD press button 1.png") LOSB2 to LOSB10=Button X(the button selected)+Button 32 LOSB12 to LOSB13=Button X(the button selected)+Button 30+Button 32 LOSB14=Button 14 flashing and after stay Off + Button 30 + Button 32 are ON LOSB15=Button 15+Button 32 LOSB16 to LOSB19= just the button on the MFD2 (Like the others") GAIN UP=Button 27+Button 32 GAIN DOWN=Button 28+Button 30+Button 32 SYM UP=Button 21 (is flashing)+Button 30+Button 32 SYM DOWN=Button 22 (is flashing)+Button 30+Button 32 CON UP=Button 23+Button 32 CON DOWN=Button 24+Button 32 BRT UP=Button 25 (see the screenshot "Left MFD press BRT UP and DOWN - same thing happen.png") BRT DOWN=Button 26 (Like BRT - UP) I also note a delay between I press button and corresponding display (rouglhy a second) when it's mapped on the script. then doctor, what do you think about ? I throw everything out the window? :pilotfly: Thanks for your help :) HiCKS. P.S : I attached screenshots a the end of this message, in one file. For HF_MFD.rar

Shit happens, but I think I did something wrong, cause all command with "JOY_BTN30, JOY_BTN31 & JOY_BTN32" are in red. [1.]Which commands are red in 1.64? See this looooong list : [2.]Do the MFDs work with any other profiles? I just test on A-10C (the second mod i have), and same thing wrong in option command. [3.]How did you test to make sure the MFDs don't work? (e.g. device analyzer, options screen, or in-game) Before i mapped directly MFD (without script), and all going well, I used them on FalconBMS4.33 without problem. [4.]Finally, do the MFDs work with the 1.63 lua loaded? No, same problem, the difference is in v163 same lines are red in Keyboard column too, and now in v164, only Thrustmaster Combined controller column have this line (see spolier in 1.) in red. I hope so :book: Regards, HiCKS

Hello Home Fries, In first, thanks very much for this amazing works :) very impressive and i was searching for a long time a TARGET profile like this for DCS. But right now, i have a problem, i'm using M-2000C profiles (MFD and TM Cougar stick and throttle) and my MFD doesn't work. In options, with v163 Keyboard and Thrustmaster Combined controller columns, a lot of line were red. With the new version (v164) only column with Thrustmaster Combined controller has line with red. I add moddifiers for JOY_BTN30, JOY_BTN31 & JOY_BTN32 with the script launched has said in documentation. (I have scrupulously followed the documentation) I don't understand why. I check all your documentation (very complete and useful) but no solutions at all. The script launch and work well, it's saying that MFD are mapped : Thanks to take a look on this :( HiCKS.