Unity build crashes when using external dll's in project that has Oculus Integration Package
Hello, for a small personal project, I'm trying to use a MySQLConnector for database read/write operations from my Quest 2 headset. However, there appears to be some type of conflict between the Oculus Integration Package and the external dll's required for the database connection to work. In Play Mode, everything is fine and works perfectly, but when launching a build, the enitre program crashes before it even has a chance to start (not even getting past the Unity logo). Removing my VR Rig or the required external dll's solves the issue, but of course, I would like both. Could this be some type of a manifest or API number issue? I don't particularly have any ideas left so I'd love to hear your thoughts.
Oculus Integration or XR?
I have been creating a game which I am hoping to get onto the Quest 2 in the future. Whilst everything has been running smoothly using the XR plugins I was recently told that for games to be published within Oculus the Integration kit needs to be used and XR is not supported on a official Oculus title. Can anybody shed some light on this please? I have spent soo much time learning XR and C# to support XR functions to now be told that it could be effectively useless if the publishing platform I'm looking at is Oculus.
Is anything being done about the state of the integration package?
I was really excited about platform features becoming available for all devs, but it seems like the current state of the OIP is just terrible. Hands don't work properly. Error messages all around. Does anyone know if the Unreal version is any better? I might just switch over if it is. Really disappointed with the unity package. 😞
