Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.1.1f1
Issue ID
951333
Regression
No
streamingAssetsPath is not relative to UnityLoader.js
-e: Application.streamingAssetsPath is relative to the html index file loading the webgl player instead of the "UnityLoader.js" script, meaning you can't load streaming assets with the webgl player on any page not in the specific spot in the build folder that Unity puts the inex.html file in.
-repro:
--open attached project
--put the example folder on a server
--start the /index.html
--NOTICE that the streamingAssetPath relative the UnityLoader is wrong
--start the /Build/index-relative.html
--NOTICE that the streamingAssetPath relative the UnityLoader is correct
-proposed user solution:
"Example/Build/Build/RelativePathExample.js" shows how to build the streaming assets path relative to the "UnityLoader.js" file rather than the index.html file using "document.currentScript.src".
Comments (1)
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
- [LinuxEditor] Crash on "XAddExtension" when opening the Unity Editor on Linux with -batchmode and -nographics on a project with a custom default cursor
- Folder attachment size is displayed as 0 bytes when a folder is added to the Hub bug reporter's attachments
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
anastrophe
May 01, 2018 08:49
how was this fixed?