Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I've sent some logs to the SteamVR team, but haven't heard a response yet. I feel they are busy working on Direct Mode, among other things. I could really use the null driver to work though, as it did in earlier builds before the steamvr.vrsettings file.
{
"jsonid" : "vrsettings",
"steamvr": {
"forcedDriver": "null"
},
"driver_null": {
"enable": true,
"id": "Null Driver",
"serialNumber": "Null 4711",
"modelNumber": "Null Model Number",
"windowX": 100,
"windowY": 100,
"windowWidth": 1920,
"windowHeight": 1080,
"renderWidth": 1344,
"renderHeight": 1512,
"secondsFromVsyncToPhotons": 0.1,
"displayFrequency": 90
},
"notifications" : {
"DoNotDisturb" : false
},
"version" : "1"
}
Have a look in vrserver.txt and be on the look out for errors like the following:
Wed Sep 30 11:34:29 2015 - Parsing of settings file failed: (D:/VR/config\steamvr.vrsettings)
Wed Sep 30 11:34:29 2015 - * Line 6, Column 4
Missing ',' or '}' in object declaration
We will improve vrmonitor, so it will notify you better when you have a broken settings file.
Please give it a try and if it does not work send your vrsettings file and the content of a system report to steamvr@valvesoftware.com for further investigation.
I copy & pasted that file, and the null driver still won't load. I get "Hmd not found (108)".
The vrserver.txt log shows this, with no errors:
Wed Sep 30 21:05:06 2015 - Load Json Settings from C:\Program Files (x86)\Steam\config\steamvr.vrsettings
vrclient_java reports:
Wed Sep 30 16:06:02 2015 - vrclient startup with PID=3424, config=C:\Program Files (x86)\Steam\config
Wed Sep 30 16:06:02 2015 - Returning HmdNotFound because the client-side presence check failed.
No idea what is going on wrong, or where...
C:/Program Files (x86)/Steam/config/steamvr.vrsettings
{
"jsonid" : "vrsettings",
"steamvr": {
"forcedDriver": "null"
},
"driver_null": {
"enable": true,
"id": "Null Driver",
"serialNumber": "Null 4711",
"modelNumber": "Null Model Number",
"windowX": 100,
"windowY": 100,
"windowWidth": 1920,
"windowHeight": 1080,
"renderWidth": 1344,
"renderHeight": 1512,
"secondsFromVsyncToPhotons": 0.1,
"displayFrequency": 90
},
"notifications" : {
"DoNotDisturb" : false
},
"version" : "1"
}
Logs
C:/Program Files (x86)/Steam/logs/vrserver.txt is not available.
C:/Program Files (x86)/Steam/logs/vrcompositor.txt is not available.
==================================================
As you can see under logs - its saying vrserver.txt is "not available" and indeed when I load the file - its empty.
C:/Program Files (x86)/Steam/logs/vrcompositor.txt is not available.
==================================================
As you can see under logs - its saying vrserver.txt is "not available" and indeed when I load the file - its empty.
Just so that I understand things properly, am I right in thinking that the Steam VR SDK will allow me to develop a game or app that will work with both an Oculus Rift and HTC Vive HMD..?
And the thing stopping us from getting this to work with a Google Cardboard-type headset and an application like TrinusVR is that Steam VR falls over when it can't see an Oculus/Vive/Gear VR headset..?
Rather than a null driver isn't there a way to detect a smartphone connected via USB tethering..? After all, Windows recognises smartphones and knows to install drivers for it. I'm a real n00b at all this malarkey so please forgive me if I'm talking nonsense lol
Not on the machine I'm trying to get the null driver working on.