dogbite

I think they all have to finish a Pimax checklist and questions from them and then they can do Q/A in the forum and release videos. They also said they would release the names of the testers when everybody confirmed they had received them and they haven't done that yet.

Great price. I figure with the Valve 2.0 base stations shipping with the Vive Pro now, I should be fine. I really would be surprised to see my Pimax before Sept/Oct. That's ok though, because I still enjoy my Rift and about 6000 people are going to debug the heck out of the Pimax before I get mine.

I was considering picking up a base station as well, but I'm so far down the list I think the base station v2 I ordered will be ready by the time they ship hmd

They have indicated the testers would be allowed to report their findings publicly after they have all filed their reports to Pimax. Many if not all apparently have VR channels (they call them influencers)and will supposedly be doing video reviews after that point. Should know very soon. Pimax seems confident in M1 which is supported by the fact they are sending 10 units out for independent scrutiny. One know tester Sweviver has said he is looking forward to running DCS up the flagpole. We should hear more in a couple of weeks. So close now. The intent is still to start backer shipment this month.

If remarks don't do it for you, feel free to ignore them. Like i said the information will come by the time you can buy one. No point in continually repeating the same point or responding at all for that matter. Just wait like the rest of us. Not that you have a choice.

The tester group is being assembled by Pimax to update the backers. Most of us, individually, given a few days with it, could answer the questions backers need before the shipping survey. So we don't need a lot of testers. Just ones with VR experience. The criteria for tester candidates is sufficient to that task. There will be a Q/A session with testers in the forum that will fill in the gaps. We have a timeline saying shipping in Q2-within 12 weeks. We don't need to bog down in testers, unless the process proves inadequate to the task. We will know soon enough. I suspect the tester list will be posted this week.

So you're "waiting for "(a) backer using in DCS" and complaining all 7000 aren't playing DCS so it it's not "enough"? I can assure you at least one of those backers will post here what we have found when our hmds are delivered. Indeed there are many on the Pimax 8K threads who play DCS. Not all 7000 but since you said "a", I think we got you covered. If by the time you can actually buy one, you don't have all the information you need, I would be quite surprised.

Some of the 7000 backers will surely offer up enough anecdotal feedback. There will be plenty written on this and plenty of comparisons long before it becomes a retail product.

I probably picked it up in a corny movie or something, but I'm glad you decoded the slang.

Text has already been remarked on in the prototype demos. It will be a little cleaner but I suspect the really small font stuff to still be difficult. Don't expect to read some of the really fine labels in say the Huey and SA342, and such. Zoom will still be a wanted tool. Remember these cockpits weren't designed for VR. Where the Pimax will likely shine is SITAW and possibly a little better target identifying at greater distance. I wouldn't expect miracles unless an effort is made to revamp some of the cockpits for VR. The SITAW should be crazy good though.

I don't know why you bring up OH. I already said I don't run it unless I want to run something from it. It's a storefront is all. just like Steam isn't Steam VR. Speaking of Steam VR which runs OpenVR and which Oculus also supports-when you run an OpenVR title in the Rift you can toggle ASW. This is because it's part of Oculus's software. ASW is always on by default unless you tell it otherwise. I haven't read anything suggesting DCS has a specific implementation of ASW and would certainly be interested in any link you could offer regarding that. It certainly isn't necessary for them to do so, but if true, I see no advantage in it, as DCS artifacts as badly as anything I have seem when it's running.

ASW isn't "in DCS" it's part of the Oculus runtime that starts when DCS starts up the hmd in VR mode. Unless I misread you there. I too, don't run OH unless I want it for something.

For reference I used the NP keys today and they were functioning for ASW. Just a thought, is your numlock on?

I prefer ASW off for both NTTR and Caucasus as there are too many artifacts. Normandy is less of an issue, so I leave it on there. Never seen any edge bleed in my Rift. Don't get double vision or eye strain either, but I don't get VR or motion sickness in RL either so perhaps that's why I suffer none of these maladies.

What makes you think I said otherwise?

Another demanding title through the lens on v5

My bad. I should have checked your link and I would have seen they created a new item since I was a customer. Very interesting and not at all surprising considering the previous solution could be hit or miss. Thanks for bringing me up to date.

I don't see ED needing to do anything proprietary for Pimax since they have joined the Khronos initiative and support OpenVR at this time but I suppose one would have to ask Wags what "we are in touch with Pimax regarding their 8K system and how we can best cooperate for an amazing DCS VR experience" means in regards to that rule.

Not sure what it means beyond whatever solutions come to advancing how things work will at least have a standard where all parties are on the same page. If something like 2 GPUs, one for each eye in VR can be developed in OpenXR and be brand agnostic it might make coding for it more attractive. I'm thinking other things like foveated rendering will come before multi gpu especially when cost of admission is a factor to building a user base.

There can be caveats to both VRLensLab and Ben Franklin frames. VRLL lenses can cause barreling especially in a strong prescription (I had to return mine) but if they will still offer a refund they may be worth trying. They do add quite noticeable weight to the hmd. BF frames can be hard to find that support thicker (again strong prescription) lenses and depending on your head size one could have the fitting issues with the arms. I can fit my glasses in the Rift and then put it on (67 IPD) but when removing it the glasses come with it. Always worried about scratching the fresnels. I settled on contact lenses. I would have done Lasik but it would have ruined my reading unaided.

That's how I took it and why I pointed out he could re-center with NP5. Although I should also have pointed out that his lament was that he was too close to the panel and leaning back before centering would only have put him closer. leaning forward first would be the appropriate method or he could use the camera controls Buckeye pointed out.

VRSLI is only supported partially in DX11 hence the direct support needed in game engines such as Unreal Engine and Unity. Add to that Nvidia only and you cut in half what is already a small group of muti-gpu users. The hmd drivers would also need to support it. AMD's Liquid VR offers the same quandary of being proprietary. I'm thinking we are quite a ways off from seeing either of these as viable. I have a feeling that meaningful advances made in how VR hardware and software work together will need to be resolved in OpenXR now that everyone who matters has signed on from Oculus and Valve to recently Microsoft and Pimax. As I understand it Vulkan is also part of the initiative. https://www.khronos.org/openxr

Have you tried re-centering your headset once in the game? Numpad 5 or you can bind it to a button on your stick.

FWIW I rolled back from 388.71. I was having lighting issues in Elite Dangerous which got solved as far as I can tell. I then went back to tweaking DCS 2.5 and immediately noticed it was smoother at the setting I left off at.