View Issue Details

IDProjectCategoryView StatusLast Update
0004634NoesisGUIUnitypublic2026-01-15 20:43
Reportereric_lucky Assigned Tojsantos  
PriorityhighSeveritymajor 
Status resolvedResolutionfixed 
Product Version3.2.10 
Target Version3.2.11Fixed in Version3.2.11 
Summary0004634: Multi-Pass rendering cause World Space UI to duplicate after upgrading to 3.2.10
Description

Since upgrading our project from Noesis 3.2.7 to 3.2.10, Multi-Pass rendering has been broken on Oculus PC platform. Other platforms seem unaffected.
WorldSpaceUI are now rendering separately for each eye and have a different angle in each eye camera, causing them to be visibly duplicated.

PlatformWindows

Activities

jsantos

jsantos

2025-12-11 01:49

manager   ~0011593

Last edited: 2025-12-11 01:49

  • Is single pass still working well?
  • Please, indicate Unity version and pipeline
  • And confirm only Noesis was updated and not Unity
eric_lucky

eric_lucky

2025-12-11 15:28

reporter   ~0011601

  • Single pass is still working well (but not a solution for us at the moment)
  • 2022.3.62f2 with URP
  • Upgrading Noesis has been done on that version and multi-pass was functional on 3.2.7
jsantos

jsantos

2025-12-12 02:34

manager   ~0011606

Thanks for the information. Another question, please confirm this is using the Oculus XR Plugin and not OpenXR Plugin.

eric_lucky

eric_lucky

2025-12-12 13:30

reporter   ~0011613

We are using the Oculus XR Plugin.
In case it is relevant, our NoesisView Injection Point is set to Before Rendering Post Processing.

eric_lucky

eric_lucky

2025-12-16 18:58

reporter   ~0011646

Hello Jesús,

Do you have an update or ETA on this issue ?
It's become a blocker on our end.

Thank you

jsantos

jsantos

2025-12-16 23:59

manager   ~0011647

Hi Eric,

We’ve identified the issue, but the solution is not trivial. In version 3.2.9, we introduced an optimization that breaks some of our assumptions in a few edge cases, including this one involving the Oculus plugin.

This will take a bit more time than initially expected, and with the Christmas holidays in between, I don’t think we’ll be able to provide a new version with this fully resolved until early next year.

I’ll try to provide a hotfix ahead of the next release.

jsantos

jsantos

2026-01-15 20:43

manager   ~0011697

Fixed in r16489

Issue History

Date Modified Username Field Change
2025-12-10 22:54 eric_lucky New Issue
2025-12-11 01:48 jsantos Assigned To => jsantos
2025-12-11 01:48 jsantos Status new => assigned
2025-12-11 01:49 jsantos Note Added: 0011593
2025-12-11 01:49 jsantos Status assigned => feedback
2025-12-11 01:49 jsantos Note Edited: 0011593
2025-12-11 15:28 eric_lucky Note Added: 0011601
2025-12-11 15:28 eric_lucky Status feedback => assigned
2025-12-12 02:32 jsantos Target Version => 3.2.11
2025-12-12 02:34 jsantos Note Added: 0011606
2025-12-12 02:34 jsantos Status assigned => feedback
2025-12-12 13:30 eric_lucky Note Added: 0011613
2025-12-12 13:30 eric_lucky Status feedback => assigned
2025-12-15 14:34 eric_lucky Priority normal => high
2025-12-16 18:58 eric_lucky Note Added: 0011646
2025-12-16 23:59 jsantos Note Added: 0011647
2026-01-15 20:43 jsantos Status assigned => resolved
2026-01-15 20:43 jsantos Resolution open => fixed
2026-01-15 20:43 jsantos Fixed in Version => 3.2.11
2026-01-15 20:43 jsantos Note Added: 0011697