nwagtmustang

Smart smoothing and foveated rendering.

I did have a g2. Stipped uisng because I did not like wmr. Then used trackir and tried tobii eye tracker 5. I actually did a clean I stall of windows to remove ant potential old drivers/files conflicting with pimax. Dcs has no mods on a fresh I stall of windows. Latest drivers for gpu. I did tey bypassing the hub on the headset. What I did was disabled a setting in limax that was conflicting with quadviews. Flickering is gone. However, with all settings maxed out in dcs, in the Caucasus map I'm getting 90fps and gpu usage is about 50 percent. In the marianas i am getti g 45 to 50 fps and gpu is still only at 50 percent usage. I still get freezes sometimes. They are short lived and goes away after a second or 2. I could turn down some settings but I have questions. If my gpu is only being used at 50 to 60 percent, why am I getting freezes? Why is my gpu at only 50 percent? I have watched so many videos and read so many forums that for dcs and msfs vr with pimax, a 4090 is the best. I feel maybe I purchased the 4090 when I did not need to. Kind of bummed about that. I am very happy with the pimax. Only had it for a day, so I am still learning and tinkering. I want to max it out to get the best performance and graphic quality as possible.

I received my crystal yesterday. I am having an issue with flickering. Almost like random flashes of lightning. Only in vr. Do not have this problem with msfs 2020. I'm sure it's a setting issue. I am not sure where to go from here. Firmware on headset is updated. 12900 k and a 4090 gpu. 64 gb of mem. I tried different settings in pimax software. Different settings in dcs. Different settings in openxr in the sim. Any ideas?

I figured it out. I was so concentrated on trying to calibrate the eye tracking and I kept unplugging and plugging usb cable in. I had the pimax software running but was concentrating on the usb not being recognized. I finally decided tk try the hub that came with the crystal, even though I tried it before. I un checked eye tracking and heard a sound Lome usb is being disconnected. Light bulb went off. I checked it again, then went into device manager and there was the eye chip. For some reason the eye chip is not recognized unless you check the eye tracking. I put on the headset. Had me position it correctly. The looked at the dots and it was all fine. Played msfs 2020 and dcs for the past 2 hours. No problems. For some reason I could only use their hub to get it to initialize. Then plugged the cables into my usb in motherboard and no issues. I wish pimax would give more instructions and tips. I was so focused on usb not being recognized, not knowing the eye tracking box needs to be activated. Hope this helps anyone else with this problem

I tried with ipd ticked and un ticked. Now I'm getting unrecognized usb device. Think it's the eye chip. I tried the supplied usb hub, my otjer powered usb hub and tried directly plugged into the pc. Multiple problems. Firmware is upto date. Windows is updated. I don't know where to go from here.

Received my crystal yesterday. The visuals are amazing. However I am struggling with some basic setup issues. Eye tracking calibration not working. I follow the dots with eyes. At the end say my eye movement does not match graphic movement. I reseated the lenses. Un-installed and reinstalled the pimax software. Same problem. I did a fresh I stall of windows. Dcs is currently downloading. Still can not calibrate eye tracking. I then Uninstaller and deleted all remaining pimax folders. Start the client. I get a message in headset to move my headset down. I move it all around and nothing happens. Ctrl all delete the program. Open pimax up again and I don't get the position message. Eye calibration still does not work. Delete the program again. On first startup get the position message, can't get past it. Ctrl all delete again. Open software. Calibration fails. I have rinsed and repeated for the past hour or so. I would of posted on pimax forums, but to sign up they give you 20 images and have to get everyone right. One wrong, and start over. I'm getting frustrated. The visuals are fantastic. I did put a ticket in with pimax. Anyone here have any ideas? Oh yeah one more thing. In dcs I am getting flickering which I did not get with my g2 or rifts s. Running 13900k and a 4090. Thank you all.

I love my reverb g2, hate wmr. Bought quest 3 because windows will kill off wmr. I am running 13900k, 7900 xtx and 64 gb mem. On the g2, everything looks great. On the quest, in the cockpit is great. However far off objects are pixilated. For instance the super carrier. When I do a case 1 recovery in the hornet, the closer I get to the carrier, the worse it looks. When I do a fly by, the island, masts and the rest of the carrier have lot of jagged lines. On the g2, it was crystal clear. I am using a quality usb 3 cable. I have played with settings, watched YouTube videos. However all the YouTube videos are with Nvidia gpus. I always had Nvidia, but with the recent price hikes above msrp and or out of stock, I went with amd. Never had a problem with the 7900xtx in dcs world or msfs 2020. Very smooth. Vr and non vr mode I am willing to upgrade to a 4090 as a last resort. However, since the g2 performed great with the 7900xtx, I am hoping there is something I'm missing with the quest. Never checked fps but it feels smooth. When doing a bfm with mig 29, I can the see the jet nicely. It might be pixilated but can't tell. Maybe because it's a much smaller object than a carrier. In bfm with the 29, when I get low, the terrain looks beautiful I have not tried any missions with ground targets. Can't comment on that. Just bought the quest 3 yesterday so I'm learning. Any ideas, pointers or tips?

I am struggling with acls. I get to the point when 6 miles out I get the correct call out from carrier. At 5 miles I push couple on auto pilot. The plane starts a gradual ascent, I do not get p/r symbology. Just distance to carrier lower right of hud. If I take control then the cpl p r flashes. Like it was deactivated. However it was not activated because the plane kept getting higher. I was on speed and had auto throttle engaged at Round 145 knots. Once I take control and center up the needles I try again and it won't engage. I hand fly it in. Other times I get p and r on hud but when I couple the autopilot it still won't engage. I have watched several you tube videos and I'm doing what they are doing, but I must be doing something wrong cause it won't work for me. My fuel state is about 40 percent full. I make small corrections. I even wait till I'm about 3 miles from carrier and still the acls autopilot will not engage. I wish there more indepth videos explaining the process and why and what to do if it won't work and how much tolerance you can be off for it to still work.

maybe not update old missions, but maybe put the mission wags used for acls on the download site. I created a mission exactly as wags did, andI having great difficulty. I set my plane out about 60 miles. I get message to descend to 5000 feet. and wait and wait and wait. I am at 3 miles to the carrier and still waiting. It would be nice to have a longer more indepth video, because it is not working for me.

I reported this issue a couple of weeks ago but I got one response and then nothing. I did more troubleshooting. So the issue I am having is if Im using the f18 with super carrier I can get the lso view with the missions, but not catapault view. If I use the hornet in instant action I can get the catapault views but no lso view. With the f14 I can not get either view no matter what mission or instant action I do. I did a clean windows install and then installed dcs world to troubleshoot. This only happend with 2.7 version. 2.5 worked fine. I am attaching 2 tracks with f18. Cant attach f14 track due to file size limitation. I really hope I can get a response from eagle dynamics. f18 case 1 recovery instant action.trk f18 case 1 recover mission.trk

in case anyone cares, narrowed it down a little more. any instant action missions, lso view does not work. The prescripted missions with f18 and any missions I create with f18, lso view works. Any mission or instant action with f14, lso view does not work.

Ok. So if i esit a missiin that us supplied by the module i can not view lso. But if i do a mission that is not modifies then it works.

I tried that. It does nothing. I tried default commanda, custom and back to default. Nothing.

Been a while since i used dcs. Updated to latest build. I can not enter lso view. I tried the f14 and f18. I reamapped the keys to see if that works. It does not. I then reset keyboard to defaults. Still does not work. I tried going to ship view first. I can only use the catapault views. Can not get into lso view.

Hello all, I noticed the icls is not working on the hornet after the last January update. I created a simple mission wanting to try landing in various weather conditions. I set the carrier to broadcast icls and tacan. The tacan works. So I then went into the f18 missions and performed a case 1 recovery. turned on icls and input channel 11. Put in the right channel for tacan. went to hsi and highlighted tacan and ils boxes. Again tacan works, but not the icls. I do not know if there is a bug with the latest update, or if there is an added step that I am missing. ICLS worked fine until the Janaury update. Anyone else have this problem or tell me if it is user error on my end???