Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
if your thumbsticks dont work propely in skyrim it could be a problem whit the game controls maping in skyrim VR
Thanks a lot man, you saved my stuttering ass
:D
im soo happy to ear that! all thanks to Julian from vive support!
Mr. (or Mrs.?) Nameless Soul is officially my hero of the day.
awwwww <3 that warms my hearth, a pleasure to help.
julian from vive support is also our hero, she gave me the info
Still having events in vrcompositor.txt trying to load old drivers like null, driver4vr, vridge etc.
So far I can not do any room setup anymore...
It thought Julian was male and Julianne was female. LOL
In my case there have been leftovers from 3rd party programs. Did not find that useful information on my own so I think it can maybe help someone other.
thanks for the extra info, im gonna add it
Short version for people who's still suffering this issue:
Make a clean reinstall of your nvidia graphic drivers.
If you're on AMD side, prolly this error would be solved with Alma's tutorial.
Longer version:
If you're using as me a Valve Index headset, which achieve 120 Hz and 144 Hz modes, what happened to you was one of the frecuencies (Hz) went corrupt by the drivers side, so you need to reset the drivers.
That means if you, for example, use as regular 144 Hz mode, and thens you get the 435 error, going to C:\Program Files (x86)\Steam\config\steamvr.vrsettings and removing that file, would put your Index into 90 Hz mode, the default Hz amount, then work; but the plot twist here is the driver stills corrupt, so if you swap to differents modes as 120 Hz or 80 Hz, you would be ok, but when bringing back 144Hz, you Will be bringing back the 435 error as well.
So yes, if you was using 90 Hz when corrupted, you totally suffered a complete soft brick of your HDM as long you don't use any another PC/laptop nor considering to reinstalling Windows.
After a week, when 144 Hz got bugged, and stick myself in 120 Hz, yesterday this frecuency mode (120hz) got corrupted too.
This meant to use the freaking horrible 90 Hz or 80 Hz modes (I'm got so used to 120+, that rolling back to 90 now makes me feel all messy n blurry when moving my head), so I didn't bear it anymore, and checked n removed all valve's software, cleaned manualy all Valve and Steam regs on regedit, and after all that don't working, then I noticed the graphic card drivers would be the fair logic conclusion I completely ignored.
I heard clean Windows re-install makes the error to dissapear for good, so, after emulate a "first time steam clean launch", this driver theory suspicion I called myself obviously steadly raised, due to a Windows reinstall means install drivers from 0.
After go to Geforce Experience, you should look and find any updates there, and if don't, look for the "reinstall driver" option.
Select manual, and check ALL the option boxes.
After that, congrats, you would be able to use again your corruped frequency, and if you suffered the same as me, congrats, you would be scaping this time from using the hell-ous 90 to 80 Hz range.
-----
I hope this would help anyone with the same issue, now Google would postion this post on first places when searching "error 435" or "Steamvr error 435", so, if we want to help more people...
P.D.:
Just in case, I tried a lot of extra stuff, like changing ports and etc, so I localiced the error after unistalling steam, but before that I tried a lot more things. My message only talks about the last resort I had to use (erase and delate all Valve signal of life from my disks) and how this failed, only to notice the error where on the drivers.
In my case, I'm using 446 driver with a 1070 EX 8GB.