Rift 1.32 Release Notes (Public Test Channel) - Page 3 — Oculus
New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Rift 1.32 Release Notes (Public Test Channel)

13»

Comments

  • GeekyGamiGeekyGami Posts: 105
    Art3mis
    edited November 2018
    Agreed.
    Not to be disrespectful, but as a VR enthusiast, while I can understand this is all part of the brand Oculus is trying to build, it's ultimately nothing more than annoying at best, and paranoia inducing at worst

    Having all the information you need would be precisely what you would see with something like Steam, for instance,
    before a new update.

    When all the information is there, it's quite simple.
    Instead of having to speak with actions, we can rectify misunderstandings with words.

    It otherwise also leaves you in the scenario where people accuse you of something instead of just telling you an idea could be done better.


    Point is, what I'd expect is quite simple:

    For hotfixes like the one we got for the Oculus Brick apocalypse a while back, getting a hotfix ready and distributing it without bothering with a fancy page for a simple patch would have been the best course of action.

    Making an entire web page for a hotfix patch is.. A tad misguided, but I digress.

    How little information is held in changelogs reeks of PR shenanigans, and people are catching on pretty quick that any time there is a lot of PR and obfuscation, something is being hidden.

    Changelogs are incredibly important, both to the end-user, and to developpers.



    On that note, I'll note I have about 5% less CPU used by OVRServer64 when headset is on, so that's nice.


    Any word on when we can see the problems with the Oculus Client not fully installing things because of third-party installs, installer failure shenanigans and programs failing to finish downloading midway being fixed?

    Because those issues are actually more annoying than any other software I've ever used.

    I've neglected downloading games because they won't finish installing or updating, like Echo VR.
    I'm starting to neglect buying any games from the store for this reason as well.

    Downloading 5 gigs every time the client fails is steep.
  • Digikid1Digikid1 Posts: 1,859 Valuable Player
    Also I mean FULL DETAILS and not the shortcut of

    ”bug fixes and improvements “


  • TomCgcmfcTomCgcmfc Posts: 1,031
    Wintermute
    edited November 2018
    Vote with your feet for sure but in my case I haven’t seen any problems with 1.32/core 2.

    If you really want to see worse/bigger problems try wmr, imho, lol!
    Alienware 17r4 Laptop with i7-7700hq 2.8/3.6, 32 gb ram, gtx1060 w/6gb ram, 256gb ssd, 1tb hdd, Oculus Rift w/2x sensors.  Now using an Alienware Graphics Amplifier (AGA) with Zotac gtx1080ti Blower and Asus vg248qe 144hz external monitor.  All works great!
  • nroskonrosko Posts: 954
    Neo
    Oculus keeps updating to 1.32 5th time now. 
  • dburnedburne Posts: 2,302 Valuable Player
    nrosko said:
    Oculus keeps updating to 1.32 5th time now. 
    Probably the official release of 1.32.
    https://forums.oculusvr.com/community/discussion/70953/rift-1-32-release-rolling-out-now#latest
    Don

    EVGA Z390 Dark MB | I9 9900k| EVGA 2080Ti FTW3 Ultra |32 GB G Skill 3200 cl14 ram | Warthog Throttle | VKB Gunfighter Pro/MCG Pro grip | Crosswind Pedals | EVGA DG 87 Case|
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Yes, we just starting rolling out live this morning.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • nroskonrosko Posts: 954
    Neo
    ok makes sense. 

    I'm still having issues with the mouse cursor in desktop. I think it might be related to using a 4k monitor as if i set my monitor to a lower resolution the problem goes. Anyone else have this issue with a glitchy mouse pointer? 
Sign In or Register to comment.