Bob_Bushman

Most likely indeed. In fact I would say anytning below 40 native is below my threshold to tolerate. I have and tested the Pimax 5k at 32, and it was simply not enjoyable.

Virpil themselves say this was meant to be used in conjunction with the other straight extensions as needed. It also depends greatly with how your seat is from the floor, an office chair nearly two feet off the floor, isn't ideal. In a simpit using something like a car seat that's less than a foot from the floor. One long extension on the bottom, then the s-extension, followed by perhaps a shorter straight on top of that, as needed of course. The shorter throw range of the t50 is starting to make sense.

I got a t50, original albeit, and a warbrd. And if I where to sell one of them I'd probably sell the t50. The WarBRD is rather nice. Since ED is not carrying forward with VR in Odyssey, I'm not likely to carry forward with Elite, so I might at some point re-affirm my decision to go center mounted stick, and the warbrd, with a heavier spring might be the way to go.

Making a statement that 90% use OB is a guess. But practically every one I know who play online use OB, so for all intents and purposes it's pretty safe guess. But OB often gets new features for the various modules in early access, as well as the modules themselves a week or two before they release in stable.

I believe you don't "step on the ball" in the Hornet. The fcs is taking care of it. You have a slip indicator down under the artificial horizon , you can also place that on an mfd if you want. But under normal flight it barely moves out of center.

I have been happy with the Rift-s as well, but I would personally right now be looking at the Reverb G2 with improved panels and lenses, sorting most of the reasons I haven't gotten a reverb yet. I use a regular headset over the rift, no issues with the can's fitting over the band, just increase the notches on the band by a few and it's sorted.

My cat chewed over the cable to all my Virpil gear in a matter a minute. Filed a ticket with virpil and they shipped me new ones np.

That's because "gaming" chairs are cheap office chairs, with neon trimmings, and the price tag multiplied with a factor of 2.5.

I made my decision to keep the 1080ti and wait for next gen. That next gen was anticipated to launch about a month ago, but has been delayed due to this current run of the "drowning-snifles", or Kung-flu.

I could use my 32" ultrawide, a 65" 4k tv, or a 100" projection screen. I never bother to play this game in anything but my HMD. It doesn't really matter how large the view is, it still feels like a go-pro video feed from some other dudes helmet cam. I own the Rift, Rift-s, vive, and Pimax 5k+, use the Rift-s now, don't get me started on the pile of dogshit the pimax is. I do 'technically' use the monitor on occasion, but that's only for mission editing. I find myself leaning the same way now with ultrawides as I was with trippel screens when I had them. For certain task's they are great, which is web browsing and spreadsheets etc, for games. Well so many games, Doom 2016 can't even get the UI correct, don't manage to get this right, primarily the FOV usually goes a bit weird and more often than not I now end up playing games at 2560*1440 instead of the native res of my monitor that is 3440*1440. Next up I think I would just get a big monitor at a 16:9 res, even though this thing is 32" inches it's no taller taller than a 24". Sim's, and games now are practically VR only anyway as far as I'm concerned.

Only thing I don't use VR for is the mission editor.

This I'm running PD of 1.2 and MSAA 2x. Setting AF or MSAA out of game via nvidia control panel doesn't work. Those who think it does fails to notice the fact that it isn't on at all, and of course that brings some perf benefits and they announce it as "better", heck I have been there. The shader mod does indeed help with performance a lot, but last time I tried it it borked up cockpit canopy reflections something awful when I was over water and went back to regular.

well, your current mobo doesn't suppport much if any overclocking so for that motherboard a K CPU isn't a good match. If you are also swapping the motherboard as you say, then I'd seriously take some time and check out some reviews and or spec sheets of both intel's and Ryzens. The last gen of Ryzens have really come together compared to especially first gen, with far more reliability and hassle free operation, something they have struggled a bit with at first. But honestly the upper end of Ryzen's the 3900 and over are more out to compete with the workstation line of cpu's for desktop bucks. But it's 3am here and I'm not really seeing straight at the moment so shouldn't really be saying much of anything and just go to bed. One thing though, the ryzen's do run significantly cooler than the i7-i9 intels.

The new t50cm use a completely different set of cams and cam screws, from the pic's I'd seen it looks much much better than the first version, being that I am one of those whose screws just shredded under my phillipshead. You should not have anything to worry about and you have a sweet stick base on the way.

Currently DCS is mostly Single core. Hardly nothing else is. Even though DCS primarily only uses the one main thread, VR doesn't, it has a lot of extra processes, more than track-ir etc, also DirectX uses it's few threads for it's business, then there is all the other things you want to run, Discord, SRS etc etc. More cores always finds work, even as it is. Right now. And even though DCS isn't very multicore right now, that is likely to change rather soon. Buying a CPU now focusing only one single core performance, would most likely leave you wanting an upgrade inside of a year when DCS does update, as well as leaving you wanting the higher core count immediately for any use case outside of DCS. I'm on an i7 8700k right now, and if I could justify it I would have upgraded that to a Ryzen 3900x for the additional core count.

I wouldn't spend money on a 1080p display today. Going 1080p myself to a 1440p is imo a no brainer with not that much of an increase in resolution to power while gaining nearly as much as going 4k but far easier on a GPU. Just because DCS has an issue with the spotting, meaning it's considered a problem, meaning it will be fixed one day I wouldn't put to much weight on it. If you ever do anything besides DCS on your computer like most here, even if it's just your online banking the increased resolution and increased readability is substantial. To be frank though I couldn't comment to much on this game and a 1440p ultra wide since I have never played this game outside of VR. So con might be considered DCs spotting, I think they have been working on it. The pro is: everything else you might use the monitor for. Including anything in DCS inside 15 miles.

Can't really comment to your initial question. Don't look at the hose or the basket. In the f18 I find it more reliable to keep the refueling pod, the one on the wing right above the HUD glass panels but below the canopy rail. I might give a quick glance on the basket right before I hook up, but when I am connected I don't look at anything but keeping the pod in the right position, from experience even just glancing at the basket or probe during refueling almost guarantee the start of an oscillation.

Hear hear, this is some really tricky stuff, I have had the hornet for over a year already and I still mess this up, often. I sometimes think there are magnets attached to the hook and the three wire cause I can't catch one for the life of me. As has been mentioned you can check how your axis responds directly in the controls section. The warthog should not need calibration, but a few units do, but those are rare and far between. They would also need a special software to do so, and TM only give that out after giving you the ring around in the support system. It has been linked around here somewhere but not seen it for an age. I'd first check DCS's axis settings, where you can also add a curve and edit the axis, if you move each throttle and the axis responds at 0-100% at each end of the travel you should be good. So far for what you described sounds normal for the hornet. The response delay is short enough to almost not kotice, and yet long enough to really throw you off at times. Earlier I found this vid from the 104th, it stands out with that it has the control indicators up, and you can see how much his throttle is bouncing around, and also you can see how he puts it from nearly idle to mil at one point and you can hear it takes about a full second for you to hear the engines rpm spool up.

Yes but doing so would remove any tweak or improvements done from ED's part. Or potentially if any of the action ID's change it could worst case break the bindings enterily, although that is very unlikely.

I believe it would, but I'm uncertain if that is simulated currently.

Not a bug. There is significant latency in the throttle response on the hornet irl and you need to anticipate where you need your thrust positioned preferably at least a second or two in advance of when you need it. There is no magic throttle position but my preferred method is to time my movements, you should be constantly moving the throttle on approach, again in anticipation of where you need your thrust ahead of time. So that as you are about to touch down you are coming back up to full power as you touch down.

His main thread is updated with it. https://forums.eagle.ru/showthread.php?t=215373

There has been a lot of changes with the open beta, then again you don't mention being on it, so I'm mostly just assuming that you are. With 2.5.6 a lot of changes was introduced to maps and series of shaders, if you are still running the old shader cache from before, this should be automatically taken care of but often seems to need a little help, This also means that the old Kegety's VR shader mod IS NOT COMPATIBLE there is a new one out if you must. I recommended when updating to 2.5.6 to wipe all pre calculated shaders, remove all mods, just delete all folders containing mods you have installed, and run a DCS repair. Patching processes can also go wrong, and they very often do, so running a repair is not a bad idea regardless. This current beta also has issues with most custom scripted missions, my own basic target practice mission I barely notice any difference apart from the increased saturation on 2.5.6. Missions with heavier scripting though are in some form of utter ruin. If these things don't help try switching to stable. I still think most people should be on stable, but I guess people really need to mount the hornet pod on the side station. The main shader caches are by default "c:\users\username\Saved Games\DCS.openbeta" in the folders "fxo" and "metashaders2" Even just updating a driver could require a shader recalculation so if something has gotten between dcs's built in process for this it's a good idea to wipe these anyway. After doing this the first couple of map loads will be longer than usual. I honestly don't have all that much difference in performance between the 2.5.5 and 2.5.6 if I also account for not running the VR shaders mod so it's definitely possible.

It's probably the method with the most satisfactory and more correct result. Problem is everytime DCS updates you will have to manually edit every file for every module all over again. Granted you will be likely able to just copy paste your lines in, but it can quickly become a long process for every hotfix ED deployed, if you have a 5-6 modules that you hope to use with some regularity it becomes old fairly quickly.

I believe you can setup target to simply have the switches work as impulse swithces, that also triggers on both movements, but it's been a while since I have used my warthog.