[Plugin][WIP][OpenSource] Bezier Surface
-
When there is incompatibility (Sketchyphysics 3, SKalp, (my case) etc...
Who is faulty ? These plugins or Bezier Surface ?@oxer : Rodin 2
-
Bezier Surface is confined to its own namespace - so the only thing I can think of would be possibly other extension clashing with observers. SketchyPhysics has been known to clash with many extensions - though I'm not sure if it's been updated recently to address that.
Odd if Skalp clashes... maybe observer fights?
Do you get any errors in the Ruby Console? -
@unknownuser said:
Do you get any errors in the Ruby Console?
See my previous posts from here
Messages were the same that the restant on my post linked
So for have no message errors I disconnect plugins after plugins.
-
ok, in my case progressbar.rb is the culprit
now it's smartdrop
it changes..
-
@thomthom said:
Re: [Plugin][WIP][OpenSource] Bezier Surface
Postby thomthom Β» Mon Nov 24, 2014 4:18 am
unclex wrote:It's just always updating... Like the GIF 8.gif Cannot Click or DoubleClick and when SU openingοΌ nothing prompt
Any errors in the Ruby Console?
What SketchUp version?Now I Know what happened
Smartdrop clash with TTlib2
something named "definition"so I change "definition" to "a4sddefinition" @ smartdrop.rb
and it works -
.
here's a simple introductory example.. maybe something a lot of people can use..
seamless background for rendering
1- draw the patch next to a flat plane:
2- double click the patch to enter the editing mode.. select the back line:
3- using the blue arrow on the gizmo, move the edge vertical:
4- using the red arc, rotate the edge downwards 90ΒΊ (degrees will be shown in the measurement box)
5- using the blue square, scale downwards.. align the green control point with the green axis
6- change the segmentation in the measurements box (i think i used 20)
-
Wow, this topic is moving fast now.
Ok, so it's cubic 4 X 4 Bezier Patch. (As can be seen).
The idea I had was to conform my surfaces(from the node editor) to be valid with your nice editing possibilities after baked down to Sketchup.
I've built a simple translation-Gizmo for moving points(must have that at least) but your editing abilities are way more advanced. More than I would need actually in my GUI, since mostly dependent on parameter values..
This would be at a later stage anyway. There is still plenty of Math to deal with
In all case.
Congratulations to this version! The Gizmo is spectacular.BTW
I don't know if you are gonna continue updating this plugin, since focus is on the subdivision pligin. But if you do and stay with Beziers, have you had a look at the power basis forms ? I studied them a little before since easier to grasp.
They are used a lot in gamers code.They should perform better.
It's also possible to have other degree curves with different matrix.
For example a 3 X 3 Patch with degree 2 Power basis.
Although the @last Bezier code base the degree on n_points so that should be the same.. ?
(this is for a curve)# β β β β # β β1 3 β3 1 β β P1 β MATRIX FORM for Cubic Bezier with 4 controlpoints. # P(t) = [tΒ³ tΒ² t 1] Β· β 3 β6 3 0 β . β P2 β # β β3 3 0 0 β β P3 β # β 1 0 0 0 β β P3 β # β β β β # # t = interval-value between 0 and 1. t2 = t*t, t3 = t2*t # For even greater efficiency a,b,c,t3 coefficients could be cached and reused, # and updated when interval/subd changes. # def power_basis(t3,t2,t, p0, p1, p2, p3) # Calculate 4 coefficients (MATRIX T*U) where 4th coefficient is simply reusing t3 a = t3*(-1) + t2*3 + t*(-3) + 1 b = t3*3 + t2*(-6) + t*3 c = t3*(-3) + t2*3 # Calculate Points coordinates (MATRIX U*V) x = a*p0.x + b*p1.x + c*p2.x + t3*p3.x y = a*p0.y + b*p1.y + c*p2.y + t3*p3.y z = a*p0.z + b*p1.z + c*p2.z + t3*p3.z return Geom;;Point3d.new(x,y,z) # Return 1 point from interpolation end
-
I found a little problem with it.
If you scale to 0 as a way of straightening an edge it freezes and won't update the surface. If you get out of edit mode and go back in an move a point it will revert to the unscaled skin. -
I'm not seeing that occur for me
-
IT doesn't happen on all axis, I have yet to determine exactly when it happens, but I will pin it down.
-
Try this and see if it is just me.
The patch is drawn up the blue along the red. Second patch added, joint moved up on the blue. Select the two edges(3 points) on the red and scale to 0.
Please excuse the sloppy movements, I find it's very hard to maneuver on a trackpad. -
@pilou said:
@unknownuser said:
Do you get any errors in the Ruby Console?
See my previous posts from here
Messages were the same that the restant on my post linked
So for have no message errors I disconnect plugins after plugins.
Ah, there's something suspicious:
@unknownuser said:
Error: #<NoMethodError: undefined method
parent' for nil:NilClass> C:/Users/Pilou/AppData/Roaming/SketchUp/SketchUp 2014/SketchUp/Plugins/ChrisP_PutsCompOnFace.rb:21:in
definition'Looks like this extension has injected itself into the system somewhere. Maybe it modified .definition. What happens if you remove that extension?
(Also, where did you get that extension?) -
@cadfather said:
ok, in my case progressbar.rb is the culprit
now it's smartdrop
it changes..
Ah yes, progressbar.rb is also known. But wasn't that updated?
Is smart drop also conflicting?
-
@unclex said:
@thomthom said:
Re: [Plugin][WIP][OpenSource] Bezier Surface
Postby thomthom Β» Mon Nov 24, 2014 4:18 am
unclex wrote:It's just always updating... Like the GIF 8.gif Cannot Click or DoubleClick and when SU openingοΌ nothing prompt
Any errors in the Ruby Console?
What SketchUp version?Now I Know what happened
Smartdrop clash with TTlib2
something named "definition"so I change "definition" to "a4sddefinition" @ smartdrop.rb
and it works[attachment=0:nay6raup]<!-- ia0 -->Smartdrop.rb<!-- ia0 -->[/attachment:nay6raup]
Right, so this is what is happening:
Smartdrop is modifying the SketchUp API classes - which is a Bad Thing (TM)
class Sketchup;;Group def definition return(entities[0].parent) end end
This method is bugged - it will fail when the group is empty because it tries to get the parent of the first entity in the entities collection. entities.parent would have worked though - so close. (But not perfectly in all older SU versions as there was a SU bug. There is a workaround for that, but that is not implemented here.)
This is a good example of why modifying classes and modules that doesn't belong to your own extension is a bad thing. Before SU2015 it was adding a method that was not there, but as of SU2015 we added .definition for Group - meaning now it's also overriding the Ruby API.Was this the latest version of smart drop - or is there a new one that might have fixed this?
-
@jeff hammond said:
.
here's a simple introductory example.. maybe something a lot of people can use..
seamless background for renderingWow, tutorials already! I'm really baffled that people find it usable in any sense - considering it's so much that's missing.
-
@box said:
I found a little problem with it.
If you scale to 0 as a way of straightening an edge it freezes and won't update the surface. If you get out of edit mode and go back in an move a point it will revert to the unscaled skin.Yea, I'm not surprised there are errors - I actually would have expected many more reports.
I'm going to guess that there are errors in the Ruby Console when your issue occur? -
Yes indeed, was just looking at that. a long error I think repeated.
Error: #<ArgumentError: Cannot convert argument to Sketchup::Point3d> C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_patch_quad.rb:528:in
intersect_line_line'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_patch_quad.rb:528:ininterpolate_points' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_patch_quad.rb:553:in
interpolate_interior'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_patch_quad.rb:262:inrefresh_interior' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_surface.rb:1046:in
block in refresh_automatic_patches'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_surface.rb:1044:ineach' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_surface.rb:1044:in
refresh_automatic_patches'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_surface.rb:1026:inupdate_after_transformation' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/bezier_surface.rb:427:in
transform_entities'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/operator_gizmo.rb:105:inblock in init_gizmo' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TT_Lib2/gizmo_manipulator.rb:65:in
call'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TT_Lib2/gizmo_manipulator.rb:65:inblock (2 levels) in initialize' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TT_Lib2/gizmo_manipulator.rb:319:in
call'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TT_Lib2/gizmo_manipulator.rb:319:inblock in initialize' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TT_Lib2/gizmo_manipulator.rb:1504:in
call'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TT_Lib2/gizmo_manipulator.rb:1504:inonMouseMove' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TT_Lib2/gizmo_manipulator.rb:473:in
onMouseMove'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TT_Lib2/gizmo_manipulator.rb:156:inonMouseMove' C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/operator_gizmo.rb:70:in
onMouseMove'
C:/Users/Ben/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/tt_bezier_surface/operator_manager.rb:56:intrigger_event'
It appears this keeps repeating, but I could be wrong.
Edit: on a second look it doesn't repeat, but is very very long.
-
@thomthom said:
I'm really baffled that people find it usable in any sense - considering it's so much that's missing.
i bet what people could do out of Sub-d "as it is" would be even more surprising
-
I have one request that would make it much more useful.
Add support for editing without messing up UVs like your vertex tools works. -
@box said:
Yes indeed, was just looking at that. a long error I think repeated.
Edit: on a second look it doesn't repeat, but is very very long.
Thanks for posting the error message.
Advertisement