muzica9

something is very strange. with latest version 9.4.1 it is not loading if i have haze reduction on. and vr tech off. 9.4 was working just with haze. i have reverted back all the way to 8.4. nobody else is using with quest 3 with link cable or VD?

i did, same thing. first time, first activation is working. i can see the technique applied. but if restart game, stuck and freeze at loading screen bar.

Options.luaDCS_VREM.ini FILES asked

wich file exactly? there to many log file. this one is the biggest ReShade.log

sorry but i don't understand this part. i have no message. if launch in vr, before loading to main menu, when the blue loading progress bar reach 100% game freeze and become non responsive.

DCS_VREM_techniques.iniReShade.logReShade.log1 i think even with none selected do the same if box is ticked for Activate reshade Techniques btw , with v 8.1 load in to the menu, but there is no effect for reshade Techniques

how exactly to fix errors in red? i can not find button "initialize preprocessor variable" LE: nevermind, i found this << In order to get rid of the red technique : go into cockpit in 2D set the option "Activate reshade Techniques in VR" into "Reshade Techniques in VR displays" activate any tehcnique that is not red in the list you shared above => it should launch recompliation and fix all techniques in red unset the option "Activate reshade Techniques in VR" into "Reshade Techniques in VR displays" >> But now i have other problem. Game don't load in main menu in VR mode. Freze after 100% loading. Using Virtual desktop Quest 3. V9.4 and reshade 6.5.1 It is related to thick box Activate reshade Techniques. If it's on can not load. Need to go back to 2D load, untick box.

hi. work with quest 3 in cable link mode? from what i know, meta quest link app does't support hand tracking. i don't use virtual desktop.

than how do you access windows desktop without taking helmet off?

Yeah, I figured that out. The only remaining problem is the controller tracking/wrong position. If the headset or controller goes to sleep, everything goes to hell—the controller pointer ends up all over the place and i can not acces windows. This is driving me crazy, and I don’t know how to solve it. I’ve done multiple factory resets and tried pairing/unpairing the controllers, but the issue persists. It sounds like a firmware or software bug.

yes. everything configured like here https://github.com/mbucchia/Quad-Views-Foveated/wiki/Meta-Quest-Pro le: after unchecking and checking eye tracking and face tracking again, I managed to get it working. By the way, that option is now called 'Forward Tracking Data to PC' nothing specifically related to eye tracking anymore. Back to link cable... I’d also like to know how you guys get rid of the annoying on screen message when using the Link Cable: 'Controllers lost tracking,' which stays forever." Also, the controllers seem to lose tracking or have incorrect tracking most of the time. I’m not using them much, only to switch to the desktop and most of the time, I can't use them. Quest is on v72 firmware.

it's latest from meta store. photo is just reference from mbucchia gifhub

Any idea why I can't activate eye tracking in Virtual Desktop? I have eye and face tracking enabled, and eye tracking works with the Link Cable. I just don’t have the option available to check it. missing from the menu

So, confirmation that Quest Pro suffer from the same problem in VoiceAttack as I experienced with the Quest 3. Low signal notifications leading to commands not being executed. From what I understand, the problem comes from Meta's noise-canceling implementation, which Meta does not want to change or allow us to modify

Not quite. Quest Pro is €1100 new, while Quest 3 is €550 new. However, Quest 3 was very frustrating for me, so price is not an issue at the moment. I just want those functions to work so I can use them properly.

I used the Quest 3 with the Quad Views Foveated Rendering app in fixed mode, which did give a noticeable FPS boost. However, the sleep issue was still present, so that didn’t solve the problem. Is there any setting that needs to be added to settings.cfg to bypass the sensor/sleep or is just default.

Hi guys! I’m considering buying a Quest Pro after testing the Quest 3 for a few days, which left me disappointed. My main problems were: Sleep Mode Issue: If you took the headset off, it went to sleep, and most of the time DCS crashed. I had to go into the Oculus Debug Tool every time to enable the "Bypass Sensor" option. If I forgot to check it, my DCS session was gone. Microphone Quality: The microphone was very bad. I use VoiceAttack for commands, but I couldn’t get it to work properly with the headset. Even after hours of voice training, it failed to recognize commands, and I kept getting a constant low signal/red notification. I’d like to know if these two issues also occur with the Quest Pro so I can avoid a potential return and save time. PS: I plan to use the Quest Pro exclusively via Link Cable, as VR Desktop is not an option for me.

map don't load and dcs crash if i modify atmosphere file. any suggestions? null Le: nevermind. it is working. but loading process took a while. much more than usual.

i don't do room setup. just right click steam vr in tray>> click recenter. I use HP G2. With Pimax Crystal had to do same thing+ room setup. others with Aero do the same https://gitlab.com/NobiWan/xrnecksafer/-/issues/7#note_1327625967 PS: do the recenter in the position you play, and don't move after to another position.

In the end, i have returned the product. Pimax Crystal at this moment is junk. Beside image quality, everything is wrong with this product. And PImax support is non-existent. My advice, if you still wish to try it: Don't buy this directly from Pimax! Buy only from other shops with good return policy!

only way to make it work decent(not perfect) is to do a recenter in steam VR app before using dcs and XRNeckSafer. everytime!! yes in steam vr even if you use DCS with open XR. MT build use native open XR which XRNeckSafer don't support. Developer did not update this for more than 4 months. ST build use open composite open XR.

Well, different helmet(8kx vs crystal). for example crystal don't get hot. G2 does.

yes, very uncomfortable. after 3 hours my nose was hurting me. in G2 i can stand 8 hours or more without any discomfort. Basically, bottom plastic frame of the lens sit on my nose, and my eyebrowse touch the top part of lens But now i understand the gimmick of the Pimax. They promised big FOV and they sacrificed everything for FOV. The make you sit closer to lenses to have big FOV. This means that you have less foam/bumper around your face. If they or you change the face gasket with something more comfortable, you narrow your FOV. Pimax gimmick.

strange. something is wrong in you sistem. 7800x3d should push more. i have lower cpu, same gpu and i get better results with even higher settings. G2 mostly 90 fps. Crystal 50-60 fps at native resolution and 2x MSAA. 75-80 fps with 3500x4150. But Flying helo, other story. Under 50 fps

native resolution you get 90 fps? without downscale?