open-project-1 VS godot-proposals

I wish they'd go the way of Epic and make an actual game with their engine. They've tried a few times and given up each time. It's pretty embarrassing when they've done things like released a fully featured multiplayer FPS demo that doesn't actually work out of the box and has a custom editor tool manager, custom scene loader, and custom networking layer that were never merged into mainline unity. Meanwhile they still have no official stable networking module. The old functional one was sunset and the new ones are still in beta.

https://github.com/Unity-Technologies/FPSSample

> This project is based on Unity 2018.3

> NOTE: Due to a bug in Unity 2018.3, you have to take the following step right after the initial import: 1 Search for Firstperson_Projection in the Project search field. Select the 4 shaders, right click and reimport them. 2 If you have script compile errors related to entities, you need to remove and re-install the entities package.

> One day soon we will remove this note and there will be cake.

> Once the editor is ready, open the Project Tools Window by navigating to FPS Sample > Windows > Project tools.

> Keep this window docked as you will use it a lot. From here you can open the levels, build assetbundles and build standalone players.

https://github.com/UnityTechnologies/open-project-1

> Note: As of December 2021, Open Projects and Chop Chop are not in development anymore.

Unity has some official open source games https://github.com/UnityTechnologies Chop Chop is one of the best. https://github.com/UnityTechnologies/open-project-1

Additive scenes are great but a bit more advanced. Moving your player to the right location after changing scenes is something you will need to solve regardless of using a single scene or additive scene structure. That said for the "transfer" you can have your player in its own player scene (another additive scene) or the base scene and just move the position. Instead of trying to have a reference to everything you should be using events, it is more performant, and there is no need to have a reference there for you do not need to drag and drop between scenes. Here is a project where you can reference a scriptable object event system that has no issues working across scenes: https://github.com/UnityTechnologies/open-project-1/tree/main/UOP1_Project/Assets/Scripts/Events

The fantastic UOP1 project has great examples of this using scriptable objects as event channels to communicate between a persistent managers scene and the current gameplay scene.

For starters, it might be worth checking out the Scriptable Object demo project and the videos on youtube that deal with it. https://github.com/UnityTechnologies/open-project-1

And for anyone else looking for real-world examples: this repo is interesting: https://github.com/UnityTechnologies/open-project-1

I didn't use any particular tutorial for my save system but Unity actually developed a community based Open Project a year or so ago. Their save system is probably a good reference to get something started. They have a few other systems implemented in that project as well that you might find useful, although personally I didn't love how much they used scriptableobjects for their event system.

Hi, so apparently some people (including me) after downloading zip containing unity open project 1 from it's github page had problems with unpacking it. The (one of the possible) solution(s) was downloading it using github desktop - which is quite unpractical since if you lost internet connection during the process you have to re - download the entire project. So if you want to download it, you can use this google drive link: https://drive.google.com/drive/folders/1o5Db5fI9HHD3T8wv2C7PlDV1pu8unma1?usp=sharing

When you download the Unity Hub, it will have a learn tab. Selecting that you can download sample games that will show how Unity works. Besides that Unity has an Opensource project this was canceled after the community dried up around it.

What might work well for you is taking apart one of the example projects, add new features or just mess with existing systems. For Unity there's https://github.com/UnityTechnologies/open-project-1 for example.

Godot was fine, for the most part, it's a good engine for small games. The main issue was around working together and resolving conflicts with git (Godot isn't really working and constantly kept changing IDs in resource files), and it kept losing data in scenes when the code changed so we had to rebuild things several times. On previous test games we also ran into huge performance issues in the editor when we wanted to do too much work in scenes, so we had to switch to doing most of the work in code.

The worst part was when I had to rip out a bunch of testing code that used @tool for release as it seemed to cause issues when doing a release build. The engine is generally not great when you want to follow clean software engineering (e.g. dependency injection is not possible, I opened a proposal to that end here[1]).

[1]: https://github.com/godotengine/godot-proposals/issues/8850

If we had a Mask2D, this would be super easy and straight forward.

So if that's what OP meant, clip_children property won't work. Instead OP needs to use a CanvasGroup parent and the Line2D (with CanvasItem Material in Subtract mode) and TextureRect as siblings, or any of the other methods explained here until we have a Mask2D node.

There is an open proposal to have a compile option for a LibGodot, as a Library https://github.com/godotengine/godot-proposals/issues/6267

Yes, there could be the option to open at least 2 tabs at the same time, when working with scripts. This has probably already been suggested in: https://github.com/godotengine/godot-proposals

I cannot tell exactly where the jitter is from the video, but if it is what I'm thinking of, it is a known issue, see here. There is a proposal to fix this, with tons of discussion here. Try some of the workarounds mentioned in these two links. Game looks great by the way!

It's in the release notes. Here is a link to the pull request, based on this proposal.

Currently not possible: https://github.com/godotengine/godot-proposals/issues/7213