NastyFruit

Yeah, I am also struggling with the idea of my bonus points just disappearing. I am actually quite surprised that no conversion is being done of existing points, I hope ED reviews and changes this. Like mentioned before, I would even be ok with a 1/2 value conversion, but to just say cheers to your bonus points feels like I am being cheated. Just my 2c

Just ordered mine as well, and also ordered the VRCover sponge stuff that apparently fixes the comfort / light leak. Very excited for them to arrive.

Hi, I appears the door gunners in the Huey are broken. They cannot fire at anything. Even when getting into the Huey side guns (M60 or mini-gun) when you press fire, it fires one round in the M60 or the barrel just spins a bit on the mini-gun. Can someone please confirm? Kind regards

Holy crap! Were you able to enable the fixed foviated rendering as well? I also have a 2080ti (But only a rift CV1, did not realize the Pimax would be THAT much harder to drive.) Hoping DCS can get some more VR optimizations soon!

Anyone tried brainwarp in DCS yet? I heard MRTV say its now available in the BETA PiTool or something like that. Also fixed foviated rendering. I do not have a pimax, but am very interested if the brainwarp stuff works as well / better than the Rift's ASW?

Yeah, I understand its not really IPD, even though it sounds like some are recommending you set it to your real IPD. What I meant was, as I understand it, if you tick the box, and you change the values, stuff will become larger and smaller, but what value does it use when nothing is ticked. For instance, if I tick it and set 80, and everything becomes smaller (I am guessing here) and then I set it to 50, and everything is bigger, what value would make it the same as not ticking it. The reason for my question is, it sounds like its quite difficult to "See" the difference, so it would be good to have a specific base value that I have been using all along (By not ticking it) to compare to whilst testing. Will give it a go soon, sounds promising from some of the reports I have read :) Cheers

That part of your own answer implies DCS uses some value as a default if one does not tick the box and enter something else. If you look at my original question, I was merely asking if someone knows what the default value was.

I am not sure I follow you 100%. Lets say I have two people, A and B Say A has a real worl IPD of 70mm, and B has a real worl IPD of 55mm If I uncheck the box in DCS (Thus letting it use its default value), how does it default to 1:1 for both people, as dcs does not know their IPD's?

If you leave the IPD option unchecked in DCS, what distance/value is it actually using as default?

Great, thanks!

Yeah, if you have any mods etc, you cannot join servers that require a pure client. Not sure if this will also trigger an IC fail, prohibiting you from joining pure servers. I will only be home later tonight, I suspect someone will be able to test soon. Kind regards

Not sure if I can ask here, but will it still pass multiplayer IC with the fix? Thanks

Hi, This one is a bit more complicated to recreate, please let me know if anything is unclear or if you need more information. And again, apologies if this is already reported / intended behavior. Summary: When you have GBUs in Auto(CCRP) mode, and you then select a LMAV, and have it lock to a laser spot (Not fire it, just using it as a spot finder), then re-cage it, and go to the gbu again, the gbu will display a "DUD" indicator above Auto on the hud. Changing the gbu mode to CCIP and then back to Auto again, fixes it. It appears once the gbu shows "DUD", the mav will as well. Only after changing the gbu's mode to CCIP and back to auto, will the mav not display "DUD" any more. I am attaching a track, it was made in VR, hope it works. In case, I will try to list the steps below as well: 1: Set GBU / MAV laser codes 2: Set GBU to Auto, and fuses to nose / inst 3: Select MAV, uncage to find laser spot 4: Once locked, re-cage MAV 5: Select GBU (Usually it shows DUD above Auto now on the hud, and will not function. 6: Set GBU to CCIP, then back to Auto. (Dud indicator should now be gone and weapon functions again. 7: If dud did not present, drop the gbu on something, and just repeat steps 3 - 5 again. Please let me know if you need more information. Kind regards CCRP Auto mode DUD when LMAV locked.trk

Wow, someone got up on the wrong side of the bed. Seeing as there is no way for us to know if it will have higher system requirements, the only stupid thing here is asking that question and expecting a real answer.

Just to confirm, I have the JetSeat, use it with SSA, and have a oculus rift as well, all works perfectly together. Also the Seat + VR + Wheel + Shifter is fine. So no worries about what you plug in with it. (All of this assumes you are using the seat in USB mode of course, I have no idea how sound mode works with the other things, but USB mode is the way to go for dcs) Cheers

As stated in other thread, just a bump, to perhaps entice a response from the new community manager, if possible ;) Thanks!

Yeah, there are quite a few threads on it, but maybe the new community manager can comment and set our hearts at ease whether a CH-53 will see the light of day, and if a rough projected time frame is 1 or 2 or 3 or 4 or 5 years, or whatever it might be, of course understanding its not a commitment and all subject to change. Phew, quite a mouth full, but this is one of the modules I am hoping for the most! Cheers Edit: Will bump the other, larger thread as well, as I think if we do get a response, it will be better there.

Could not resist, placed order for 5k+ with the hand tracking. I know at some point, people were taking about having your hands tracked and interacting with the cockpit switches with your "finger". Are there any ways of making that work currently? I am hoping as DCS have kind of declared they will support pimax, that it will eventually work. Same for wrainwarp.

Yeah, I have been wishing for a 53 for soooo long. Please RAZBAM, make it happen :) Will pre-purchase it, I promise! Hehe

Hmm, I did a quick test, I don't have the same resultion 2d, I have 2560x1080. With these settings (Going to try to attach. Trying again, not sure if I am allowed to attach pictures), on Caucus Huey Free Flight (Flying around the airbase there) I get between 110 - 150 fps, depending on where I look. With a fast mover higher up, it might be higher fps, not sure. Edit* Tested with F/A-18 as well now, free flight, 120 - 180fps with settings as below. The use of msaa 4X making it unplayable, is that in VR or 2D? For VR I use the same settings, just the MSAA X 2, with a PD of 1.5 Cheers

Thank, yeah, seems the SSAA might not be the best idea. Although, if I just run PD, its for more jagged teeth that a saw! So will probably stick to 1.5PD and MSAA 2x. Cthulhus, what res are you running at?

Found a thread on it. Sounds like it (SSAA) should not be used with VR. Weird that my session with it and msaa on was so smooth. Will test more later. Like if someone is interested: https://forums.eagle.ru/showthread.php?t=209183 Cheers

Tweaked some settings last night, very pleasantly surprised with the results. Set super sampling to 1.5, everything else max except shadows flat only, draw distance extreme, MSAA 2x, SSAA 1.5x Got solid and smooth 45fps, with frequent jumps up to 90 when not near big cities. What is SSAA in dcs? I had not seen the setting before. Does someone have a link to some discussion around it? (Preferably discussion in the context of DCS) So yeah, 2080ti seems like a real beast for VR.

Very limited testing, but with 1080ti on Nevada and huey quick action free flight mission, when looking at the city I was struggling to keep 45fps, usually with 90 - 95% ish gpu usage, now with 2080ti solid 45fps with 55 - 60% gpu usage. When not looking at the city, getting nice 90fps now. (All same settings, 1.3pd, MSAA X 2, other things high etc.) Feels much better now, also with the F/A-18 Could probably lift the PD now, but does not make the visuals much better in the rift. Need higher res HMD. All in all, if feels like the boost has helped my VR perf quite a bit.

Unfortunately, I did not realize it only has one HDMI and the rest are all DP. (And the virtual link usb-c) So I can connect only my monitor, or the HMD, and the one does not work without the other. Interestingly, I have a usb-c to hdmi that I use with my laptop. When I plug that into the usb-c port on the 2080 ti, the screen shows nothing, but if I plug the HMD's HDMI into the adapter, it shows the image, but it has a bunch of weird pink lines all over the image. I should be able to get a displayport cable to connect my screen tomorrow, freeing the hdmi up for the rift. I suck at waiting though :(