@rpalandri
@motorsep
Hi again. Still haven't been able to make much progress on this.
I'd like to do a recap of what I have so far, just in case.
The situation is that I am using UMG widgets in world space and I see a lot of aliasing (more than I'd expect with MSAA x4) in images, text and the widget borders themselves.
Here you can see a screenshot:
When actually using the GearVR headset of course the artifacts are further amplified.
While text and image aliasing might have fixes that are unrelated to MSAA, you can see the orange rect which is a bare minimum UMG widget displayed in world space. The edges are pretty jagged. And this is what makes me think MSAA could be off.
BTW @motorsep I am not using multi view. At least not that I know of: it is not checked under project settings.
Another interesting thing is that in Project Settings, I do not have GLES3 checked but according to the adb logs which I posted on a previous comment, the still seems to be running on GLES3 instead of 2.
Now on to the current hypotheses:
1. Is MSAA on? Or why are the rect edges so jagged?
I don't know. We did confirm that:
a. The adb log spits out: "LogRHI: GL_EXT_multisampled_render_to_texture"
This seems to imply that multisampling is supported.
b. The adb log spits out: "LogHMD: Enabling r.MobileOnChipMSAA, previous value 0"
This seems to imply that MSAA is being turned on when running on GearVR mode. Though it does not tell what level of MSAA (2,4,8?).
I was not able confirm that:
glFramebufferTexture2DMultisampleEXT(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + RenderTargetIndex, RenderTarget->Target, RenderTarget->Resource, MipmapLevels[RenderTargetIndex], 2);
is being called however. I tried downloading the source for UE, adding log statements around the above and compiling the engine. The engine compiles, the editor starts up and I am able to open my project. But when I try to package for Android it errs out saying there are a lot of missing files (related to all sorts of subsystems in the engine, like physics). So not sure what I'm doing wrong since I followed the instructions on Epics site to run from source.
2. Does mipmapping and filtering make a difference for the images?
Again, not sure... I'd expect it should but it is not clear to me if changing parameters from the Texture editor should be visible immediately even inside the general editor. For instance, if I change Mip Gen Settings, Texture Group or Filtering, I see no difference in the image. I also hit Save just in case (since I don't know if changing the settings takes effect before hitting save) and nothing seems different.
3. Would Stereo Layers help?
I'm actually gonna give this a try, since I tried the sample project in the thread @motorsep
linked to and it definitely looks good. Also I was under the false impression that stereo layers required the surface tracking the headset but from the example project it is clearly not the case :).
Again, not sure. The doc link @motorsep provided is of little use: like many areas in the UE docs, it appears to simply be the generated doc from the source code, which merely lists method names without any context on how to use.
From the second link @motorsep sent, what I gathered so far is that stereo layers are meant to place HUD-like elements that track with the headset. But this would not serve my use case since the cards I show in the image are to stay put in their world positions. The player can stare around in the world and stare at the cards and activate them with their gaze, but the cards themselves should not follow the camera or headset.
Last, another thing I notice when running on the device (the Galaxy S6), is that the black eye vignettes stutter a lot as I move the phone around. But I'm not sure this might have anything to do with the aliasing.
@motorsep
Hi again. Still haven't been able to make much progress on this.
I'd like to do a recap of what I have so far, just in case.
The situation is that I am using UMG widgets in world space and I see a lot of aliasing (more than I'd expect with MSAA x4) in images, text and the widget borders themselves.
Here you can see a screenshot:
When actually using the GearVR headset of course the artifacts are further amplified.
While text and image aliasing might have fixes that are unrelated to MSAA, you can see the orange rect which is a bare minimum UMG widget displayed in world space. The edges are pretty jagged. And this is what makes me think MSAA could be off.
BTW @motorsep I am not using multi view. At least not that I know of: it is not checked under project settings.
Another interesting thing is that in Project Settings, I do not have GLES3 checked but according to the adb logs which I posted on a previous comment, the still seems to be running on GLES3 instead of 2.
Now on to the current hypotheses:
1. Is MSAA on? Or why are the rect edges so jagged?
I don't know. We did confirm that:
a. The adb log spits out: "LogRHI: GL_EXT_multisampled_render_to_texture"
This seems to imply that multisampling is supported.
b. The adb log spits out: "LogHMD: Enabling r.MobileOnChipMSAA, previous value 0"
This seems to imply that MSAA is being turned on when running on GearVR mode. Though it does not tell what level of MSAA (2,4,8?).
I was not able confirm that:
glFramebufferTexture2DMultisampleEXT(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + RenderTargetIndex, RenderTarget->Target, RenderTarget->Resource, MipmapLevels[RenderTargetIndex], 2);
is being called however. I tried downloading the source for UE, adding log statements around the above and compiling the engine. The engine compiles, the editor starts up and I am able to open my project. But when I try to package for Android it errs out saying there are a lot of missing files (related to all sorts of subsystems in the engine, like physics). So not sure what I'm doing wrong since I followed the instructions on Epics site to run from source.
2. Does mipmapping and filtering make a difference for the images?
Again, not sure... I'd expect it should but it is not clear to me if changing parameters from the Texture editor should be visible immediately even inside the general editor. For instance, if I change Mip Gen Settings, Texture Group or Filtering, I see no difference in the image. I also hit Save just in case (since I don't know if changing the settings takes effect before hitting save) and nothing seems different.
3. Would Stereo Layers help?
I'm actually gonna give this a try, since I tried the sample project in the thread @motorsep
linked to and it definitely looks good. Also I was under the false impression that stereo layers required the surface tracking the headset but from the example project it is clearly not the case :).
From the second link @motorsep sent, what I gathered so far is that stereo layers are meant to place HUD-like elements that track with the headset. But this would not serve my use case since the cards I show in the image are to stay put in their world positions. The player can stare around in the world and stare at the cards and activate them with their gaze, but the cards themselves should not follow the camera or headset.
Last, another thing I notice when running on the device (the Galaxy S6), is that the black eye vignettes stutter a lot as I move the phone around. But I'm not sure this might have anything to do with the aliasing.
