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.

@fredo6 said:

there is nothing I can do (or other scripts can do)

Well, actually I've found myself in the same exact situation with the TAB key causing the viewport to lose focus in SU2023+, but i guess I've managed to find a working solution for this in a couple of plugins.
Check your inbox, is included in the things I shared today.

@JanSteinman said:

When you pay money for a product

Isn't Lord Of The Toolbars free??

Bestiale!

@fredo6 said:

I will probably dicontinue the plugin.

Please no, is my favourite plugin ever

@AISmebel said:

I would like to ask you to share this interesting plugin. I created a lot of interesting things myself with the help of Claude. It's interesting to see what others are doing.

It's currently in the last (I hope so) alpha stage, I'll need to fix a couple of edge cases before it can go beta.

@fredo6 said:

I also want to suggest that after using the plug-in, the components do not deform, bend in shape and retain their component properties

I don't understand what you mean.

Wow, I realize that I didn't understand correctly the proposal, so I retreat my + 20 on this.
Because you basically can't do that in Sketchup (you'd need some sort of modifier system similar to the 3dsMax one to accomplish this).
I understood that he was talking about a non-slicing behavior instead (which would be preferable).

@fredo6 said:

I am not sure it is possible to identfy and carry over the quad mesh, because of the slicing.

I guess it's super-difficult when you need to slice (so you are creating new geometry with new vertex-order/face-IDs), but it's actually quite easy when you just need to deform.
The key is that you apply preemptive triangulation (with different properties for planar quads/planar n-gons) at the very beginning of the deforming operation in order to stabilize vertex order, edge properties and UV mapping, then you can safely preserve/restore everything once the deformation is done.

I'm not a programmer, but I managed to formalize the whole algorithm decently enough that Claude can execute that brilliantly (based on the steps that I use to do manually in order to stabilize a mesh for proper Subdivision/Uv-mapping workflow).

I achieved good deformations which are reliably preserving quads, and UV mapping with decent fallback methods for n-gons.
I was planning to share the code with you regardless (for review before publishing it on Sketchucation), I think it could be interesting if you could integrate (and probably improve) it in some of your plugins, this one could be a clear candidate.

@AISmebel said:

the triangulating line that appears after using the plugin should become soft+smooth

Nope.
It should be soft = true; smooth = true AND cast shadows = false otherwise it will not work.

@AISmebel said:

I also want to suggest that after using the plug-in, the components do not deform, bend in shape and retain their component properties

I agree +20 on this!
I already said that in the original discussion on Trimble forum and I 100% stand on that.
Slicing should be optional. The default behavior should be "deform only", that would make more sense.