Bug The scene catalog has not been loaded yet on Android client

As you said, the ConvertToClientServerEntity is deprecated, apart for some hybrid use cases should not be used.
Seyo the build pipeline can be a little annoying. First: did you add some systems (or whatever else) that assign the

Code (CSharp):

1. SceneSystem.BuildConfigurationGUID

property to the correct build configuration ?

Also, please check that the catalog.bin is present in your build. I also know there was a bug in the GetFileNameWithoutExtension that was cutting the filename and not loading the proper data.

 

There will be no replacement as far as I know. The ConvertToEntity and ConvertToClientServerEntity are deprecated. You should always use subscenes (at the moment). Converting game object on the fly via ConvertToEntity has some problem and caveats.
Regarding yours issue, could you please try to debug the Android build (by putting a breakpoint in GetPathFromGUID or GetGUIDFromPath in ResourceCatalogData.cs and check why you get that error ? (nothing was loaded or is a path/guid mismatch)

 

This does not seem a problem with NetCode. I suggest to ask specific question on the forum.

 

Why do you need to convert a Unity UI to entities ? I Don't think the UI rendering is actually supported at all. Why not using it as classic game object?

Is not just for NetCode. The scriptable build pipeline require you to set that property, but it is not documented very well yet unfortunately.
You can see an example of use in Asteroids. Please look for ConfigureClientSystems and ConfigureServerSystem.
The value of the hash is the guid that come from the your build configuration metafile you would like to use.
[/quote]

 

I don't think in your case you need the custom bootstrap.

I tried to build the project and running on an android emulator (I don't have an android device at home, sorry) and I also got the "scene catalog ..." error as well, even though the file present but the File.Exist report is not there. This is not not again a NetCode issue, probably a regression.

umm I need more information in order to really understand what is going on. In the project you shared you have two build configuration for Android: a ClientServer and a Client. I suppose you are using the client one and not the client server right?
In general I don't see how the window server can affect an android build. it is on another machine .. The only thing I can think of is that you are running for some reason multiple client at the same time or a Client-Server build.

I didn't saw the Address Already in use error at all when I tried it. Also, if I started the client first and then the server, really nothing happen in my case.
But I can repro the spawn problem. I'm investigating why

 

Hi @Occuros, I investigate a little the "non spawning" problem you have in your project.
I would say I got that issue running the emulator, so it may be not the case with real device, but it is likely to be.

The problem is due to fact the client game code does not wait until the scene is loaded to send the server the RPC that tell to spawn the cube and set the network stream in game. The RPC is sent by the GoInGameClientSystem as soon a connection is established, that is happening in parallel with the scene loading.
Usually loading scene is super fast (ms) but on Android devices may take longer (hundred of ms, seconds).

NetCode 0.6 expect that when you set the network stream "in-game" all the game scene are loaded. We don't support streaming entity scenes once the network stream as the NetworkStreamInGame tag. The ghost prefabs must be already present in world when the client receives the first snapshot from the server and it populate the GhostCollection accordingly.

I would suggest to add some logic on the client code to wait until the scene is loaded. Since you are still using the GhostCollectionAuthoringComponent you can can just add a

Code (csharp):

1.  
2. RequireSingletonForUpdate<GhostPrefabCollectionComponent>();
3.  

to the GoInGameClientSystem inside the OnCreate method. That should fix your problem