davide445 Posted July 1, 2020 Share Posted July 1, 2020 (edited) Strange behavior, testing Unigine VR applications all of them have this odd corrupted part on the right, also there are heavy racking problems. This is oil refinery This is one of our projects. SteamVR app are running fine. Restarting Vive Console and SteamVR didn't solve the problem. Using Vive Cosmos latest firmware, 1.12.5 SteamVR, latest Nvidia drivers, all 2.11 SDK. GTX 1070 GPU. Edited July 1, 2020 by davide445 Link to comment
silent Posted July 2, 2020 Share Posted July 2, 2020 That's expected behavior. We are not clearing OpenVR render targets to save some performance. You can change the output texture to the monitor via API: AppVive:setViewportMode() and choose between following options: VIEWPORT_BLACK_SCREEN = 0 No image (black screen). VIEWPORT_MONO = 1 Mono image. VIEWPORT_STEREO = 2 Stereo image (left and right eye). How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
davide445 Posted July 2, 2020 Author Share Posted July 2, 2020 @silent was all working fine till few days ago - didn't remember exactly when tested last time. Also the performance and tracking inside VR are heavily affected, i. e. illumination cascade never finish to be updated, all is going super slow, etc Will check this afternoon for other elements. Link to comment
davide445 Posted July 2, 2020 Author Share Posted July 2, 2020 (edited) @silent checked changing USB port for the Vive controller, updated to latest Cosmos beta firmware, nothing changed. Curiously the older oil refinery demo based on 2.9 SDK is working fine in VR, but show always the corrupted part Testing the newer 2.11 VR projects all of them not only show this problem on screen but also VR it's extremely unresponsive and the right controller doesn't appear in VR, the left yes. The only hw change was last week an upgrade to 64GB RAM, but all was working till yesterday. Checked Windows 10 is using build 1909 so standard one and there is no recent big update. To be noted also I have seen this behavior happening before, possibly after some Vive/SteamVR software update, but was never able to track down the reason and after a reboot/update/whatever disappear and all was back to normal (so no corruption on display, no tracking problems in VR). I never had this problem running for days, as is now. Edited July 3, 2020 by davide445 Link to comment
silent Posted July 3, 2020 Share Posted July 3, 2020 Just did a brief check with the latest SteamVR and 2.11.0.2 demos from the SDK Browser - everything is working just fine. Have you tried to reinstall SteamVR and delete all of it's configs? Thanks 1 How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
rohit.gonsalves Posted July 3, 2020 Share Posted July 3, 2020 Hello there, More tests. Tested it with the 2.11 and HTC Vive. Updated Steam-VR and all devices firmware to latest one. Working fine for me too. @davide445 Sometimes programming kills. :-) Probably a HDMI or DP cable connecting to devices. Regards, Rohit 1 Link to comment
davide445 Posted July 3, 2020 Author Share Posted July 3, 2020 Good ideas thanks for testing, will need to test this on Monday. Link to comment
davide445 Posted July 8, 2020 Author Share Posted July 8, 2020 (edited) After more testing: - tested with the second GPU - changed GPU DP port - clean uninstalled and reinstalled SteamVR - reinstalled OilRefinery demo All the same. Seems old demo projects are running fine: tried a 2.9 foxhole demo released as build and is working perfectly, 2.9 oil refinery is showing the corrupted part on display but is running fine in VR So seems oil refinery demo 2.11 it's not working well with my setup: just to start the right hand is always missing. I also can't use the left hand for any activity. Every other 2.11 project or demo I can test in VR is behaving wrongly, but let's verify this one first. Unfortunatelly can't test the old projects apart the released one due to the license problem. Edited July 8, 2020 by davide445 Link to comment
davide445 Posted July 10, 2020 Author Share Posted July 10, 2020 I noticed something weird: I have two GPUs and use only one of them by using an HDMI switch. Now discovered if I use the slot 1 GPU only this one is loaded if I switch to the second slot (where the VR headset is connected) both of them are used at the same time within the Unigine 2.11 editor Considering I seems to have problems only on Unigine 2.11, something has changed on GPU loading in thise relase? Link to comment
davide445 Posted July 17, 2020 Author Share Posted July 17, 2020 (edited) @silent As last test I removed the second GPU and installed the one associated at SteamVR on the first slot. The behavior is the same, also not only the right side of the screen is corrupted but also on the left side something is odd. This is true for every demo or custom project on 2.11 SDK. i.e. the right side of one of our projects the left side of the oil refinery Also on these demo no VR interaction is possible since only the left controller is available (even powering on only the right one), as from this screenshot So - it's not the GPU slot or the GPU - the headset is working fine on other VR applications - the old pre-2.11 projects I have a delivery are working correctly - It's not the specific DP or USB port - It's not SteamVR installation - it's not the specific application Attached the log file of our project. How can we proceed? log.html Edited July 20, 2020 by davide445 Link to comment
davide445 Posted July 21, 2020 Author Share Posted July 21, 2020 (edited) @silent another problem with 2.11: using a slow internet connection the projects didn't start neither in VR or 2D. Was using a wireless connection on my PC in a demo room and the projects remains stuck at the texture loading point and never proceed. Returned with the wired connection in the office and the very same projects started without problems. 2.9 projects was starting correctly in the first and second case. Edited July 21, 2020 by davide445 Link to comment
Recommended Posts