Scudslaker Posted March 29, 2010 Posted March 29, 2010 Hey Pilots, as i installed my new FC2 download version, i started to create a new Macro and a new Joystick file. Well my problem is: i can assign, right Shift, right Control and right Alt, with the Korgy Code Generator. compileing and downloading this string to the device, is working without any failures but the assigned function: right Control + L = RCTL l is interpreted as: CTL l in the KEy Tester.:megalol: Anyone heard of this before? For me, i just found out and don t want to change keyassigns from FC2 to be able to use my Cougar :joystick:. I really hope you guys have the solution for me.. Sincerely Scudslaker TM HOTAS WH :joystick:, Saitek Pro Pedals, Track IR 4, 2xJoyWarrier, 1x KeyWarrior, i52500k @4600MHz, ASUS P8Z68-V Pro, NV 670GT, SSD+ WD BC+ WD Raptor, 32HD:pilotfly:[sIGPIC][/sIGPIC]
AustinN360 Posted March 29, 2010 Posted March 29, 2010 As far as I know you should not use CTRL/Alt or Shift hold for anything, instead it should be which ever modifier that you want (i.e right control) then the key clicking insert to macro after each one the putting the 2 on the same line and wrapping them with { } so it looks something like this: AutopilotBankhold = {LSHF b} or INUpowerswitch = {RCTL RALT i} Hope this helps. Route Out 1
Necroscope Posted March 29, 2010 Posted March 29, 2010 just assign required button as DX button and set it right in FC2 to required action. If you want to use flags\u-m-d and other cougar features - create your own combination and set it both in Cougar and FC2. or use method above :) Всех убью, один останусь!
Scudslaker Posted March 29, 2010 Author Posted March 29, 2010 Thanks for your hint Route, but i checked with negative result. Well i go for some other tests with it!) TM HOTAS WH :joystick:, Saitek Pro Pedals, Track IR 4, 2xJoyWarrier, 1x KeyWarrior, i52500k @4600MHz, ASUS P8Z68-V Pro, NV 670GT, SSD+ WD BC+ WD Raptor, 32HD:pilotfly:[sIGPIC][/sIGPIC]
KillaALF Posted March 29, 2010 Posted March 29, 2010 (edited) It's just the key tester though, the keypresses will be interpreted correctly by the simulation. You can even verify it with Foxy's DX8 key tester, found under the "Apps" heading or alternatively by clicking "View" in the normal key tester. Oh and yes {} are very important, especially if you want to use the macro with a /H modifier, without the brackets only the last key will be repeated. Edited March 29, 2010 by KillaALF 1
AustinN360 Posted March 29, 2010 Posted March 29, 2010 Don't worry about the keytester. It just picks up that a modifier has been tapped, I don't think it can really tell which side of the keyboard but as long as the macro says either LCtrl or RCtrl it's fine. 1
Scudslaker Posted March 29, 2010 Author Posted March 29, 2010 Thx Pilots!!!! it s working, you re right most important is the: {} +1Rep for Route :joystick: TM HOTAS WH :joystick:, Saitek Pro Pedals, Track IR 4, 2xJoyWarrier, 1x KeyWarrior, i52500k @4600MHz, ASUS P8Z68-V Pro, NV 670GT, SSD+ WD BC+ WD Raptor, 32HD:pilotfly:[sIGPIC][/sIGPIC]
coolts Posted March 30, 2010 Posted March 30, 2010 Doh. I was just creating a new thread about this and read your answers. Cheers guys. I will try this tonight as i gave up the other day and just started changing the in-game keys. Bad idea when you have 8 or so separate sets to do now.:doh: [sIGPIC][/sIGPIC] i7 9700k | 32gb DDR4 | Geforce 2080ti | TrackIR 5 | Rift S | HOTAS WARTHOG | CH PRO Pedals
Scudslaker Posted March 30, 2010 Author Posted March 30, 2010 It's just the key tester though, the keypresses will be interpreted correctly by the simulation. You can even verify it with Foxy's DX8 key tester, found under the "Apps" heading or alternatively by clicking "View" in the normal key tester. Oh and yes {} are very important, especially if you want to use the macro with a /H modifier, without the brackets only the last key will be repeated. +1 Rep for KillaAlf, i had forgotten to say!) many happy landings:pilotfly: Scud TM HOTAS WH :joystick:, Saitek Pro Pedals, Track IR 4, 2xJoyWarrier, 1x KeyWarrior, i52500k @4600MHz, ASUS P8Z68-V Pro, NV 670GT, SSD+ WD BC+ WD Raptor, 32HD:pilotfly:[sIGPIC][/sIGPIC]
Legolasindar Posted March 30, 2010 Posted March 30, 2010 If you like can use my Cougar profile for the FC2. http://forums.eagle.ru/showthread.php?t=51736 1 [sIGPIC][/sIGPIC] Cavallers del Cel - Comunintat Catalana de Simulació http://www.cavallersdelcel.cat
coolts Posted March 30, 2010 Posted March 30, 2010 (edited) Cheers for that! Someone had to do it and yours looks a lot tidier than mine. +1 rep (I think it worked anyway) ps. Have you done a FSX one? A few of the guys here have been after a pre-made one of those for a while. Edited March 30, 2010 by coolts [sIGPIC][/sIGPIC] i7 9700k | 32gb DDR4 | Geforce 2080ti | TrackIR 5 | Rift S | HOTAS WARTHOG | CH PRO Pedals
AustinN360 Posted March 30, 2010 Posted March 30, 2010 I have included all the necessary functions of each aircraft, in a single profile. Thus, with this profile can fly any aircraft that includes FC2 without changes. FC2 is very simple systems, so that the creation of this profile has been among the least gratifying, forcing me to include features that I usually leave out of my profiles. I have followed the Nico's profile for FC 1.12b as a guide. I'm guessing this means ALL aircraft!
Scudslaker Posted March 31, 2010 Author Posted March 31, 2010 already had a look into your files,..great help, but i prefer to set fuctions on my own,.. i must have a look, have build an profile for FSX in the pat but used the X52pro in last time for FSX When i find mine, you ll receive an pm!) TM HOTAS WH :joystick:, Saitek Pro Pedals, Track IR 4, 2xJoyWarrier, 1x KeyWarrior, i52500k @4600MHz, ASUS P8Z68-V Pro, NV 670GT, SSD+ WD BC+ WD Raptor, 32HD:pilotfly:[sIGPIC][/sIGPIC]
Marder Posted March 31, 2010 Posted March 31, 2010 (edited) i have a question in programming the joystick-file in the foxy-software. e.g.: i'd like the release-weapon button not to be active while in nav-mode. is this following syntax korrekt? : BTN S2 /D /U /I weapon_ripple_quantity /O /H weapon_release /M /I lights_gear_toggle /O lights_nav is this the right way? or do i have to use /M /U /D seperatlely? Edited March 31, 2010 by Marder MB: Intel DX79TO; Core i7 3820 (3,6 ghz); SPU: Asus Xonar D2X; GPU: AMD XFX 7970 BE OC (3GB); RAM: Kingston 8 GB DDR3-1333 Quad-Kit; HHDs: G.Skill Phoenix SSD (for OS&DCS), WD 1 TB + WD 160GB; PSU: be Quiet! Dark Power Pro 10 550W; Display: EIZO Foris 2333-BK; OS: WIN8 Pro 64bit (latest updates); TM HOTAS Warthog; CH Rudder pedals; Cougar MFDs; iPad Mini with iControl DCS; TrackIR4 + TrackClipPro. A10 startup procedure -->
Scudslaker Posted March 31, 2010 Author Posted March 31, 2010 (edited) it should be in separated way: BTN S2 /U/I weapon_ripple_quantity /O weapon_release /M/I /O /D /Iweapon_ripple_quantity /O weapon_release cheers and good luck!) Edited March 31, 2010 by Scudslaker 1 TM HOTAS WH :joystick:, Saitek Pro Pedals, Track IR 4, 2xJoyWarrier, 1x KeyWarrior, i52500k @4600MHz, ASUS P8Z68-V Pro, NV 670GT, SSD+ WD BC+ WD Raptor, 32HD:pilotfly:[sIGPIC][/sIGPIC]
Legolasindar Posted March 31, 2010 Posted March 31, 2010 This is the correct syntax. BTN S2 /U /I weapon_ripple_quantity /O /H weapon_release /M /I lights_gear_toggle /O lights_nav /D /I weapon_ripple_quantity /O /H weapon_release 1 [sIGPIC][/sIGPIC] Cavallers del Cel - Comunintat Catalana de Simulació http://www.cavallersdelcel.cat
Marder Posted March 31, 2010 Posted March 31, 2010 reputation for you both - thank you. MB: Intel DX79TO; Core i7 3820 (3,6 ghz); SPU: Asus Xonar D2X; GPU: AMD XFX 7970 BE OC (3GB); RAM: Kingston 8 GB DDR3-1333 Quad-Kit; HHDs: G.Skill Phoenix SSD (for OS&DCS), WD 1 TB + WD 160GB; PSU: be Quiet! Dark Power Pro 10 550W; Display: EIZO Foris 2333-BK; OS: WIN8 Pro 64bit (latest updates); TM HOTAS Warthog; CH Rudder pedals; Cougar MFDs; iPad Mini with iControl DCS; TrackIR4 + TrackClipPro. A10 startup procedure -->
Recommended Posts