I know this is a Beginner tutorial, but this is still VERY insightful on your process and is very fascinating to watch. I'm probably not the target audience since i already make my own worlds, but I will say that it is a breath of fresh air to see how someone else does world development. Its a good sanity check for me. Thank you for making this, Spooky!!
I played this while working to try and absorb some Unity knowledge, and it seems a lot less terrifying to me now! You are a great teacher, seriously, you go straight to the point in such a clear and easy to follow way. Thank you so much for this!
Hello, thank you a lot for making this tutorial it really really really helped me. The parts that I found the most challenging were the ones about textures, by far, specially in Blender. On my first try when I did the unwrapping in Blender the meshes(?) had a weird shape (kinda like yours at 1:19:20 but way worse), I messed up by joining several planes together and trying to cut them at the same time (like you were trying with the seams, I failed that), so my approach ended up undoing it and keeping the planes separate (hall walls and room walls be separate planes etc), that made it have simple shapes to work in the UV editor, at the expense of a little more repetitive work obviously. When it comes to Unity I think the tip about the baked lights was great because a lot of worlds seem to struggle with that from what I've read, so thank you for that. However, Unity can be such a mess, it's amazing how introducing a little asset that deals with something more than basic textures (like an asset that has an Udon Script or whatever) can absolutely get your entire scene bugged and wrecked. I learned the hard way that, before introducing anything more than simple props, I backup the project folder and keep constantly testing if the project is able to compile or not. For example, a lot of times it happened to me that after importing a unity package and introducing a prefab into the hierarchy, then later if I deleted it, then it wouldn't compile anymore (Common errors including "InvalidObject at", "InvalidNetworkIDs") I know this is obviously too much for a tutorial that is already 3 hours long, so don't worry but I just wanted to mention how important is being careful when introducing things to a project (especially if you have almost zero troubleshooting skills). What else can I say, I think the tutorial was great, if you decide to make another video I would say make more of your workflow like this but obviously skip introducing Blender and so on so it's not a chore for you, more like a continuation of this video if anything, but you know just make another map. If you decide to do so I would like to see more things regarding textures, why sometimes when importing a unity package of an asset the textures come missing (even though they are there wtf??), a little bit more about "shaders", why do some objects/textures while the users in VRChat are able to see them they may not end up showing up in the camera when a user is going to take a picture, maybe on how to select good assets from BOOTH and fix them if they come with wrong textures or wrong shader pipeline or whatever it's called, how to have a music player that plays background music (not using the TV), how to make some toggles or make use of famous toggles that can be found on BOOTH, other things regarding AudioLink or introducing shades into the scene (like those that are water shades or whatever), maybe talk about particles as well. Regarding Quest, it seems like if you want to build for that platform you have to have it in mind since the beginning, because a tooon of textures/shades/objects whatever are not compatible and you may find yourself at the end of the project with a huge list of warnings that are just unrepairable without redoing the entire thing, so an idea for a video would be on how to target world optimized for Quest since the beginning (I recogn it may not always be possible though). When I finished my PC world it ended up being around 250MB, among the other thousand warnings I had when I changed platforms for uploading to Quest, one of them is that the size limit is only 100MB! lol. Maybe a bit of a stretch, but something useful could be how to make our own unitypackages based on different assets for future reuse, because sometimes I end up buying an asset/prop that is too small/too big or I have to "mix it" with another furniture to look good. For example, the famous "[VRC] Coffee Set - MiniGreen" which default table is super small, I had to stretch the table a little bit and move some props to a second furniture (which was not originally part of the asset), in this case I would like to save everything in a unity package for future reuse so I don't have to do all that again. Also referencing another comment you made and I might have misunderstood, but you don't have to do a tutorial like this in one sitting you know, you can just pause and do a section every couple of days or whatever, also modeling is a massive pain and I think it's ok if you do more simple shapes or just skip the modeling part from scratch entirely, I think most of the important knowledge here is from Unity and how it behaves with VRChat, if you want to use a prefab of a cube house as long as you deal with textures, assets, optimization, shades, I think it would be extremely useful (specially because I don't want to model complex shapes, not even stairs again god I hated them). Anyway thank you, also liked the bowling asset.
also you can visit my world if you want, it's the second one I made, it's still extremely simple it's called "The BJD Museum" I made it public yesterday
honestly kind of forgot about them. If I don't use the in unity stuff, I tend to use the scripts I've had commissioned. I don't ever do anything crazy usually
Cant wait to watch this! Im curious, would you say it's easier to build a world in blender than in unity? I've been trying to decide which way to go as I see both methods alot
if youre modeling, unity will be more simple. but you wont get the amount of control that blender offers. If you ask me, its a no brainer. Use blender. Learn the program. infinity better.
it shouldnt matter. its possible something is different with newer versions of blender, so if something doesn't work, you may need to google it. I was modeling in blender 3.1.2
@@spookyghostboo I encountered issues with the current LTS version 4.2. Some features are missing or different, so I downloaded version 3.1.2 and will start fresh.
So if I wanted to make a light switch would I have to make a duplicate of that room and bake it with no lights and bake the other room with lights? And just write a script that sets one or the other active? Idk if that makes sense 😅
yes. kind of. its more complicated. if youre a programmer, it might be easier for you cause you'll understand more than me. every forum post ive seen on it, mentions scripting a toggle between multiple lightmaps. The way I do it, is I bake a light scene seperately in blender. take those texture bakes and use a special shader to simulate unity lighting. then I toggle between the objects that have unity baked lighting and the objects that have the blender texture bake. most people just use post processing tho to dim the entire scene
make sure your objects are set to cast shadow in the mesh renderer. realtime light will go through backfaces, so make sure you bake lights to see the results
Fantastic tutorial, but I think the only feedback I may give may be to slow down a little bit before moving from point to point when talking to give people either time to absorb it, or for kinesthetic learners the chance to follow on in a natural way that also gives the time to absorb it as they're doing rather than simply copying. It was a great tutorial, but you sound like you were super in a rush, which left me having to pause you a lot, which did disrupt the flow of things a bit.
45:53 Smooth Angle is no longer in data, it is a modifier
pinning this just in case anyone needs to see it
Learned from you back when I made my first creations, now I'm getting to refresh my knowledge with a new tutorial??? You spoil us lol
I know this is a Beginner tutorial, but this is still VERY insightful on your process and is very fascinating to watch.
I'm probably not the target audience since i already make my own worlds, but I will say that it is a breath of fresh air to see how someone else does world development. Its a good sanity check for me. Thank you for making this, Spooky!!
Thank you SO MUCH I finished my first good looking world lastnight!
Best comprehensive blender videos out there🙏🏼
I love your videos so much. They give me the confidence to try to jump in and start making worlds
I played this while working to try and absorb some Unity knowledge, and it seems a lot less terrifying to me now! You are a great teacher, seriously, you go straight to the point in such a clear and easy to follow way. Thank you so much for this!
ANOTHER one?? i followed the last two at different points in my life, your dedication is unthinkable. keep it up, love your work!
thank you!
Damn! u did it again! Wonderful Tutorial as always!
Hello, thank you a lot for making this tutorial it really really really helped me.
The parts that I found the most challenging were the ones about textures, by far, specially in Blender. On my first try when I did the unwrapping in Blender the meshes(?) had a weird shape (kinda like yours at 1:19:20 but way worse), I messed up by joining several planes together and trying to cut them at the same time (like you were trying with the seams, I failed that), so my approach ended up undoing it and keeping the planes separate (hall walls and room walls be separate planes etc), that made it have simple shapes to work in the UV editor, at the expense of a little more repetitive work obviously.
When it comes to Unity I think the tip about the baked lights was great because a lot of worlds seem to struggle with that from what I've read, so thank you for that.
However, Unity can be such a mess, it's amazing how introducing a little asset that deals with something more than basic textures (like an asset that has an Udon Script or whatever) can absolutely get your entire scene bugged and wrecked. I learned the hard way that, before introducing anything more than simple props, I backup the project folder and keep constantly testing if the project is able to compile or not. For example, a lot of times it happened to me that after importing a unity package and introducing a prefab into the hierarchy, then later if I deleted it, then it wouldn't compile anymore (Common errors including "InvalidObject at", "InvalidNetworkIDs") I know this is obviously too much for a tutorial that is already 3 hours long, so don't worry but I just wanted to mention how important is being careful when introducing things to a project (especially if you have almost zero troubleshooting skills).
What else can I say, I think the tutorial was great, if you decide to make another video I would say make more of your workflow like this but obviously skip introducing Blender and so on so it's not a chore for you, more like a continuation of this video if anything, but you know just make another map. If you decide to do so I would like to see more things regarding textures, why sometimes when importing a unity package of an asset the textures come missing (even though they are there wtf??), a little bit more about "shaders", why do some objects/textures while the users in VRChat are able to see them they may not end up showing up in the camera when a user is going to take a picture, maybe on how to select good assets from BOOTH and fix them if they come with wrong textures or wrong shader pipeline or whatever it's called, how to have a music player that plays background music (not using the TV), how to make some toggles or make use of famous toggles that can be found on BOOTH, other things regarding AudioLink or introducing shades into the scene (like those that are water shades or whatever), maybe talk about particles as well.
Regarding Quest, it seems like if you want to build for that platform you have to have it in mind since the beginning, because a tooon of textures/shades/objects whatever are not compatible and you may find yourself at the end of the project with a huge list of warnings that are just unrepairable without redoing the entire thing, so an idea for a video would be on how to target world optimized for Quest since the beginning (I recogn it may not always be possible though). When I finished my PC world it ended up being around 250MB, among the other thousand warnings I had when I changed platforms for uploading to Quest, one of them is that the size limit is only 100MB! lol.
Maybe a bit of a stretch, but something useful could be how to make our own unitypackages based on different assets for future reuse, because sometimes I end up buying an asset/prop that is too small/too big or I have to "mix it" with another furniture to look good. For example, the famous "[VRC] Coffee Set - MiniGreen" which default table is super small, I had to stretch the table a little bit and move some props to a second furniture (which was not originally part of the asset), in this case I would like to save everything in a unity package for future reuse so I don't have to do all that again.
Also referencing another comment you made and I might have misunderstood, but you don't have to do a tutorial like this in one sitting you know, you can just pause and do a section every couple of days or whatever, also modeling is a massive pain and I think it's ok if you do more simple shapes or just skip the modeling part from scratch entirely, I think most of the important knowledge here is from Unity and how it behaves with VRChat, if you want to use a prefab of a cube house as long as you deal with textures, assets, optimization, shades, I think it would be extremely useful (specially because I don't want to model complex shapes, not even stairs again god I hated them).
Anyway thank you, also liked the bowling asset.
also you can visit my world if you want, it's the second one I made, it's still extremely simple it's called "The BJD Museum" I made it public yesterday
you're actually a saint for this 🙏
always the best vrc tutorials. I'm surprised to see you aren't using cyan triggers anymore though!
honestly kind of forgot about them. If I don't use the in unity stuff, I tend to use the scripts I've had commissioned. I don't ever do anything crazy usually
@@spookyghostboo True, I definitely guess it can be overkill sometimes
This is a great video to fall asleep to for me xD
lol. 3 hours of me talking does not sound very relaxing imo
Excellent tutorial! Thank you so much!
Thank you so much!
Big thank you for totorial.
yay good job spooky!!!!
OMG thank you! 😎
np!
Cant wait to watch this! Im curious, would you say it's easier to build a world in blender than in unity? I've been trying to decide which way to go as I see both methods alot
if youre modeling, unity will be more simple. but you wont get the amount of control that blender offers. If you ask me, its a no brainer. Use blender. Learn the program. infinity better.
@spookyghostboo awesome! Thanks so much. I do feel more comfortable in blender while making avatars so I'm glad to hear this. Appreciate the response!
Does the version of Blender matter, or will the current LTS do?
it shouldnt matter. its possible something is different with newer versions of blender, so if something doesn't work, you may need to google it. I was modeling in blender 3.1.2
@ Thank you for the reply. I’m starting on this right now. Wish me luck 😁
@@SenpaiSkyy Good Luck!!
@@spookyghostboo I encountered issues with the current LTS version 4.2. Some features are missing or different, so I downloaded version 3.1.2 and will start fresh.
Anyone having luck downloading the sample object files? The google drive link is being weird and the download keeps failing?
maybe try a different browser. i just tried it on chrome with no issues
So if I wanted to make a light switch would I have to make a duplicate of that room and bake it with no lights and bake the other room with lights? And just write a script that sets one or the other active? Idk if that makes sense 😅
yes. kind of. its more complicated. if youre a programmer, it might be easier for you cause you'll understand more than me. every forum post ive seen on it, mentions scripting a toggle between multiple lightmaps.
The way I do it, is I bake a light scene seperately in blender. take those texture bakes and use a special shader to simulate unity lighting. then I toggle between the objects that have unity baked lighting and the objects that have the blender texture bake.
most people just use post processing tho to dim the entire scene
my light is going through objects and not casting a shadow, im not sure why
make sure your objects are set to cast shadow in the mesh renderer. realtime light will go through backfaces, so make sure you bake lights to see the results
@@spookyghostboo you're amazing thank you
Fantastic tutorial, but I think the only feedback I may give may be to slow down a little bit before moving from point to point when talking to give people either time to absorb it, or for kinesthetic learners the chance to follow on in a natural way that also gives the time to absorb it as they're doing rather than simply copying.
It was a great tutorial, but you sound like you were super in a rush, which left me having to pause you a lot, which did disrupt the flow of things a bit.
I think i need more simple things to model. after an hour of modeling, im like, oh god, this is going to be a 5 hour video. but thanks. noted.
Unbann KingM please