Not saying that couldn't still happen though, people make stupid decisions all the time. some kind of runtime DRM check that Oculus own hardware is present) but given that they have publicly stated that they do not want a closed platform, that would be a PR disaster and probably hurt them more than it would gain them. ![]() There is of course the possibility that Oculus will start intentionally blocking this (e.g. no proper support for room scale VR), but a very worthwhile low hanging fruit. Then change nameobj 'scenes/chartemplate' to be nameobj 'scenes/charnew' Then. ![]() After that has been done go into the testini folder and open up runchar.ini. (backup the settings.ini if you want) And add/replace the following. Of course it would not be as good as native Vive support (e.g. Go back to 1.Installing template character and copy the testini to the root folder. So XStoryPlayer developers would need to enable this, but (at least in theory) that should be very easy to do - definitely much easier than adding native Vive support. ![]() This is trivial for the developer, but less easy for others. this Ars Technica article, each game (XStoryPlayer in this case) needs to be patched because Oculus has included a code signing check on the runtime DLLs, so to load the librevr replacement DLLs instead you need to patch the application. Not sure if librevr will work with XstoryPlayer, couldn't figure it out anyway.Īccording to e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |