07-30-2014 07:08 AM
[b][*](8/11/2014)Update : v1.0.5336.14017:[/b] [i]*Minor Update No functionality changes*[/i]
Redirected all Troubleshooting data grabbed from devCon internally instead of redirecting output to text file, then into a variable (Eliminated the timeout issue 🙂 )
Added Running Processes to the report to help troubleshoot issues.
[b][*](8/8/2014)Update : v1.0.5333.18034:[/b]
Now added event logs from the last 48 hours that have the OculusVR source to the troubleshooter!
[b][*](8/8/2014)Update : v1.0.5333.15723:[/b]
Added more useful information to the troubleshooter. Now detects when the wrong display driver is installed for the Rift. Shown in screenshot below:
[img]http://www.mediafire.com/convkey/a384/3olu9uw19w1ye886g.jpg[/img]
[b][*](8/7/2014)Update : v1.0.5332.26221:[/b]
Added a feature to the utility that lets you add a context menu option called "Open On Oculus Rift" - basically runs the exe you selected with the -Adapter argument.
[b]Example Screenshot:[/b]
[img]https://www.mediafire.com/convkey/82e2/ko2ub7jd58zrgax6g.jpg[/img]
[*](8/7/2014) v1.0.5332.18722:
Added a "LowFilters" check to the troubleshooter to help locate issues where the End users video card drivers become un-usable and where the DK2 Camera fails to install due to "[b]The specified service does not exist as an installed service[/b]" Error
[*]Update (8/6/2014) v1.0.5331.1335:
Changed the way the program sets the current working directory so files are not put into system32 when ran as a scheduled task. Increased the timeout for the troubleshoot link, as some computers did not run it fast enough - was causing it to crash while accessing the file.
[*]Update (8/5/2014) v1.0.5330.15088:
Added a "Troubleshoot Issues" Link on the bottom right corner of the utility. When you press this, it will put all relevant debugging information on to your clipboard, or to textfile if your computer has problems accessing the clipboard (admin issues usually). You can post this info on this forum or on Reddit. [b]I highly suggest that you wrap the contents in code tags [code]like this[/code] because it is VERY long.[/b]
[*]Update (8/1/2014) v1.0.5326.10214:
SSE-Fix has been optimized and no longer uses 7zip to extract the SSE-Emulator since a few users were having issues. Now it's a self contained self extracting executable. This has added about 2MB to the file size, totaling at 6MB which isn't too bad. Added more error checking with some new log files that should only have text if something goes wrong.
[*]Update v1.0.5325.14213:
When SSE fix is Enabled, it will remember to re-enable it the next time you run it, even by scheduled task.
[*]update v1.0.5323.12638:
Now when My Custom Watchdog is enabled, it will create a scheduled task that will auto launch the watch dog when you reboot your PC.
[*]update
Now includes an Option for SSE-Emulation as shown in this thread: http://www.reddit.com/r/oculus/comments/2c65vb/found_a_solution_for_the_ovrservice_x64exe_has/
Just check the checkbox "Enable SSE Fix" and you're good to go!
[*]If you press "Restart Drivers", it will actually restart the drivers for the Camera and the HMD. This is useful if you need to reboot - now you don't have to!
07-30-2014 07:12 AM
07-30-2014 07:15 AM
"Semicidal" wrote:
I am sorry, but what is this for?
07-30-2014 07:17 AM
07-30-2014 07:18 AM
07-30-2014 07:19 AM
"Semicidal" wrote:
Wow, I am apparently way behind on how to use my rift. I didn't know the service needed stopping to play certain games. (Didn't know my DK2 COULD play anything below 0.4). I'm still stumbling around trying to get it to accept the camera.
07-30-2014 07:23 AM
07-30-2014 07:24 AM
07-30-2014 07:31 AM
07-30-2014 07:37 AM
"Semicidal" wrote:
Is there a way to tell what SDK a game was compiled in without trial and error?