[Plugin][$] TopoShaper - v2.7a - 01 Apr 24

pbacot

The plugin requires Point cloud or isocontours.

pilou

requires Point cloud

Seems that is the key !
When I create points from the file then use TopoShaper that works!
(except for the little triangle bottom left corner? )

PS The alert message when you select points who are not a group/ component is empty!

fredo6

Pilou,

Could you post the file with the point cloud. I'll check for the missing triangle and the missing message.

Which Sketchup version do you use by the way?

Fredo

pilou

It was from the file previous linked!
But here with the points!
I have the 2015 and all at the last versions (plug and Lib) !

test_topo_points.skp

pilou

Resolved!
We must press Concave contour first!

Ben Ritter

When I run the toposhaper using terrain generator, although the contour lines setting is set to 1.0' increments, the first contour line above O.O' becomes 0.783' instead of 1.0'. After that, the contour line intervals are all 1.0' apart.

What could be the cause of this? How can I fix this?

Thanks. Ben

Ben Ritter

topo.skpHere is the file of cloud points

orei

Hi my friends,

i have a little problem.. i tried to model a cloud point to get a soil.. everything ok, except some peek and deep that the plugin generate, and i don't know to get rid.

You see in the attached screen, and in the skp file with point.

Hope in your help! Thanks man!!

PE_9064 - MODELLAZIONE TERRENO_light.skp

orei

no one could help me?

cotty

What would you expect from such a point?

If you only have some of these, you can move the vertices afterwards manually.

Or you can use a plugin to smooth the surface after the creation.

Kenny

If you only have a limited number of these points above the terrain causing the spikes then delete these points before running Toposhaper.

pilou

Why not use Triangulate Points first by TIG ?

derei

After playing with TopoShaper I ended up with several (three) terrains overlapped. Why this happened? It seems I am missing something in functionality of this plugin, so instead of refining the just created terrain, I end up with new modified copies of the terrain.

orei

@kenny said:

If you only have a limited number of these points above the terrain causing the spikes then delete these points before running Toposhaper.

I have some deeps and some peeks. I don't know why this happened.
I know that i can move up and down these points to get a level.. but i would like to understand how to evitate those problem.

Why suggest to use triangulate point instead of toposhaper? toposhaper is much better than triangulate point for this, or not?

Thanks mate!

pilou

It was just a suggestion for have a preview of the terrain and maybe see if there are not aeras where some confusion between near vertices are possible!
And give to Toposhaper faces and not only vertices!

fredo6

@pilou said:

Why not use Triangulate Points first by TIG ?

Pilou,

The first iteration of TopoShaper is precisely the Delaunay Triangulation (same results normally as with the Falé /TIG plugin).

@orei: the spikes are due to singular points with very different altitudes compared with immediate neighbours. TopoShaper CloudPoints generates a surface passing through the points.

My suggestion would be that:

you generate the group of isocontours from the triangular mesh (an option in TopoShaper Cloud)
then from the isocontours group, you generate a quad mesh terrain, using the other tool of TopoShaper.

This will smooth the spikes

Fredo

pilou

orei

@fredo6 said:

@orei: the spikes are due to singular points with very different altitudes compared with immediate neighbours. TopoShaper CloudPoints generates a surface passing through the points.

My suggestion would be that:

you generate the group of isocontours from the triangular mesh (an option in TopoShaper Cloud)

then from the isocontours group, you generate a quad mesh terrain, using the other tool of TopoShaper.

This will smooth the spikes

Sorry Fredo, tried to do what you suggest, but nothing change. I generate the group with triangular mesh (how always i did) and peek and deep are present. After that, used the quad mesh terrain, but peek and deep still present.

Could you, please, verify those things with my skp file previously attached to last post?

Thanks mate. You are the best!!!

fredo6

Orei,

Your cloud points data includes these sharp peaks and deeps. Because TopoShaper Cloud ensures that the terrain surface goes through ALL the points, these peaks will be reflected in the terrain.

Orei terrain.png

If they do not correspond to the reality, then simply discard the points or change their altitude.

Attached is the file with your original points in both Triangular and Quad Mesh mode.

Fredo

SKP file

pbacot

@orei said:

@fredo6 said:

@orei: the spikes are due to singular points with very different altitudes compared with immediate neighbours. TopoShaper CloudPoints generates a surface passing through the points.

My suggestion would be that:

you generate the group of isocontours from the triangular mesh (an option in TopoShaper Cloud)

then from the isocontours group, you generate a quad mesh terrain, using the other tool of TopoShaper.

This will smooth the spikes

Sorry Fredo, tried to do what you suggest, but nothing change. I generate the group with triangular mesh (how always i did) and peek and deep are present. After that, used the quad mesh terrain, but peek and deep still present.

Could you, please, verify those things with my skp file previously attached to last post?

Thanks mate. You are the best!!!

I find that if you to as Fredo suggests: generate terrain from the isocontours, you get a much more regular terrain and you can smooth the few remaining anomalies more easily. If you have bad points in the cloud, there is nothing the plugin can do to change that, but the above procedures helps to "average" them out some.