Addressables Editor Hosting Window Removed?

Unity Engine
, , ,
1

I can no longer find the Editor Hosting window on Unity 6/Addressables package 2.2.2 (or 2.3.0/2.3.1). Has it been removed or is this a bug? I looked in Window > Asset Management > Addressables, as well as the Tools > Window menu in the Addressables Group window.

2

It has been removed. There are a lot of simple command line webservers you can use in its place. One I use for testing is just to use python3’s built in webserver. From my main project directory I run:

python3 -m http.server 9000 --directory ServerData

Then I define my remote load path as:

http://127.0.0.1:9000/[BuildTarget]

image
image632Ă—194 21.5 KB

Hope that helps!

2 Likes
3

Hey, I appreciate that workaround! My team does have a server I can use, but using the Editor Hosting service was just so easy so I thought it weird that they would have removed it. And I tried searching but couldn’t find any information on it’s removal, so thought it might be a bug.

But now that I know it was just removed, I can move on and use the team server or your command line webserver. Thanks again!

1 Like
4

Hi, thanks for the heads-up. In the past we already used that python http.server to host the output of WebGL build: i.e., not the addressable packages, but a “plain” standalone build.

We are now fiddling with using that same python server to host the output of addressable build as suggested in this thread.

Is it a known issue that with just that python server, requests to bundles are blocked by CORS?

Requests are blocked in the same way when using Editor Hosting (we’re on a older Unity version). And it looks like that simple python server cannot be customized (StackOverflow thread).

In order to enable CORS on the server we’re now trying with node.js http server:

npx http-server ./ServerData -p 9000 --cors

We already used this one for a plain, non addressable WebGL build and it was working fine.

1 Like
5

Just came to add that this was a borderline essential feature that I have used on every team I ever worked on. Removing it is completely ridiculous.

1 Like
6

I hope this is a mistake. Because this tool is very necessary and it is very inconvenient without it.

7

I’ve also moved to this nodejs based solution because of issues in python. I think this is the best solution.