Sadist_Cain

Something is very not right if you need to limit the fps to 60 with that system for smooth gameplay :S Especially with gsync on the world should be gravy down to 30 fps. have you tested your monitor for frame skipping perhaps?

I'll have to look but I'm fairly sure it says in the manual that you should be able to see the fuel leaving the rear of the wingtips, if you have a butchers there is indeed what appears to be a lil fuel dump nozzle on the trailing edge of the wingtip. would be nice, I thought fuel dumping was broken when I couldn't see it

Opentrack - Free PS3 eye - a Tenner https://www.amazon.co.uk/dp/B00LME2JGQ/ref=asc_df_B00LME2JGQ56858063/?tag=googshopuk-21&creative=22146&creativeASIN=B00LME2JGQ&linkCode=df0&hvadid=310552180045&hvpos=1o1&hvnetw=g&hvrand=12719002280496561890&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9045605&hvtargid=pla-754758627832 Grab either a Lukeclip, Delanclip or a genuine Trackclip Pro and you're up and headtracking with a set up that's superior to a trackir in many ways and at a fraction of the cost. No excuses, time to ascend, shoot me a PM if you need a hand.

absofrigging lutely. Then do the monitor with Gsync and you'll never look back.

Have to say that the new OO (Online Only) option underneath chatter autostart is fantastic! Absolute silence until the radios are on and then boom, SHE'S ALIIIIIIIVE!!! Top notch Hollywood

not getting the volume staying on for much time, turns itself off after a while, is this intentional? Lovely addition though cheers!

FFB2, still getting stall shake and feeling the loss of hydraulics when flipping over to manual reversion. I might be imagining it but I'm sure that before powering on the aircraft the FFB pitch would be off but centering for roll would be on, reflecting the stick in game, loose on pitch and tight on roll. Yet now my stick just stays centered even without powering the jet. I swear this is different than before, any other folk notice this?

Been looking for a mod to do the same thing since I first saw that video. Always felt the Cannon was lackluster compared to the visceral experience it appears to be irl.

Use the iffcc and change the airspeed to 'True' it's a bit more granular and can help you keep a matching speed with the tanker. IAS just seems like it's not as responsive

that seems like it's an incredibly low framerate especially for those specs, though it could just be an artifact of recording. What are the frames? what resolution are you running?

I Saw you edit those values from 0.5 to 0.65 in this last patch Razbam ;) If it helps at all I've been going hard with 1.0 quite happily for a while now and it's a noticeable improvement in feel from my point of view. Keep on tweakin' :P

No need to shelve it my good man, I too had a struggle with Batumi. Have you tried adding it to the actual speech dictionary within windows? That's what did it for me, that way you have a record of your voice in the windows speech library being used for that specific word, you can even listen to it to ensure your own pronunciation is consistent. Right click the windows speech recognition toolbar that pops up when you click training in voice attack and there's a speech dictionary option in there, just follow the steps for adding a word and job's a goodun. Also if you're getting overlapping commands for windows (i.e. copy and delete) that suggests you have windows speech recognition on ALL the time when there's no need to do so. You only need voice attack to be open. When training you need windows speech (thus the toolbar) but outside of that you can just exit it and VA will continue to work without any windows commands getting in the way. On a side note, wanna get proficient in the A-10C? gimme a shout

Interesting article, never heard about the 3d audio stuff before. I'm holding onto hope that now they have the JHMCS for the F/A-18 they might consider making moves to put it in the A-10, would sure make a lovely addition to this cockpit upgrade that's happening for VR. Wouldn't hold my breath too much though, I thought there was some kinda deal where ED couldn't modify the A-10's functionality.

Happy days dude :) Was about to say it should be just as easy as chucking the any old axis from the ffb2 in there to tell the game it's in use to send ffb signals towards. I'm most intrigued by how you're going to go about adding dampers as my only issue now is that in the old 'hole' where the deadzone used to be there's just no force feedback ergo no centering so anything to hold it in place whilst preserving ffb would be lovely

Great news, you're a legend

Thought I'd share the outcome of my frustrations with hover stops and carrier landings. Firstly the hover stop is a block on the throtttle that stops the nozzles rotating when they hit 82 degrees (called the "hover stop") irl the pilot lifts the throttle ala A-10 engine start style to continue rotating the nozzles past the hover stop, into a braking stop. You can see this hover stop plate if you zoom in on the throttle assembly in game, on the right side of the lever to control nozzle angle you'll see a wee metal plate that the lever itself raises up to move past, that's the hover stop. Using the rotaries on the X-52 to control the nozzle angle with a slight curve (30-35) you can line up the 82 degree hover stop angle with the detent in the centre of the rotary without any real ill effects, works very nicely and might help you getting into that hover a bit easier. Use in conjunction with the STO Stop for your short take offs and nozzle angles shouldn't be a worry for you anymore :)

Well the Harrier *should* have pressure build up on the stick as airspeed increases over a certain threshold. There should also be something to do with the puffer jets when in a Hover though I'm not sure what the feedback from that is supposed to be. As it stands currently you can increase the Gain values in the forcefeedback.lua to get a lil more tension on the stick but thats about it from what I can tell.

The deadzone being referred to is hardwired into the FFB2, there's no removing it without adding a second board for the input. Outside trying to mitigate this issue with the ffb2 there's no need to add curves to the gazelle, nor is there any other deadzone.

Take a bodnar or a teensy and attach it to the potentiometers in the ffb2 if you reeeaaally wanna get rid of the deadzone

Couldn't help but notice a default binding for Q-feel in the controls. Also couldn't help notice a "forcefeedback.lua" in the files with a couple of gain values. Me and my hacked FFB2... We are most intrigued.

Having the same problem as redtail and others but none of their steps work for me. F10 menu imports, commands are recognised but nothing happens (through the inferno trying to spawn a target) And Chatter is always on regardless of radio settings or if the game is even running. Tried removing all the .lua files mentioned by vaicom manual page 33 and repairing dcs. Tried manually placing the .lua files. Tried removing Vaicom entirely, redownloading, same issue. EDIT: So it appears that chatter will play if the game isn't running, then play through the menu and turn off once I've loaded in a plane with radios off, it'll then turn back on when radios are on :S is that intended? seems a tad redundant if it's just turn on all the way up till I'm in the plane to just turn off for a few moments before I start the radios? EDIT 2: Radio menus aren't hidden anymore. Tried resetting everything except for the license info, no dice, the option simply doesn't do anything. Now no matter what I do the Keyword database keeps asking to be finished, despite being done many times in many ways. Everytime I follow the steps advised from other posts more things break, if I uninstall to start again it still doesn't work, this is driving me bonkers. Everything was fine and all I wanted was to have the imported f10 commands work, now everything is buggered. EDIT 4: Now I've removed all profiles, reset everything in vaicom, reinstalled and I still get the radio menus, even if I toggle the option back n forth they just won't go away. 80% of the time I don't get a squelch sound either. Tis totally inconsistent and short of completely burning everything DCS related off my drive and starting over completely I am at a loss. Here's a log: And a voice attack fault that occasionally comes up EDIT TWILIGHT ZONE: Did a reset of everything completely uninstalled and removed all traces of voice attack and vaicom, removed all the scripts mentioned in the manual, did a repair install on DCS. Can still bring up radio menus with the communication key despite menus set to off. Chatter still plays until I'm in a plane with the radio off. Squelch often stops working upon loading DCS. Trying to load the inferno F10 menu results in the keyword list being stuck in a "finish" loop, stops when I remove all the commands that were imported. Voice attack is throwing out the following errors when I try changing the config for use in multiplayer and disable menus. EDIT MORE SLEEP LESS COFFEE: So after cleaning up and reinstalling my keyboard controls went a bit skewiff, odd considering I thought they lived in saved games but I digress. Menus are hidden for the most part however sometimes they will still pop up, squelch is less temperamental and ties in with the power state of the aircraft somewhat better. Has to be said this is an absolutely essential program for DCS, it is magnificently done and I cannot live without it.

Been flying operation bactria using this and all was going fine with JTACs Playboy and Anvil. However with Deathstar, despite voice attack recognizing me I kept getting a message "JTAC recipient does not match currently selected unit" Followed by APC or HMMVW malarky. Constantly saying "Deathstar, boar one one - checking in playtime 60 minutes" In a variety of flavours and nuances with some *extra* words thrown in after a while Just gives me thuds and not understanding, JTAC recipients not matching etc. Used the mic keys on my keyboard and no problem, Deathstar exists and hes quite happy to natter, except now so much time has gone by there's no more targets, immensely frustrating and can't for the life of me figure it out.

Does work but it's more of a bodge rather than a way it should be done :) for one it's adding a whole lot of unnecessary clutter and mark points and as others have stated the targets may well reposition. More importantly if you have the mav on a triple ejector rack (lau-88) then it should be set up to fire as a 'Quickdraw' when you're rippling multiple mavericks, What this means is the next missile should be pointing at where the last one was fired. Being that a mav is a visual weapon you wanna see what you're hitting with it before you let it off the chain. A 'better' way to do business is to set your mark atop your first target then just use stabilization and slew to next target, china hat fwd to zoom/change the FOV of the maverick. If you struggle to keep the mav stable then just slave it to the tgp, use space stabilisation after each move or just use path hold autopilot whilst rippling mavs.

So how about that update there flyboy? :P In my eyes this is the definitive A-10c experience, feels about as real as you can get in a sim, twould be a great shame to not see some new life zapped into it following the 2.5 upgrade. Congrats and many thanks for your hard work!

Seeing as no one has answer this yet. As I understand it the A-10C stick only provides FFB when in landing configuration, that is reflected in the Sim. So flaps down to 30, landing gear down and you'll get the stick shaking hard to warn of an impending stall. I *think* when using manual reversion controls that you'll get changes in some of the feedback, cables and pulleys attaching the elevator if I remember right and feedback from the electric motors controlling the trim tabs though I may be wrong there. Certainly gives me stall shake in the landing config though, very useful to bring it down smooth as silk :)