Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.9.4
Issue ID
UVSB-983
Regression
No
[Xbox One][Visual Scripting] Potential XR violation error is thrown at runtime when the Visual Scripting package is used
~2024 Report~
~How to reproduce:~
- ~Open the attached Project "Visual_Scripting_Report.zip"~
- ~In File > Build Settings, make sure Xbox One is set as the Platform~
- ~Build and deploy the project to an Xbox One devkit~
- ~Before launching the build, open an xbWatson window from the Xbox Manager~
- ~Check the xbWatson window as the project is launched~
Expected results: the build launches without any warnings in the xbWatson Window
Actual Results: The following "POTENTIAL XR VIOLATION" warning error can be seen in the xbWatson window, caused by the Visual Scripting package trying to initialize PlayerPrefs on load.
-~++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++~-
~[PlayerPrefs] WARNING: MainThread delayed for 99.966504 milliseconds~
~[PlayerPrefs] while fetching machine storage.~
~[PlayerPrefs]~
~[PlayerPrefs] POTENTIAL XR VIOLATION! THE SYNCHRONOUS INITIALIZATION OF PLAYER~
~[PlayerPrefs] PREFS IS AN ALMOST GUARANTEED XR VIOLATION. PLEASE PRIME AND INIT~
~[PlayerPrefs] PLAYER PREFS PROPERLY BEFORE USING THEM FOR ANYTHING!~
-~++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++~-
----
~2020 / 2021 Report~
-~How to reproduce:~-
-~1. Open the user's attached project "BugReport.zip"~-
-~2. Go through the Bolt Setup Wizard if prompted, choosing the default options (if it is impossible to choose the Naming Scheme due to errors, see Notes)~-
-~3. In File > Build Settings, make sure that Xbox One is set as Platform~-
-~4. Build and Run~-
-~5. Observe the xbWatson window in Xbox One Manager while the build launches~-
-~Expected results: the build launches without any errors, there is no potential XR violation~-
-~Actual results: "POTENTIAL XR VIOLATION" error can be seen in the xbWatson window, caused by Bolt trying to initialize PlayerPrefs on load~-
-~Reproducible with: 1.4.12 (2018.4.26f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0a21)~-
-~Full error:~-
-~[PlayerPrefs] Failed to get Data from MachineStorage. Error Code: 0x80830008~-
-~[PlayerPrefs] (Has PROPERTY LudiqSavedVariables)~-
-~[PlayerPrefs] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++~-
-~[PlayerPrefs]~-
-~[PlayerPrefs] WARNING: MainThread delayed for 99.966504 milliseconds~-
-~[PlayerPrefs] while fetching machine storage.~-
-~[PlayerPrefs]~-
-~[PlayerPrefs] POTENTIAL XR VIOLATION! THE SYNCHRONOUS INITIALIZATION OF PLAYER~-
-~[PlayerPrefs] PREFS IS AN ALMOST GUARANTEED XR VIOLATION. PLEASE PRIME AND INIT~-
-~[PlayerPrefs] PLAYER PREFS PROPERLY BEFORE USING THEM FOR ANYTHING!~-
-~[PlayerPrefs] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++~-
-~Notes:~-
- -~If trying to choose Naming Scheme in the Bolt Setup Wizard throws ArgumentNullException, Assemblies and Types can be generated by going to Tools > Bolt > Unit Options Wizard~-
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This issue has been closed because we know with certainty that we will not be able to address it in the coming year.
We understand that it is personally important enough for you to have filed a bug report, and we are sorry that we will not be able to address it in a timely fashion, but we have to address bugs in order of impact, and unfortunately this one is minor compared to the other issues listed in our backlog.