Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.42f1
2021.3.18f1
2022.2.5f1
2023.1.0b2
2023.2.0a14
Issue ID
UUM-25512
Regression
No
Performance issues when instantiating a recognizer under UnityEngine.Windows.Speech
Reproduction steps:
# Open the attached project “RecognizerIssue”
# In the project, navigate to "Assets/Scenes" and open "Sample Scene"
# Open the profiler (Window → Analysis → Profiler)
# In the CPU Usage module disable everything except Scripts
# Enter Play Mode
Expected result: Performance stays consistent
Actual result: Around frame 100 there is a large spike in the CPU usage section of the profiler
Reproducible with: 2020.3.42f1, 2021.3.18f1, 2022.2.5f1, 2023.1.0b2
Reproducible on: Windows 10
-
tharakan
Jan 28, 2023 07:24
https://157.245.84.48 = poker 88 ialah permainan perjudian popular yang digemari ramai orang. Ia adalah satu bentuk perjudian di mana dua atau lebih pemain bersaing antara satu sama lain. Dalam permainan ini, pemain bertaruh wang terhadap satu sama lain dan bersaing untuk jumlah cip tertinggi.
Permainan https://162.243.175.185 = dewapoker88 dimainkan dengan dek 52 kad dan 8, 5 atau 9 bidai. Versi taruhan tinggi poker dipanggil poker tanpa had dan merupakan bentuk perjudian yang paling menguntungkan jika anda tahu cara bermain dengan baik. Cuba permainan kami sekarang untuk merasai keseronokan menang besar.
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
- [Metal] "undeclared identifier 'RemapFoveatedRenderingResolve'" error is thrown when compiling a shader
- "NullReferenceException" is logged when adding a visual element to a list using the Item Template setting
- Errors are thrown and the view is not rendered properly when using Overlay Camera with Non-Default 2D Renderer
- Fog density value is not returned when using the Fog node in a sprite Shader Graph
- UI ToolKit ListView does not rebind some of the items when source data changes
Resolution Note:
Thank you for your bug report.
We are not able to improve the performance of the API provided by Unity without a major internal rewrite. After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
A workaround is available on the UWP platform. You can use, from a background thread, the Windows.Media.SpeechRecognition.SpeechRecognizer class from the Windows Runtime APIs.
For more information on using Windows Runtime APIs in Unity, see https://docs.unity3d.com/Manual/IL2CPP-WindowsRuntimeSupport.html. For more information on using the SpeechRecognizer API in C#, see https://learn.microsoft.com/en-us/windows/apps/design/input/speech-recognition.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.