Bob_Bushman

I got a 1080ti and currently find this OK, If finances allow though I'm aiming to get the 3k series 80(ti?). But I got the 1080ti since I found my 980ti lacking, so can absolutely understand wanting an upgrade right now. And why not just get a 2080 or 2080ti if you can, I can attest DCS uses 10+ GB of VRAM while I'm playing so that extra ram on the TI is welcome, unlike most other games out there that barely uses half of it. Nothing says you can't get a 2080ti, skip the 3k range, maybe even the 4k range coming in another two years ish. The 80ti range is mainly considered as five year cards so there is going to be a pretty large shift in demand before you need to upgrade much more often than that.

Is anyone surprised ?

I'm sure you can land and get an f-16 off a carrier if you wanted. If you used an M-26 to sling load it like cargo.

Again from what I heard in Carmack's speech, with Quest Link, there will never be the option of disabling spavewarp, it will only send the 36 fps to the HMD and use the internal cpu of the Quest to scale back up to 72hz. This to ease the response on job on the USB interface.

@chapa I know full well what Supersampling is, and what it does. and those numbers are actually a little bit off. To account for loss of detail in the lens distortion they render a fair bit higher than the native panel resolution, in essence The CV 1 has a render target of 2688*1600. These numbers account for both panels. The S has not one but two, in the Oculus software for the device there is a semi buried between "Performance" or "quality", this affect the default render target. Performance: sets a default render target of 3008*1616, this is surprisingly close to the original rift resolution, but the lenses on the S has a much lower distortion than the CV1. The second Quality option has a render target of 3296*1776. How this setting is applied by default also varies, but I think the main trigger was having a GPU considered\identified by the Oculus software as equal or greater than a 1070. As for Pixeldensity vs steamvr custom resolution, PD of 1.3 is about the same as a SteamVR custom resolution of 170%, As for the inspector settings, yea the more I test these, they less they do, or make things worse, and yes I'm using negative LOD values, and even at native resolution, no SS I might hit 80fps slightly quicker, but I still spacewarp around cites <5k', and even on some airfields I was dropped as low as 20fps sitting on tarmac. With my original settings of 1.3 I would stay a little more in spacewarp, but I would NEVER go below it either, so, so far these settings has been nothing but a drop in both quality and performance.

Have a hard time figuring what that would be. As mentioned I completely close DCS and reboot the rift-S between changes. And I'm running the inspector with elevated privileges.

Yup, but as with all Pimax backer benefits there has been zero communication about it since the kickstarter. And since the Kickstarter Leap Motion has been bought out as well, unknown if they have any interest in honoring old deals. At which point I'd be expecting my $100 back, and I mean refund, not YET another $100 voucher from Pimax.

Yeah, I'm not sure what could be the cause if some settings doesn't kick in or not. I have not only been restarting DCS but I have also been restarting the oculus service between testing applied changes. So short of a fresh reboot between applying each setting I'm at a loss. Hmm, checking drivers, seesms I'm on 441.20, and current are 441.41 Updated drivers, Testing some more, and I will have to conclude for now: The only thing the inspector does for me, is to override what usual tweaks Nvidia/Oculus is done from before, making things generally look like garbage in and out of DCS. Anisotropic filtering from the inspector never kicks in, but forces it to off for the ingame setting, even when set to allow application control. AA settting, regardless of mode, does nothing. LOD BIAS, no, can't really see that does anything at all, at least nothing I would consider beneficial. Pretty much anything done with the inspector leaves DCS looking as if it's running very low texture detail, for example, any detail texture on the cat's, skid marked section on the runway, all gone. and all textures in the cockpit generally blurrier with more aliasing artefacts. Even when upping PD back up, which removes any performance increase from this. I'm back to defaults, and PD 1.3, anything suggested, and bunch of other settings suggested in this thread was a huge drop in image quality with hardly any performance gain whatsoever.

It definitely works, no doubt of that. And it's been a while since I did my comparing with custom res vs oculus pd, but from my guesstimate is 208% in Steam is approximately 1.5x in PD and 178% is in the neighborhood of 1.3. Now that can't really compare with the Index all that well, I have never even seen one since Valve still refuses to sell hardware in the EEA. And well my opinion and disappointment of the 5k+ is hardly any secret. I also suspect desired PD is highly individual in the S since we can't adjust lenses in it, it varies between each anyone how each eye hits the lenses. So far I have all only done my testing in the F18, I'll give the viper ago we well but so far I'm not having to much of an issue with performance and pd at 1.3.

I did some more A/B testing and indeed SSAA doesn't work at all. So I'll admit to that one, ;) Also been testing a little more but there it's as if the anisotropic setting doesn't kick in from the profile inspector, past 2 am here do getting to tired for vr now so will test more later. So far the shimmering is far to bad for me with a lod bias of less than -0.375 and it's still a far cry in fidelity as what I had with supersampling of 1.3, I'm testing this with a PD setting of 1x And regardless of of running with 1x PD, I drop to 40 when looking over a city scape or any other some what busy place. So I don't really see much point in taking a drop in pq when I won't get any big performance increase when it matters. And run PD at 1.3.

Tested this out with the S tonight, and honestly find it vastly inferior to what I had from before. These 'recommended' settings was as if someone smeared grease on my lenses with the bonus of heavy aliasing and shimmering. Sure, ASW triggered a little less than my usual settings but only barely and even the Dashboard\desktop view in the rift took a nose dive in clarity, reverting back to defaults clear that back up and running at pd 1.3 and SSAA 1.5x is much much better in DCS. Anyhoo that's my two cents opinion.

As with all things it could vary between each person, but for me the top section of the cup goes over my ears and under the halo band without much if any interference.

I own the original t50, and a warbrd. The differences are quite severe, but in the essence the warbrd is designed to be used under less custom circumstances, you can plop this on a desk, and use, even though I wouldn't recommend that for any stick, the springs and cams are thus designed to present less of a force profile, it's meant to be used as is, with no extensions. It also have a large throw range, about similar to that on the warthog, on the stick compared to the t50. The t50 has been designed towards those with dedicated setups and pits in mind. You are expected to use extensions, long ones, hence the shorter throw range becomes a plus side, it features more aggressive cams and springs and it requires to be bolted into a position and a fairly low one at that. With the added adjustability with t50's spring tension mechanism you can fin tune it to be either a nice easily pushed stick, to an arm wrestling simulator, and anything in between. For instance if you are looking for a center stick with a gooseneck extension the t50 is your go to. Both are exceptionally precise and a joy to use. I suggest buying all the appropriate cams you can, that way you can test out and tweak to your own desired feel.

Only issue with bluetooth earplugs is the bluetooth part, you will require dongle for the bluetooth part, and BT connectivity is a nightmare problem with potent EM fields that there happens to be a a lot of near a computer. Some laptops have BT builtin, but yea mileage varies greatily, for dekstops, getting the transceiver on an extension cord and a little out of the main EM fields of the desktop would help greatly. Also often suffer heavily from delayed audio, there is a reason no-one has made a BT gaming headset, and instead just do their own setup on an RF connection. Personally I have no issues using a regular gaming headset, a g533 to be specific, it fits over the halo just fine, in fact better than with the old CV1, where the band would pass under the cushion, puncturing the over ear sealing. Most gaming headsets won't be bigger than those, and most otheres I have tried as well like the Kingston hyperX's work just fine. Any on-ear headset as well would work with no issue.

How much? Apparently it's tree fiddy. No seriously it's ok amazon for $350.

If you are a kickstarter I belive you would.

I'm just looking to clarify something. Will this be your sons stick, your stick, or for the both of you ? I know from my own childhood that if wanted something like this, I would be expected to cover the cost, so mowing lawns and whatnot. I'm sure it's been talked about a bit and I can throw in my own $.02. CH has stagnated completely, there has been no development, no iteration since the switch to USB 2,0, they have however moved factories and taken a nose dive in QA. I can no longer recommend CH as relevant at all. Their user support forum server has even been turned off, that saying something about their interest. Saitek\logitech is fine, yeah it's not perfect, but so wont something that is 3x as expensive be either. There is nothing really that could be an issue with those that wouldn't be similarly an issue with the more reasonably priced t16000m from Thrustmaster. The warthog, well the warthog is a bit of an odd one. for 10 or so years it has been the only major offering for a serious sim like DCS. And since it has been the only HOTAS on the mainstream market for so long that has even tried to do it, it has gotten a rep that I find a little to lenient. It has flaws, and there are shortcuts taken in it's design, but don't get me wrong, it is a very very good setup that will\should last for 4-5+ years without developing to many issues. Whereas most t16000m's start developing a problem in the twist axis after a year or two. Then again, the warthog has no twist axis at, and will rely more on pedals, adding to the cost of the setup even further. Personally though I would have to say rudder pedals are a very important piece of a good setup well worth possessing. You can also go all the way batshit crazy, which I consider myself to have done, with a full virpil\MFG setup. But truth is there really isn't much of anything if at all, I can do with my $1300 Virpil HOTAS that someone with a x56 or even a t16000m cannot do right along side me. There is no guarantee for instance that someone with warthog, or even virpil\VKB hotas will dominate those with lesser kit in a proverbial PVP match, to put it to a point.

I never uninstalled anything I just unplugged my CV1, and plugged the S in. No issue, and that was a pre-order S.

It's not going to be a year, five months if not earlier, I honestly expect the 3000 series to be launched near March or April.

Just mentioning, if you re-installed the Oculus software make sure that the "unknown sources" is enabled under settings->general. Without that rift won't work for anything not launched from within the oculus library.

Problem with touch controllers is you have to find them. Pick them up properly, do the thing, then put them back somewhere that allows for them to be picked up again and more likely than I would like I drop it during that last part and have to fish out from under me. Capto gloves or leap motion would promise to solve most of this, but a trackball is a lot cheaper, better supported and can be velcroed to a fixed position..

I have never played DCs without VR, and in my experience finding buttons isn't a big deal. Except for keyboard mappings those are impossible. The crucial thing is to make sure the buttons and setup itself doesn't move around much that way muscle memory will set in. I don't find it difficult to fly several planes becaude my landing gear flaps etc i keep mapped to the same buttons. What I don't have buttons for I use a trackball. Capto gloves sounds neat and all, but hardly anyone is getting them, and this they will hardly have any support and bug fixes

They are two forms of AA, but MSAA would be newer, and should be the more efficient, and less power hungry, but I for some reason get better perf with the SSAA setting. Might just be that, that is less taxing for VR than MSAA. Personally I just chalk it up to "VR being weird" or just me.

It does, but 40 is perhaps pushing it, it's about as low I would be comfortable to go with motion interpolation. For instance I couldn't reach that stable with the Pimax 5k and that is one of the main reasons it's shelved in favour of the Rift-S, best I got with that was 36 and that was honestly not good enough, seriously those 4 fps really matter. With the S as well, the new LCD panel is so much more responsive than the OLED of the CV1 80 in that feels like 120 would with the other, you would have to look hard for edge cases and panning motion to actually notice it. I run my S with a oculus traytool setting of 1.3x supersampling, with SSA ingame of 1.5, oddly enough this performs better than MSAA for me, it really shouldn't but it does.

Because in every aspect except for FOV it's beaten by the rift-S and to look nearly as good the S, it needs to supersample to nearly 2x. And that's before we even start on the bugs, it's lack of comfort and the fact that pimax as a company is an absolute joke that responds to criticism by making lofty and evading promises followed by absolute silence for months.