ProjectSettings

[michaelheiml]

Hi there,

thanks for your great asset. I wanted to let you know that "import package" alone does not work in a fresh new project, the webserver is not reachable - I use Unity 2017.4.2. After importing the package, I can start the scene and it says that the server is running, but the browser cannot connect.

Since the websever works with the provided demo scene (not the one from the package but the one that comes with cloning the repo), I thought I just copy the Project Settings files one by one from the demo project to a new fresh project where I just imported the package - and voila, all of a sudden the new fresh project works as well.

I figured out that it must have something to do with the ProjectSettings file itself and compared the ProjectSettings file of the repo with the one that is created when creating a fresh new project. There are some minor differences but I couldn't figure out which difference is the reason that in the repo demo project the webserver starts and in a newly created project it does not.

Maybe you could have a look by yourself and fix the issue?

• Michael

[if1live]

I release new release, v0.0.3
I make new project, import v0.0.3 package, and test. It works.
could you test again?

note: Use development build.
in release build, server is running, but assets are not included in final build.

class MyBuildPostprocessor {
	[PostProcessBuild(1)]
	public static void OnPostprocessBuild(BuildTarget target, string pathToBuiltProject) {
		if (!Debug.isDebugBuild) {
			EntryPoint.RemoveSteamingAssets(target, pathToBuiltProject);
		}
	}
}

[michaelheiml]

Hi, sorry for my late answer.

Thank you for the 0.0.3 update but the problem is still there in the same way as described.

I use a Mac with Unity 2017.4.16f1

Steps:

1. Create fresh Unity project
2. Download & import package
3. Open SagiriExample, Start, Open URL in browser: Result = "Connection refused" in Browser

Then I copied the ProjectSettings.asset file content from this GitHub Repo into the ProjectSettings.asset file of the project (overwrite its content), start the SagiriExample scene again and it works.

I've used DiffMerge to compare the YAML files and found the reason, it's pretty obvios but if you do not know what to look for..

You have to allow the app to run in background, by default in a new project this is FALSE and therefore, if you switch to the browser on the same device where the editor is running, the connection gets refused.

So for anyone else facing this issue, after creating a new project & importing the package, go to
Build Settings > Player Settings > Settings for PC, Mac & Linux Standalone > Resolution & Presentation
and set "Run In Background" TRUE