And stuff like this...
Going to watch this now. Thank you and keep the episodes coming!First test episode of my track building series. I will also include stuff that mainly pertains to road courses so it's not just for ovals.
Where can I donate to buy you a case of beer for doing this?First test episode of my track building series. I will also include stuff that mainly pertains to road courses so it's not just for ovals.
All of my downloads here on RD have a donate button. Just click on my name and you will see 4 resources.Where can I donate to buy you a case of beer for doing this?
No, imperial units are only the default. You can metric select units when downloading the data from US govt sites.-las data from US is in imperial units.
most people that attempt this will be doing it in 2.8 and everything in default is metric in 2.8.
so scales will be off in 2.8 using US lidar data when imported
No, imperial units are only the default. You can metric select units when downloading the data from US govt sites.
Add it to your shopping cart and then go through the checkout procedure.Where do you see that option?
Add it to your shopping cart and then go through the checkout procedure.
Click on download LAZ.
I'm just showing my process. You can choose to do it whatever way you want. As for 2.8 I'm just still comfortable with 2.79 and as I mentioned the same theories still apply with 2.8. I plan to move to 2.8 at some point. Probably after Road America is finished I'll look deeper into it.Thanks for doing this!.
Just few thoughts after watching.
-wish it was all blender 2.8
-there is really nice addon that can turn two curves into mesh. its pricey but nice time saver
https://blendermarket.com/products/curves-to-mesh
-the part where you made two bezier curves on the flat plane that you projected photo how precise are you being?
(curve resolution and z up?)
-las data from US is in imperial units.
most people that attempt this will be doing it in 2.8 and everything in default is metric in 2.8.
so scales will be off in 2.8 using US lidar data when imported
-how did you import raw point cloud (what format from cloud compare was saved?)
-trying to match google satellite data doesn't work as their images are not flat top view.
-when it comes to road course how are you breaking track into chunks and importing?
(what are the limits for physical mesh for AC import?)
As I sort of mentioned before the whole point is to just document my process. It won't work in every case, but it should give you a general idea as to how the process works and you can work on your own from that. In the case of a lower resolution cloud you may have to just stick to the smoothed mesh version of the data and shrink to nearest surface point and not vertex. Any data is better than no data you just may have adjust your approach depending on what you get. I can't go over every single process or the video would be hours long and I wouldn't have much of a life.Okay thank you.
Btw something that you should mention for next episode if possible.
What is suitable quality of LIDAR data required to even attempt this.
Last night playing around....I noticed this random small track I found on USGS when segmented out had only ~500,000 points.
(4770 Waterford Rd, Village of Clarkston, MI 48346, United States)
When I shrink wrapped the curves to the raw ply file it didn't have much verts to catch on and couldn't align to track lines.
..........
btw will you cover in the next video. on the surrounding of track like grass or infield for that case.
How much do you remove of data.
.....
If this is asking to much from you sorry....this first video was good enough for someone to figure out rest by trial and error.
Sure but that won't be until much later. First will be to finish the core track model and sort out the physical mesh and get it in game. I'll show some laps with different levels of displacement to show how it all works.It is excellent video @LilSki. Lots of neat little tricks. I never thought putting the beziers under the lidar mesh. So simple trick but makes perfect sense. Although I prefer to use the projected shrinkwrap which can be limited to just z movement. Are you planning to include some of the shaders patch magic in later episodes?
As I sort of mentioned before the whole point is to just document my process. It won't work in every case, but it should give you a general idea as to how the process works and you can work on your own from that. In the case of a lower resolution cloud you may have to just stick to the smoothed mesh version of the data and shrink to nearest surface point and not vertex. Any data is better than no data you just may have adjust your approach depending on what you get. I can't go over every single process or the video would be hours long and I wouldn't have much of a life.
And yes I will cover just about every aspect of building the outside/inside land using subsample in CC to lower the resolution and bring that into blender. I will also likely show examples of my finished tracks as well and explain what I did for certain aspect of road course design.