วีดีโอ

You and me both! 🫡

Glad to hear that! ❤️

Thanks 😊

In our scenario - yes, you can! However, if you want to add a mini-game like Memory, or handle some custom UI popups, or anything else to your game, you can split the responsibility to the MemoryGameInputSystem and SomeCustomInputSystem. For me, PlayerInputSystem is strictly related to the "Game" section, so - if it is more readable for you - you can call it GameInputSystem ❤️

You're welcome! 🤗

You are welcome 🤗

In the video it is the solution for the managed components (in this case - Camera). If you have unmanaged custom components on the Entity or want to simply get LocalTransform - you can use SystemAPI.GetComponent<type>(entity) 🫡

Thanks! 😊 And good job to you too 🫡

Thanks ❤️

Thanks! ❤️ I invite you to Discord community 😊 discord.gg/gZssNGuDdc

It is instantiated only once thanks to the WithAll / WithNone EntityQuery parameters 🫡. In other words - Update method is called only once if conditions are satisfied Without state.RequireForUpdate(query) - it will be executed many times.

Thanks! Really appreciate your comment ❤️

Also, I will be more than happy if you join the Discord community: discord.gg/gZssNGuDdc

I'm so glad to hear that! 😊

Also I will be glad if you join us on Discord: discord.gg/gZssNGuDdc

I am in the process of creation, already edited 20 minutes, should also be ready for next weekend 🥳

The tutorial is ready, so let's dive in ❤️ Also let me invite you to join Discord community: discord.gg/gZssNGuDdc

Couldn't agree more! Thanks mate 🎉

I warmly invite you to join our Discord community: discord.gg/gZssNGuDdc

Hi Subject478, All the content we create on TH-cam - is available for free in the form of tutorials. In return, for those who appreciate our hard work and support us financially - as a token of gratitude - we offer - as part of our support on Patreon (Tier 2) - additional content - including the ability to download the entire project. If you are interested in supporting us in such a way - I have provided a link on Patreon: patreon.com/TaleForge A small note: Since preparing tutorials does not pay off in any way (unfortunately, such are the realities of creating videos as a small content creator), we have adopted the strategy that for the backers we provide various materials - from the project code to other useful Utils. This is always an incentive for us to keep going, and we appreciate any support we get 😊 Our dream is that one day we could make a living out of creating tutorials - who knows, maybe we can achieve that? We are of good thoughts! And then we would also be able to focus only on that = more content❤️

Thanks a lot for your feedback, glad you are with us ❤️

Thanks!

Thanks for your kind words 😊

Glad you think so! I will be more than happy if you want to join our community on the Discord ❤️ discord.gg/gZssNGuDdc

Make sure you only add the subscription to the Input event once 😊

Harry's case (after talking on Discord) - He was using Unity Netcode for ECS, so there were two worlds: client and server - so he had duplicated Debug.Logs Solution: - Use [WorldSystemFilter(WorldSystemFilterFlags.ClientSimulation)] attribute for InputSystem class, so only client instance gets Debug.Log()

Glad it was helpful! 🥳

Great, thanks ❤️

SRP batcher is enabled .. but still i cant see background sprite in camera :/

Solved -> the problem was that the entity graphics package was incorrectly included.

Glad to hear that ❤️

Unfortunately, they are changing the flow a bit (Personally, I like aspects). However you can also achieve everything from video without aspects ❤️

Can you please tell. What alternative features are currently available instead of aspects?

@@ЛариссаКарандашева Currently, there is no official information regarding alternatives to Aspects. The simplest and I think the only sensible solution - although obviously inconvenient if you have several components in an Aspect - is to build Query after all required components (instead of withAspect<XyzAspect> as before). Analogously in Job. From the developers' assumption: “The long term plan was for Aspects to be used in helper methods to manipulate component data in a simpler, safer, and more stable manner.” Fortunately, helper method data manipulation can be achieved with static ECS systems - although unfortunately this requires passing components or data, and you can't reference directly as in the case of, for example, BulletSpawnerAspect (one of the first tutorials on the channel), where I reference a buffer or component directly. An example of such a static class, here acutely with ComponentData in the form of LocalTransforms: [BurstCompile] [UpdateInGroup(typeof(SimulationSystemGroup))] public partial struct MathUtilsSystem : ISystem { [BurstCompile] public static bool IsEntityInOtherEntityRadius(in LocalTransform entityLocalTransform, in LocalTransform otherEntityLocalTransform, float radius) { float distanceFromEntity = math.distancesq(entityLocalTransform.Position.xz, otherEntityLocalTransform.Position.xz); return distanceFromEntity < radius * radius; } } For new tutorials, I avoid creating new Aspects. Of the good news, according to the source: discussions.unity.com/t/dots-development-status-and-next-milestones-may-2024/946863 “Both Entities.ForEach and Aspects will remain supported in Unity 6”. I hope you find it helpful ❤

Glad you think so! ❤️

You are welcome!

Any time ❤️

You are welcome ❤️

And tutorial is landing tomorrow ❤️

Thanks for your support ❤️

Welcome aboard! 🍎

Thanks, keep going - you can improve your performance ❤️💪

Thanks! 😊

Exactly ❤️

Looks

I'm glad to hear that!

Thanks!

Thanks! I am big fan of the Bad Apple, so it was "must have" for me ❤

Sorry for the late reply, I've been busy this week. Indeed, you need SRP Batcher to render in ECS - this setting is available in the UniversalRenderPipelineAsset. If you disable SRP Batcher, you will get an error: Attempting to render a BatchRendererGroup with SRP Batcher OFF. This is not supported.

@@TaleForgeStudio So this may be something only available in the 3D environment and not the 2D. I don't see those options available in a 2D environment game.

@@heroslegendstudios1658 you need to have URP package and enable Static Batching for 2D or 3D environment. If you need help You can reach me out at the Discord: discord.gg/gZssNGuDdc

Generally - if we have suppose a player: RequireForUpdate<PlayerComponentData> and RequireForUpdate <PlayerMovementComponentData> - this is equivalent to queryBuilder.WithAll<PlayerComponentData, PlayerMovementComponentData> Performance-wise most likely too, I haven't checked it in great detail, but it happens in OnCreate, towards which there is a negligible cost. However, if we have projectiles and a player, we need to do two RequireForUpdate or Query - for the reason that the player does not have a projectile, in view of which Query: queryBuilder.WithAll<SomeBulletCompData, PlayerComponentData> will be empty! Similarly, if in the Execute in Job I add a parameter "in BulletComponentData bulletCompData" where I have "in Entity player", such Job will also fail to execute (because it will not find matching entities, i.e. those that are both player and bullet). This is quite a complex topic, I hope I managed to explain it reasonably :)

@@TaleForgeStudio Thanks for your response. As i researched, if we use RequireForUpdate<Component> n times, that means we Query n times, if either of those Queries return none, OnUpdate() won't run. In the other hand, if we use EntityQuery as i said, that means we only Query once. Ex: RqForUpdate<PlayerData> RqForUpdate<BulletData> System runs correctly RqForUpdate(query) (query with all said 2 components) System won't run cause there is no entity contains both BulletData and PlayerData

@@hoangtongvu9952 Exactly. All depends from what we need. For example query WithAll<PlayerComponentData, PlayerMovementComponentData, ...> etc makes great sense, but we rather don't need Bullet AND Player in one query. If we want to query something generic, I think it is a good idea to group things like "InteractableCompData" or "DamagableCompData" etc

Glad you like them!

I checked it out and yes: - giving public makes the Component visible, but you can't highlight its data - instead, there is information about what components the aspect has - however, we don't want to expose direct public access to the RefRO/RefRW field - giving [SerializeField] also makes the RefRW/RefRO field visible, this is quite an unusual action, you have to admit So far, I have not been able to find a way to preview the fields of the Components from the Aspects tab. However, you can use the Components tab and find the IComponentData of interest there.

Thank You very much! ❤️

Indeed, you should look at: docs.unity3d.com/Packages/com.unity.entities@1.0/manual/iterating-data-ijobentity.html Chapter "Specify a Query" Remember, that manually created EntityQuery allows you to set restrictions / specify different invocation requirements in very polish way.

Thanks!

Yes, after Input section, I would focus on the Animations!