Doprez

Weird yeah, I cant recreate this anymore for some reason... Ill close it, maybe the FPS project just didnt create properly or something strange.

Not that I have found sadly. This would likely need to wait for the plugin system to be integrated into Stride for it to be fully featured and the community...

Also it may be better to add this issue to the main Stride repo if you havent already. Its not irrelevant here but I dont think the toolkit will be...

If I remember corectly last time I tried to build it was the CompilerApp that failed the build. I know Jkao has done a [ton of work](https://github.com/stride3d/stride/compare/master...Jklawreszuk:stride:linux-runtime) that I am...

`GetCamera()` and `GetCamera("Main")` are basically the same as they both look for a Camera with the name Main in the GraphicsCompositors. I dont know why but Stride has an issue...

If I remember correctly it gets the name from the camera slot in the GraphicsCompositor so naming through AddCamera would not work with that extension, BUT you could use that...

``` ScriptComponent.GetCamera() ScriptComponent.GetCamera(string) ScriptComponent.GetFirstCamera() ``` Have replaced the old GetGCCamera functions. These ones should work on scene load now. This also releases 2 Entity extensions for making getting componenst in...

I have these in my [repo examples](https://github.com/Doprez/Awesome-Stride) that may be helpfull for the research. [Stride assets importer](https://github.com/VirtualBrightPlayz/AutoImportStride). [Saving entities in a running scene](https://gist.github.com/Eideren/0aa59644eb7c5b029d04b7fa5a285e62) may be a good starting to see...

What about the Obsolete attribute?  That way we can warn users but keep it for advanced users.

I dont think this has relevance anymore right?