search

OSVR / SteamVR-OSVR

An OSVR plugin for SteamVR, providing SteamVR support for OSVR HMDs.
Apache License 2.0
138 stars 57 forks source link

[Totally And Utterly Resolved Non SteamVR-OSVR Issue] Steamvr Compositor Issue/s #75

Closed Balderick closed 8 years ago

Balderick commented 8 years ago

N.B. If You Have Been Directed Here Through OSVR Support Please read the comments from most recent backwards to try and track issues in reverse chronological order to best understand my most recent status regarding configuration being used etc.

CURRENTLY

No Headset Detected (108)

Main current issue seems to be usb device (ir camera) firmware issue with usb 3.0 female ports. steamvr does not detect device. running latest current steam client, steamvr, osvr control, osvr runtime 1204 and latest osvr drivers. Latest drivers firmware and everything else which meeans nvidia 368.81 drivers. Regardless of which osvr_server.config.json or sample file is used all that is shown in osvr server output is what is listed at https://github.com/OSVR/OSVR-Docs/issues/63

Before launching osvr server i check that all OSVR devices are showing as well and healthy in devices app, control panel device and printers as well as in device manager.

OSVR Control gives ` >#?v Version 1.92 Mar 24 2016

Tracker:1.8.4.415 `

SteamVR Compositor Is Not Available (400)

After receiving a HDK 1.4 kit on Thursday it took me till late on Friday to get drivers installed with no problem devices showing in device manager. It took another twelve hours + of applying workarounds, reinstalling drivers and searching the interweb to work out i had to try rolling back from 1197 to 1194 core and steamvr-osvr drivers to improve chances of a steamvr title to launch. My HDK display appeared to die on Saturday evening and spent most of Sunday to work out my hdk was stuck in direct mode and not dead. The furthest in set up process i have been is launching steamvr and being asked to switch to direct mode but steamvr compositor can not start when steamvr restarts in direct mode. Using 1197 runtime and steamvr-osvr drivers i managed to go through room setup before being asked to switch to direct mode.

Describe the issue you've encountered. What is the exepected and actual behavior? What steps have you tried to fix the problem? osvr audio device showing as problem device i.e. unusable, not started in device manager. windows devices and devices and printers showing no ssues with displays but nvidia control panel sees hdk display as using portrait. selecting landscape helps with steamvr issues/errors (400 and 109). To help with steamvr setup and osvr complaining about no beacon configuration done i used https://www.youtube.com/watch?v=MObPn_U4IYg but allthough the file appeared to save osvr could never use it. The other bugs still needing workarounds applied are described well in this video. https://www.youtube.com/watch?v=1ZaboSUUpcI I do not expect drivers to be an issue on modern operating systems. Killing hardware makes the drivers not fit for purpose.

Steps to reproduce the problem

How can the problem be reproduced? Plug in and power up HDK Launch OSVR client Start Steam Start SteamVR Switch to direct mode using steamvr ui Can not get passed "compositor is not running (400)" dialogue. Clicking the "launch compositor" button does nothing. If i start steamvr with hdk in extended mode after deleting steamvr.vrsettings the compositor (white meshed environment) is visible in hdk display. The compositor never loads after switching to direct mode.

The enable/disable direct mode switches that come with osvr runtime work as expected the majority of the time. Roughly 3 out of 10 times get unexpected behaviour ranging from appearing to do nothing and nothing. i.e. gets stuck in direct mode after steamvr switched from extended to direct mode. Getting osvr audio device not be shown as trouble device in device manager is an issue in its own right but steamvr not starting compositor is what is stopping any app to launch as expected in vr mode imo.

System configuration

Please specify any relevant system configuration information.

After finding 1.2.6 and 1.2.7 drivers installed at same time i suspect what caused this to happen is same thing that has caused hdk display to die. I double checked my downloads folder and am 100 per cent positive i did not install 1.2.6 drivers. The only currently available drivers from https://github.com/OSVR/OSVR-HDK-Windows-Drivers/releases are 1.2.7

OSVR audio device has issues with driver management. It is a problem device. I need to disconnect usb from i/o on pc and use device manger to show hidden devices. Only after deleting all disconnected devices and drivers allows the reinstall of driver for osvr audio device with no issue or problems.

Attached files

Please attach the following files:

N.B. Two HDK's and 100 + hours down and still not one steamvr app launched successfuly. :-(

Now that i have faceplate removed am currently working my way through https://www.youtube.com/watch?v=GLgxJxbsalM to try and get going again

Why isn't there a screwdriver for removing faceplate included with hdk? I used a 00 phillips screwdriver with care and still rounded off a screwhead probably due to the screws being overtightened on assembly imho.

HDK was stuck in direct mode but still can not get passed "compositor not available (400)".

Balderick commented 8 years ago

HDK

What is the HDK?

The HDK or Hacker Development Kit is a virtual reality HMD designed to bring the benefits of the OSVR ecosystem to fans of VR out of the box. Not only does it allow you to experience VR, its support for the OSVR ecosystem means access to the growing range of VR controllers and technologies that support the ecosystem.

There are two HDKs currently available:

  • HDK 1 – Designed to provide all the essential technology you need to experience VR.
  • HDK 2 – Designed to deliver mind bending visual experiences with more advanced technology.

Why is it called a Hacker Development Kit? Is it for developers or consumers?

The HDK is for both. The HDK was designed to embody the vision of the software platform – to allow for unrestricted innovation for developers and to deliver innovation to consumers. It was created to address the needs of the emerging VR industry that requires flexibility and technology that is open to evolution. This to help power innovation and allow owners of the hardware to access the latest technologies as soon as they are supported by the ecosystem. While this is something we will continue if a consumer focused iteration is released, the Hacker Development Kit exists to be that perfect fit between industry innovation and the evolution of a consumer’s needs and true to the OSVR software – it is open source.

http://www.razersupport.com/osvr-hacker-dev-kit/

Why have i had two hdk's and never experienced vr?

godbyk commented 8 years ago

Do you have the HDK plugged into the Intel card or the nVidia card? It may be that SteamVR has trouble with direct mode on dual-card machines. Do things work as expected in extended mode?

russell-taylor commented 8 years ago

The latest nVidia drivers prevent DirectMode from operating on dual-GPU machines with non-HDCP-compliant displays. You should be able to run in extended mode, where the laptop is on the Windows display. You can put the display into that state using the DisableDirectMode program that should ship with the SDK.

Balderick commented 8 years ago

Please specify any relevant system configuration information.

Graphics card(s): Main display: 4K TV 3840x2160 Intel 530 igpu HDK Display: 1920x1080 Asus Matrix Nvidia GTX 980TI discrete gpu

The hdk needs to be plugged into discrete card as the igpu (onboard - intel 530 graphics on a i7 6700k cpu ) does not support vr . The two gpus are being used as there is only one hdmi port on nvidia discrete card. I'll look into seeing if there is such a thing as a display port to hdmi adapter or other cable options that i could use to get both displays working from nvidia gpu only.

All latest news, reddit and update info say everything should work with latest nvidia drivers.

Both the enable/disable direct mode switches that ship with osvr runtime and steamvr ui work fairly reliably for me.

I am going to test osvr content before retrying steamvr with hdk in extended mode (not direct mode) before considering rolling back nvidia drivers.

Balderick commented 8 years ago

Can now confirm more unexpected behaviour. Since receiving hdk 1.4 have very rarely put the hmd display on head due to nothing launching as expected. When trying OSVR content from http://www.osvr.org/featured.html#page-1 not one launches as expected.

DreadEye VR demo, Showdown (direct mode), Cityscape Repairman, SightLine The Chair and even the Palace Demo mentioned in documentation which is not even listed as official osvr content does not launch as expected. Even extended mode is not working as expected as after viewing the extended desktop in hdk display it is upside down.
After setting landscape in nvidia control panel settings the extended desktop in hdk is upside down. If i try to launch anything (steamvr or osvr content) in hdk and i go back to nvidia control panel the orientation has changed to portrait and changing it back to landscape gives a rotated portrait with task bar at side instead of bottom of screen - which is not the true extended desktop.
When any osvr content is launched a stereoscopic window opens on main display. The hdk display just stays blank due to being in direct mode.

So i got drivers (osvr) that windows hates and are actualy causing wdf_violation bluescreen of death, no VR content showing in hdk display other than a borked unusable extended desktop.

Where do i start debugging this shit? It would appear everything is FUBAR as nothing is working as expected for me.

Having no z axis and reversed x axis on tracker view and led calibration settings not saving or being usable adds to that list of things not working as expected. I can add more believe you me ....

Nothing in latest updates works for me predicably or reliably.

I am needing help to work all this out. Being told "latest version fixes that" is not helping at all nor is being given outdated and irrelevant information.

Balderick commented 8 years ago

@godbyk With refernce too https://www.reddit.com/r/OSVR/comments/4qrin6/news_osvr_runtime_more_update/d4vy4x3 please put the orientation issue higher on your priority list.

Balderick commented 8 years ago

How does latest nvidia drivers break osvr direct mode? Nvidia are OSVR partners; aren't they? How can OSVR partners break OSVR support?

I just updated to 368.69 purely because of http://www.nvidia.co.uk/download/driverResults.aspx/104828/en-uk https://youtu.be/6jJr-DMLka8 and still hope to use hdk to enjoy such content in VR mode.

Upgrading gpu driver seems to have helped extended mode as what i see in extended mode in hmd is expected behaviour i.e. correct orientation

OSVR content is still running in windowed mode on main display and but not in hmd though.

Steamvr is loving the new gpu driver simply get green lights on launch. Have only tried extended mode so far but can complete room setup and the tutorial appears to be alive now too. I even got to launch a game in vr mode. However ....

... it is coming back to needing main display and hmd connected to same gpu. Steamvr support pages demand this for vive when seeing errors 400 and 109. https://support.steampowered.com/kb_article.php?ref=8566-SDZC-9326#headset Steam compositor loads when launching elite dangerous in extended mode but nothing gets rendered in hmd (other than compositor)

I found it is possible to purchase male display port to female hdmi 2.0 adapters which should allow me to connect both displays to same gpu so other than rolling back to older drivers i might have to chomp at the bit for a while longer yet.

But can i wait to try out the new steam-osvr drivers ....

Balderick commented 8 years ago

Everything works as expected with 1197 osvr runtime, 209 build steamvr-osvr drivers and current stable steamvr with 368.69 drivers; up until trying to launch an app. The 400 and 109 issue/s are no longer reproducible. The orientation issue and direct/extended mode switching isues are no longer reproducible for me. Still can not get any steamvr app to show in hmd as expected though.

Getting wdf_violation bsod when powering down or restarting pc with hdk connected and powered up is still reproducible.

Rolling back to 365.19 drivers with current steamvr stable and current osvr runtime is a no go. I can see only one osvr steamvr beta version available (osvrsvvr) but not sure which osvr runtime versions to be trying.

rpavlik commented 8 years ago

Should not need a beta of steamvr. If the hdk was "killed" that's a known hardware issue, contact support for RMA.

You might consider unplugging the USB when booting for now.

rpavlik commented 8 years ago

If you still have GPUs from two vendors, then rolling back to a pre 367 driver is the only solution that will help getting direct mode apps to work: you can even see the NVIDIA driver release notes at least for the first 368 release driver, they mention intentionally breaking HDK support on multi GPU systems. If there is another reason you can't roll back that driver and can't go to a single GPU, I suggest contacting NVIDIA to let them know the trouble their decision is causing you and many others.

godbyk commented 8 years ago

From the release notes for nVidia driver version 368.69:

With R367 and future NVIDIA drivers, Crescent Bay and Open Source Virtual Reality development kit headsets will not work with VRWorks Direct Mode in systems that contain GPUs from multiple vendors (e.g. NVIDIA and Intel). For such systems, please disable the Intel integrated graphics (from the system BIOS) in order to use Direct Mode.

Balderick commented 8 years ago

When i started this thread i did believe my hdk was dead. After removing faceplate to access reset switches i noticed the tracking leds were not flashing but were on. I then realised i should try disconnecting hdk rebooting system and reconnecting hdk once again. The switches that install with runtime for enabling and disabling direct mode were functional once again. I have since had the hdk get stuck in direct mode but simply disconnected hdk and used device manager to show hidden devices to uninstall the display adaptor and then reboot and try reconnecting hdk again. Seems to be a reliable reproducible workaround for getting unstuck from direct mode.

And again tio clarify latest gpu drivers (368.69) with 1194 and 1197 osvr runtime and steamvr-osvr drivers have no issue of switching to and from direct mode (most of the time). It is getting steamvr and osvr apps to launch and show up in hmd that is the issue here.

Rolling back to 365.19 drivers with 1194 and 1197 runtime and steamvr-osvr drivers did not work out well. direct mode switching was even less predictable. Should i be using older runtime and steamvr-osvr drivers and steamvr beta with older drivers?

Disabling igpu and installing another nvidia gpu has not helped either. steamvr simply gives error 108 hmd not detected. Windows is detecting all osvr hdk hardware with no issues in control panel, devices app and device manager. Tracking has stopped working when i start osvr server.

I admit to causing PEBCAK, i admit to being unable to descrbe things well, i admit i even need to RTFM but i know that i do not need to apply for another RMA so that i can be asking all the same questions in another months time.

Rebooting with hdk connected and powered causes wdf_violation bsod consistently in all methods tried listed above when restarting or shutting down. Yes i disconnect power and usb to work around that.

Is there any useful information i can give so we can get these issues resolved?

Balderick commented 8 years ago

So this is how i read:

With R367 and future NVIDIA drivers, Crescent Bay and Open Source Virtual Reality development kit headsets will not work with VRWorks Direct Mode in systems that contain GPUs from multiple vendors (e.g. NVIDIA and Intel). For such systems, please disable the Intel integrated graphics (from the system BIOS) in order to use Direct Mode.

what i see is

Direct Mode in systems that contain GPUs from multiple vendors

as meaning a gtx 950 with one hdmi port could be used to run primary display ( 4K TV in my case) paired with a gtx 980 ti for running hmd. Nvidias release notes discriminate multiple gpus of varying vendors. Nowhere does it specify sli (combined nvidia gpu's ) or single gpu for both primary display and hmd.

If my tv and hmd are hdmi only choice of connection to pc that means there has to be two available hdmi ports on pc.

Using nvidia gtx 950 for primary display along with nvidia gtx 980 ti appears to be fine in device manager. In nvidia control panel all the display layout, configuration and settings appear to be configured correctly for both displays. There is no trouble switching from and to direct mode using 1197 runtime and steamvr osvr drivers with nvidia 368.69 drivers. I now no longer even get the 400 and 109 errors as s steamvr simply does not detect hmd giving error 108. why? because steamvr is looking for primary and hmd connected to same gpu. ref: Error 208 section of https://support.steampowered.com/kb_article.php?ref=8566-SDZC-9326#headset reads:

Make sure that your Vive’s link box and the monitor or TV you use as a primary display are plugged into the same graphics card. If you are connected to your onboard display adapter, you will see an Intel HD Graphics device listed in your SteamVR system report. Onboard cards, such as those connected to a PC’s motherboard, will not be powerful enough to use the Vive. Reconnect your Vive to your PC’s dedicated graphics card.

With a dual nvidia set up with gtx 950 as primary display and gtx 980 ti as hmd due to both having only one hdmi port each does not even get close to what nvidia describes as to what should happen with an exclusively nvidia only gpu setup. It certainly is not the behaviour i see with 368.69 drivers; nor is it what i see with a nvidia and integrated intel gpu combination.. In fact; if anything, Direct mode switching seems to be more reliable with the intel/nvidia combo.

Windows is having issues with tracking camera now too; which is definitely an osvr software/driver issue. I have no usb 2.0 ports which is what windows is saying i need to try and do for tracking camera to work as expected.

So i opened up geforce experience and discover it is saying my pc is now not VR capable. Why? possibly because my primary display and hmd are not connected to same nvidia gpu.

Looks like both valves's steamvr and nvidias's vrworks are looking for same thing but osvr/steamvr-osvr are not even aware.

Balderick commented 8 years ago

So still trying to get hdk to behave as expected and/or as described in official documentation. Not even trying to get steamvr apps running but just trying to get a working osvr server config working. After recovering hdk from being stuck in direct mode once more, making sure all my mobo device drivers are up to date, making sure there are no firmware updates for any hardware on this machine available and spending 40+ hours trying to research, troubleshoot and remedy all the issues i am having with osvr hdk and osvr software.

My main focus has shifted from trying to get by steamvr errors and is now trying to work out why osvr server has stopped giving positional tracking, tracker viewer broke and can not calibrate leds by using videotrackercalibibration utility. https://github.com/OSVR/OSVR-Docs/issues/63

Very little of the official information in osvr docs seems to be relevant to or even refer to recent builds of osvr hdk, osvr runtime and steamvr-osvr drivers .

OSVR HDK is the hardware deveolpment platform of OSVR Organisation. Please document it as such in the OSVR software documentation. https://www.youtube.com/watch?v=dxeQVBwyh8Y

Getting to see what should happen with recent releases of osvr hardware and software in Proxishs's videos has been truely life saving. Those videos are in fact the main motivation for continuiuning my vr quest/odyssey on a daily basis.

All my hardware currently being used is advertised as More than VR Ready and/or VR Ready. I spent all my life savings on this vr rig . It is a beast of a machine. Asus Maximus VIII Extreme running a water cooled i7 6700k and an Asus Matrix GTX 980 Ti with pci-e nvme solid state storage and 32GB of ddr4 RAM.

Why is OSVR hardware and software not ready for my vr machine?

Have to admit this put a smile on my face when i saw it https://www.reddit.com/r/OSVR/comments/4rxbph/release_hdk2_already/

aahhhhh the irony!

Balderick commented 8 years ago

Can anybody confirm the latest runtime (1204) and the latest steamvr-osvr drivers (209--1197) works as expected with steam vr apps?

Can anybody confirm Team Fortress 2 runs in VR mode at all nowadays?

godbyk commented 8 years ago

I do my testing with the latest runtime and the latest (non-beta) version of SteamVR.

Balderick commented 8 years ago

what steamvr-osvr driver build/version are you using with the osvr 1204 runtime?

Can anybody confirm the info at https://support.steampowered.com/kb_article.php?ref=8566-SDZC-9326#gen-pc is relevant or good advice for osvr hdk and osvr software users? i.e. does steam need to be running as admin for steamvr apps to work with osvr?

Balderick commented 8 years ago

Have found connecting a 24" 1080p monitor to same GPU as hdk hmd has indeed allowed osvr demos/apps to load in hmd but I need to switch or move primary display for different osvr demos. The demos are not using ir positional tracking so were not very enjoyable or impressive. Ir positional tracking is not working because osvr server is using saved beacon calibration config from videotracking configuration utility. There is nothing in osvr documentation that i can find describing how to remove the saved beacon config or how to switch back from using the saved config that video tracking configuration utility created to start using ir positional tracking again. I thought the whole point of saving beacon calibration was so that ir tracking worked when starting osvr server without the need to put hmd in front of camera.

Too many of my questions and issues are being left unanswered and unresolved here. The main issue is the lack of accurate and relevant information in readme.md's as well as that information made available in one easily accessible place. I still think that it is not my osvr hardware that is at fault. All the issues listed are known and documented osvr software issues and very few of the documented workarounds are even relevant never mind actual working workarounds.

I opened another osvr support ticket so will stop asking questions and trying to communicate what issues I am having and what I am trying to do to get by them here as the monologue is not easy reading even for me.

godbyk commented 8 years ago

A support ticket is a better channel for issues unrelated to the SteamVR-OSVR software itself. This issue tracker is only for the latter.

Balderick commented 8 years ago

Could a support ticket help in getting the steamvr-osvr team to drop a couple of gears? Maybe somebody at osvr support could at least take me through troubleshooting steps to actually confirm what issues I am hitting and thus determine if the issues are osvr hardware, osvr software, steam, steamvr or operating system related issues?

godbyk commented 8 years ago

From reading what you've been reporting here, I thought you'd already determined that yourself.

I'll be honest, though, this issue report has meandered quite a bit and I've lost track of what the current problem is that you're experiencing.

Balderick commented 8 years ago

;-) I can not prove or confirm the multi GPU configuration, the primary display management, the orientation or broken ir tracking are osvr hardware, osvr software, steam, steamvr or operating system issue/s.

The only change has been adding a 1080p monitor to same GPU as hdk hmd by using dvi . The outcome is I can now run some osvr demos/apps from http://www.osvr.org/featured.html but am having to change primary display, orientation and other GPU related settings to get them to run in hmd. I have not removed the gtx 950 or reenabled igpu. All I did was connect a another monitor but to the same GPU as the hdk hmd is connected to. Am running latest nvidia drivers 368.69 with osvr runtime 1204.

I have not tried the latest runtime with latest steamvr-osvr drivers as there is no 1204 version of steamvr-osvr drivers and nobody has confirmed if the 1204 runtime with the 209build 1197 version steamvr-osvr drivers are compatible. AFAIK runtime and steamvr-osvr driver version need to be matching pair to work as expected.

I did ask twice. ;-)

Vast majority of the issues I am seeing are in fact listed as open issues in osvr-core and rendermanager issue trackers.

Steam support steamvr pages are proving very helpful. They contain much useful information for osvr users imho. The ironic thing is the information for errors 109, 208 and 400 errors highlight the need for primary display and hmd to be connected to same GPU which is exactly how i got my rig to run osvr content as expected.

godbyk commented 8 years ago

While we generally try to build a new SteamVR-OSVR plugin when we rebuild OSVR-Core specifically to avoid this confusion, it's not actually necessary. The interface to the Core libraries rarely changes and the SteamVR-OSVR driver will work with almost any OSVR server version you can get your hands on. (The latest SteamVR-OSVR plugin does require a fairly modern OSVR-RenderManager, though.)

Balderick commented 8 years ago

ahh k thanks for clarifying that.

I use runtime installer which installs render manager components but not the full set of rendermanager tools. Is it safe to assume the latest version of osvr runtime uses the latest version render manager components?

Yes i understand the limitations of older osvr apps needing older versions of render manager installed. That is the main contributing factor to why i am not really interested in running older osvr applications. The main reason for me trying to run osvr apps is to prove my osvr hardware is not defective. ;-) My main incentive for getting osvr hdk was to play steamvr games. The thing that motivates me in continuing to try and get osvr software working as expected is to play steamvr games.

As an nvidia shield (tablet and adroid tv) device user the android support of hdk has me intrigued but i ain't going there till i understand what is going on here on pc platform.

Can you confirm the example game of TF2 on steamvr-osvr readme.md is even relevant nowadays? All i get is a dialogue box saying something like "TF2 is not a vr game. Trying to run it in vr mode will drastically reduce performance." that is with and without -vr launch parameter for that game.

I dare even say the readme.mds for steamosvr-osvr drivers and render manager are useless. They seem to convey mainly outdated and irrelevant information. Same for the Getting Started doc.

So now we know main display and hmd need to be connected to same gpu and that both Valve and Nvidia support pages explicitly DEMAND this and we know that osvr apps can run as expected on my rig i think the broken ir tracking is now the thing i would most like to troubleshoot; before going on to test steamvr and vr games again.

i used the videotrackingconfiguration utility to save beacon configs. ir tracking has not worked since. How do i delete the saved beacon configs? I can confirm video tracker graphical window has started showing again as well as the command prompt window when launching tracker viewer. Since saving the beacon calibration config the green light on camera has never litten up when osvr server is started. Using windows camera app i can confirm both the camera and led array on hmd are alive.

Why doesn't uninstalling and reinstalling osvr runtime reset video tracking calibration saved configs?

Even using revo uninstaller (which finds 40MB + of files and registry entries) and a registry cleaner in preparation for reinstalling osvr runtime does not help reset beacon calibration config.

godbyk commented 8 years ago

Is it safe to assume the latest version of osvr runtime uses the latest version render manager components?

Yes.

As an nvidia shield (tablet and adroid tv) device user the android support of hdk has me intrigued

Android support is still a work-in-progress. You can follow its development by monitoring the OSVR-Android-Build repository.

Can you confirm the example game of TF2 on steamvr-osvr readme.md is even relevant nowadays?

I haven't tried it personally, so I can't say. You could ask on Reddit or in the Gitter chat rooms, though.

I dare even say the readme.mds for steamosvr-osvr drivers and render manager are useless. They seem to convey mainly outdated and irrelevant information.

That could very well be. I do intend to update the SteamVR-OSVR README for the next release.

If you've found specific problems in either of the READMEs, please file individual issue reports citing the erroneous or outdated information and we'll get it updated. Or even better, you can edit the file directly and submit the changes for review.

How do i delete the saved beacon configs?

The filename is set in the OSVR server config file (under the calibrationFile key). By default it's a file named videotrackerCombinedCalibrationFile13.json or similar based on the HDK version. For more information on the calibration utility, you'll need to either contact OSVR support or read through the relevant code and docs in the OSVR-Core repository. I don't know much about it myself.

[...] the green light on camera has never litten up when osvr server is started

I believe the camera light turns green once the video-based tracker plugin is loaded. Are you seeing any error messages when you start up the OSVR server? Does it say anything about the plugin?

Why doesn't uninstalling and reinstalling osvr runtime reset video tracking calibration saved configs?

I don't know the answer to that either. I'd suggest contacting support@osvr.org and they can direct your request to someone who knows more about it than I do.

Balderick commented 8 years ago

Thanks for the feedback @godbyk it is appreciated. I really appreciate developers simply do not have the time for hand holding every osvr user step by step with an issue. I am sure the readme.md's would benefit greatly of being updated. I should have more free time once i get osvr hdk working so will try to help in contributing to that or at least making suggestions as issues!.

I did make a post listing what i can see when launching osvr server; somewhere here on github recently, and will try to find it ....

I'll add the specific tracking issue in my already opened osvr.org support ticket.

Balderick commented 8 years ago

This is what i can see when launching osvr server https://github.com/OSVR/OSVR-Docs/issues/63

Balderick commented 8 years ago

Regardless of what config i choose using osvr Config osvr server starts with same .json giving exact same read out in terminal as listed in osvr/osvr-docs https://github.com/OSVR/OSVR-Docs/issues/63 Regardless of what config i choose use to assign from command prompt osvr server starts with same .json giving exact same read out in terminal as listed in https://github.com/OSVR/OSVR-Docs/issues/63 Regardless of what sample.json or any other .json is saved as "osvr_server_config.json" in main dir osvr server starts with same .json giving exact same read out in terminal as listed in https://github.com/OSVR/OSVR-Docs/issues/63

Uninstalling and reinstalling different runtimes, deleting the main osvr dir in prgram files folder, running registry cleaner are some of the things i have been trying but the usb issues (audio device) seem to be causing other usb device errors. A ms usb tranciever wireless kb + m has needed to be reinstalled sevral times now too. No usb 2.0 ports are available on this machine ootb. All the onboard usb ports and front panel usb ports are all 3.0 or higher. Checking the mobo users manual it highlights that any usb 2.0 (legacy) device that does not work as expected on a usb 3.0 port needs a firmware update and is a well documented issue with intel z170 chipset.
issue #71

If i try to launch steamvr all i get is the hmd not detected error 108 when osvr is launched with whatever .json it using (it aint the one i, osvr config or osvr_server.exe tell it too use!)

Applying the workarounds suggested at steamvr support has not helped the issue itself have definitely made me better understand the issues going on here. https://support.steampowered.com/kb_article.php?ref=8566-SDZC-9326#gen-pc

How do i get control of osvr server again?

Most of my usb issues are gone IF i remember to unplug power from splitter cable, unplug the ir video tracking camera usb 2.0 from the pc and disconnect the large proprietary connector from belt clip before every reboot or shutdown.

godbyk commented 8 years ago

There are too many issues filed that I'm losing track of what the current problem is.

If you're having a problem starting the OSVR server, I'd suggest filing an issue in the OSVR-Core repository and closing the other issues. Be sure to include the relevant information (system configuration, HDK version, configuration files used, server output, etc.) in the new issue. You can reference these other issue reports you've created, but please provide all the useful information in the new issue so that those of us trying to provide support don't have to jump around and read long threads of (possibly now-irrelevant) information to try to determine what the problem is.

Balderick commented 8 years ago

https://github.com/OSVR/SteamVR-OSVR/issues/71

All that i have confirmed is there are multiple issues but i'll try to list the info here; if that is okay? too.

I am listing all the configurations i have tried. I have confirmed my current configuration more than once here in recent posts in reply to you here.

If i start another thread i am worried all the same suggestions all the same stuff that i have already confirmed here. in one place. Ask me a question with regard to what you will find useful. I bet the info is indeed in here already. So give me a list of troubleshooting or something because me listing seperate issues is not helping either of us.

I have an open support ticket referring to thuis and other threads so all core devs etc will see them.

Why is no questions being asked?

Many issues in many repos here all list the issues i am seeing.

So to get all the things you mention that would be useful in one place is not hard to do.

system configuration,

The op here lists my hardware config and https://github.com/OSVR/SteamVR-OSVR/issues/75#issuecomment-232380193 lists my current config. I have not changed my config other than swapping uusb ports and cables etc. I am not sitting here twiddling my thumbs waiting on a response i am actively trying to work this out too.

HDK version,

tbh i dunno if it is 2.0 or a 1.4 think it is a 1.4 . My other issue #40 describes my 1.3 hdk which was rma'd. the device i got back was returned in the same original packaging as i sent the old 1.3 hdk away in so the serial numbers etc are actualy irrelative to the device i have.

configuration files used,

Read the op and https://github.com/OSVR/SteamVR-OSVR/issues/75#issuecomment-233137316

server output

Regardless of which config file is used the server output is what is listed in https://github.com/OSVR/OSVR-Docs/issues/63

Balderick commented 8 years ago

Are the known usb device firmware issues being hugely underestimated?

Balderick commented 8 years ago

Apologies. many of the links shared were not going to where i intended to i.e. "osvr/osvr-docs/issue #63" should have been https://github.com/OSVR/OSVR-Docs/issues/63

and the links to comments have been fixed too.

godbyk commented 8 years ago

The output in https://github.com/OSVR/OSVR-Docs/issues/63 says, in part:

[OSVR Server] Using default config file - pass a filename on the command line to use a different one.
[OSVR Server] Using config file 'osvr_server_config.json'

This means that osvr_server isn't recognizing that you're passing a different configuration file to it and it's using the default as per usual.

How are you running osvr_server? If you're running it from the command line, you'd type:

> osvr_server.exe path/to/my/osvr_server_config.json

If you try this, what does the server output say (in its entirety)?

Balderick commented 8 years ago

how many times do i need to tell you.? I have tried command line using all available .jsons, manualy saving sample configs as osvr_server_config.json etc etc with three osvr runtime builds two steamvr-osvr driver versions, four different gpu drivers etc etc

When i said all available jsons i meant from all command line options to launch osvr server, all sample and other configs in osvr config, all the sample and other .jsonss in osvr main dir all give the same server output regardless of how it is launched or which .json is used

C:\Program Files\OSVR\Runtime\bin>osvr_server.exe sample-configs/osvr_server_config.HDK13ExtendedPortrait.sample.json [OSVR Server] Using config file 'sample-configs/osvr_server_config.HDK13ExtendedPortrait.sample.json' [OSVR Server] Constructing server as configured... [OSVR Server] Loading auto-loadable plugins... [OSVR Server] Loading plugins... [OSVR Server] [OSVR Server] Instantiating configured drivers... [OSVR] Added device: org_osvr_filter_videoimufusion/HeadFusion [OSVR] Client context initialized for org.osvr.analysisplugin [OSVR] Interface initialized for /com_osvr_Multiserver/OSVRHackerDevKitPrediction0/semantic/hmd [OSVR] Interface initialized for /com_osvr_VideoBasedHMDTracker/TrackedCamera0_0/semantic/hmd/front [OSVR Server] Successes: [OSVR Server] - com_osvr_VideoBasedHMDTracker/VideoBasedHMDTracker [OSVR Server] - org_osvr_filter_videoimufusion/VideoIMUFusion [OSVR Server] [OSVR Server] [OSVR Server] Aliases found and parsed from config file. [OSVR Server] Display descriptor found and parsed from config file. [OSVR Server] RenderManager config found and parsed from the config file. [OSVR Server] Triggering automatic hardware detection... [OSVR Server] Registering shutdown handler... [OSVR Server] Starting server mainloop: OSVR Server is ready to go! [OSVR] Performing hardware auto-detection. [OSVR] Added device: com_osvr_Multiserver/OSVRHackerDevKit0 [OSVR] Added device: com_osvr_Multiserver/OSVRHackerDevKitPrediction0

godbyk commented 8 years ago

I understand you're frustrated. But I can troubleshoot this without your help. I need to know exactly what you're typing to start the server and exactly what the server it outputting.

I've looked at the code and the only time the server will print Using default config file is when osvr_server.exe is run without passing in a configuration file on the command line. So I'm trying to reconcile what the code is doing with what you're seeing.

Can you run osvr_server.exe path/to/osvr_server_config.json from a Command Prompt and paste everything from the Command Prompt window here? That will show me what directory you're in, what you typed to run the server, and what the server is printing. (When you paste it here, put three backticks on a line by itself before and after the stuff you're pasting [see below]. That'll format it nicely.)

paste contents of Command Prompt window

Thanks!

Balderick commented 8 years ago 
C:\Program Files\OSVR\Runtime\bin>osvr_server.exe sample-configs/osvr_server_config.HDK13ExtendedPortrait.sample
[OSVR Server] Using config file 'sample-configs/osvr_server_config.HDK13ExtendedPortrait.sample'
[OSVR Server]
Could not open config file!
[OSVR Server] Searched in the current directory; file may be misspelled, missing, or in a different directory.

C:\Program Files\OSVR\Runtime\bin>osvr_server.exe sample-configs/osvr_server_config.HDK13ExtendedPortrait.sample.json
[OSVR Server] Using config file 'sample-configs/osvr_server_config.HDK13ExtendedPortrait.sample.json'
[OSVR Server] Constructing server as configured...
[OSVR Server] Loading auto-loadable plugins...
[OSVR Server] Loading plugins...
[OSVR Server]
[OSVR Server] Instantiating configured drivers...
[OSVR] Added device: org_osvr_filter_videoimufusion/HeadFusion
[OSVR] Client context initialized for org.osvr.analysisplugin
[OSVR] Interface initialized for /com_osvr_Multiserver/OSVRHackerDevKitPrediction0/semantic/hmd
[OSVR] Interface initialized for /com_osvr_VideoBasedHMDTracker/TrackedCamera0_0/semantic/hmd/front
[OSVR Server] Successes:
[OSVR Server]  - com_osvr_VideoBasedHMDTracker/VideoBasedHMDTracker
[OSVR Server]  - org_osvr_filter_videoimufusion/VideoIMUFusion
[OSVR Server]
[OSVR Server]
[OSVR Server] Aliases found and parsed from config file.
[OSVR Server] Display descriptor found and parsed from config file.
[OSVR Server] RenderManager config found and parsed from the config file.
[OSVR Server] Triggering automatic hardware detection...
[OSVR Server] Registering shutdown handler...
[OSVR Server] Starting server mainloop: OSVR Server is ready to go!
[OSVR] Performing hardware auto-detection.
[OSVR] Added device: com_osvr_Multiserver/OSVRHackerDevKit0
[OSVR] Added device: com_osvr_Multiserver/OSVRHackerDevKitPrediction0
godbyk commented 8 years ago

Okay, now we're starting to get somewhere. This is different output than you had posted previous. Notice the line that says:

[OSVR Server] Using config file 'sample-configs/osvr_server_config.HDK13ExtendedPortrait.sample.json'

I don't see any errors there. Does the HDK's IR camera light turn green? If not, do you have any other webcams or imaging devices plugged in to your computer? If you do, then try unplugging those, leaving just the IR camera connected, and then starting the server again. The IR camera light should turn green then.

Balderick commented 8 years ago

There is no green light and osvr ir camera is only camera connected.

Balderick commented 8 years ago

With default osvr_server_config.json which looks like

{
    "description": "This configuration supports video (so-called 'positional') and IMU fusion tracking, in addition to orientation-only tracking, with the OSVR HDK. It is configured for RenderManager applications in direct mode (portrait) on HDK 1.3 optics.",
    "display": "displays/OSVR_HDK_1_3.json",
    "renderManagerConfig": "sample-configs/renderManager.direct.portrait.json",
    "drivers": [{
        "plugin": "com_osvr_VideoBasedHMDTracker",
        "driver": "VideoBasedHMDTracker",
        "params": {
            "showDebug": false,
            "includeRearPanel": true,
            "headCircumference": 55.75,
            "calibrationFile": "videotrackerCombinedCalibrationFile13.json"
        }
    }, {
        "plugin": "org_osvr_filter_videoimufusion",
        "driver": "VideoIMUFusion",
        "params": {
            "name": "HeadFusion",
            "input": {
                "imu": "/com_osvr_Multiserver/OSVRHackerDevKitPrediction0/semantic/hmd",
                "faceplate": "/com_osvr_VideoBasedHMDTracker/TrackedCamera0_0/semantic/hmd/front"
            },
            "eyeHeight": 0,
            "cameraIsForward": true
        }
    }],
    "aliases": {
        "/headSpace": {
            "translate": [0.0, 0.0, 0.04141],
            "child": "/org_osvr_filter_videoimufusion/HeadFusion/semantic/fused"
        },
        "/me/head": "/headSpace"
    }
}

still get

C:\Program Files\OSVR\Runtime\bin>osvr_server.exe
[OSVR Server] Using default config file - pass a filename on the command line to use a different one.
[OSVR Server] Using config file 'osvr_server_config.json'
[OSVR Server] Constructing server as configured...
[OSVR Server] Loading auto-loadable plugins...
[OSVR Server] Loading plugins...
[OSVR Server]
[OSVR Server] Instantiating configured drivers...
[OSVR] Added device: org_osvr_filter_videoimufusion/HeadFusion
[OSVR] Client context initialized for org.osvr.analysisplugin
[OSVR] Interface initialized for /com_osvr_Multiserver/OSVRHackerDevKitPrediction0/semantic/hmd
[OSVR] Interface initialized for /com_osvr_VideoBasedHMDTracker/TrackedCamera0_0/semantic/hmd/front
[OSVR Server] Successes:
[OSVR Server]  - com_osvr_VideoBasedHMDTracker/VideoBasedHMDTracker
[OSVR Server]  - org_osvr_filter_videoimufusion/VideoIMUFusion
[OSVR Server]
[OSVR Server]
[OSVR Server] Aliases found and parsed from config file.
[OSVR Server] Display descriptor found and parsed from config file.
[OSVR Server] RenderManager config found and parsed from the config file.
[OSVR Server] Triggering automatic hardware detection...
[OSVR Server] Registering shutdown handler...
[OSVR Server] Starting server mainloop: OSVR Server is ready to go!
[OSVR] Performing hardware auto-detection.
[OSVR] Added device: com_osvr_Multiserver/OSVRHackerDevKit0
[OSVR] Added device: com_osvr_Multiserver/OSVRHackerDevKitPrediction0
Balderick commented 8 years ago

screenshot 31

Balderick commented 8 years ago

Just to try and add some info that might be relevant and expand on the answers to the most recent questions from @godbyk have just noticed there is driver issues related to OSVR High-Speed Infrared Tracking Camera in Device Manager.

Allthough there are no warning s or indication there are driver issues in devices app, control panel devices and printers or device manager; having two audio belt box devices is a new one to me. Settings > Devices > Connected Devices sees OSVR HDK hardware as

dev

with Device Manager seeing things like

devman

and digging into Image devices properties shows

devprop
Balderick commented 8 years ago

So after two hours to get osvr windows drivers installed for unknown device after a power cycle has now caused some more unexpected behaviour.

Using the latest 2.7 windows drivers pack without hdk connected installs drivers but in add/remove programs three osvr drivers are being used once the hdk is connected and powered up. Using the latest 2.7 windows driver pack with hdk connected installs five osvr drivers visible in add/emove programs. Both methods give unknown device/s (sometimes two unknown devices)

Uninstalling osvr drivers using add/remove programs and then rebooting (with hdk disconnected) and then connecting hdk and let windows installs the drivers it wants gets four devices (expected behaviour) showing in control panel and system settings devices with no problem or unknown devices being shown in device manager.

Windows now sees imaging device as a usb camera and yet osvr ir tracking camera is named in devices.

newdevman newdev2
Balderick commented 8 years ago

Still having issues with device drivers but would like to confirm firmware version 1.96 has helped a lot with camera issue/s.

Balderick commented 8 years ago

Upgrading firmware to 1.96 from windows 1607 fixed the camera.

Still hitting 108, 400 and other steamvr errors. Have tried recent builds of osvr runtime and steamvr-osvr drivers and the AIO. All give similar results.

godbyk commented 8 years ago

@Balderick Can you upload a system report from SteamVR using the latest build of SteamVR-OSVR?

When I've seen error 108 (HMD not found), it's been because the SteamVR-OSVR driver failed to connect to the OSVR server or if there's been some hardware or driver issue.

Usually error 400 (failed to start compositor) is just a result of error 108.

Balderick commented 8 years ago

Will do

What I got is HDK and main display using same GPU. The main display is using dp to HDMI passive adapter to allow that. Running windows 1607 build with hdk 1.4 using 1.96 firmware. Nvidia GPU drivers 372.54.

Uninstalled aio and steamvr and made sure to delete the steamvr and osvr directories. Rebooted.

Installed steamvr Installed latest runtime Extracted the osvr directory from latest steamvr-osvr drivers compressed directory to the steamvr\drivers directory. Edited the drivers.cfg to help give osvr drivers priority.

Launhed osvr server with default direct mode.json Launched steam and then steamvr

HDK hmd totally ignored direct mode json and stayed on extended mode Steam crashed and could not create a system report. For the first time ever steamvr dashboard and steamvr window were not visible on main display but only the white compositor showed in hmd. If I hovered mouse over task bar on main display I could see dashboard was giving green light for hmd and camera. I could not get focus by clicking steamvr icons in task bar. It looked like windows thought the windows should be on main display as an outline of window showed on main display when mouse cursor was over icons.

What other log files could be of any use to you?

lol steamvr crashed but did not die gracefully. An exclamation icon in system tray gave room setup etc options and create system report even after i had exited steam. steamvr.txt

Killed vr server process using task manager and restarted steam and then steamvr. SteamVR gracefully and instantly crashed this time.

Enabling direct mode and then launching osvr server with the default .json gets steamvr monitor showing on desktop but no green lights and no compositor in hmd. 108 and 400 errors.
steamvr2.txt

godbyk commented 8 years ago

The extended-mode and direct-mode configuration files are only used by RenderManager. Since SteamVR uses its own direct-mode code, it doesn't make use of those files. (The SteamVR-OSVR driver does still make use of those files in part when operating in direct mode, though, since we can't autodetect all the parameters we need in direct mode yet.)

The steamvr.txt log looks like it found the HDK in extended mode okay but then had some difficulty when trying to switch to direct mode. (At least that's my guess.)

The steamvr2.txt log looks like it's in direct mode and that you ran into the bug I just (hopefully) fixed. (Notice the crazy rotation, position, and vsync values in the vrserver.txt file? Those should be fixed in the latest build.)

Let's look at the vrserver.txt log from the latest build and see where that gets us. It seems like it's pretty close to working.

Balderick commented 8 years ago

Thank you for explaining the different direct mode needs for steamvr and native osvr apps/render manager.

System report from latest build runtime and steamvr osvr drivers, enabling direct mode and then launching server with default .json - steamvr3.txt

vr monitor showed in top left corner of main display with the 108 error. No compositor in hmd.

System report for extended mode with default.json - steamvr4.txt vr monitor showed in top left corner of main display with the 108 error. No compositor in hmd.

Just for fun i started steam as administrator and got the 108 so tried to reboot hmd - steamvr5.txt vr monitor showed in top left corner of main display with the 108 error. No compositor in hmd. Tried rebooting hmd from steamvr monitor and got error 308

made sure vr server process was killed between each attempt

Balderick commented 8 years ago

Just an observation but must say the 1.96 firmware and 1607 build windows seems to have made great advances regarding all the usb device issues i was having. We are getting closer.

godbyk commented 8 years ago

Yes, @rpavlik has been making great strides in the firmware updates!

I just pushed yet another build (255) that should fix a couple more bugs when the HDK is in direct mode. Can you test that build for me? Before you do, delete the vr*.txt log files so we can start fresh. (Easier for me to see which logs are new that way.)