IMPORTANT:

All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible: https://developer.oculus.com/quest-pitch/

For additional information and context, please see "Submitting Your App to the Oculus Quest Store".
Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.

Anyone having experience about porting from Quest to Pico Neo 2 ?

Hi.

I'm investigating about porting a Unity 2019.2 VR game targeting Oculus Quest to Pico Neo 2.

The game slightly relies on the Oculus SDK, doesn't use Oculus Touch input, and upgrading to a newer version of Unity is likely to be problematic.

I'd like to know if people here have some insight or experience about this. I know that this is a Oculus and not a Pico forum, but if any other dev has already done this, it'd be great to discuss about what are the main caveats.

I'm not worried about moving from one SDK to another, but I'm afraid there might be some major hardware or software incompatibility that would require a lot of changes in the game, especially concerning the graphics API. A lot of the game graphics features have been tailored to work on the Quest, so if things are too different on that aspect, that would imply a lot of work for our team.

Thanks in advance, any help is appreciated!
Sign In or Register to comment.