Search Results for 'Hard Reset'

[proximiy]

Occasionally while playing in desktop mode, my mouse would stop working. Unplug and replug does not fix the issue. When this happened, only a hard pc reset will fix it. This will happen almost 100% of the time when playing Halo Infinite. Sometimes 5 minutes into the game, sometimes 40 minutes.

This does not happen if I play on a monitor.

Wondering if anyone have the same issue and any workarounds/fixes available.

Specs:
Ryzen 3600x
gtx 3080
hp reverb g2
evga x17 mouse (also logitech g602 mouse. Tried both. Both have same issue.)
Halo Infinite windows store version
I always pause Vorpx watcher when using desktop mode.

Thanks

[Ralf]

@ yonkiman:

Reset the profile to default, then use the ‘Resolution Quality’ option on the DirectVR page of the vorpX menu to adjust the resolution. The highest value there will roughly yield 2400p.

Don’t touch any of the zoom etc. settings. That is not necessary at all, the profile works perfectly well without tinkering. You just make it harder for yourself otherwise. All you need to do is setting the resolution quality option.

Whenever that is possible for a game, vorpX displays an according hint in the to/left corner of the game window. Doing it that way is always preferable if the feature is available.

[Demuse]

A few random things I’ve found while dialing in all the settings to play using a gamepad and DirectVR with a Reverb G2, in case any of this helps to reduce the set-up time for others:

1. In game settings, turn off aim assist to eliminate bad jitters when in combat.

2. The HUD needs to be set to 100% or there are icons floating everywhere not attached to the in-game objects. Then the HUD is mostly out of my FOV so I have to use edge-peek to check the mini-map, etc.

3. In-game controller settings I reduce vertical sensitivity to minimum (=1), so I can turn with the right-stick and use my head to look up and down. But many times the game takes control of the camera to point your eyes down to look at some object of interest, and leaves you looking down at an angle, so you have to be able to pan your view back to horizontal quite often. It would be nice to have a button to “reset view to horizon”.

4. It’s hard to use hacking skills, as I have to use edge-peek to see the HUD, then when I move my head to read the HUD I’m no longer aiming at the in-game device I’m trying to hack. It would be really useful if there was an option to toggle off headset aiming while using edge peek, so I could move my head to look around at my HUD and control the aim reticle only with the controller joystick.

5. With RTX3080 I’m using “great” resolution, and I found I could turn the graphics settings mostly up to high, and with ray-tracing turned on, without much change to framerate. But ray-traced lighting caused the windshield of my car to sometimes become opaque so I turned off lighting but kept reflections and shadows.

6. I have DLSS set to “auto” so I’m not sure if it’s doing anything, or helping?

7. In vorpX settings, my “cap framerate” has to be turned on and set to 66 or 75%. If it’s turned off, or set any lower, then everything gets very jumpy. Perhaps related to that, in-game video settings I have monitor vsync set to 60 Hz. This combination runs pretty smooth, but if I change either of those settings it’s immediately unplayable.

8. Somethings seems broken in the inventory screens? I think when you hover over a new weapon, it’s supposed to pop up stats, and compare with your currently equipped weapon? None of that happens for me. Once when I first open my inventory, when I hover over a weapon, 2 text boxes pop up, but one box is only visible to my left eye, and the other to my right eye — I can close one eye at a time to try to read them. But if I move the cursor then the pop-up boxes disappear, and never reappear for that or any other weapon in my inventory. <shrug>

[steph12]

i was wrong vorpx supports the game in Z3D since 21.3.0 update

“F1 2021: Z3D/FullVR, DirectVR: auto settings, tracking”

try reseting the profile to default settings. delete the profile you downloaded from the cloud.
game should work.

i never played that game yet, so i cant help much, maybe someone else can.
plus i dont have the same hardware as you (valve index)

[mr_spongeworthy]

RJK_ wrote:

Just a quick note on the UGRIDS setting. The game crashed when saving with uGridsToLoad=7 and loading a savegame after resetting uGridsToLoad to 5. A value of 6 seems to work though.

Yes, that’s a know issue with UGRIDS; you can find a fix through console if you really want to, it’s not too hard. uGrids must be odd numbers, 5 works, 7 works, but 6 is actually the same as 5, that’s why you can have uGrids=6 and still load those saves if you set it back to 5. IIRC anyway. Bethesda games require so much tweaking to really get them right that it’s hard to keep track! uGrids can also cause other random problems, so if you aren’t used to that then probably don’t set it to anything other than the base 5.

Are you using G3D?

[luka2099]

Hard Reset
bioshock infinite
titanfall 2
Necromunda hired gun
Vermintide 2
Resident evil 2,3,5,6 with first person mod , 7 and 8
Legendary
Prey 2006 and Pray 2017
Halo Master Colection
Doom 2016
QUake 4
Outlast 2
Duke Nuke Forever
Earth From another Sun
Metro series
Far Cray Primal
Space Hulk Death Wing
Dream Cycle
A sTory about my Unlce
and more more moooooore

[mr_spongeworthy]

I have updated to a 3080 Ti (thanks to Micro Center actually selling GPUs occasionally at MSRP on a walk-in only basis, 1 per household. No way was I going to give a scalper even a cent, so I waited.)

I am 95% of the way to having Cyberpunk working at 4K, “Performance Mode” DLSS, Ultra Ray Tracing!, 72Hz 36fps. It all works and looks amazing. However, like many modern Z3D games, I may end up playing it in cinema mode due to the increased clarity; spreading even 3840×2160 pixels across my HMD in full VR mode just isn’t quite enough for excellent sharpness. It’s close, but not quite there.

Anyway, I have issues with the GUI. I did a full reset of the profile before I tried getting it setup correctly, so I started with a clean vorpX slate, but even at that, in VR mode any Xbox controller shortcut shown on the screen flickers several times a second between the Xbox and Keyboard shortcut for that action. This makes it very hard to see what controller input is expected for an action. Also, dialog subtitles and a variety of other text does not match up with the field which is supposed to be behind it, making it hard to read. I’ve played with a number of settings but haven’t found a solution to either of these issues.

[Picdelag]

It’s fixed Ralf!

One of this step fixed it :
-Resetting the default settings. (I don’t see why it could have gone wrong… but maybe?)
-Turning on ‘Hardware Accelerated GPU Scheduling”. Was disabled before.

I’m keeping the motion reprojection forced with the toolkit and everything seems fine now! 45fps with not drop.

Enabling FluidSync did not kick the reprojection in if i’m not forcing it…
Is it a bug/an issue?

[Ralf]

@ Picdeleg

Just checked the game for you. No problem here to keep up stable 90fps for the headset thread even if everything is set so high that the game itself only runs with 20fps. Please try the following: 1. Reset the game’s profile to default, 2. Make sure the game runs in DX11 mode (normally vorpX takes care of that). 3. Try to enable/disable ‘Hardware Accelerated GPU Scheduling’ in the Windows options. Didn’t make a difference for me, but worth a shot. Usually I have it enabled these days, but whether or not that is better may be system dependent. 4. If you happen to have the WMR dev tools installed, also check whether you maybe accidentally forced reprojection, which would make WMR cap itself to 45fps.

@ senoctar

I’m already testing a solution for the Ansel issue. There are two potential ways to deal with it. The easy one would be to add the Ansel dll to the list of overlays vorpX tries to block. The other one is initializing the headset later. That has far reaching consequences in several ways though, so it will need rigorous testing before I can decide. Ideally it will be the latter in the end, but should testing show that breaks other things, it will be the Ansel block.

[RaddyB]

Unfortunately, I have tried that a few times now. If I reset everything and follow the on screen instructions, max out the fov and perform a dvr scan, it is still zoomed in just as it did when I initially tried it. Oh well, I’ll try again at some point, could be a hardware thing, who knows. Appreciate the help!

[tauronux]

I recommend turning off Steam cloud for the game and try to set the resolution in the .cfg file located in %LOCALAPPDATA%\4A Games\Metro Last Light\<user-id>\user.cfg

But i also found this on the pcgamingwiki.com:

Resolution Issues
Some users have encountered issues such as not being able to set their native resolution; the game resetting their chosen resolution to a lower one; or the game’s maximum available resolution being lower than their monitor’s native resolution.[3] Such cases may be caused by the presence of multiple monitors attached to the computer, or attempting to play the game on an attached TV where larger resolutions may not be available. Possible solutions include unplugging any extra monitors[4] or setting the multi-monitor display mode in Windows to “Computer Only”.

Some other threads about this problem:

https://forums.tomshardware.com/threads/metro-2033-redux-resolution-issue.3451297/

https://steamcommunity.com/app/287390/discussions/0/1742232339925283291/

Good luck!

[Ralf]

You can ignore that. The factory reset does a bunch of things, the message probably just means that there was nothing to reset at some point during the procedure. The really important things like resetting all profiles and other settings almost certainly where done correctly.

The underlying issue with WMR is what I wrote above: WMR headsets just make it harder for vorpX to maintain the full headset frame rate than other headsets. if FluidSync alone does not help to stabilize things in a particular game, you can also set the ‘Headset Sync’ option to ‘Safe’ (costs FPS but frees up GPU resources) or further reduce graphics details. There isn’t really anything that can be done.

BTW: The fluctuating headset framerate most of the time isn’t really a problem. If things feel right, all is well. If you used an an external VR FPS counter, use the vorpX counter instead (ALT+F). The more important framerate is the game framerate (the first one). An external VR FPS counter only measures the headset framerate (the second one you see with the vorpX FPS counter).

[mhombach]

I installed and used VorpX for Cyberpunk 2077.
After trying around a little bit, I went to reset the config (by using the VorpX menu) so my Cyberpunk 2077 config would be the same as before using VorpX. But something is not alright. I get a hard fps-lock to 60, even if I increase the fps-lock to 144 or even disabling it completely. Before using VorpX I had around 70-80 fps. Now it’s never going to 61, it sticks exactly at 60 all time.

Can you tell me, which part of the config might not have been reset correctly or where this is coming from?
If I set the ingame fps-cap to 30, this works. But since even disabling things like RTX or quality does not change my fps to go above 60 now, some config must be invalid/corrupted. Vsync is disabled of course.
Any help is much appreciated.

[Sairai]

Ralf wrote:

I have tested both the Steam and the GoG version for several hours now and am confident to say that there are no crash conditions in conjunction with using vorpX. The only vorpX related crash condition was a conflict on AMD Radeon cards in some nVidia code the game uses, which apparently does something else on AMD GPUs than it does on nVidia GPUs. That has been fixed with yesterday’s update.

The best advice I can give you is resetting the profile to default in the vorpX config app, using the latest GPU drivers, not cranking everything up to max in the game’s graphics options and checking for potential conflicts with interfering background apps on your PC that also hook into games.

Just in case: if you happen to overclock anything in your PC, try with default clock rates.

Hi guys,

I definitely have a VorpX related crash condition since the update to 21.1.1.
My Cyberpunk profile includes the following:
– Cinema Mode, curved with ambient background, no AA
– Custom resolution ingame wqhd 2516 x 1440, ingame settings all maxed out
– No 3D, Crystal clear: normal
– Removed hud scaling from default profile: Set scaling to 1:1
– VorpX may not change any game settings (didn’t work any better with this option enabled and I prefer having full control on my own)

My hardware scenario:
– 3 monitors with 1920 x 1200 resolution (thus needed to use custom resolution for wqhd support)
– Valve Index HMD
– RTX 3090 (support for maximum raytracing and dlss on)
– i7 5820k 6x 3,8Ghz HT 12 Threads
– GPU no OC
– CPU stable OC ~8% (for years already)

Now when I launch Cyberpunk it seems like I have a 30% chance that the game does not crash after displaying the CD Project Red Logo. I wasn’t able to find the root cause so far. Tried different vorpX settings, different hooking and stuff but to be honest, I just want to play and don’t want to waste my time with troubleshooting atm.

If it does not crash right before start screen, everything runs perfectly fine and I can play for hours without any issues.
The game never crashes when I reset the profile to default. I am able to setup all my preferences in this session and can also play without any issues but of course this is very annoying in front of every gaming session because after closing and restarting the game, the same issue reappears.

It most likely has something to do with my custom resolution or the VorpX PoV changes. The whole part with ingame resolution (VorpX resolution settings) was changed with this update and maybe there is some sort of bug with custom resolutions? All I know is that this issue immediately appeared right after updating to 21.1.1 and never appeared before.

The game also never crashes during startup when I am running it without VorpX.
Hope this information can help you identifying the issue.

Kind regards,
Sairai

[CZiNTrPT]

Hi there, just tried playing this game.

Is it normal that I can’t use the controllers and/or open vorpx menus? Has that something to do with dx12?

Also there seems to be graphical glitches, it looks kind of like bad vsync. were two slightly different frames are displayed at the same time. sorry, if this is a confusing describtion, will try to think about how to describe it better.

also in controller setup / oculus touch settings there is a typo. it says right stick axis **X** 2 times instead of X and Y. I saw this while playing titanfall 2, but I assume, it’s the same in every game.

another bug with titanfall, when you disable oculus touch controllers, the gamepad stops working as well. even after the update & a full firmware reset today.

sorry, for throwing everything in here together. I didn’t know I had so much to write before starting.

thanks for your hard work!