Anti Aliasing In Unity with URP
Hiya! So I'm having issues with Antialiasing in Unity on a Quest project, it doesn't seem to matter if I have my project set up based on the Oculus documentation or not: https://developer.oculus.com/documentation/unity/unity-conf-settings/ Things are still looking pretty chunky, maybe I'm not understanding how to manually set the MSAA level, in my understanding it's the pipeline asset that has to be set to 4x MSAA Project Setup: Unity 2021.3.11f1 Unity XR System w/Oculus XR Plugin GLES not Vulkan Doesn't seem to matter if I'm in Multiview or Multipass. FXAA does... something, but its just blurry. I've read that for certain setups you have to disable antialiasing in the camera, only enabling it in the pipeline settings, this didn't have the desired effect for me. Finally, questions: How essential is the Integration Package to MSAA functioning correctly on the quest? Am I required to use an Oculus camera rig instead of the Unity XR Rig for Antialiasing to function correctly? Also if anybody can share with me screenshots of a working URP+MSAA Unity setup configuration I would be very grateful.
"OpenGL supports only the default graphics adapter."
For some reason I can no longer run the OculusRoomTiny sample program anymore because I keep getting this pop up "OpenGL supports only the default graphics adapter." It's being triggered by this code shown below in main.cpp: if (Compare(luid, GetDefaultAdapterLuid())) // If luid that the Rift is on is not the default adapter LUID... { VALIDATE(false, "OpenGL supports only the default graphics adapter."); } and static ovrGraphicsLuid GetDefaultAdapterLuid() { ovrGraphicsLuid luid = ovrGraphicsLuid(); #if defined(_WIN32) IDXGIFactory* factory = nullptr; if (SUCCEEDED(CreateDXGIFactory(IID_PPV_ARGS(&factory)))) { IDXGIAdapter* adapter = nullptr; if (SUCCEEDED(factory->EnumAdapters(0, &adapter))) { DXGI_ADAPTER_DESC desc; adapter->GetDesc(&desc); memcpy(&luid, &desc.AdapterLuid, sizeof(luid)); adapter->Release(); } factory->Release(); } #endif return luid; } I've never had this issue before, haven't changed any code, reinstalled the SDK, and I still get the same problem - did something happen to my headset - why isn't the luid the same? I'm using the DK2 and SDK 1.9.0 When I comment out the VALIDATE statement, the program runs, but the oculus just gets stuck in the "please wait" screen forever. Thanks for your help in advanceCan I download older version of Meta Link?
Hi, I have three products that were supposed to launch on December 1, and all three are dead in the water, waiting on a fix for the Meta Link v83 bugs. The headset update to v83 did not fix any of my issues on any system, Nvidia or AMD, on any of three PCs I've tested on. I switched headsets, cables, and did full uninstall / reinstall cycle. If I start with a basic Unity app and add the All-In-One SDK, it flat out refuses to work with even the most basic OVRCameraRig setup. I don't know how this isn't plaguing everyone else. But I need to ship these products. Is it possible for me to download and use an older version of Meta Link ? Does Meta have pre-release versions of Meta XR All-in-One SDK ? The official one is still v81. That might be the silver bullet. Thank you, -Chilton
Random black screen on quest
Hi First off, apologies if you see this question twice - I asked it once and the post disappeared immediately! We're experience a severe issue where, after a relatively small period of time (15 minutes to an hour) the screen in our app simply turn black and will never come back. The game is clearly still running (we can hear sfx in response to movement on controller, still use voip and verify the online connection is valid etc), however the screen is simply black. We've got some suspicious log cat output: 10-18 08:42:42.963 1037 1463 I ActivityManager: Process com.oculus.vrshell (pid 1809) has died 10-18 08:42:42.964 1037 1463 D ActivityManager: cleanUpApplicationRecord -- 1809 10-18 08:42:42.978 1037 1585 I WindowManager: WIN DEATH: Window{890a751 u0 SurfaceView - com.oculus.vrshell/com.oculus.vrshell.MainActivity} ... 10-18 08:42:43.099 1037 1583 I DisplayManagerService: Display device removed: DisplayDeviceInfo{"com.oculus.android_panel_app.AndroidPanelLayer-#main": uniqueId="virtual:com.oculus.systemux,10060,com.oculus.android_panel_app.AndroidPanelLayer-#main,0", 770 x 241, modeId 2, defaultModeId 2, supportedModes [{id=2, width=770, height=241, fps=60.0}], colorMode 0, supportedColorModes [0], HdrCapabilities null, density 160, 160.0 x 160.0 dpi, appVsyncOff 0, presDeadline 16666666, touch NONE, rotation 0, type VIRTUAL, state ON, owner com.oculus.systemux (uid 10060), FLAG_PRIVATE, FLAG_NEVER_BLANK, FLAG_OWN_CONTENT_ONLY} Specifically the 'WIN DEATH' and 'Display Device Removed' However nothing else to go on. As far as I can tell we aren't hitting memory issues or anything either - mem use stays relatively stable throughout. We're on unity 2018.4, Oculus SDK 1.29.1. Happy to upgrade if likely to fix things, but we're near ship so would rather not do so unless it's likely to help! Has anybody seen this / have a suggestion. Any help from devs or the Oculus team would be hugely appreciated Thanks Chris
what does it take for good Art assets in VR game
Context I have experience in making 2D games mostly, but of course, I'm trying my hand at quest development. What does it take to make or know great graphics in VR if you don't have any experience with creating excellent art unity assets for VR? To be more detailed, what to look for or where do I start. I have a little experience with Blender but not for making VR assets.
Has anyone without artistic ability succeeded in developing a game or app?
I want to learn to develop games or apps for the Quest 2 but I have no artistic ability. I would like to know if anyone on here has succeeded in developing games or apps despite not being able to draw or anything. I'm not looking for people that are trying to do so, just those that have succeeded, so that I will know it is possible, and so I can ask questions of them. Thanks!