Sprool

I watched a VKB Youtube video last night about this, they said it was down to the magnets coming loose. Glad you got it fixed.

But then George ai wont fly the heli for you. I just wanted to dig deeper into Faosmasters earlier claim but it seems it is not correct.

Ive recently noticed every few minutes flying in DCS the blue LED's on the X52 joystick will flash once bright and the trim will jump. This can create a sudden nose up or down for no reason. Has anyone else experienced this before and is there a fix?

I tried out jumping in the Huey checked as solo flight, and it only let me use pilot seat, I could not move to any other seat. So the solo flight checkbox is not related to anything relevant about disabling multicrew in server to be able to fly the Apache on your own as CPG, online. That was the point of this thread and this was Faosmaster's claim above, but has not been proven correct or accurate?

Im still very much settling into keybind configs for the AH-64D, takes a while to bed in what I want and need. Ive finally managed to get the ministick working as a proper joystick axis after disappearling down a long late rabbit hole last night, so I'm happy using the ministick to slew the TEDAC around, and back to the main joystick X and Y-axes to fly the heli. Now I need something to slew the cursor around....

"you can accomplish things with my method by setting up your modifier in the box on the right of the Add Modifier panel (labelled "Switches") as this will allow you to use a momentary button as an On/Off toggle for the modifier." - very interesting - I will give that a try! No- dcs does not recognise the rotary mode switch on the X52

Im wondering if the X52 mode dial could also be used in a similar way. The X52 Hotas has no latching switches but a rotary 3-way mode switch. Ive never tried using that a a modifier in DCS before, just via the Saitek programming software. [edit] the 3-pos mode switch does not seem to be flagging up as a key press so cannot be used a a mod.

I'm wondering if anyone has managed to do this, as I cannot see any option in ME or server settings, or online reference to disable multicrew and allow single player to fly from CPG seat? Would love to be able to do this in the F-14 as well.

I read there is an option to disable multicrew, which would allow players to take over the Apache CPG seat and have the a.i. fly you. It would be really cool to be able to operate the Apache from CPG seat online without the need for a human pilot to sit behind you.

I did some digging last night following a reddit thread to github and back to here, to try and get the ministick working as a proper analog axis that DCS recognises. I finally found a register tweak that worked for me (X52 here, not the X52 pro) so I can now use the ministick to slew properly for tdc and TADS on the AH-64D. There were a few threads where people said it cannot or will not function but this worked for me, you just have to sacrifice one existing axis - easy for me as I have rudder pedals and dont need the joystick z-axis turn. So as I understand it the ministick x acts instead of joystick rotate, and ministick Y acts as the (previously unused) slider 2. I attached the program here, its not my work, I just found it, it has options for which axis you can do without and just edits the registry for you. x52_ministick_axes.zip

Im guessing not, that was the question that brought me to this thread and reading the above, I think its not possible, which is a shame. When you join a server you have to join as pilot and then you cannot change seat.

Thanks Ed, much appreciated esp as you noted you dont maintain them any more

I think 'Set' replaces 'tune' as its less erroneous for VA to understand. Im struggling to get the radios to tune according to what I tell them and I've imported the custom keybinds. Maybe I need a different setting or a better mic but Im getting a lot of issues with VA understanding me and I'v run thru the voice learning lots of times now. UHF - UHS, VHS, VHF, two or to, many errors I need to iron out before these become usable, but I appreciate them now being made free! I also have an issue with keybind not working in the huey (hence voice command not working) - it's Lctrl+Lshift+R which is set to decrease the UHF 1MHz knob

I'd probably look into getting it if it halps me use the Huey radios just via voice commands, Ive spent hours over the last few days trying to get VA profiles to work properly.

I did a fresh install of your Huey profile, also added a bit more gain to my mic. Now I can get it tuning the radios but the tuning they come up with does not match my request, and as shown in the log. I checked all keyboard commands are mapped properly as per the html page in the zip. I tried resetting and realigning. If you take the UHF radio, when you spawn in its set to 251.00 as default. I ask to tune to 255.0 and I get 306.0 I reset the freq to 300.00 as per your ReadMe, then command ' quick Reset Frequencies'. then I try tuning to 255.0 and I get something completely differnt. Do you think something may have changed in the default Huey frequencies since you released the profile? Can you confirm I should be setitng the following for a 'quick reset' as the frequencies I call are ending up on very different positions; On a fresh spawn, Nav = 107.0, quick reset recommends 113.0, VHF comm = 116.00, quick reset recommends 130.00, UHF = 251.00 quick reset recommends 300.00

Im only talking about changing the speech tigger phrase, eg from 'UHF comms tune' to 'set UHF radio' - that shouldnt break all the coding behind it? NB: even when I manage to get VA to understand UHF Comms tune I get the text parser error.

No I dont have Viacom, I have a workaround in VA to name the position of ctld options at the start of a mission so commands know where to find it.

I love these profiles - thx Bailey for all your work, but really struggling to get your Huey profiles working properly. I keep getting an error message in VA when I try to tune any of the radios to a certian frequency. I changed the trigger to "Set VHF Radio" then speak the freq, it seems to recognise this command easier, then I get; "Decimal token could not be converted : {TXT:saidTxtB4Decimal} With the UHF radio I get: Recognized : 'u.h.f. comm tuning' Error converting, [thirdDigit] to [thirdDigit] : Text parse error. Any way to correct this? This is version 1.00 of the Huey profile, has there been an update? Thanks!

I found a workround from Pfeil on the VA forum. It just needs to be told where CTLD is in the menu at the start of the mission then that F-key is assigned as a variable txt and used whenever ctld is called. THe position of the CTLD options is the only bit that changes, the rest of the ctld structure remains fixed. From Pfeil's post: Set logistics F[1..12] Code: [Select] Set text [logisticsMenuSlot] to '[F{TXTNUM:"{CMD}"}]' Code: [Select] "when I say: Logistics menu" Execute command - Open main menu press F10 Press variable key(s) [logisticsMenuSlot] and hold for 0,06 seconds and release

@Baileyis there a way to program voiceattack to get round the problem with ctld where it can appear at different positions in the comms menu? As such its breaking all my nice chained commands to drop smoke or pick up troops if i cannot guarantee the ctld submenu is not always at the F6 (for example) position of the comms / f10 options.

This doesnt work with ctld as it moves around the comms/F10 menu, depending on server, mission, airframe. I saw a voiceattack script where they guy first stated into voiceattack where the ctld option was, then the rest of the chained commands ran perfectly. I can set it all up to work in multiplayer but only if ctld is fixed on a same function key sa ive progranmmed.

Hi - I'm trying to standardise some joystick keypresses to trigger menu options in CTLD, using macros in the joystick software as well as trying to use VoiceAttack for things such as 'drop smoke', 'pick up troops', 'drop troops', but I found the comms menu items can be in differnt orders so pressing comms, F10 other, then CTLD can be sometimes on F4, f5, f6 or f7 (depending on server). If youve programmed everything to need F4 for CTLD submenus then it will no longer work properly on other servers. What part of the script will control this so I can get the position of the CTLD menu same keypress each time, to standardise it?

I have the x52 and find the pots so crap if i assign an axis to zoom it will not stay fixed, it keeps juddering the zoom in and out all the time

Back to the FC3 models again.. I just want to confirm if my understanding is correct, I am working on some bare-metal high specular skins for the FC3 airframes. Short example: {"su27_tex04", 0 ,"Su27_tex04_AAF4",true}; {"su27_tex04", 2 ,"su27_tex04_spc",true}; {"su27_tex04", 3 ,"empty",true}; 0 = the skin texture, 2 = the specular layer,, 3 = decal layer, I create a roughmet texture for Su-27_tex04.dds and call it Su-27_tex04_RoughMet.dds I then edit the above part of the description lua file to replace the '2' with "ROUGHNESS_METALLIC" and set the texture to read Su27_tex04_RoughMet {"su27_tex04", 2 ,"su27_tex04_spc",true}; -------> {"su27_tex04", ROUGHNESS_METALLIC ,"su27_tex04_RoughMet",true}; I then leave the 3rd line the same as its calling for a decal layer but the decal layer is to be left empty and pointing towards the default texture folder. Repeat process for tex01, tex02, tex03, tex05, tex06, tex07. Not sure about the tex02_compos and tex03_compos part - what does this control? Is that all correct so far?

Mines set up in the joystick profiler to spit out the default key presses to zoom in and out ('/', '*') - works a treat across every airframe