Skip to main content
HartLabs
Up and Coming
November 4, 2014

Request for C API Changes/Additions/Depreciations List

With the update to 0.4.3 there was at least one change made to the C API which affects most/all custom Oculus SDK integrations (see this thread). There was no communication of this change, or of other potentially existing changes to the C API in the change-log. The integration documentation still shows the old, incorrect, syntax. I understand this is extra work for internal Oculus developers who could be spending time elsewhere in the SDK, but the lack of it makes updating SDK versions painful as the resulting errors which could be trivial to solve ahead of time, are instead unforeseen.

I would like to request that changes/additions/depreciations to the C API be announced with each release.

Please add a comment if you are interested as well.

    3 replies

    cybereality
    Inspiring
    November 4, 2014
    Sorry about this. I have informed the team.
    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
    HartLabsAuthor
    Up and Coming
    November 4, 2014
    Once again. Amazing Oculus developer support!
    Synthesis - Abstract Molecular Dynamics Simulator @HartLabs
    matte
    Up and Coming
    November 4, 2014
    Thanks, cybereality.

    It would also be great if the Oculus developer guide PDF could be updated to the latest API best practices with each SDK release. I see in the 0.43 guide, there are still references to the ViewAdjust translation vector, as well as other code snippets which are made redundant by the aforementioned API change. I understand this takes developer man-hours, and I can personally work around it when I see it, but I imagine people new to the SDK could be in for quite a confusing time.
    Terms & ConditionsAccessibility statement