Big Changes Coming With Oculus Runtime 0.7
Posted: Fri Aug 07, 2015 1:59 pmhttps://developer.oculus.com/blog/upcom ... y-changes/
Oculus lays out the road map for the path to the 1.0 SDK and it might be a little bumpy. Looks like 0.7 is going to break a fair amount of stuff - one in particular is extended mode is gone. Also, they are going to truncate support for older SDKs. As each new version comes out, support for anything older than one revision looks like it will be dropped so it's going to be fairly lock step as things move along. Anyone interested should read the release.
Not sure what all this will mean for Dan supporting versions of FlyInside built against the older SDKs. I think at a minimum it will mean more work for him if he backports much.
Hopefully the issues with OOMs and aftermarket scenery like Orbx can get sorted so we can all at least move up to 0.6.0.0 run time or else we may need to disable the Orbx stuff for a bit. Regardless, it looks like we'll all need to be a little flexible with the SDK and runtimes being this much in flux and with Oculus truncating support for older runtimes.
On the plus side, it looks like there may be some big performance gains coming the way they talk in the blog post.
Oculus lays out the road map for the path to the 1.0 SDK and it might be a little bumpy. Looks like 0.7 is going to break a fair amount of stuff - one in particular is extended mode is gone. Also, they are going to truncate support for older SDKs. As each new version comes out, support for anything older than one revision looks like it will be dropped so it's going to be fairly lock step as things move along. Anyone interested should read the release.
Not sure what all this will mean for Dan supporting versions of FlyInside built against the older SDKs. I think at a minimum it will mean more work for him if he backports much.
Hopefully the issues with OOMs and aftermarket scenery like Orbx can get sorted so we can all at least move up to 0.6.0.0 run time or else we may need to disable the Orbx stuff for a bit. Regardless, it looks like we'll all need to be a little flexible with the SDK and runtimes being this much in flux and with Oculus truncating support for older runtimes.
On the plus side, it looks like there may be some big performance gains coming the way they talk in the blog post.