jasonstory44

All textures high, water medium, shadows high, terrain shadows flat, AF-16, MSAA-8, heat blur low, deferred lighting on, visibility high Is there a way to take a screenshot of my settings if I forgot any important ones? Or even save a track? Those still don't work right on VR correct? Thanks Jabbers

Hi guys, trying to get my settings dialed in with VR. Couple questions if I may...I really like the way the deferred lighting setting looks but I'm running into a problem where the horizon is blinding white. Also blinding white anytime looking near the sun. Anyone else getting this and any solution? Also with shadows, if I set shadows to high but flat for terrain, doesthat gve high resolution shadows in the cockpit but simple shadows on the ground? Thanks, Jason

Anyone else running this in VR with deferred lighting enabled and find it way too bright and washed out? I had to turn it off. Any suggestions?

I was calibrating in the vkbdevconfig...maybe i was doing it wrong but the weight of the TMW kept pulling thew stick aft. Seems all good now with those modifications Loving the stick

So just a suggestion or bit of advice for anyone when they get their gunfighter PRO and Warthog adaptor. After tweaking and experimenting all day I can strongly suggest using the "w" cam and also using 2 50# springs for the pitch axis. Otherwise I found their was a constant and annoying tendency to pitch up in sim. I hope this saves someone quite a bit of assembly and breakdown time. For the record this thing is marvelous feeling. Oh, I also greatly tightened the dry clutch

The dry clutch is the screw on the base that inserts into the spring in the gimbal?

Oh and I noticed it looks like they removed the ground on the PCB board for the adaptor? That's the only difference I noticed from your guide. I hope that's the case

Will do. Gonna choke back some coffee and get back to work on it

I'm gonna have to play with the dry clutch a bit. I'll let you know! Haven't permanently mounted my base yet. Maybe I'll swap out the cam as well. I put in the 50 springs but I'd say my grip has a tendency to pitch back if anything. Maybe the w cam will fix that

Btw, I think everyone is in for a treat when they get their new bases and setups! This base feels nice! Huge improvement over the TM base

Got the buttons working thanks. Not sure if I didn't have the grip seated properly or was doing something else wrong but that was good advice thanks. One last question, what's the purpose of the "w" cam with the warthog adaptor? And why only one and not two? I didn't install it but maybe I should? Thanks Jason

Thanks UIV. I can't seem to find the quick guide though

Does anyone have any experience using the vkb configurator? Just got my gunfighter pro and warthog adapter, went through all the physical alterations fine. Can't for the life of me get the configurator to not throw errors. DCS recognizes the axis but no buttons. I've tried the VKB forums and registered but it won't let me log in there. Ugh so frustrating.

thanks for the input guys...greatly appreciated

Does anyone feel there would be an appreciable gain or benefit to upgrading to a faster RAM (3200) from the 2400 I have now? Just curious if anyone has insight on this especially regarding VR. Thanks Jason

glad you got it sorted. That stupid scaling thing had me stumped me for 5 days last year. And microsoft windows support was zero help. I finally stumbled on it by accident on my own Happy flying!

Elphaba...I believe I went through this headache last year when I set mine up. Spent hours on tech support with microsoft before I finally stumbled apon the fix. Make sure in the windows option that the magnification of the desktop Icons is set to 100% and not something like 150% etc. I found my touchscreen sensed my touches and input but never seemed to hit the right spot on helios. I really hope this helps Jason

Ugh. Problem solved...I do t k ow how or why but by fuel flow kept getting switched off. That's what was choking out the engine. Smh You guys were right...works like a charm. As per usual, operator error

Okay guys a little update...I attached the second throttlr and it for sure shows up and programs like normal....Though when I sim I can't seem to get it to behave. For example, I've removed an axis inputs for the second throttle...Yet when in the sim and flying, my prop and throttle just slowly die off as if its getting a secondary input from the throttle...though they don't actually seem to be functional when moving the sliders. If I disconnect the second throttle while flying everything immediately goes back to normal. Any thoughts on this? Not sure if its specific to the spitfire as its all I have tried it in.

Thanks guys...yea I know I should of just tried it but that would have involved me not being lazy and breaking it out of storage lol. Then programming some inputs blah blah blah. Not a ton of work I know but I usually get complacent and just jump in the cockpit for a quick hop instead! ☺ Thanks I'll report back Jason

Awhile back I had to buy a second TM setup because my HOTAS broke. It left me with a brand new and unused throttle quadrant. I was curious, has anyone ever tried to use two throttle setups and obviously map different axis and commands to the buttons? Is this even possible or would it screw up DCS and confuse it where it's two of the same input devices? Any input appreciated Thanks jason

Can someone help me understand this better? Is this a process that would also help offline single player missions as well?

thanks for the insight guys...I am now pretty convinced that I am blowing my engine because I am dropping my speed too much and getting too caught up in the small turning fight. Appreciate the guidance

Ah....so you guys keep RPM maxed? And just manage throttle?

Ok guys thanks. Looks like I have some more studying to do! Thanks for the input