Tagged: steamvr steam ipc
2018-03-26 at 09:14 #4435
Registering the driver immediately causes steamvr to throw error 301.
Driver folder in steam config directory is created but is left empty.
SteamVR detects no hardware as long as Driver4VR is registered.
Drive4VR also sees no hardware when it is registered.
SteamVR functions fine as long as Driver4VR is NOT registered/installed.
Driver4VR sees all hardware when it is NOT registered.
In normal, non-beta steamvr driver4vr reports ‘error- IPC_connectfailed’
In the new beta steamvr driver4vr reports an issue with compositor.
I have a dell visor and an xbox one kinect. I am trying to get body tracking set up.
I am using the paid version, if that makes any difference (are they different?)
My brother had no issues with the free version.
I have done a lot of troubleshooting on this and nothing seems to fix it.
2018-03-26 at 22:30 #4441
- This topic was modified 5 years, 8 months ago by chaoddity. Reason: more details
Also added driver4vr log files.
Will bump again in around 12 hours. For now I have homework to do.
Attachments:You must be logged in to view attached files.2018-03-27 at 06:47 #4445
i will look once i make 4.0 video. hopefully today.2018-03-27 at 07:09 #4447
Many thanks. I’ll keep an eye on this post.
Just to rule some stuff out:
– the paths seemed fine but i tried deleting steams vrpath in appdata and re-registering the paths to be sure steam wasn’t getting confused.
– i have set literally everything involved to run as admin. no dice.
– i’ve tried uninstalling and reinstalling wmr, steamvr, and driver4vr. I’ve done it many times in several orders.
– i have tried running them in various orders. Though it SEEMS like you have it set up so we can just run driver4vr and it should automatically run both WMR and SteamVR.
I can’t find many things on this specific error.
Oh, also- latest drivers on everything and running a fully up-to-date Windows 10. 64 bit.
If I can furnish any other useful information feel free to ask.
Any help I can get with this is super appreciated. I’ve really hit a wall on this one.2018-03-28 at 04:55 #4455
today’s bump. because no replies and because nothing I tried today worked.2018-03-29 at 11:57 #4469
i see no error in logs. do you mind trying test version?2018-03-29 at 12:02 #4472
Not at all. Any leads are good. Will report back here within the hour.2018-03-29 at 12:12 #4476
ok. can you join discord ?2018-03-29 at 12:20 #4477
Sure. :] I use it regularly. Though i normally stick to text even in it.
2018-03-29 at 17:13 #44832018-03-31 at 00:04 #4491
- This reply was modified 5 years, 8 months ago by chaoddity. Reason: update
Sure! Testing it now.
This bug can be considered squashed. The new version works perfectly!
2018-06-01 at 19:25 #4966Kay TisumaParticipant
- This reply was modified 5 years, 8 months ago by chaoddity.
Has this issue been solved? because i am having this same issue right now so if it has been solved could you please tell me how? thanks2019-02-07 at 12:39 #6145Tanner ToshParticipant
i am also haveing the same issue2019-02-08 at 18:18 #6162Rob van den BergParticipant
I know how to solve this, go to your userdir\appdata\local\openvr and edit the openvrpaths file there.
I removed an older not-in-use buggy driver from the external_drivers list in that file. Now it works again.2019-03-25 at 09:46 #10721Zachary FlorenceParticipant
Rob van den Berg – where did you make the edit? I open mine and see this? (My OVR runtime tries to do it’s thing when SteamVR crashes!):
“config” : [ “C:\\Program Files (x86)\\Steam\\config” ],
“external_drivers” : [ “C:\\Program Files (x86)\\Driver4VR\\lib\\drivers\\driver4vr” ],
“jsonid” : “vrpathreg”,
“log” : [ “C:\\Program Files (x86)\\Steam\\logs” ],
“runtime” : [ “C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR”, “C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR\\” ],
“version” : 1
- You must be logged in to reply to this topic.