you can move in scene view by holding RMB and pressing wsadqe keys. You can control movement speed with mouse wheel while holding RMB. You can use mouse middle button to pan and mouse wheel to zoom.
A first step should always be to ensure the color space is liniar (should be default in URP now, used to be gamma in the past) and set the tonemapping (ACES likely the best choice, unless you have some specific different goal)
Hello, can you make a tutorial of ball dribbling in Unity, like proper dribbling and the ball is a separate piece of physic instead of a part of the body transform, I can not find any tutorial about this. Btw thank you for your great content
Could you make a video on how to carry objects over to different scenes and on making save files? it seems a little sketchy to have objects detect if they already exist and then have them delete themselves when returning to a previous scene. I was also curious about different types of lighting in unity, so thank you bundles for taking the time to make this video!
I'm also not too keen on having singleton objects that delete themselves. Sometimes this is the only way. For example if you want music to continue playing across scenes. For most other cases though you can use a prefab to have the same object type in each scene. Then you can save and load the state data between scenes. For example, say you want to keep track of the player score and current weapon between scenes, this data could be either held in memory or serialised and saved to disk. Then in the next scene this data can be loaded back in to the relevant object. Saving to disk will keep the code cleaner but will be a bit slower. If you want to hold it in memory, it's a bit harder to find a clean way. You could have a static class that you set the values to, or you could use a Scriptable Object that you keep alive between scenes. Hope that helps 😊
@@KetraGames okay thank you! i think it has to do with how when i first started with unity, I kept looking for a Main() 😅 it's at a very high level where it seems like the code starts per scene and per object, instead of having a namespace or a global Main function. so as long as you're saying the only ways to do it can be a bit odd, i'm okay with moving forward with that. what engine did you use before Unity? or you stuck with it from the beginning?
It is a bit strange to not have that entry point 😂 I used XNA before which is a framework rather than a full engine. It was much harder but you did have a Main method!! 😊
@@KetraGames oh okay cool!! i had 2 xna C# classes in college, then it switched to unity after that. we never did much in 3d in xna because i think if you were to load up 3d models in it, you wouldn't be able to see their position until you run the program. it's almost like you'd have to make an engine out of it, and then use that engine to make the game. if there are any other engines in C# you think i should learn, please let me know 🙂
I baked (40mins!!) a scenario and then I change on single item, small (point light) and editor rebaked ALL again, taking forever again! Thats how it works? Do you have any advice to when is the time to bake light on static environment?
guys i have to tell something, its useless to know all this stuff (not only from this video) if you dont know really good C# or code. safety, polymorphism, and prevent failing tests in a lot if scenarios. and that's just the tip of the spoon.
Tutorials can't cover everything, nor should they. This is an EXCELLENT tutorial to introduce lighting in Unity. C# code is important to Unity development, but so is good lighting, audio, and countless other aspects. Saying that it's "useless to know all this stuff" is rather naive.
This was best nearly 24 mins of my Unity Lightning learning experience, I wish there was more.
Very complete, with a great explanation of the essence of different types of lighting modes. Great work!
Perfect tutorial
Thanks very much for this comment 😊
The most comprehensive unity lighting video I've seen! thanks for the great explanation and demonstration!
Thanks very much for this comment 😊
this is a hidden gem of a guide...
Thanks for this comment 😊
Perfect tutorial, I love your work! Keep doing this amazing content
Thanks so much for this comment 😊😊
I always wondered how that worked thanks for the great video
Thanks for this comment, glad it was useful 😊
Amazing Tutorial, loved it!
Thanks for this comment 😊
Another great tutorial. Thank you 😀
Great to hear, thanks 😊
Thank you for this very Enlightening video 💡😂💯👍🏻
😂👍😊
you can move in scene view by holding RMB and pressing wsadqe keys. You can control movement speed with mouse wheel while holding RMB. You can use mouse middle button to pan and mouse wheel to zoom.
great video!
Thank you 😊
Thx a lot for this Tutorial ;-)
To know each settings backing-time would be awesome for next tutorial :D
cool video, 10x :)
I'm also impressed by this no-shits-n-giggle but pure info
Thanks for this comment 😊
A first step should always be to ensure the color space is liniar (should be default in URP now, used to be gamma in the past) and set the tonemapping (ACES likely the best choice, unless you have some specific different goal)
Thanks for sharing this 😊
Someone from comments says it was a perfect tutorial
YES INDEED!
😊😊
Hello, can you make a tutorial of ball dribbling in Unity, like proper dribbling and the ball is a separate piece of physic instead of a part of the body transform, I can not find any tutorial about this. Btw thank you for your great content
Could you make a video on how to carry objects over to different scenes and on making save files? it seems a little sketchy to have objects detect if they already exist and then have them delete themselves when returning to a previous scene. I was also curious about different types of lighting in unity, so thank you bundles for taking the time to make this video!
I'm also not too keen on having singleton objects that delete themselves. Sometimes this is the only way. For example if you want music to continue playing across scenes. For most other cases though you can use a prefab to have the same object type in each scene. Then you can save and load the state data between scenes. For example, say you want to keep track of the player score and current weapon between scenes, this data could be either held in memory or serialised and saved to disk. Then in the next scene this data can be loaded back in to the relevant object. Saving to disk will keep the code cleaner but will be a bit slower. If you want to hold it in memory, it's a bit harder to find a clean way. You could have a static class that you set the values to, or you could use a Scriptable Object that you keep alive between scenes. Hope that helps 😊
@@KetraGames okay thank you! i think it has to do with how when i first started with unity, I kept looking for a Main() 😅 it's at a very high level where it seems like the code starts per scene and per object, instead of having a namespace or a global Main function. so as long as you're saying the only ways to do it can be a bit odd, i'm okay with moving forward with that. what engine did you use before Unity? or you stuck with it from the beginning?
It is a bit strange to not have that entry point 😂
I used XNA before which is a framework rather than a full engine. It was much harder but you did have a Main method!! 😊
@@KetraGames oh okay cool!! i had 2 xna C# classes in college, then it switched to unity after that. we never did much in 3d in xna because i think if you were to load up 3d models in it, you wouldn't be able to see their position until you run the program. it's almost like you'd have to make an engine out of it, and then use that engine to make the game. if there are any other engines in C# you think i should learn, please let me know 🙂
Can you make a video on Joystick. I really want it.
Hi, may I know why make scene become darker when I reload the scene at runtime? Thank you
I baked (40mins!!) a scenario and then I change on single item, small (point light) and editor rebaked ALL again, taking forever again! Thats how it works? Do you have any advice to when is the time to bake light on static environment?
guys i have to tell something, its useless to know all this stuff (not only from this video) if you dont know really good C# or code. safety, polymorphism, and prevent failing tests in a lot if scenarios. and that's just the tip of the spoon.
Tutorials can't cover everything, nor should they. This is an EXCELLENT tutorial to introduce lighting in Unity. C# code is important to Unity development, but so is good lighting, audio, and countless other aspects. Saying that it's "useless to know all this stuff" is rather naive.