o3de/o3de-atom-sampleviewer

Atom sample viewer project for the Open 3D Engine

O3DE (Open 3D Engine)

O3DE (Open 3D Engine) is an open-source, real-time, multi-platform 3D engine that enables developers and content creators to build AAA games, cinema-quality 3D worlds, and high-fidelity simulations without any fees or commercial obligations.

Contribute

For information about contributing to Open 3D Engine, visit https://o3de.org/docs/contributing/.

Roadmap

For information about upcoming work and features, please visit https://o3de.org/roadmap. Progress against the roadmap is tracked here.

Download and Install

This repository uses Git LFS for storing large binary files.

Verify you have Git LFS installed by running the following command to print the version number.

git lfs --version 

If Git LFS is not installed, download and run the installer from: https://git-lfs.github.com/.

Install Git LFS hooks

git lfs install

Clone the repository

git clone https://github.com/o3de/o3de.git

Building the Engine

Build requirements and redistributables

For the latest details and system requirements, refer to System Requirements in the documentation.

Windows

• Visual Studio 2019 16.9.2 minimum (All editions supported, including Community): https://visualstudio.microsoft.com/downloads/
  • Check System Requirements for other supported versions.
  • Install the following workloads:
    • Game Development with C++
    • MSVC v142 - VS 2019 C++ x64/x86
    • C++ 2019 redistributable update
• CMake 3.22.0 minimum: https://cmake.org/download/#latest (Release Candidate versions are not supported)

Optional

• Wwise audio SDK
  • For the latest version requirements and setup instructions, refer to the Wwise Audio Engine Gem reference in the documentation.

Quick start engine setup

To set up a project-centric source engine, complete the following steps. For other build options, refer to Setting up O3DE from GitHub in the documentation.

1. Create a writable folder to cache downloadable third-party packages. You can also use this to store other redistributable SDKs.

2. Install the following redistributables:

   • Visual Studio and VC++ redistributable can be installed to any location.
   • CMake can be installed to any location, as long as it's available in the system path.

3. Configure the engine source into a solution using this command line, replacing <your build path>, <your source path>, and <3rdParty package path> with the paths you've created:

   cmake -B <your build path> -S <your source path> -G "Visual Studio 16" -DLY_3RDPARTY_PATH=<3rdParty package path>
   

   Example:

   cmake -B C:\o3de\build\windows -S C:\o3de -G "Visual Studio 16" -DLY_3RDPARTY_PATH=C:\o3de-packages
   

   Note: Do not use trailing slashes for the <3rdParty package path>.

4. Alternatively, you can do this through the CMake GUI:

   1. Start cmake-gui.exe.
   2. Select the local path of the repo under "Where is the source code".
   3. Select a path where to build binaries under "Where to build the binaries".
   4. Click Add Entry and add a cache entry for the <3rdParty package path> folder you created, using the following values:
      1. Name: LY_3RDPARTY_PATH
      2. Type: STRING
      3. Value: <3rdParty package path>
   5. Click Configure.
   6. Wait for the key values to populate. Update or add any additional fields that are needed for your project.
   7. Click Generate.

5. Register the engine with this command:

   scripts\o3de.bat register --this-engine
   

6. The configuration of the solution is complete. You are now ready to create a project and build the engine.

For more details on the steps above, refer to Setting up O3DE from GitHub in the documentation.

Setting up new projects and building the engine

1. From the O3DE repo folder, set up a new project using the o3de create-project command.

   scripts\o3de.bat create-project --project-path <your new project path>
   

2. Configure a solution for your project.

   cmake -B <your project build path> -S <your new project source path> -G "Visual Studio 16"
   

   Example:

   cmake -B C:\my-project\build\windows -S C:\my-project -G "Visual Studio 16"
   

   Note: Do not use trailing slashes for the <3rdParty cache path>.

3. Build the project, Asset Processor, and Editor to binaries by running this command inside your project:

   cmake --build <your project build path> --target <New Project Name>.GameLauncher Editor --config profile -- /m
   

   Note: Your project name used in the build target is the same as the directory name of your project.

This will compile after some time and binaries will be available in the project build path you've specified, under bin/profile.

For a complete tutorial on project configuration, see Creating Projects Using the Command Line Interface in the documentation.

Code Contributors

This project exists thanks to all the people who contribute. [Contribute].

License

For terms please see the LICENSE*.TXT files at the root of this distribution.

o3de-atom-sampleviewer's Issues

RHI/AlphaToCoverage sample only renders a white screen

Describe the bug
The RHI/AlphaToCoverage sample does not render anything but a white box covering the entire Viewport.

Please note that the issue does not occur on Linux.

Please refer to the attached screenshots for more details.

Prerequisite

• O3DE installed from the Stabilization/2205 installer.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load the RHI/AlphaToCoverage sample.

Expected behavior
The sample contents are rendered successfully.

Actual behavior
Only a white screen is rendered.

Screenshots/Video

AlphaToCoverage.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

ASV Samples That Require Baked ShaderVariantAssets Must Check The Registry Key "O3DE/Atom/Shaders/BuildVariants"

For the sake of iteration speed, sometimes engineers set the registry key "O3DE/Atom/Shaders/BuildVariants" to "False" and forget about it.
One day they run ASV Samples like "RHI/IndirectRendering" and the samples fail to run properly because the sample is waiting for some particular ShaderVariantAssets to be ready, but the OnShaderVariantReinitialized() notification never arrives. The engineer can struggle for hours because they forgot to set "O3DE/Atom/Shaders/BuildVariants" back to "True".

Solution:
All ASV Samples that require Baked ShaderVariantAssets must check if the registry key "O3DE/Atom/Shaders/BuildVariants" is enabled. If it is not enabled, then an explicit message should be presented to the user.

By default, the file: "\GIT\o3de\Gems\Atom\Asset\Shader\Registry\atom_shaders.setreg" has such key set to "True".

Standalone/GameLauncher crash when loading RPI/RootConstants sample

Describe the bug
Loading the RPI/RootConstants sample crashes the Standalone (and GameLauncher).
Additionally, the following Assert is displayed prior to the crash:

(System) - Trace::Assert
 D:/workspace/o3de/Gems/Atom/RHI/Code/Source/RHI/ConstantsData.cpp(433): (14476) 'const class AZ::RHI::ConstantsLayout *__cdecl AZ::RHI::ConstantsData::GetLayout(void) const'
(System) - Constants layout is null
(System) - ------------------------------------------------
(System) - 00007FF99EA28B87 (AtomSampleViewer) : AZ::RHI::ConstantsData::ValidateConstantAccess
(System) - D:\AtomSampleViewer\Gem\Code\Source\RootConstantsExampleComponent.cpp (294) : AtomSampleViewer::RootConstantsExampleComponent::DrawModel
(System) - D:\AtomSampleViewer\Gem\Code\Source\RootConstantsExampleComponent.cpp (260) : AtomSampleViewer::RootConstantsExampleComponent::OnTick
(System) - 00007FF6EBB11745 (AtomSampleViewer.GameLauncher) : AZ::Internal::EBusContainer<AZ::TickEvents,AZ::TickEvents,0,2>::Dispatcher<AZ::EBus<AZ::TickEvents,AZ::TickEvents> >::Broadcast<void (__cdecl AZ::TickEvents::*)(float,AZ::ScriptTimePoint) __ptr64,float c
(System) - 00007FF6EBB47E4F (AtomSampleViewer.GameLauncher) : AZ::ComponentApplication::Tick
(System) - 00007FF6EB2C957D (AtomSampleViewer.GameLauncher) : O3DELauncher::Run
(System) - 00007FF6EB2CC30D (AtomSampleViewer.GameLauncher) : WinMain
(System) - d:\a01\_work\6\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl (288) : __scrt_common_main_seh
(System) - 00007FFA09DC7034 (KERNEL32) : BaseThreadInitThunk
(System) - 00007FFA0A042651 (ntdll) : RtlUserThreadStart
(System) - ==================================================================

Please note that the issue does not occur on Linux.

Please refer to the attached screenshots for more details.

Prerequisite

• O3DE installed from the Stabilization/2205 installer.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load the RPI/RootConstants sample.

Expected behavior
The sample loads successfully.

Actual behavior
The Standalone/GameLauncher crashes.

Screenshots/Video

RootConstantsCrash.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

Attachments
error.log
Game.log
error.zip

DynamicDrawExampleComponent.cppp does not compile

The code doesn't compile because the function CreateDynamicDrawContext is called without an argument.
The function needs either a Scene pointer or a RenderPipeline pointer.

New labels needed

Hi!

We would need the priority labels, as well as needs-triage and needs-information labels on this repo.

Thanks!

Update `scripts/PassTree.bv.luac` to use another sample instead of RPI/Shading (removed in #306)

LuxCore was removed which this file was relying on.

@VickyAtAZ may have more details

ASV: RPI ShaderReloadTest only loads a flat red screen, no menu options present

[Migrated from JIRA ATOM-17448]
ASV: RPI ShaderReloadTest only loads a flat red screen, no menu options present

Found in Build:

O3de:
commit a78dcd3177ec441dc1d3329fb2fe71e9b0c4f0f1

ASV:
commit 6037b51

Reproducibility:
100%

Prerequisites:

• Build the above commits and process all assets

Steps to Reproduce:

1. Launch AtomSampleViewerStandalone.exe
2. Go to: Samples > RPI > ShaderReloadTest
3. Observe sample

Expected Result:

• Sample loads with menu options

Actual Result:

• Sample loads to a flat red screen with no menus

[Linux] ASV launcher does not work properly with multiple render pipelines

Describe the bug
After loading one of the samples related to the multiple render pipelines (MultiRenderPipeline, MultiScene, MultiViewSingleSceneAuxGeom) the secondary window is displayed correctly, but the main window view is scaled down and the renders inconsistently.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch the AtomSampleViewer.GameLauncher.
2. Load the MultiRenderPipeline, MultiScene or MultiViewSingleSceneAuxGeom (Samples > RPI).

Expected behavior
Both render pipelines are working as expected.

Actual behavior
The main window view is scaled down and renders inconsistently.

Screenshots/Video

2022-04-12.08-53-18.mp4

Found in Branch
Stabilization/2205 (3e47df2)

Desktop/Device

• Device: PC
• OS: Ubuntu
• Version 20.04
• CPU Intel Core i5-9600k
• GPU Nvidia GeForce RTX 2060
• Memory 16GB

AtomSampleViewer.Private.Static library cannot be built

The member function SetOutputScope is missing from DynamicDrawContext class.

ASV: RPI AssetLoadTest crashes if Lattice Width/Height/Depth is turned up past 50 (only halfway to max value)

[Migrated from JIRA ATOM-17446]
ASV: RPI AssetLoadTest crashes if Lattice Width/Height/Depth is turned up past 50 (only halfway to max value)

Found in Build:

O3de:
commit a78dcd3177ec441dc1d3329fb2fe71e9b0c4f0f1

ASV:
commit 6037b51

Reproducibility:
100%

Prerequisites:

• Build the above commits and process all assets

Steps to Reproduce:

1. Launch AtomSampleViewerStandalone.exe
2. Go to: Samples > RPI > AssetLoadTest
3. (optional) Turn off "Switch Materials Every N Seconds", and "Switch Model Every N Seconds"
4. Increase Lattice Width/Height/Depth to 55

Expected Result:

• ASV remains stable

Actual Result:

• ASV crashes (see attached logs)

Note:
I noticed that the value goes much higher for Lattice Width/Height/Depth than before, used to be 30 I think, now it is 100. Maybe this was increased by mistake?

The Minimum Exposure in the Exposure sample contains a typo

Describe the bug
The Minimum Exposure on the Sidebar contains a typographical error ("Minumum Exposure").

Please note that the issue occurs both in Windows and Linux.

Please refer to the attached video for more details.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load the Exposure sample (Samples -> Features -> Exposure).
3. Read the options on the Sidebar.

Expected behavior
There are no typos on the Sidebar settings.

Actual behavior
There is a typo in Minimum Exposure setting.

Screenshots/Video

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

Culling Debug Window is not functional

Describe the bug
The Culling Debug Window does not show any statistics no matter what options are enabled, which sample is loaded and where the camera points.

Please note that the issue occurs both in Windows and Linux.

Please refer to the attached video for more details.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load any sample (i.e. Samples -> RPI -> CullingAndLod).
3. Open the Culling Debug Window (Culling -> Culling Debug Window).
4. Enable Debug Draw option and all the checkboxes below.
5. Navigate around the sample and/or load other samples.

Expected behavior
Culling Debug Window displays the Culling Jobs Statistics.

Actual behavior
The Culling Debug Window is not functional.

Screenshots/Video

CullingDebugWindow.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

AtomSampleViewer project fails to configure through the terminal when no engine named "o3de" is registered

Describe the bug
AtomSampleViewer project cannot be configured using the terminal when no "o3de" engine is registered. This causes issues when using the o3de installer, as it registers the engine as "o3de-sdk" (or registering the engine with another name).

The workaround is to configure and build ASV using the Installer's Project Manager.

Please note that the issue occurs both in Windows and Linux.

Please refer to the attached files for more details.

Prerequisite

• O3DE installed from the Stabilization/2205 installer.
• No other O3DE engines registered.

Steps to reproduce
Steps to reproduce the behavior:

1. Clone the AtomSampleViewer repository.
2. Attempt to generate the Cmake project by executing the following command in the CLI:
   cmake -B "C:\AtomSampleViewer\build" -S "C:\AtomSampleViewer" -G "Visual Studio 16" -DLY_3RDPARTY_PATH=C:\o3de-packages

Expected behavior
The CMake project is generated successfully.

Actual behavior
The CMake project fails to generated due to missing "o3de" engine.

Screenshots/Video

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

[Linux] AtomSampleViewerStandalone cannot be built

Describe the bug
The "AtomSampleViewerStandalone" executableis not built using the PM or terminal commands. The "AtomSampleViewerStandalone", "AtomSampleViewer.Standalone" or "ALL_BUILD" are not recognized as a target when building via the terminal. Only the GameLauncher can be built as an alternative.

Steps to reproduce
Steps to reproduce the behavior:

1. Clone the project using the following commands:
   git clone https://github.com/o3de/o3de-atom-sampleviewer.git AtomSampleViewer
git pull Stabilization/2205
2. Navigate to the project location and execute the following commands:
   cmake -B build/linux -S . -G "Ninja Multi-Config" -DLY_3RDPARTY_PATH=$HOME/o3de-packages
cmake --build build/linux --target Editor <targets mentioned in the description> --config profile -j 8
3. Launch the Project Manager and rebuild the AtomSampleViewer project.
4. Navigate to "build/linux/bin/profile" location and verify the absence of the "AtomSampleViewerStandalone" executable.

Expected behavior
The "AtomSampleViewerStandalone" executable can be built.

Actual behavior
There is no way to build the "AtomSampleViewerStandalone" executable on Linux.

Found in Branch
Stabilization/2205 (o3de/o3de@3e47df2)

Desktop/Device:

• Device: PC
• OS: Ubuntu
• Version 20.04
• CPU Intel Core i5-9600k
• GPU Nvidia GeForce RTX 2060
• Memory 16GB

[Android] Asset Processor fails to process SubpassInputComposition.shader file for AtomSampleViewer project

Describe the bug
The following Shader Asset job fails processing for the .shader asset:
SubpassInputComposition.shader

Please refer to the attached .log files for more information.

Prerequisites

• AtomSampleViewer is built using --target ALL_BUILD for Windows.
• Android assets are enabled in \o3de\Registry\AssetProcessorPlatformConfig.setreg.

Steps to reproduce.

1. Launch the AssetProcessor.exe from the /AtomSampleViewer/build/bin/profile/ directory.
2. Wait until all the assets are processed.

Expected behavior
All assets are processed without failure.

Actual behavior
The SubpassInputComposition.shader job fails processing.

Screenshot

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205(3e47df2)

Desktop/Device:

• Device: PC
• OS: Windows
• Version: 10
• CPU: Intel Core i5-9600K
• GPU: NVIDIA GeForce RTX 2070
• Memory: 16GB

Additional context
SubpassInputComposition.shader-367477699-19997.log

[Linux] Materials in RPI/DynamicMaterialTest sample are not rendered properly

Describe the bug
Material is not rendered correctly after changing it in the Debug Menu. After switching to Lua or C++ test material, the material assigned to the entity is rendered as a static gray and the dynamic modifications are not occurring like it was observed with the default material.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch the AtomSampleViewer.GameLauncher.
2. Load the DynamicMaterialTest sample (Samples > RPI > DynamicMaterialTest).
3. Change the default material.

Expected behavior
The material is changed and rendered correctly. The dynamic material modifications work as expected.

Actual behavior
Both C++ and Lua test materials are not rendered properly.

Screenshots/Video

2022-04-11.13-09-49.mp4

Found in Branch
Stabilization/2205 (3e47df2)

Desktop/Device:

• Device: PC
• OS: Ubuntu
• Version 20.04
• CPU Intel Core i5-9600k
• GPU Nvidia GeForce RTX 2060
• Memory 16GB

ASV: Shadow Test spot_filter_method Fails With Acne

[Migrated from JIRA ATOM-17145]
Provide a detailed description of the defect here and include any possible workarounds.

Found in Build:

commit a690c76ad4716233f726f60277f72636eebaf295 (HEAD -> development, upstream/development, origin/development)
Author: santorac [email protected]
Date: Wed Jan 12 08:54:22 2022

Reproducibility:

Prerequisites:

Steps to Reproduce:

Run ASV shadowtest script

To get a better look at this issue, modify the shadowtest.bv.lua script to remove the "OpenSample(nil)" command at the end,  so  you are left with the exact settings that fail. Then under "Positional Lights", select the "Red" Control Target, and you can fiddle with the settings from there. I noticed the acne disappears for some "Filtering" values (5-8) only.

Expected Result:

Actual Result:

See acne in attached gif

[Android] Generating Android project for AtomSampleViewer fails

Describe the bug
Running the generate_android_project.py script fails for AtomSampleViewer set as active project with the following error:
Missing key from android project settings for project at C:\o3de-atom-sampleviewer:''android_settings''

Please note that the same script generates the Android project for AutomatedTesting when it is set as active without any issues.

Please refer to the attached logs for more information.

Prerequisites

• AtomSampleViewer project is built for Windows.
• Assets for the Android platform are enabled and have been processed.
• All the required environment variables are set as described in the instructions: https://o3de.org/docs/user-guide/platforms/android/generating_android_project_windows/

In this test the following settings have been used:

SET O3DE_ENGINE_PATH=C:\o3de
SET O3DE_PROJECT_PATH=C:\o3de-atom-sampleviewer
SET O3DE_BUILD_ROOT=C:\o3de-build

SET O3DE_ANDROID_SIGNCONFIG_FILE=%O3DE_BUILD_ROOT%\o3de.keystore
SET O3DE_ANDROID_SIGNCONFIG_STORE_PASSWORD=o3de_android
SET O3DE_ANDROID_SIGNCONFIG_KEY_ALIAS=o3de_key
SET O3DE_ANDROID_SIGNCONFIG_KEY_PASSWORD=o3de_android
SET O3DE_ANDROID_SIGNCONFIG_KEY_SIZE=2048
SET O3DE_ANDROID_SIGNCONFIG_VALIDITY_DAYS=10000
SET O3DE_ANDROID_DN="cn=atom-sample-viewer, ou=o3de, o=LF, c=US"

set O3DE_ANDROID_SDK_PATH=C:\Android\Sdk
set O3DE_ANDROID_NDK_VERSION=22.1.7171670
set O3DE_ANDROID_SDK_API_LEVEL=30
set O3DE_ANDROID_ASSET_MODE=LOOSE
set O3DE_ANDROID_DEPLOY_TYPE=BOTH

Steps to reproduce

1. Generate KeyStore to allow APK signing:
   keytool -genkey -keystore %O3DE_ANDROID_SIGNCONFIG_FILE% -storepass %O3DE_ANDROID_SIGNCONFIG_STORE_PASSWORD% -alias %O3DE_ANDROID_SIGNCONFIG_KEY_ALIAS% -keypass %O3DE_ANDROID_SIGNCONFIG_KEY_PASSWORD% -keyalg RSA -keysize %O3DE_ANDROID_SIGNCONFIG_KEY_SIZE% -validity %O3DE_ANDROID_SIGNCONFIG_VALIDITY_DAYS% -dname %O3DE_ANDROID_DN%
2. Use Python to run generate_android_project.py:
   %O3DE_ENGINE_PATH%\python\python.cmd %O3DE_ENGINE_PATH%\cmake\Tools\Platform\Android\generate_android_project.py --engine-root %O3DE_ENGINE_PATH% --project-path %O3DE_PROJECT_PATH% --build-dir %O3DE_BUILD_ROOT%\android --third-party-path %USERPROFILE%\.o3de\3rdParty --android-sdk-path %O3DE_ANDROID_SDK_PATH% --android-ndk-version %O3DE_ANDROID_NDK_VERSION% --android-sdk-platform %O3DE_ANDROID_SDK_API_LEVEL% --include-apk-assets --asset-mode %O3DE_ANDROID_ASSET_MODE% --signconfig-store-file %O3DE_ANDROID_SIGNCONFIG_FILE% --signconfig-store-password %O3DE_ANDROID_SIGNCONFIG_STORE_PASSWORD% --signconfig-key-alias %O3DE_ANDROID_SIGNCONFIG_KEY_ALIAS% --signconfig-key-password %O3DE_ANDROID_SIGNCONFIG_KEY_PASSWORD%

Expected behavior
Generating the Android project finishes successfully.

Actual behavior
Generating the Android project for AtomSampleViewer fails.

Assets required
https://github.com/o3de/o3de-atom-sampleviewer

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205(3e47df2)

Desktop/Device:

• Device: PC
• OS: Windows
• Version: 10
• CPU: Intel Core i5-9600K
• GPU: NVIDIA GeForce RTX 2070
• Memory: 16GB

Additional context
AndroidLog.txt

[Stabilization Release/22.05.0] Building ALL_BUILD target of AtomSampleViewer project in Debug configuration fails creating executable when building via CMD

Describe the bug
Building the debug configuration of the AtomSampleViewer project's ALL_BUILD target fails resulting in no executable files (like AssetProcessor.exe, Editor.exe) being created when building via the CMD. Please note that the same target seems to fail but actually builds the executables successfully in debug configuration when building via the Visual Studio solution, note the Visual Studio logs attached.

The following error can be seen in the log of the Command Line:

Automatic MOC for target EditorLib
C:/Builds/o3de-atom-sampleviewer/Gem/Code/Source/CommonSampleComponentBase.cpp(255,15): error C2664: 'void AZ::Render::
LightingPreset::ApplyLightingPreset(AZ::Render::ImageBasedLightFeatureProcessorInterface *,AZ::Render::SkyBoxFeaturePro
cessorInterface *,AZ::Render::ExposureControlSettingsInterface *,AZ::Render::DirectionalLightFeatureProcessorInterface
*,const Camera::Configuration &,AZStd::vector<AZ::Render::DirectionalLightFeatureProcessorInterface::LightHandle,AZStd:
:allocator> &,AZStd::intrusive_ptr<AZ::RPI::Material>,AZ::RPI::MaterialPropertyIndex,bool) const': cannot convert argum
ent 7 from 'bool' to 'AZStd::intrusive_ptr<AZ::RPI::Material>' [C:\Builds\o3de-atom-sampleviewer\build\windows_vs2019\o
3de\o3de-atom-sampleviewer-b3671a39\Gem\Code\AtomSampleViewer.Private.Static.vcxproj]
          preset.ApplyLightingPreset(
                ^
  C:/Builds/o3de-atom-sampleviewer/Gem/Code/Source/CommonSampleComponentBase.cpp(262,31): note: No constructor could ta
  ke the source type, or constructor overload resolution was ambiguous
              useAlternateSkybox);
                                ^
  C:\Builds\o3de\Gems\Atom\Feature\Common\Code\Include\Atom/Feature/Utils/LightingPreset.h(91,18): note: see declaratio
  n of 'AZ::Render::LightingPreset::ApplyLightingPreset'
              void ApplyLightingPreset(
                   ^

Please refer to the attached logs for more information.

Steps to reproduce
Run the following CMD commands from the AtomSampleViewer project's directory:
cmake -B build/windows_vs2019 -S . -G "Visual Studio 16" -DLY_3RDPARTY_PATH=C:\o3de-packages
cmake --build build/windows_vs2019 --target ALL_BUILD --config debug -- -m

Expected behavior
The debug build is successful.

Actual behavior
The debug build does not create the executables and errors are printed to the Command Line.

Screenshots
After building via CMD:

After building via VS:

Assets required
https://github.com/o3de/o3de-atom-sampleviewer

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205(3e47df2)

Desktop/Device:

• Device: PC
• OS: Windows
• Version: 10
• CPU: Intel Core i5-9600K
• GPU: NVIDIA GeForce RTX 2070
• Memory: 16GB

Additional context
AtomSampleViewer_Debug_ALL_BUILD.txt
DebugASVErrorListVS2019_failedALL_BUILD.txt
DebugASVoutputWindowVS2019_failedALL_BUILD.txt
DebugASVoutputWindowVS2019successfulStandalone.txt

Atom Sample Viewer build failure

Atom Sample Viewer fails to compile from the following commit

o3de/o3de@701e36f

n file included from /src/github/o3de-atom-sampleviewer/Gem/Code/Source/SampleComponentManager.cpp:83:
/src/github/o3de-atom-sampleviewer/Gem/Code/Source/MeshExampleComponent.h:98:75: error: no member named 'NoLodOverride' in 'AZ::RPI::Cullable'
        AZ::RPI::Cullable::LodOverride m_lodOverride = AZ::RPI::Cullable::NoLodOverride;
                                                       ~~~~~~~~~~~~~~~~~~~^
1 error generated.
[14/6486] Building CXX object o3de-atom-sampleviewer-2dcd6a22/Gem/Cod...Viewer.Private.Static.dir/debug/Source/RHI/MultiThreadComponent.cpp.o

and

src/github/o3de-atom-sampleviewer/Gem/Code/Source/MeshExampleComponent.cpp:268:52: error: no member named 'SetLodOverride' in 'AZ::Render::MeshFeatureProcessorInterface'
                        GetMeshFeatureProcessor()->SetLodOverride(m_meshHandle, m_lodOverride);
                        ~~~~~~~~~~~~~~~~~~~~~~~~~  ^
/src/github/o3de-atom-sampleviewer/Gem/Code/Source/MeshExampleComponent.cpp:277:56: error: no member named 'SetLodOverride' in 'AZ::Render::MeshFeatureProcessorInterface'
                            GetMeshFeatureProcessor()->SetLodOverride(m_meshHandle, m_lodOverride);
                            ~~~~~~~~~~~~~~~~~~~~~~~~~  ^

testdata/objects/cube/cube.azmodel cannot be processed when using the O3DE installer

Describe the bug
If the AtomSampleViewer project was set up using the o3de installer, the testdata/objects/cube/cube.azmodel does not finish processing. This prevents multiple samples to be loaded (i.e. RPI/MultiRenderPipeline, RPI/MultiScene).

Please note, that AssetProcessor is idle while the Waiting For Asset... window is displayed in the AtomSampleViewerStandalone.

The issue does not occur when the ASV was built from the source engine O3DE.

Please refer to the attached video for more details.

Prerequisite

• AtomSampleViewer set up using the Stabilization/2205 O3DE installer

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load Samples/RPI/MultiScene.

Expected behavior
The sample loads succesfully.

Actual behavior
The sample does not load as the cube.azmodel asset did not finish processing.

Screenshots/Video

WaitingForAsset.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

Enable Debug Color is not functional in the DepthOfField sample

Describe the bug
Checking the Enabled Debug Color box does not have any effect in the DepthOfField sample.

Please note that the issue occurs both in Windows and Linux.

Please refer to the attached video for more details.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load the DepthOfField sample (Samples -> Features -> DepthOfField).
3. Check the Enabled Debug Color box on the Sidebar.

Expected behavior
Debug Colors appear in the sample.

Actual behavior
Nothing happens.

Screenshots/Video

DebugColors.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

ASV: Readback RPI sample crashes ASV executable if the "Readback resource dimensions" width value is set above default value

[Migrated from JIRA ATOM-17525]
ASV: Readback RPI sample crashes ASV executable if the "Readback resource dimensions" width value is set above default value

---

Found in Build:

O3de:
commit 0db15cfa0be2d86210a91b8aa761ed413aab824f

ASV:
commit 0db15cfa0be2d86210a91b8aa761ed413aab824f

Reproducibility:
90% occurred on 9 out of 10 attempts, not sure why it succeeded once, maybe it was a specific height/width ratio?

Prerequisites:

• Build the above commits and process all assets

Steps to Reproduce:

1. Launch AtomSampleViewerStandalone.exe
2. Go to: Sample > RPI > Readback
3. Turn up the "Readback resource dimensions" width value past 512
4. Press the "Readback" button

Expected Result:

• ASV remains stable

Actual Result:

• AtomSampleViewerStandalone.exe crashes

Missing or wrong icons for AtomSampleViewer executables

Describe the bug
The AtomSampleViewer.GameLauncher.exe still uses the Lumberyard icon (on Windows) or the generic icon (on Linux) instead of the O3DE one.
Additionally, AtomSampleViewerStandalone.exe uses the generic .exe icon (on Windows, unable to verify on Linux due to #392).

Please refer to the attached screenshots for more details.

Prerequisite

• AtomSampleViewer.GameLauncher and AtomSampleViewerStandalone built.

Steps to reproduce
Steps to reproduce the behavior:

1. Navigate to the folder with ASV executables.
2. Find AtomSampleViewer.GameLauncher.exe and verify its icon.
3. Find AtomSampleViewerStandalone.exe and verify its icon.

Expected behavior
The executable files use correct O3DE icons.

Actual behavior
AtomSampleViewer.GameLauncher.exe uses the Lumberyard icon, while AtomSampleViewerStandalone.exe uses the generic one.

Screenshots/Video

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

ASV: Parallax Feature sample crashes on load

[Migrated from JIRA ATOM-17450]
ASV: Parallax Feature sample crashes on load

O3de:
commit a78dcd3177ec441dc1d3329fb2fe71e9b0c4f0f1

ASV:
commit 6037b51

Reproducibility:
100%

Prerequisites:
Build the above commits and process all assets

Steps to Reproduce:

1. Launch AtomSampleViewerStandalone.exe
2. Go to: Samples > Features > Parallax
3. Observe sample

Expected Result:

• Sample loads

Actual Result:

• ASV crashes (see attached logs)

Missing photosensitive seizure warning for the RPI/SceneReloadSoakTest sample

Describe the bug
The SceneReloadSoakTest sample contains a lot of screen flashing, however there is no photosensitive seizure warning when attempting to load it.

Please note that the issue occurs both in Windows and Linux.

Please refer to the attached video for more details.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load the Exposure sample (Samples -> RPI -> SceneReloadSoakTest).

Expected behavior
A prompt with the photosensitive seizure warning appears.

Actual behavior
The photosensitive seizure warning does not appear.

Screenshots/Video

PhotosensitiveWarning.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

MacOS (Intel): Samples/RPI/AssetLoadTest rendering bug

Several samples from ASV don't render properly in MacOS. I'm attaching the starting rendered frame for "Samples/RPI/AssetLoadTest".
My Machine:
Model Name: MacBook Pro
Model Identifier: MacBookPro16,1
Processor Name: 8-Core Intel Core i9
Processor Speed: 2.3 GHz
Number of Processors: 1
Total Number of Cores: 8
L2 Cache (per Core): 256 KB
L3 Cache: 16 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
System Firmware Version: 1715.81.2.0.0 (iBridge: 19.16.10744.0.0,0)

[Stabilization Release/22.05.0] Building a Pre-built SDK Monolithic Release configuration of AtomSampleViewer project fails

Describe the bug
Pre-built SDK Monolithic Release build of the AtomSampleViewer project fails, resulting in the \bin\Windows\release\Monolithic not being created. The following error can be seen near the middle of the building:

C:/o3de-atom-sampleviewer/Gem/Code/Source/Automation/ScriptManager.cpp(1145,22): error C5233: explicit lambda capture '
message' is not used [C:\o3de-atom-sampleviewer\build\windows_mono\External\o3de-atom-sampleviewer-79f2bcb2\Gem\Code\At
omSampleViewer.Private.Static.vcxproj]
          auto func = [message]()
                       ^

Please refer to the full Command Line log for more information.

Prerequisites

• AtomSampleViewer is already built for Windows in Profile.
• All of the project's assets have been processed.
• Engine, Asset Processor, and the Project Manager are all closed.

Steps to reproduce
Run the following CMD commands from the AtomSampleViewer project's directory:
cmake -B build\windows_mono -S . -DLY_MONOLITHIC_GAME=1 -DCMAKE_INSTALL_PREFIX=C:\o3de-install
cmake --build build\windows_mono --target INSTALL --config release

Expected behavior
The release build is successful.

Actual behavior
The release build does not create the install directory and errors are printed to the Command Line.

Assets required
https://github.com/o3de/o3de-atom-sampleviewer

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205(3e47df2)

Desktop/Device:

• Device: PC
• OS: Windows
• Version: 10
• CPU: Intel Core i5-9600K
• GPU: NVIDIA GeForce RTX 2070
• Memory: 16GB

Additional context
AtomSampleViewer_Release_INSTALL.txt

Compilation is so slow, is there any way to optimize it?

Thank you very much 0.0

RPI/BakedShaderVariant: Sample crashes when exiting the application

Steps to reproduce:

1. Run AtomSampleViewerStandalone
2. Open the sample Samples - > RPI -> BakedShaderVariant
3. Do nothing.
4. Exit the application from the menu File - Exit

The application crashes:

Callstack:

	AtomSampleViewerStandalone.exe!AZ::Debug::Platform::DebugBreak() Line 90	C++
 	AtomSampleViewerStandalone.exe!AZ::Debug::Trace::Assert(const char * fileName, int line, const char * funcName, const char * format, ...) Line 385	C++
 	AtomSampleViewerStandalone.exe!AzFramework::EntityContext::DestroyEntity(AZ::Entity * entity) Line 316	C++
 	[Inline Frame] AtomSampleViewer.dll!AZStd::Internal::INVOKE(bool(AzFramework::EntityContextRequests::*)(AZ::Entity *) &) Line 177	C++
 	[Inline Frame] AtomSampleViewer.dll!AZStd::invoke(bool(AzFramework::EntityContextRequests::*)(AZ::Entity *) &) Line 55	C++
 	[Inline Frame] AtomSampleViewer.dll!AZ::EBusEventProcessingPolicy::Call(bool(AzFramework::EntityContextRequests::*)(AZ::Entity *) &) Line 437	C++
 	AtomSampleViewer.dll!AZ::Internal::EBusContainer<AzFramework::EntityContextRequests,AzFramework::EntityContextRequests,1,1>::Dispatcher<AZ::EBus<AzFramework::EntityContextRequests,AzFramework::EntityContextRequests>>::Event<bool (__cdecl AzFramework::EntityContextRequests::*)(AZ::Entity *),AZ::Entity * &>(const AZ::Uuid & id, bool(AzFramework::EntityContextRequests::*)(AZ::Entity *) && func, AZ::Entity * & <args_0>) Line 146	C++
 	AtomSampleViewer.dll!AtomSampleViewer::DestroyEntity(AZ::Entity * & entity, AZ::Uuid entityContextId) Line 27	C++
 	[Inline Frame] AtomSampleViewer.dll!AtomSampleViewer::CommonSampleComponentBase::ShutdownLightingPresets() Line 135	C++
 	AtomSampleViewer.dll!AtomSampleViewer::BakedShaderVariantExampleComponent::Deactivate() Line 116	C++
 	[Inline Frame] AtomSampleViewer.dll!AZ::Entity::DeactivateComponent(AZ::Component & component) Line 400	C++
 	AtomSampleViewer.dll!AZ::Entity::Deactivate() Line 236	C++
 	[Inline Frame] AtomSampleViewer.dll!AZ::Entity::Reset() Line 105	C++
 	AtomSampleViewer.dll!AZ::Entity::~Entity() Line 97	C++
 	[External Code]	
 	AtomSampleViewerStandalone.exe!AZ::ComponentApplication::Destroy() Line 710	C++
 	AtomSampleViewerStandalone.exe!AzFramework::Application::Stop() Line 256	C++
 	AtomSampleViewerStandalone.exe!AtomSampleViewer::RunGameCommon(int argc, char * * argv, AZStd::function<void __cdecl(void)> customRunCode) Line 356	C++
 	AtomSampleViewerStandalone.exe!main(int argc, char * * argv) Line 14	C++
 	[External Code]	

Black Flicker Seen in AtomSampleViewer Parallax Test Case

Describe the bug
When moving the camera round in AtomSampleViewer's Parallax sample, a black flickering can be seen occasionally. This flicker is actually not random, it's based on camera and light angle. There is now a test case in the automation script ParallaxTest.bv.lua that demonstrates the problem. See #366

Steps to reproduce
In AtomSampleViewer, run the script ParallaxTest.bv.lua

Expected behavior
Test should pass

Actual behavior
Test fails

ASV crashes in IMGUI if RenderTick is not on main thread

[Migrated from JIRA ATOM-16035]
Provide a detailed description of the defect here and include any possible workarounds.

Found in Build:git ea10ef566641efaaed1e3d3d4bff1ad4934833c8 on origin/JobifyRenderTick branch

Reproducibility:100%

Prerequisites: build ASV at the above commit/branch

Steps to Reproduce:Launch ASV

Expected Result:ASV runs normally

Actual Result:ASV crashes access a null pointer in IMGUI.

The currentWindow pointer in the global Imgui state is null.

Issues when loading RPI/AuxGeom sample

Describe the bug
The following issues occur when loading the RPI/AuxGeom sample on a specific platform:

• Windows:
  Loading the RPI/AuxGeom sample takes over 15 minutes on a mid-range machine. During that time, the Standalone is frozen and unusable.

• Linux:
  Loading the RPI/AuxGeom sample crashes the AtomSampleViewer.GameLauncher (we were unable to verify on the Standalone due to #392).

Please note that the logs are not generated for the Linux crash.

Prerequisite

• AtomSampleViewer built.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load Samples/RPI/AuxGeom.

Expected behavior
The sample loads succesfully.

Actual behavior
Windows:

• The Standalone freezes for a very long time (over 15 minutes) before loading the sample.

Linux:

• The GameLauncher crashes.

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

Windows:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

Linux:

• Device: PC
• OS: Ubuntu
• Version 20.04
• CPU Intel Core i5-9600k
• GPU Nvidia GeForce RTX 2060
• Memory 16GB

ASV Vulkan Full Test Suite Crashes Device Lost

[Migrated from JIRA ATOM-17400]
When I run ASV full test suite on vulkan it almost always crashes with "Device Lost" during the "FastCheckSample" stages. It seems like this crash does not happen when the cache was deleted and freshly built. But then any subsequent runs will crash. But I'm not sure this is true 100%.

Found in Build:

Reproducibility:

Prerequisites:

Steps to Reproduce:

Run ASV full test suite on vulkan.

Expected Result:

Complete all test cases.

Actual Result:

Device Lost and crash.

Changing the Quality Level does not have any effect in the DepthOfField sample

Describe the bug
Modifying the Quality Level setting does not have any effect in the DepthOfField sample.

Please note that the issue occurs both in Windows and Linux.

Please refer to the attached video for more details.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load the DepthOfField sample (Samples -> Features -> DepthOfField).
3. Change the Quality Level to 0 on the Sidebar.
4. Change the Quality Level back to 1 on the Sidebar.

Expected behavior
Quality Level changes accordingly to the selected value.

Actual behavior
Nothing happens.

Screenshots/Video

QualityLevel.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

The Bloom sample default settings are too intense

Describe the bug
The Bloom sample looks exaggerated. Most of the color bars are white while they should be more diverse, with preserved color shades, progressively brighter from left to right.

Additionally, the default Bloom settings seem to be too strong, as enabling Bloom without changing these, results in the entire Viewport being overblown to the point of showing a white screen.

Please refer to the attached video for more details.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load the Bloom samples (Samples -> Features -> Bloom).
3. Check the Enable box on the Sidebar.

Expected behavior
The default Bloom settings have moderate intensity. Color bar brightness is increased gradually from left to right.

Actual behavior
The default Bloom settings are too intense. Color bar brightness change is abrupt, with most of the bars being white.

Screenshots/Video

BloomDefaultSettings.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

ASV: Auxgeom tranparency is darker

[Migrated from JIRA ATOM-17269]
ASV screenshot test is failing
!auxgeom_asv.PNG!

Found in Build: o3de/development commit 2560d6b41e1f4ae85d2ae773ed70d56badeae1a7

Reproducibility:

Prerequisites:

Steps to Reproduce:

Expected Result:

Actual Result:

AtomSampleViewer: Samples That Require Baked ShaderVariantAssets Must Check The Registry Key "O3DE/Atom/Shaders/BuildVariants"

[Migrated from JIRA ATOM-17192]
Description:

See github issue: [https://github.com//issues/324]

 

Details:

Acceptance Criteria:

Additional Information:

[Linux] AtomTest fails to build via CLI and Ubuntu freezes after attempting to build it via Project Manager

Describe the bug
System freezes after a few minutes of building AtomTest project via the Project Manager. A hardware reset is required for the system to recover. When attempting to build the project using CLI, building fails and a "ninja: build stopped: subcommand failed" error is displayed.

Steps to reproduce
Steps to reproduce the behavior:

1. Clone the project using the following commands:
   git clone https://github.com/o3de/o3de-atomtest.git
   git pull Stabilization/2205
2. Launch the Project Manager, press New Project> Add Existing Project.
3. Select the AtomTest project and add it to the Project Manager.
4. Press Build Project> Build Now.

Steps to build via the CLI:

1. Clone the project using the following commands:
   git clone https://github.com/o3de/o3de-atomtest.git
   git pull Stabilization/2205
2. Move to the AtomTest folder and build the project using following commands:
   cmake -B build/linux -S . -G "Ninja Multi-Config" -DLY_3RDPARTY_PATH=$HOME/o3de-packages
   cmake --build build/linux --target Editor AtomTest.GameLauncher --config profile -j 8

Expected behavior
The project build successfully. The system is responsive.

Actual behavior
The project fails to build via the CLI. The system freezes after a few of minutes of building via the Project Manager.

Found in Branch
Stabilization_2205 (3e47df2)

Desktop
• Device: PC
• OS: Ubuntu
• Version: Ubuntu 20.04.4 LTS
• CPU Intel Core i7-9700K
• GPU Nvidia GeForce RTX 2070
• Memory 16GB

Warning is displayed after creating MaterialEditorTest type of material

Describe the bug
After creating the MaterialEditorTest material, "No per-object ShaderResourceGroup found" warning is displayed.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch the Material Editor.
2. Create a new material using the MaterialEditorTest type.

Expected behavior
The MaterialEditorTest material is created without issues.

Actual behavior
"No per-object ShaderResourceGroup found" warning is displayed upon creation of the material.

Screenshots/Video

2022-04-12.10-09-00.mp4

Found in Branch
Stabilization/2205 (3e47df2)

Desktop/Device

• Device: PC
• OS: Ubuntu
• Version 20.04
• CPU Intel Core i5-9600k
• GPU Nvidia GeForce RTX 2060
• Memory 16GB

Settings categories names are blank for multiple materials

Describe the bug
Multiple materials (ReflectionProbeVisualization, ShadowCatcher and HotReloadTest) categories are blank and without any tooltips.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch the Material Editor.
2. Create the ReflectionProbeVisualization material.
3. Look at the Inspector pane.

Expected behavior
Each settings category has a proper name and a tooltip.

Actual behavior
Settings category names are blank and tooltips are not displayed.

Screenshots/Video

2022-04-12.12-32-47.mp4

Found in Branch
Stabilization/2205 (3e47df2)

Desktop/Device

• Device: PC
• OS: Ubuntu
• Version 20.04
• CPU Intel Core i5-9600k
• GPU Nvidia GeForce RTX 2060
• Memory 16GB

[Linux] Incorrect rendering in MaterialHotReloadTest sample

Describe the bug
Colors are not rendered correctly in the MaterialHotReloadTest sample. The default color for the stripes should be gray instead of red. The shader variant field is rendered as black rectangle. Changing the stripes color to blue results in rendering the whole square as black.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch the AtomSampleViewer.GameLauncher.
2. Load the MaterialHotReloadTest sample (Samples > RPI > MaterialHotReloadTest).
3. Change the color of the material.

Expected behavior
Colors are rendered correctly. The shader variant field is always readable.

Actual behavior
Blue color is rendered as black. Grey color is rendered as red.

Screenshots/Video

HotReload.mp4

Found in Branch
Stabilization/2205 (3e47df2)

Desktop/Device:

• Device: PC
• OS: Ubuntu
• Version 20.04
• CPU Intel Core i5-9600k
• GPU Nvidia GeForce RTX 2060
• Memory 16GB

ASV: RPI Multiscene sample hangs indefinitely load

[Migrated from JIRA ATOM-17451]
ASV: RPI Multiscene sample crashes on load

O3de:
commit a78dcd3177ec441dc1d3329fb2fe71e9b0c4f0f1

ASV:
commit 6037b51

Reproducibility:
100%

Prerequisites:

• Build the above commits and process all assets

Steps to Reproduce:

1. Launch AtomSampleViewerStandalone.exe
2. Go to: Samples > Features > Multiscene
3. Observe sample

Expected Result:

• Sample loads

Actual Result:

• Sample never loads and hangs indefinitely until canceled (see attached)

Asset Processor failure on RenderTexture.pass in AtomSampleViewer on Linux

Describe the bug
When running AssetProcessor on Linux for Atom Sample Viewer, job failure occurs with RenderTexture.pass. It also appears that this affects any .pass files

To Reproduce
Steps to reproduce the behavior:

Create a linux project for o3de-atom-sampleviewer on Ubuntu 20.04
Build o3de-atom-sampleviewer for linux with the profile configuration
Launcher AssetProcessorBatch
Note the error in the output log

Expected behavior
No error occurs related to .pass

Screenshots

AssetProcessor: JOB LOG: 8/25/21 10:38 AM | ERROR | Failed processing /src/github/o3de-atom-sampleviewer/Passes/RenderTexture.pass from Error
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | ERROR | CreateJobs of Passes/RenderTexture.pass has failed. from Error
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | ERROR | This is often because the asset is corrupt. from Error
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | ERROR | Please load it in the editor to see what might be wrong. from Error
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | Info | AssetBuilder: Source = /src/github/o3de-atom-sampleviewer/Passes/RenderTexture.pass from AssetBuilder
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | Info | AssetBuilder: Platforms = pc from AssetBuilder
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | Info | 1 errors, 0 warnings from AssetBuilder
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | ERROR | PassBuilder: Trace::Error from AssetBuilder
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | ERROR | >	/src/github/o3de/Gems/Atom/RPI/Code/Source/RPI.Builders/Pass/PassBuilder.cpp(102): 'bool AZ::RPI::AddDependency(AZ::RPI::FindPassReferenceAssetParams &, AssetBuilderSDK::JobDescriptor *)' from AssetBuilder
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | ERROR | >	Could not find referenced file [shaders/luxcore/rendertexture.shader] from AssetBuilder
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | DEBUG | Job request written to /src/github/o3de-atom-sampleviewer/user/AssetProcessorTemp/JobTemp-sUFTFz/request.xml from Debug
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | DEBUG | To re-run this request manually, run AssetBuilder with the following parameters: from Debug
AssetProcessor: JOB LOG: 8/25/21 10:38 AM | DEBUG | -task=create -id="" -project-name="AtomSampleViewer" -project-cache-path="/src/github/o3de-atom-sampleviewer/Cache" -project-path="/src/github/o3de-atom-sampleviewer" -engine-path="/src/github/o3de" -port 45644 -input="/src/github/o3de-atom-sampleviewer/user/AssetProcessorTemp/JobTemp-sUFTFz/request.xml" -output="/src/github/o3de-atom-sampleviewer/user/AssetProcessorTemp/JobTemp-sUFTFz/response.xml" --regset="/Amazon/AzCore/Bootstrap/engine_path=/src/github/o3de" from Debug

ASV: RPI DynamicMaterialTest crashes if Lattice Width/Height/Depth is turned up past 50

[Migrated from JIRA ATOM-17447]
Provide a detailed description of the defect here and include any possible workarounds.

Found in Build:

O3de:
commit a78dcd3177ec441dc1d3329fb2fe71e9b0c4f0f1

ASV:
commit 6037b51

Reproducibility:
100%

Prerequisites:

• Build the above commits and process all assets

Steps to Reproduce:

1. Launch AtomSampleViewerStandalone.exe
2. Go to: Samples > RPI > DynamicMaterialTest
3. Increase Lattice Width/Height/Depth to 55

Expected Result:

• ASV remains stable

Actual Result:

• ASV crashes (see attached logs)

Note:
I noticed that the value goes much higher for Lattice Width/Height/Depth than before, used to be 30 I think, now it is 100. Maybe this was increased by mistake?

Linker errors against engine libraries when building "AtomSampleViewerStandalone" project

Steps:
Followed steps from .

When building the project, 3 projects fail due to linker errors.

Example of build output:

6>------ Build started: Project: AtomSampleViewerStandalone, Configuration: debug x64 ------
6>Vcpkg is unable to link because we cannot decide between Release and Debug libraries. Please define the property VcpkgConfiguration to be 'Release' or 'Debug' (currently 'debug').
6>LINK : fatal error LNK1104: cannot open file '$<$<CONFIG:profile>:D:\Users\<Folder>\o3de\install\lib\Windows\profile\AtomCore.lib>'

Seems the path is in correct. Not sure where the "$<$CONFIG:profile: " bit comes from.

NOTE: I have ensured that the asset processor was not running when trying to build this solution.

Minimum and Maximum Exposures are inverted in the Exposure sample

Describe the bug
The Minimum and Maximum Exposure settings are inverted.
At the moment, increasing the Minimum Exposure results in the scene to appear darker, and decreasing the Maximum Exposure brightens the scene.

Please note that the issue occurs both in Windows and Linux.

Please refer to the attached video for more details.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Load the Exposure sample (Samples -> Features -> Exposure).
3. Increase the Minimum Exposure on the Sidebar.
4. Decrease the Maximum Exposure on the Sidebar.

Expected behavior
Increasing the Minimum Exposure brightens the scene. Decreasing the Maximum Exposure darkens the scene.

Actual behavior
Increasing the Minimum Exposure darkens the scene. Decreasing the Maximum Exposure brightens the scene.

Screenshots/Video

MinMaxExposure.mp4

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB

RPI/StreamingImage sample uses incorrect textures for Hot Reloading Test

Describe the bug
Textures used in the Hot Reloading Test are incorrect. Instead of streaming3.dds and streaming11.dds textures, green and yellow rectangles are displayed.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch the AtomSampleViewer.GameLauncher.
2. Load the StreamingImage (Samples > RPI > StreamingImage).

Expected behavior
The streaming3.dds and streaming11.dds textures are used in the Hot Reloading Test.

Actual behavior
Green and yellow rectangles are used instead.

Screenshots/Video

2022-04-12.09-13-12.mp4

Found in Branch
Stabilization/2205 (3e47df2)

Desktop/Device

• Device: PC
• OS: Ubuntu
• Version 20.04
• CPU Intel Core i5-9600k
• GPU Nvidia GeForce RTX 2060
• Memory 16GB

ASV: "Shadow" Feature sample hangs then causes AtomSampleViewer to crash when user cancels "Waiting for assets..." dialog

[Migrated from JIRA ATOM-17452]
ASV: RPI Multiscene sample crashes on load

O3de:
commit a78dcd3177ec441dc1d3329fb2fe71e9b0c4f0f1

ASV:
commit 6037b51

Reproducibility:
100%

Prerequisites:

• Build the above commits and process all assets

Steps to Reproduce:

1. Launch AtomSampleViewerStandalone.exe
2. Go to: Samples > Features >Shadow
3. Wait for asset to finish processing
4. Select "Cancel" on the "Waiting for assets..." dialog

Expected Result:

• Sample loads

Actual Result:

• Sample never loads and hangs indefinitely until canceled (see attached)

Launching AtomSampleViewerStandalone displays 3 warnings in the command line terminal

Describe the bug
The following warnings appear in the command line terminal after launching the AtomSampleViewerStandalone.exe:

Memory: Trace::Warning
 D:/workspace/o3de/Code/Framework/AzCore/AzCore/Memory/AllocationRecords.cpp(420): 'void __cdecl AZ::Debug::AllocationRecords::SetMode(enum AZ::Debug::AllocationRecords::Mode)'
Memory: Records recording was disabled and now it's enabled! You might get assert when you free memory, if a you have allocations which were not recorded!
Memory: ==================================================================

SettingsRegistryMergeUtils:
==================================================================
SettingsRegistryMergeUtils: Trace::Warning
 D:/workspace/o3de/Code/Framework/AzCore/AzCore/Settings/SettingsRegistryMergeUtils.cpp(686): 'bool __cdecl AZ::SettingsRegistryMergeUtils::MergeSettingsToRegistry_ConfigFile(class AZ::SettingsRegistryInterface &,class AZStd::basic_string_view<char,struct AZStd::char_traits<char> >,const struct AZ::SettingsRegistryMergeUtils::ConfigParserSettings &)'
SettingsRegistryMergeUtils: Unable to open file "D:\AtomSampleViewer\Cache\pc\user.cfg"
SettingsRegistryMergeUtils: ==================================================================

AssetProcessorConnection::ConnectThread:
==================================================================
AssetProcessorConnection::ConnectThread: Trace::Warning
 D:/workspace/o3de/Code/Framework/AzFramework/AzFramework/Network/AssetProcessorConnection.cpp(231): 'void __cdecl AzFramework::AssetSystem::AssetProcessorConnection::ConnectThread(void)'
AssetProcessorConnection::ConnectThread: Network connection attempt failure, Connect returned error AzSockError::eASE_ECONNREFUSED
AssetProcessorConnection::ConnectThread: ==================================================================

Please note that we were unable to verify the issue on Linux due to #392.

Please refer to the attached screenshots for more details.

Prerequisite

• O3DE installed from the Stabilization/2205 installer.

Steps to reproduce
Steps to reproduce the behavior:

1. Launch AtomSampleViewerStandalone.exe.
2. Switch focus to the CLI.

Expected behavior
There are no warnings in the CLI.

Actual behavior
Three warnings are displayed in the CLI.

Screenshots/Video

Found in Branch
ASV: Stabilization/2205(3efc7e3)
O3DE: Stabilization/2205:Installer

Desktop/Device:

• Device: PC
• OS: Windows
• Version 10
• CPU AMD Ryzen 5 3600
• GPU Nvidia RTX 2060 SUPER
• Memory 16GB