I am getting a catastrophic failure opening the pix.

Are you able to open it?

Yes, I re-downloaded and it opens successfully for me. My PIX says June 2023 Update 2 (2261.4304).

Would a new PIX help? Or I can try zipping the PIX file -- but I can't imagine bit corruption is an issue here during download.

I am still getting catastrophic failures opening both captures. :( I can try upgrading to your version, but right now I am locked to this version (March 2023 Update 2) to avoid more issues with Unity and Unreal.

Could you try with March 2023 Update 2 by any chance?

If not, I am going to need a bit more of time for this.

Thank you!

Hi Jesus. Unity 2022.3.10 LTS requires the version we are on. My understanding is that GDKs can be installed side by side. Unity only uses the version “required” by the Editor version.

Any updates for this bug? Thank you.

I have been analyzing both captures, but it seems all frames are correct? Could you please check this, and indicate what's the frame that's showcasing the flickering in pix1 or pix3?

By the way, both captures have blur

I have been analyzing both captures, but it seems all frames are correct? Could you please check this, and indicate what's the frame that's showcasing the flickering in pix1 or pix3?
I noticed that the artifacts do not appear in the captured screenshot. I wasn't sure if this was a timing issue on my part and when I paused it. I will recapture or see if I can figure out what frame it is -- not sure how to do that but I will try.

By the way, both captures have blur
Do you mean motion blur, or blur in the Noesis output? Not sure what this means.

The above example is simpler (no blur).

I understood by this, that one of the captures didn't have blur (effect) but both have.

The captures reveal an performance issue (common to PC and XBox) that we are going to fix, but yes, having another capture showing the flickering issue is definitely going to help us a lot.

This PIX should have BackgoundEffectBlur disabled: https://stellarconquest.blob.core.windows.net/tmp/noesis/pix3.xpix In the video you can see that the blurring is off, at least visually.

Is this PIX reproducing the flickering issue? That's what I need :)

I will check this later

I am unable to capture the flickering within a PIX dump. I tried 20 exports and each of them fail to capture the flicker -- or at least I don't see it in the PIX screenshot. I have some observations related to the behavior:

• If BackgroundEffectBlur is DISABLED, the only time the flickering behavior manifests is if an active secondary RenderTexture is used with Noesis via a TextureSource.

• On the PC platform, a newly created RenderTexture is initialized to clear or it is initialized to a valid state before it is displayed. But on XBOX it contains an uninitialized state, which can look like a visual glitch before the RenderTexture is updated by a camera. A Noesis TextureSource assigned to a Rectangle will briefly show this uninitialized state. The solution is to initialize RenderTexture via a color BLT on XBOX before assigning it to a Noesis TextureSource. This change has eliminated most 'pops' of bad visual state, but it does not resolve the flickering.

I'm trying to think of what I can do. What about sending an image of the entire game? It is 22.3 GB, and it can be deployed directly to the GDK. Could this work?

-

A while back, there was an issue with adorner elements resizing repeatedly (https://www.noesisengine.com/bugs/view.php?id=2615 ) -- maybe that is what I am seeing here in this video?
https://stellarconquest.blob.core.windows.net/tmp/noesis/XBOXSX_Video_3.mp4

I'm just trying to figure out what could cause this on XBOX but not PC.

• removed * nevermind.

The fact that you can't capture this with PIX, makes me think that this is a "timing" issue in the GPU. This could be related to barriers, and the render texture not properly transitioned from render target to texture. I think our code is correct on this side but I need to carefully verify this.

Do you think you can reproduce this issue in a minimal sample? This would help us a lot to narrow the cases that can lead to this issue,

Although I couldn't reproduce, this is quite similar to 0002776 and I have already fixed for 3.2.3, please reopen if needed