Jump to content

NJJediZ

Verified Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey John, Thanks for jumping in to try and save my sorry butt. Ok, I get what you're saying about the HMD possibly being hijacked by windows. My primary monitor is a Dell S2716DG running at 2560 x 1440 native resolution and 144hz refresh rate. The Nvidia control panel sees the monitor and it's settings. Interestingly, Win 10 system display only sees a generic PNP monitor at 2560 x 1440 and 60hz refresh. Of course, I have no idea how to make Win 10 see the Dell as other than a generic PNP monitor and I have no idea if that has anything to do with my Vive problem. As far as I can tell from Win 10 settings or device manager - the Vive does not exist. I generated the a SteamVR report and maybe you can make sense of what's going on from it, but it's way too big to post here. Frankly, this is past my pay grade. Is there a way for me to email you the report, it's pretty detailed about what was happening. Sorry bout the network comment. I only meant that this is a standalone machine with internet access so in that sense, of course I'm networked, but I am not on a home or fileserver network. And yeah - I figured out that the C:\ProgramData folder was hidden and I unhid it, but it didn't make a difference. Oh, and thanks again for giving me help, hopefully someone else will see this and not have to bother you. - njjediz
  2. Okay, it's Dec. 12th, 2017 and I just encountered the same error while attempting to reinstall the Vive software following a glitch in SteamVR. For background - I've been running my Vive on my gaming system (i7 7700k; GTX 1070; 32Gbs RAM; Win 10 creators fall update) since Jan. 2017 through Steam with few problems other than some latency issues on occasion. Yesterday, I fired up SteamVR and got the following error message: Error Starting SteamVR SteamVR failed to initialize for unknown reasons: (Error IPC Compositor Connect Failed (306)) FYI - The Vive status box shows all physical devices in the green and a red NOT READY Above the status box there's another error message: Compositor is not available You'll need this to run SteamVR to work correctly There's a link to "Launch Compositor" but after clicking it, nothing happens. I sent Steam a support request and so far Steam doesn't seem to have an answer. Vive support recommends uninstall and reinstall which brings me to the problem of the installer not finding "Setup_VivePCClient.msi" I am running as an administrator and this computer is not on a network, although the error message also says "The feature you are trying to use is on a network resource that is unavailable" - like duh, the machine is not on a network. The installer default location for Setup_VivePCClient.msi is: C:\ProgramData\Package Cache\{56C14CA2-FA7A-4A95-A429-8C5B7F1C1689}v1.0.8889.966\ There is no C:\ProgramData folder on my C drive, or my D drive, nor my E drive. So why is the installer calling for a file from a folder that doesn't exist? Anyway - the Vive installer thinks everything's just fine and shows both the Vive software and Steam software as being properly installed. If I run SteamVR - I'm back to the original "Starting Steam error message - Compositor Connect failed. I will check back here to see if anybody has an answer because I'd rather have a Vive then an Occulus
×
×
  • Create New...