santorac
santorac
If you have non-ASCII characters in an AZSL source file, the compiler will report an obscure error message with no line number information: "bad conversion" Try adding the following comment...
O3DE already uses the latest release of DXC: 1.6.2112. This includes preview support for the new HLSL 2021 feature set (see https://devblogs.microsoft.com/directx/announcing-hlsl-2021/) but AZSLc does not support these new features....
Run a command like "azslc.exe --namespace dx MyShader.azsl". It will report an error "input file could not be opened". If you step through in a debugger, you'll see that the...
Work is being done on a branch to add general support for bindless resources in the Atom renderer (see https://github.com/o3de/o3de/pull/8410). This required some updates to AZSLc to support an unlimited...
Run the PassTree.bv.lua test script. It reports the following error message. ``` PassSystem: Trace::Error D:/o3de/Gems/Atom/RPI/Code/Source/RPI.Public/Pass/ParentPass.cpp(145): 'void __cdecl AZ::RPI::ParentPass::RemoveChild(class AZStd::intrusive_ptr)' PassSystem: Do not remove child passes outside of the removal, reset,...
I run the full test suite and got this result. Notice it says "PASSED" at the top but has an error listed in the results below. 
Shadows are missing on MultiRenderPipeline test. Failing screenshots include: - TwoCameras_window2.png - NoDOF_window2.png - WithDOF_window2.png All three screenshot failures look similar to this: 
## What does this PR do? Debugging some ImGui issues was difficult because multiple render pipelines were handling mouse input, but only one of them actually used ImGui features. Note...