I draw a circle 96 sides, 1250 MM radius.I draw a rectangle on the circle. make a component. rotate it 90° /50. Make a group. Rotate the group and crash. to finish the project I’ m working on, I go back to 2024: great
Are you rotate + copy (to divide by 50)?
There is a known bug with that. Try moving the cursor far away from the geometry you are rotating.
It was present in 2023 and 2024 for me as well.
Thanks for the advise, it seem to work on 2024.
Fontainbe V5 2500.skp (512.4 KB)
I rotate by and angle then multiply or divide, change the number of copy and crash.
Can you share a .skp file that crashes when you use Rotate/Copy?
Crash rotating.skp (77.7 KB)
basic command crash. I work on Version 25.0.574 and stop working on dropbox with layout. Any trouble with plugins ?
No crash for me.
Update to the current SketchUp 2025 maintenance release and see if that fixes it.
In addition to @Box’s advice to do your modeling with the camera set to Perspective, NOT parallel Projection. I note incorrect tag usage in your model.
ALL edges and faces should be created AND REMAIN untagged. Only groups and components should be given tags.
2 Likes
pretty sure the latest update from a few days ago adresses it.
That was in the release notes for it.
yes !
I was searching for the thread
so, @poulet.thierry , check for updates, then see if it still crashes ?
Apparently this got lost in my reply.
.)
Let’s go for an update, thanks for the support
I don’t get it, why there different type of line if I can’t tag them to put on layer like autocad ?
the rectangle is supposed to be a component. I find it easy to place entities in 2D before making any process.
SketchUp is not like AutoCAD. Don’t try to use it like AutoCAD.
In AutoCAD you have to be perpetually chasing the active layer. This can lead to errors. Layers imply a hierarchy or stacking order which doesn’t make any sense in a 3D modeling application. Layers also imply separation. In SketchUp they aren’t layers, they are tags. They are primarily used for controlling visibility of groups and components.The do not determine a hierarchy in the model nor do they provide a stacking order. And they do not prevent geometry from erging. You must use groups or components for that. Or simply space between the geometry.
If you use tags the way they are meant to be used, that is leave Untagged active at all times, create groups and components to prevent geometry from erging, and give the tags to the groups and components, there’s no need to chase active tags. This reduces the chances of inducing errors into your model.
If you are tagging geometry you have to be constantly concerned about which tag you’ve given to those edges and face. If you follow the rules and tag only groups and components, you don’t need to even know what tag the object has when you open it to edit the thing.
You’ll find that the entire modeling process is simpler if you just use the tools the way they are designed to be used.
1 Like
That’s fine. I didn’t comment about the rectangle being a component. Using a component for that is perfectly logical. By making it a component you’ve prevented its geometry from merging with the circle is laying on. (You could not do that by tagging loose geometry.)
After an upgrade, it seems fix, thanks for your help.
It is fix with upgrade, un tout grand merci, ça sentait le roussi pour les livraison
2 Likes