02-03-2020 05:38 PM
02-10-2020 08:59 PM
SergeMeister1234 said:
TomCgcmfc said:
ShowbizDonkey said:
@TomCgcmfc - The rule of thumb is that the changes listed in release notes are the things you should be on the lookout for in a given version. Re: your mention of X Plane 11, I may have said this to you previously, but I always recommend testing with apps that from the Oculus store. We don't always have great visibility into compatibility with specific apps run via Unknown Sources.
Sorry but I would expect a bit more detailed release notes, esp. for non-Quest users.
As far as 3rd party apps go, this is the usual useless Oculus Support response. The fact that X Plane 11 shutdown worked perfectly for a long time (since v1.36 to and including v12) and v13ptc broke this (without any changes to xp11 btw) then this seems to me to be an Oculus related issue, not a 3rd party one. I did send Oculus Support my previous 13ptc logfiles but I'm starting to doubt that anything happens with these. Once my current v12 auto-updates I guess I'll find out for sure, lol!Welcome to my wold with Assetto Corsa Competizione. Logs seem to go nowhere, and I’m just being told to test with Oculus content. I haven’t run any Oculus content before so only way that test would be useful is if OCULUS LET US ROLL BACK TO PREVIOUS WORKING VERSIONS!!! That way you could at least back to back test it. Would also require sone Oculus content software based on the Unreal engine which I have no interest in paying for out of my own pocket to troubleshoot Oculus’s failures.
People are blaming Kunos for the bad performance when it’s Oculus, was running really well then an Oculus update destroyed it.
Affirmative. They are acting like there is no patient zero, no specific event that started all of this mess. The fact that they will not allow people to revert to a working version without hacking it is proof positive that the wheels have come off of their development. This has all been going on since Mid-December of last year! Sure, its obviously hardware specific for most, but if they cannot churn out software that is compatible all around then don't advertise requirements that people meet and then buy their product to be introduced to this circle jerk. Man up as a company and provide a reversion path and then those who still can't get it to work........send it back.
02-10-2020 09:10 PM
02-10-2020 09:41 PM
TomCgcmfc said:
Just an idea but it might be useful to split new Oculus version threads into Rift cv1/S and Quest Link. Maybe even move the Quest one to the Quest subgroup. It seems to me that problems/solutions for each are not very relevant. Anyway, just a suggestion.
It would probably even be better if they did not share the same Oculus desktop app imho. I think that this may allow Oculus to hone in on each platform separately instead of trying to do all this within one app where changes on one seems to make a mess of the other.
Edit; I could even envision the Quest Link app ending up similar to the good old Oculus v1.0. This could potentially add extra performance to the Quest Link.
02-11-2020 05:42 AM
SergeMeister1234 said:
TomCgcmfc said:
ShowbizDonkey said:
@TomCgcmfc - The rule of thumb is that the changes listed in release notes are the things you should be on the lookout for in a given version. Re: your mention of X Plane 11, I may have said this to you previously, but I always recommend testing with apps that from the Oculus store. We don't always have great visibility into compatibility with specific apps run via Unknown Sources.
Sorry but I would expect a bit more detailed release notes, esp. for non-Quest users.
As far as 3rd party apps go, this is the usual useless Oculus Support response. The fact that X Plane 11 shutdown worked perfectly for a long time (since v1.36 to and including v12) and v13ptc broke this (without any changes to xp11 btw) then this seems to me to be an Oculus related issue, not a 3rd party one. I did send Oculus Support my previous 13ptc logfiles but I'm starting to doubt that anything happens with these. Once my current v12 auto-updates I guess I'll find out for sure, lol!Welcome to my wold with Assetto Corsa Competizione. Logs seem to go nowhere, and I’m just being told to test with Oculus content. I haven’t run any Oculus content before so only way that test would be useful is if OCULUS LET US ROLL BACK TO PREVIOUS WORKING VERSIONS!!! That way you could at least back to back test it. Would also require sone Oculus content software based on the Unreal engine which I have no interest in paying for out of my own pocket to troubleshoot Oculus’s failures.
People are blaming Kunos for the bad performance when it’s Oculus, was running really well then an Oculus update destroyed it.
02-11-2020 02:04 PM
TomCgcmfc said:
OK, I got my dreaded v13.1 auto-update 1.5 hours ago. Seems to have the same problems as I got when I tried v13ptc but at least I have found a couple of workarounds that are not too much of a pita.
1) The Oculus dash/desktop continues to show a lot of black artifacts on both sides of the Desktop panel when I shift my head right/left. The workaround is to go to the dash/settings/graphics and enable the bottom option VR panel rendering. This fixes this and looking at task manager it does not seem to have any effect on my cpu/gpu % usages. BTW, the top option to enable AA still does not seem to make anything clearer for me. However it does double my gpu % usage. So for now I just disable it.
2) X Plane 11 once again has the good old pre v1.36 shutdown bug (hangs on exit) again and I need to use task manager to kill it. The workaround for me is to startup xp11 from the Oculus dash/desktop, selecting its shortcut. When I want to exit I just pause xp11, then press the Oculus button. This brings up the usual reset view/exit app panel (with the dash/desktop panel in the background). Minimise the Oculus reseat/exit app panel and use your mouse to select task manager (I have it pinned to my bottom task bar) and right click on xp11/end task. This kills the program and lets me continue on without the need to remove my headset. Not very elegant, but at least it seems to work ok.
Overall, the performance of all the Oculus Store and Steam games I've tried so far seems to be about the same as v12.1. Still not quite as good as v1.38/1.39 imho, but not too bad. At least for me with my Rift cv1 w/2x sensors v13.1 hasn't Bricked it, lol!
Edit; I do not have ACC but Assetto Corsa (original version) seems to work perfectly fine for me.TomCgcmfc said:
OK, I got my dreaded v13.1 auto-update 1.5 hours ago. Seems to have the same problems as I got when I tried v13ptc but at least I have found a couple of workarounds that are not too much of a pita.
1) The Oculus dash/desktop continues to show a lot of black artifacts on both sides of the Desktop panel when I shift my head right/left. The workaround is to go to the dash/settings/graphics and enable the bottom option VR panel rendering. This fixes this and looking at task manager it does not seem to have any effect on my cpu/gpu % usages. BTW, the top option to enable AA still does not seem to make anything clearer for me. However it does double my gpu % usage. So for now I just disable it.
2) X Plane 11 once again has the good old pre v1.36 shutdown bug (hangs on exit) again and I need to use task manager to kill it. The workaround for me is to startup xp11 from the Oculus dash/desktop, selecting its shortcut. When I want to exit I just pause xp11, then press the Oculus button. This brings up the usual reset view/exit app panel (with the dash/desktop panel in the background). Minimise the Oculus reseat/exit app panel and use your mouse to select task manager (I have it pinned to my bottom task bar) and right click on xp11/end task. This kills the program and lets me continue on without the need to remove my headset. Not very elegant, but at least it seems to work ok.
Overall, the performance of all the Oculus Store and Steam games I've tried so far seems to be about the same as v12.1. Still not quite as good as v1.38/1.39 imho, but not too bad. At least for me with my Rift cv1 w/2x sensors v13.1 hasn't Bricked it, lol!
Edit; I do not have ACC but Assetto Corsa (original version) seems to work perfectly fine for me.morphee7 said:
oculus im sorry but how can you release v13 for everyone over this week i believe the quote was when you have had reports from us PTC users provide feedback on the issues and before everyone has it you release a v14 PTC knowing there must be issues with v13
02-12-2020 12:55 AM
Oculus Rift CV1, Valve Index & PSVR2, Asus Strix OC RTX™ 3090, i9-10900K (5.3Ghz), 32GB 3200MHz, 16TB SSD
"Ask not what VR can do for you, but what you can do for VR"
02-12-2020 05:00 AM
ShowbizDonkey said:
Hey everyone - thanks for the rapid feedback. I passed this info along to the team. They quickly investigated and found that there was indeed a previously unnoticed issue with the Rift rollout which prevented it from being available to the community. Really sorry for the miscommunication there and any inconvenience this caused! We’re working to remedy the situation as quickly as possible. We have confirmed that Rift S / Rift v13 has now been released to 30% of users. Our engineering team will review performance data, and assuming everything looks okay there, we will be making the update available to all users as soon as possible. The v13 Quest rollout is unaffected by the issue we discovered and that update has been made available to all users at this time. Thanks for your patience and understanding.
02-12-2020 11:19 AM
02-13-2020 12:16 AM
02-13-2020 05:42 AM