Headwarp

Installed my damper kit last night.. and WOW. Lol. I haven't had a chance to use them in a sim yet.. but, the damper is capable of really requiring a bit of a work out to move the pedals. And then when I lower the damping enough for the pedals to easily return to center I can use one foot, go to full deflection, take my foot off and basically it stops any oscillation that would normally be present without the damper. Doing so before the damper could be a little noisey, and the pedals would oscillate around center 3-4 times, not that there's any situation where I'd want to do that. Just an observation. My pedals are even more silent than they used to be with the damper attached. Next time I'm in a helo I'm going to detach the spring, and I'm sure that's going to be awesome. Also, installing this kit gave me a chance to appreciate the genius behind Milan's design and how easy it is to replace damaged parts that he now offers for sale on his site. These things are built to last. In 2018 my MCU bricked and Milan sent me a replacement MCU.. easiest install I've ever done in my life. Damper kit? Some disassembly and assembly required.. but. so much easier to do than 99% of consumer electronics. I almost didn't need instructions to install the damping kit on my v2 pedals. I watched a youtube video to make sure which way to orient the damper.. other than that it was pretty easy to see how everything fit together.

I ordered mine on March 3rd. They billed me on the 10th. I received it by the 8th. Literally two weeks.. they told me it would be 5-6 weeks when I asked them on Facebook. I almost wonder if I got someone's return. Still.. well worth the wait. At the same time.. if WH throttle #2 hadn't bricked I'd probably still be using it. Afaik the delta sim mod is solderless as well, and significantly less expensive if that's a factor for you. Probably will be some hotglue you have to carefully remove. Don't try to pull out plastic connectors with your finger tips.. use a flathead. The stick will be a huge upgrade from the slew nub. Back before Milan at MFG upped his overall production for his rudder pedals I waited 6 months for him to fufil my order. Was worth it. Of course these day's he keeps himself stocked. Or of course.. just lower y saturation on both axes for that warthog slew nub. I was fine that way for years. Doesn't stop the virpil ministick from feeling leagues better. But.. I made the slew nub work.

The deltasim mod mentioned above me would definitely make things a lot easier than that slew nub. But, honestly I used the slew nub on the WH for years without much issues. The T-50cm3 ministick is a huge upgrade, but I likely wouldn't have it if my 2nd WH didn't brick. I used to lower the y saturation on the x and y axis to like 15 or less to get it at a comfortable speed in certain aircraft. Other aircraft didn't need so much. Seeing as it did brick though and experiencing the T-50cm3's ministick.. I will say if you're comfortable doing a little DIY the DeltaSim mod for the warthog throttle would instantly feel better once you got it working. It's a solderless job, but you should still be careful with the connectors Thrustmaster used on their PCBs. Pull too hard you'll bend the pins or shred the plastic connectors.

I was previously using the slew nub on a warthog throttle, (went through two of the things) now I use the mini-stick on my Virpil T-50cm3, which imo, while pricey, is the best consumer throttle on the market right now without even considering that each button can have 5 different shift states toggled by a physical dial on the unit. You rig an xbox controller nearby and use that if you wanted to, it would probably behave very similar to the mini-stick on my T-50cm3. I also have a Logitech G13 but they have been discontinued for a long time, and where you could previously get them for like $90 or less while in production, they aren't worth shopping for refurbs or used as the prices are jacked way up. It has an analogue thumbstick, which I honestly disable the drivers for to limit the amount of input devices on my system. I'm still able to assign that to keypresses however, and if I didn't have the mini-stick on my throttle, I could easily assign the up, down, left, and right keys to it and bind those to the TDC slew in any jet and it would be usable. In fact it's easier to setup key commands or button presses and get a smooth functional tdc cursor than two axes. Some jets I don't have to do anything but assign the axes and invert the y axis. Some jets (mostly FC3 aircraft) I have to adjust the y-saturation to keep the cursor from being too fast. You could even get a cheap logitech extreme 3d pro and set it up next to your throttle and use that or the hatswitch on it. Or, if you have one, use a spare hat switch on the stick or throttle. Don't forget DCS allows you to assign buttons to modifiers. So you could make the primary function of a given hatswitch TDC Slew, and then assign a button than when held causes that hatswitch to control something else. I love the slew stick on my throttle, especially coming from the little nub on the Warthog, but, if I weren't willing to spend the kind of money I have on my setup, I could get used to a hatswitch and using modifiers. That being said.. one of the biggest benefits from my first usage of say the F-16C stick that comes with the WH, or even my new MCGU which has even more hat switches and buttons + a brake lever, was having more buttons to use for useful stuff. It's quite a bit more intuitive imo to not need modifiers. On the more budget friendly side of things, CH Products offers an F-16 style stick (with the CMS switch, not the one with the red button) that has two less buttons than the Warthog or TM Cougar stick. Their throttle is a little lackluster but, it does have a little slew nub on it, and quite a few hat switches to work with. And their rudder pedals, while fugly imo, by most accounts, will do the job and last quite a long time. Unfortunately I don't think CH's stickhas a twist axis, so you'd probably want a set of pedals with a setup like that. There is the Logitech/Saitek x55/x56, many people have used and enjoyed that would cover most of your button and slewing needs in DCS as well. I had an X52 Pro for a couple years.. mine didn't hold up, which led me higher quality designs. On the other hand.. the inexpensive Extreme 3d Pro, while not offering much in the way of buttons is a killer stick that for $40, is cheap enough to easily replace if something goes wrong.

I have the flip trigger on my MCGU setup as 4 buttons, up and down, the button press at the "Click" mid travel, and then a logical button when I fully depress the trigger. So it's a two stage trigger with an arm/safe function. Even if there is no arm/safe function in a given aircraft, flipping the trigger up acts as a safety. I enjoy the flip trigger much much more than the dual stage trigger, which, IRL was to active autopilot or radio or something along those lines. Coming from the warthog, I was initially less than impressed when I hit the red trigger.. but now it's just 2 extra buttons because I use the flip trigger for my guns in every aircraft. The trigger pull feels like shooting a Browning .22LR semi-auto pistol. A little heavier than that even. I love the audible click at the break point but being able to pull right through it.

Milan or someone who works for him shipped out my damper and a set of replacement toe brake cables yesterday. @dburne does the damper add any noise to the pedals? Aside from a small thud when I use the toe brakes the crosswinds are mostly silent.

Yeah, that's my guess with whatever's doing this. Old or broken unit models. But it's just a guess.

F-16 SP mission "Combat Training: Home On the Range" in Nevada When I spawn in facing forward my FPS start jumping all over the place. My GPU is nowhere near 99% utilization, none of my CPU cores are maxing out. This doesn't seem like a hardware bottleneck. In most single player situations I can maintain 55-60FPS no problem, and have my WMR headset running at 60hz. But something I believe around the parking area of this mission is destroying my framerate. I have taxi'd around the airfield and facing certain directions I jump right back up to 60FPS. Anybody else get lower than usual framerates that sporadically fluctuate by like 20-30fps looking forward with this track file? I had to upload to google drive because it's 30MB. If not, could you please load the F-16 mission "Combat Training: Home on the Range" on Nevada map and look around and examine your fps and system resources? Someone with more time knowledge and determination than me might be able to work out the cause. here is the link to the .trk file https://drive.google.com/file/d/1JwFwmCJ7UKjvuqpeTGf0ZUpMGNbPv-uy/view?usp=sharing Click download link in upper right hand corner, for some reason google drive is treating it like a zip file. My fps drops by like 20-30, and like I said my system isn't showing any signs of bottleneck.. so I'm hoping this is something similar to an experience we had back in 1.5 where certain models needed tweaking or something was causing similar behavior, but ED had it fixed within a day or two of it being pointed out. Hopefully whatever is causing this can be fixed and leads to more fixes for current performance issues.

wow, this made my hud actually readable in VR. Thanks Taz.

The HTC Vive's native resolution is 1080x1200 per eye. The Valve Index has a resolution of 1440x1600 per eye, and therefore requires a higher demand from your gpu in order to run at the minimum of 45fps required for motion smoothing from SteamVR. Start with a 1.0 PD in DCS, and 100% SS in SteamVR settings for DCS.exe (you can only change this while it's running but you have to restart the game for it to take effect. From there you can increase the supersampling settings in SteamVR for the Index to the best balance between performance and image quality.

While appreciated, the whole point of asking for a feature like this built into the DCS Engine, which has been done before by at least one other engine and could probably be done easily again, is to reduce the amount of time we spend configuring devices. I'm fully aware of that post and it's good info.. but as I said on the virpil forums there are software solutions that would reduce the tedium involved in the current options we have for doing things. The fact that you felt an urge to write a guide for people just kind of makes my point, that this simple feature would make users lives easier. My wishlist includes a solution that doesn't require a written or video guide or hours of tinkering to get into the game and using your controls. Hopefully Virpil provides a solution within their software sooner than ED ever gets to this.. but I think a feature like this in DCS World would make all of us that have the option of using detents happy campers. At least on the setup of input configuration. I mean.. like many of you I have the A-10C, Harrier, Hornet, F-16C, F-14, JF-17, Viggen all of the available helos in DCS world. FC3. It can be a pretty daunting task sitting down to a fresh installation of DCS W, even with control exports on hand.

With many people using TM Warthog throttles or the new Virpil release.. it'd be nice to simplify the process (for the end user at least) for configuring an axis for a physical detent. Personally, I'm against using curves on my throttle axis. Linear travel allows one to develop a feel for power increases and decreases, where a curved axis will vary more in how much a millimeter or two of throttle movement affects the engine RPM depending on where the stick lies.. generally becoming more sensitive as you move away from the center. Currently the only way to use detents in DCS is to adjust the curves of your throttle axes. I'm not going to specifically name them, but at least one other title has a very simple solution to this where you can press a button on the screen and it will mark the position of your throttle as the point at which your afterburners engage, and there's another button to set an idle stop position. This allows the user to keep a linear axis from 0-100% between the two points on the axis, as well as allowing users to utilize their throttle detents with two simple clicks of a button rather than back and forth into the axis tune menus. It may not sound like a big deal.. but the fact that this feature doesn't exist in DCS World generally means simply not using the physical detents provided with our throttles for me. I can't imagine the feature being difficult to an experienced coder, and I think it would go a long way with your biggest fans who throw down hundreds of dollars on gear to enjoy your program. Please.. let's not turn this thread into a discussion about another sim. I'd prefer to leave titles out of it, and my only reason for bringing it up was because it provides an example of a feature I'd really love to see in DCSW. If anybody ED reads this.. I appreciate your time and hope this resonates as a good idea with you guys.

My throttle bricked too. I think it happened during a power outtage. What's worse is It was my second warthog throttle. The first one had a few mechanical failures, like one of the throttles had no resistance whatsoever. I tried to pull the pcb out from the old one and put it into my newer one but the plastic connector snapped off the wires in the one I was putting the PCB into so I threw it in the garbage. I just got my tracking number from Virpil today for the T-50 CM3 throttle.. which I hope lasts me the rest of my simming life for the price I paid for it lol.

The chart below is the Silicon Lottery Binning Statistics. The 8600K based on the samples they received has a 100% chance of being stable at 4.8GHZ at 1.375V. Their top 98% hit 4.9Ghz at 1.387V, their top 87% of chips hit 5.0Ghz stable @ 1.4V . Find a guide on how to overclock your cpu, make sure you can fit an AIO liquid cooler in your case or maybe get a case that will fit one, buy an AIO unit with at least a 2 fan radiator.. You're pretty much gauranteed to be able to OC that thing to 4.8 and I'd be you could even disable the AVX offset as long as your cooling was adequate. At that point.. you probably wouldn't notice the difference between your chip and a 9900k as far as DCS World is involved currently. That could change with Vulkan hopefully by the end of this year, but there's no guarantee that DCS code on a modern API will make better use of multi-core CPUs. We certainly hope so, a 9900k would be a decent upgrade to an 8600K at that point. But by then we're just around the corner from AMD and Intels next slap to each other's faces.

I have to chime in and say VR performance for me has been a bit disheartening since 2.5.6 and the recent updates have fixed nothing. In SP and instant action missions I can run @ 60FPS which i've recently set my odyssey to run at 60hz and it's nice, but if I join any populated MP servers I'm dropping down to like 30fps on the runways, and while it does improve a little once I get in the air, there are still significant drops in FPS that make the experience not fun at all while in VR. In 2.5.5 I was able to maintain at least 45fps for reprojection no matter what server or conditions I was playing in.. but lately in MP it's regularly dropping below that 45fps miminum, meaning even if I switched back to 90hz and turned on reprojection, it wouldn't always work because I'm dipping below the 45fps minimum. I know the DEVs and community managers like to enforce rules when it comes to comparing DCS to other games.. but I can fly in my other favorite sim and maintain 60+fps at all times no matter what with 150%ss + msaa 4x in VR with my rig, all the while they've increased the rendering distances of many details. I almost am able to maintain 90FPS, but I switched my WMR headset to 60hz so I never have to worry about reprojection (it's much easier to ID targets without reprojection..pretty awesome) Simply put, I've kind of given up on DCSW for the time being.. which is a shame considering how many modules I have a license for. I'll happily come back to playing DCS when the VR performance issues are sorted, or hardware allows for it.. but rocking an 8700k and a 2080Ti, I don't intend to upgrade for some time. I'm in the opinion that any graphics improvements that hinder performance from where it was in the last 2.5.5 patch aren't worth it when it comes to flying DCS in VR. I'd rather have a smooth playable experience rather than prettier but unplayable.

I know this post is a few months old. But I have to say.. my first experience with DLSS was horrible. It wasn't far off from the downsampling options built into the game it was implemented in. But it was DLSS not DLSS 2.0. I just jumped in to a different title that I believe has to be using DLSS 2.0.. and it looked freaking amazing. Frankly I'd love to see this revisited by ED as an option. MSAA seems to have even more of a performance hit after the lighting update. FXAA or without AA leaves shimmering buildings and landscapes that tend to drive me crazy. I know it's a long shot to think the team might explore DLSS 2.0, but I think it potentially answers a problem we've been dealing with as players since deferred shading was decided upon as the sole rendering method. Ray traced shadows and light sources (minus reflections) could be cool too...but less important by far than anti-aliasing that works with minimal performance impact. After experiencing DLSS 2.0, I feel like this could be a solution for newer nvidia gpu owners.

The FC3 aircraft are "simplified" but imo harder to set up controls for than clickpits.. as for click pits I just map my hotas to be similar to the real thing. For FC3 aircraft pretty much every button on my stick has dual functionality using the paddle on the WH stick for a modifier, and most of the buttons on my throttle are mapped for dual functionality too. Once done though, the major difference between them and full fidelity pits are that I have to click switches in the full fidelity pits to prepare for combat.. where by the time I'm in combat it's all hotas controls in both pit types. I have to setup my FC3 controls again, as I haven't been flying them since my latest install.. if I manage to find the motivation perhaps I'll export my control settings for stick and throttle and put them somewhere for download. My FC3 bindings for the WH have gotten me some compliments in the past.

Wwhen creating or quoting a post or all you have to do is hit the youtube button up top towards the right and insert the part after "watch?v=" from the url between the command line it creates.. in this case buQ-gLVxrdI {YOUTUBE}buQ-gLVxrdI{/YOUTUBE} Except I replaced the brackets with { to show my example, pressing the youtube button enters the correct command. When editing your own post or using "q:reply" you can access this via the go advanced button, which lets you have all the posting controls.

While overall, my frames have smoothed out in certain situations.. with 20+ people on Growling Sidewinder my FPS still tanks.. but once I'm off the ground I get back up to a steady 60fps for the most part. The saved games rebuild does seem to have smooth things out a bit as I was experiencing some weird framerate issues in SP. Seems turning Anisotropic filtering off in game and setting it to 16x in nv control panel/profileinspector helped a bit too. I'm not having the same experience with other servers. Hoggit for instance I pretty much stay at 60fps even when there's 20-30 people connected, both on caucasus and PG. Might have to check out DCS but I'll quit bumping this thread.. as not everybody might be dealing with the same stuff I was experiencing.

Not saying you aren't already aware... but for anybody who sees this and decides to try it.. Be sure not to delete your original saved games\dcs folder.. mine was Saved Games\Dcs.openbeta and I simply renamed it to DCS.openbeta.bkp.. that way i was able to grab the input folder (DCS.openbeta.bkp\Config\Input) and drop it into the new folder created by DCS to save my controls.

Edited my post thinking no one had replied to it yet but I think I was having some kind of conflict in my saved games folder.. and it wasn't just the fxo/metashaders folders either. I let it build a new dcs.openbeta folder in my saved games and my framerate seems much more consistent. Currently running at 160% SS in steamVR and msaa 2x in my odyssey. I also ran nvprofileinespector and changed some things up but I think that had less to do with my issues than whatever was going on in my saved games folder, which was likely still around from 2.5.5. Then again I need to check this out when the GS server is more populated.. but I feel like I fixed something with the saved games folder rebuild.

so this post initially said something about my frames tanking on growling sidewinder.. but I think something might have been going on with my DCS install, as I renamed my saved games\DCS.openbeta folder and let the game rebuild it. I copied my input folder out of the old one.. and now I'm getting better performance than I was last night. Unfortunately, GS isn't as populated as it was last night when I joined but, I'm pretty sure there must have been some conflict in my saved games folder as my framerate seemed lessed consistant in certain scenarios even in single player yesterday. Going to do more testing.. think I'm back to the belief that 60fps VR for flight simming is BAWS.

I gave my TrackIR away after getting my Odyssey. There are a couple sims I refuse to fly, despite kind of wanting to, because they don't have VR support. like.. resolution be darned, I can't go back to a flat image on a screen vs looking to my right/left and seeing a life sized wing and being surrounded by a lifesized cockpit.

Not something I've noticed personally and I have the OG Odyssey. You're on Win10 Build 2004? And you're adjusting the IPD in DCS not the PD setting, (Pixel density)? Can't tell if typo or not. ;)

Honestly, reading this is disappointing. Guess I'll be sticking with my Cougar MFD's and adding a Blackhog b-explorer to my setup for less mouse necessity. And then... there's also this "Total Controls multi function box" which basically acts as a hornet/f-16 UFC with some optional attachements like landing gear and hook.. Stupid expensive hobby... making me wish I was rich and stuff.