Regular terrain
-
this is interesting. I asume you figured out that the edges are bound together in a component (that you have to explode to use the edges).
your computer seems to regard the bottom endpoints of the edges as well. only way would be to increase their lengh, until SketchUp finds them too far away and ignores them.
(the only way to do this quickly that I can think of at the moment is to scale them in Z-direction downwards (lets say 10x) then create the terrain. then select terrain and edges and scale it back (0.1x)
[Edit] or you could connect all the bottom points with horizintal lines. that is quite easy for all the vertical edges are assembled in an array. now you can select these horizontal connection lines and move them down. thus you don't have to mess arround with scaling... []
-
Well, I scaled them 10x down on the z axis (BTW it distorted the whole "should be" terrain 10x as well) but the same result happened.
-
Csaba, I am at a complete loss. just tried it with my tutorial model and got the same screwed up result like you do.
tried different things, like skaling or enhancing their length (a hundret times) did not work.anyway, I thought about your suggestion, TaffGoch, to use the "drop at intersection" ruby.
and it is indeed a very elegant way to speed up the workflow considerably.here a short demo, how I used the script.
regular_terrain2.skp -
Definitely a very elegand solution - and the funniest is that now it worked!
-
Csaba, just found the cause for the first model not working.
when setting up the different scenes and therefore copying the geometry several times, I must have worked inaccurately, what resulted in the vertical lines not being entirely vertical.
therefore SketchUp did not, like we assumend, ignore the lower endpoints, but included them into it's terrain calculations.problem solved - at last we have peace of mind!
-
Jakob,
Your 'drop' demo model works great. I hadn't foreseen the option that this technique provides -- giving you the power to change the degree of detail (spacing.) This can be a great way to reduce the polygon-count for a complex terrain; producing larger mesh triangles.
Since the drop ruby finds intersections corresponding to lines AND planes, automatic interpolation is provided. A smaller grid spacing should, therefore, also produce useful results.
Thanks for the demos!
Taff -
@plot-paris said:
Csaba, just found the cause for the first model not working.
when setting up the different scenes and therefore copying the geometry several times, I must have worked inaccurately, what resulted in the vertical lines not being entirely vertical.
therefore SketchUp did not, like we assumend, ignore the lower endpoints, but included them into it's terrain calculations.problem solved - at last we have peace of mind!
Thanks Jakob - I was already going nuts the other day
-
Dear Gaieus and Jakob,
A revised/summary posting listing the do's and dont's with attached tutorial skippy's should now appear in the Tutorials section. Do you chaps have the time and energy to do this?
Kind regards,
Bob -
It's Jacob's idea with Taff's addition - I just chimed in and would not take any credits by creating a revised tutorial of it so please, Jakob, go ahead and post a refined version of it in the Tuts section!
-
now, that the method has been refined, it is ready for the tutorial section
I just tried to redo the tutorial. but my laptop is so old, that he crashes every other minute, when opening the file.
therefore, Gaieus, feel free to write the tutorial (if you have got the time).
[Edit] if you do, don't forget to include a link to the "drop" ruby into the description[]
I will only be able to do it on monday in the office; and my boss surely doesn't like it, when I spend too much time doing stuff for SCF instead of for the officeif you do, could you post the link to the tut in this thread? would be great.
cheers, Jakob
ps: this is an example why I like the SCF community so much. you have an idea, post it, and after a pleasant discussion a much faster and better way to solve the same problem is born!
-
I'll see how lazy I am between my drinks during the week-end
(I have the same problem with my boss in the office but fortunately he cannot see my monitor) -
of course. there is no hurry for that tutorial, I think.
enjoy your drinking!
after months of cider and guinnes it will be Sambucca tonight for me (with big glasses, tissues and straw. I love hearing other people coughing while I keep the pleasantly burning vapours in my lungs until lack of oxygen forces me to breathe again )by the way, my monitor is completely exposed. and in addition to that everyone tries to get a glipse of my screen every now and then, because I am doing all the SketchUp work.
-
Cool, clever, good
@unknownuser said:
I don't really know, what this cleanup is good for
It sure helps a better terrain display whith smooth/soft faces (long and narrow triangles never display well).
My question is: don't we loose some information during the process ? I guess the new terrain is not exactly the same as the original (the greater the vertical faces spacing, the more you loose terrain details and distort it) ?
This may be a plugin idea: drop a virtual flat TIN over the current terrain, compute intersections and automatically get the "clean" regularly triangulated terrain.
What do you think ? -
that would be an awesome tool, because it really saves a lot of time and can help you to clean up your model considerably.
I would definitely love such a script!!!
-
@plot-paris said:
that would be an awesome tool, because it really saves a lot of time and can help you to clean up your model considerably.
I would definitely love such a script!!!
+1!
-
+2
Nice idea Didier
-
+3
-
Very nice approach for simplify a terrain mesh !!
Thanks for sharing it.
-
Ha! Yes, 14th of July!
When I was in Paris and used the Metro and got off (up) at the Bastilles, I was looking around to see it when finally I realised that "ah these dudes destroyed it on occasion of one of their regular revolutions" (well, the first in the row)
Amazingly, I was a last year history student at that time. Such is life!
BTW - English is quite keen on separating its Germanic and Romance layers of origin so I bet "Liberté, Égalité, Fraternité" would read as "Liberty, Equality, Fraternity" - but then again; who am I to judge it?
And the plugin seems to be a beauty again!
-
oh dear, I am really looking forward to your plugin. the image looks very promising.
enjoy the 14th!
Advertisement