Game crashes when script is attached

#1

I am trying to setup a project with non-portable codebase. I have followed for that the advice on the forums and it seems to work. Yet some times the project will stop working in the following way. When I attach any script to any entity (even the provided BasicCameraController to the camera) running the game will crash it with the following exception
No serializer available for type id 0600f714370f6fa3bc70597e8a4c0417 and base type SiliconStudio.Xenko.Engine.EntityComponent.

Once this happens removing the scripts will make the game run again but attaching anything again will make the game crash. The only solution I have found is to recreate the project from scratch but I have done so 3 times now and always at some point it comes to the above problem.

I am using windows 10 and the 1.7.4 release of Xenko

EDIT: When turning the code to non-portable I get a list of errors in the BasicCameraController.cs in the lines that define the public parameters like:
public Vector3 KeyboardMovementSpeed { get; set; } = new Vector3(5.0f);
VS tells me that ‘=’ is an invalid token in a class, struct, or interface member decleration and that Vector3 should have a return type. I get around this by removing the {get; set} but that shouldn’t be the real solution now.

EDIT 2: I kept trying to solve the problem and have come up with the following.

  1. I have tried both Win 10 and Win 7 and get the same behavior
  2. Just before the code starts breaking I get a notification after compilation (from VS 2013) asking me for the GameBase.cs. When I cancel this I start getting the error as described above (in all subsequent compilations).
  3. I have tried both portable and non-portable projects and I still get the above problem.
  4. I have tried to follow precisely (given the changes in the new version) the tutorial on adding scripts and I still got the same problem right after I added the script on the Entity (the starting sphere).
  5. I mix compilation from the editor and VS 2013 (I cannot see another way to compile for Release). Would that be a problem?
  6. Some times instead of the compilation succeeding and the running crashing I get a compiler error saying that it cannot compile with the given compilation parameters.

Do all of the above make any sense to you guys?

Thanks

#2

Property initializer are only available with C# 6 (i.e. when using Visual Studio 2015). That’s why the line public Vector3 KeyboardMovementSpeed { get; set; } = new Vector3(5.0f); failed to compile. We will fix it for the next release.

As for the other issues, did you make sure that all assemblies are correctly referenced from the main application assembly (i.e. YourGameName.Windows if you target the Windows platform)? Assemblies that are not referenced (and thus not automatically loaded at the start of the game) might cause deserialization issues when loading a scene if their type is used in a script or an entity (see issue #390 on GitHub).

#3

Thanks Kryptos

Your suggestions seem to have solved my issues.

I now use VS 2015 and add my nuget packages to the whole solution (i.e. to all the projects).

#4

You are welcome. Glad I could help.