@fredo6 said:

For information, you CANNOT put 'r' in front of the number. If you type 'r' as first character, then Sketchup will switch to whatever command has a shortcut 'r'.

Doh, that's right!

@fredo6 said:

there is question of the precedence

I guess option 2 is the correct one.

@fredo6 said:

I also have to find a way to specify the radius in the VCB

I guess r3,5 should be model uinits
And r3,5 plus units should set an arbitrary unit (different from the default model unit)

If you put the "r" BEFORE the number I guess that you can safely assume that it will be radius based.
If there's no "r" in front, then the number specify the angle.

If you put it after the number how do you specify the arbitrary unit?
In your example should be something like 3,5rcm (wich is weird compared to r3.5cm in my opinion).

@fredo6 said:

whether you know in your model what value of radius you would enter

To be fair, I see quite a lot of real world use cases where it's easier to know which radius is needed, rather than the angle.
Sounds like a reasonable feature request.

@valerostudio I've sent you the rbz files in a private message
@rv1974 I've also sent the same stuff to you, because as far as I can remember, you are also a 3dsMax user and most of my tools are "porting" of Max features still missing in the current Sketchup quads/subdivision workflow. So maybe you can have some fun with that.

@maxosmedia said:

confirmed my answers with screenshots,

Your screenshot looks like this

because of this

So probably you are the one who can't read.
Can you please stop to be an ass?
Thank you in advance.

@majid said:

using Su Make (2007 I guess ) version

2017

@Rich-O-Brien
So much triangles
Btw, Z colinear could work better if the road is not supposed to be perfectly straight in XY.

@valerostudio I'm refining a tool that can do this interactively (along with many other freeform modeling features). It also integrates very well with Artisan2 and VertexTools/SubD. Let me know if you're interested in beta-testing.

@Rich-O-Brien said:

your — launch

gotcha

I like the wooden version better!

Is there a legal way to use SU 2023 and SU 2022?
As far as I can tell, since 2022 they went full subscription.. and with subscription you can only install the last 3 versions (so currently 2024/25/26).

For this exact reason in the plugins I'm developing I'm supporting all the way down to Sketchup 2017 (which was the last free version) and I try to make sure that everything works properly up to SU 2021 (which was the last perpetual version and my favourite one). Then I test on 2024-26.

I personally don't give a fraction of a shit about SU 2022/2023, because they are currently available only as pirated versions.. isn't it?

@artemisglt does it happen with a specific model or with all models?

@artemisglt You just select the diffuse map and call it a day.
(you can add the other maps after the import if you really need them)

@mamoodoo said:

I do have to learn to be better organized and be orderly as you said

The model I uploaded has as few polygons are possible (given your initial shape). I included plenty of steps and comments on the process.

There are a couple of thing that you could learn from that process.

1. The less unnecessary polygons you use, the better.
2. Order of operation matters. Keep your model as modular and low poly as possible before doing the heavy deformations. Add thickness and join modules later on.
3. When you have a big problem, don't try to one-shot at it. Divide it into multiple more manageable problems instead.

I hope that can be helpful.

@mamoodoo said:

here is just the model

To be fair you included a whole bunch of hidden useless stuff.

Here's your model fixed and solid.
I included the different stages that I used to completely rework it, so you can take a closer look to a better approach.
Facade_fixed.skp

You don't necessarily need Rhino to work with this kind of stuff, as long as you are well organized and do everything in the proper order.

Your approach was fundamentally wrong because you duplicated the geometry 4 times and gave it a thickness BEFORE the deformation.
Is better to work with modular flat pieces, then deform, then add thickness, then merge them together.
In this way you avoid feeding ~90k veritces into the deformation algoritm when you can Flowify just ~3k vertices.

I didn't touch your curves, but I would strongly recommend that next time you balance the polycount of your curves in a more clever way.
You have tons of segments for very small curves, but on the other hand you have only 4 segments on the main curvature.
That's a quite bad density balance. You should have more segments for the big curve and less segments for the small curves.
I suggest to have a look to Fredo's Curvizard for this kind of optimization

As a side note, your Flowify rig was completely wrong.
You need to connect the corresponding vertices, not the closest ones (that was causing flipping even with basic test shapes) and you should not add tons of unnecessary cells to the grids.

@mamoodoo I'll try it tomorrow

@mamoodoo can you share just the shape and the intended flowify rig?
So maybe we can try to take a closer look at the problem?

The new half-baked pbr thing does more harm than good.

I see a lot of percentages going on in your tool.
I would genuinely be curious to know: percentage based on what?

How do you define "100% geometry load"?
What is "Crash Risk percentage"? Is there some deterministic way to calculate crash risk percentage?

What about "Texture memory percentage"? 117 MB is 1%, ok, then 100% is supposed to be 11,7 GB.
What does this actually mean? It's calculated based on actual free system RAM? VRAM?

What is the "Health" percentage? What parameters is it based on?

Is there a documentation available for this tool that explains what all this parameters are supposed to represent?

Massive work.. do you model everything in Zbrush or you do something in Sketchup (e.g masses/concept)?

Try to turn on all the layers in the "tags" panel and se if it's something related to layer visibility.