Search Issue Tracker
Won't Fix
Won't Fix in 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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2022.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.