Search Issue Tracker
Active
Under Consideration for 2022.3.X
Votes
0
Found in
2022.3.57f1
Issue ID
UUM-96343
Regression
No
Crash on UnityMain when running Player which was built on 32-bit architecture with "Direct3D12" set as graphics API
Reproduction steps:
1. Open the “repro_IN-90406“ project
2. Make sure you have “Direct3D12” set as your graphics API (“Edit → Project Settings… → Player → Other Settings → Graphics APIs for Windows“)
3. Open the Build Settings (“File → Build Settings…“)
4. Add “Scenes/SampleScene“ Scene to the build index
5. Change the “Architecture“ parameter to “Intel 32-bit“
6. Press “Build“
7. Once the project is built, run the .exe
8. Observe the crash
Reproducible with: 2022.3.57f1
Not reproducible with: 6000.0.37f1, 6000.1.0b5, 6000.2.0a2
Reproducible on: Windows 10 (22H2), Windows 11 (23H2) (user’s environment)
Not reproducible on: No other environments tested
Note: Not reproducible with Direct3D11 and Vulkan
First few lines of the stack trace:
0x6BD122A4 (UnityPlayer) UnityMain
0x6BD1258E (UnityPlayer) UnityMain
0x6BD1434F (UnityPlayer) UnityMain
0x6BD11437 (UnityPlayer) UnityMain
0x7673FCC9 (KERNEL32) BaseThreadInitThunk
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
Add comment