Truly Global City Builder Game - Tech Demo - Unity DOTS

A quick demo of a game I am working on. A truly global city builder at a scale of 1:1. 🏙️ Say goodbye to boring and limiting game borders 🥱. It uses the Unity Data Oriented Technology Stack (DOTS) for optimal performance and allows up to 200.000 trees in the scene.
Please ignore the floating trees. it's aliens 🛸
If you enjoyed this demo, consider supporting me and buy me a coffee at: www.buymeacoff... ☕ Updates are also posted there or on twitter: / program_sam_yt
The awesome soundtrack is from www.bensound.com/

[@arturrabei7937]

your idea is fantastic, keep going and you will get it, I believe in you!!

[@ProgramSam]

Thank you so much for the motivation! I'm currently working on a new prototype that has less technical issues than this demo :D The one I am working on now has quite a good change of working out

[@fajaralim365]

looking forward about this game 🤨

[@GoodNewsJim]

I'm reaching out for help everywhere. If you can answer either of these questions, I could have an awesome game out: How do I capture an entity into a monobehavior variable: public Entity myEntity; ? OR If I have a single entity in a scene. How do I get a reference to that entity? I want to change it's acceleration by monobehavior script. I have the entityManager, but no reference to the entity.

[@ProgramSam]

Hi! Simple answer as I understand it, you can't. You need to find another way to do what you want. Entities can only be 'controlled' trough systems. What you can do, is have your system make a reference to a game object, and then when you apply the system on relevant entities, a game object attribute can be part of the function. If this explanation is still not clear to you, I can post a quick code snippet ☺️

[@CollMomo1]

I feel like in 1 year, unity will change the whole dots logic and all your precious work will have to be redone. I wanna do the same but Im hesistan, Im sure it took many of hours of experimenting to achieve this level of polish with almost no documentation available

[@ProgramSam]

Good point. I am aware that a lot of the syntax and functionalities can still change. But I don't want that to stop me from understanding the concept and getting into an ECS mindset. Also if I am already 'up to date' on the current state of things, it shouldn't be to hard to understand the updates they make and I have it easier to adopt those changes. At least that is my mindset 🤓. I'm just to exited about it to simply wait because they might still change some stuff in the future.