Errors In Scale
Forum rules
and Helpful information
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help
Also, be nice to others! Read the FreeCAD code of conduct!
Also, be nice to others! Read the FreeCAD code of conduct!
Errors In Scale
I have this part, (attached), that shows no errors in it's geometry as is, but when any attempt is made to scale it, either with Mario's Macro or the simple one he helped me with, I get this failed result.
Using the Draft > Scale results in no visible object being produced.
Other parts scale just fine with the Draft Scale or either Macro. I'm not getting any errors out in Report view (redirects enabled in Preferences).
I am wondering, is this a problem with FreeCAD/Scale, (bug???), or is this a case where OCE is not performing - causing the error?
The attached .fcstd file has the original part with the 2 scaled by macro parts, (simple copy and clone), along the Draft > Scale clone.
Anyone working on the Draft > Clone tool, this seems to be a problem. Any hope for a fix?
Mark
OS: Ubuntu 13.10
Platform: 64-bit
Version: 0.14.3501 (Git)
Branch: master
Hash: 7d427480823a2e56e900fd28564fb08e3d0f2a9f
Python version: 2.7.5+
Qt version: 4.8.4
Coin version: 4.0.0a
SoQt version: 1.5.0
OCC version: 6.7.0
Using the Draft > Scale results in no visible object being produced.
Other parts scale just fine with the Draft Scale or either Macro. I'm not getting any errors out in Report view (redirects enabled in Preferences).
I am wondering, is this a problem with FreeCAD/Scale, (bug???), or is this a case where OCE is not performing - causing the error?
The attached .fcstd file has the original part with the 2 scaled by macro parts, (simple copy and clone), along the Draft > Scale clone.
Anyone working on the Draft > Clone tool, this seems to be a problem. Any hope for a fix?
Mark
OS: Ubuntu 13.10
Platform: 64-bit
Version: 0.14.3501 (Git)
Branch: master
Hash: 7d427480823a2e56e900fd28564fb08e3d0f2a9f
Python version: 2.7.5+
Qt version: 4.8.4
Coin version: 4.0.0a
SoQt version: 1.5.0
OCC version: 6.7.0
This post made with 0.0% Micro$oft products - GOT LINUX?
Re: Errors In Scale
No success at all with Draft WB Scale, varying results with Clone:
The cone on the left is recessed unlike the cone at the right..
OS: Windows XP
Platform: 32-bit
Version: 0.14.3252
Python version: 2.6.2
Qt version: 4.5.2
Coin version: 3.1.0
SoQt version: 1.4.1
OCC version: 6.5.1
=====================
Just a shell with missing faces.
OS: Windows XP
Platform: 32-bit
Version: 0.14.3343 (Git)
Branch: libpack
Hash: 8dcb8f68cf17ef152d34d226d7699c98c5bb59fb
Python version: 2.7.6
Qt version: 4.8.5
Coin version: 3.1.3
SoQt version: 1.5.0
OCC version: 6.7.0
========================
This one seems OK.
OS: Windows XP
Platform: 32-bit
Version: 0.14.3389
Python version: 2.6.2
Qt version: 4.5.2
Coin version: 3.1.0
SoQt version: 1.4.1
OCC version: 6.5.1
The cone on the left is recessed unlike the cone at the right..
OS: Windows XP
Platform: 32-bit
Version: 0.14.3252
Python version: 2.6.2
Qt version: 4.5.2
Coin version: 3.1.0
SoQt version: 1.4.1
OCC version: 6.5.1
=====================
Just a shell with missing faces.
OS: Windows XP
Platform: 32-bit
Version: 0.14.3343 (Git)
Branch: libpack
Hash: 8dcb8f68cf17ef152d34d226d7699c98c5bb59fb
Python version: 2.7.6
Qt version: 4.8.5
Coin version: 3.1.3
SoQt version: 1.5.0
OCC version: 6.7.0
========================
This one seems OK.
OS: Windows XP
Platform: 32-bit
Version: 0.14.3389
Python version: 2.6.2
Qt version: 4.5.2
Coin version: 3.1.0
SoQt version: 1.4.1
OCC version: 6.5.1
Re: Errors In Scale
http://tracker.dev.opencascade.org/view.php?id=24890
EDIT: But we should not use transformGeometry for uniform scaling and mirroring which could be better done using
EDIT: But we should not use transformGeometry for uniform scaling and mirroring which could be better done using
Re: Errors In Scale
Then there is the good news that it has been reported. Thanks! For now, that seems to put this to the side. At least there is hope it will get fixed by the next release.shoogen wrote:"Upstream Problem"
Resolution: unfixable
http://tracker.dev.opencascade.org/view.php?id=24890
Mark
This post made with 0.0% Micro$oft products - GOT LINUX?
Re: Errors In Scale
hi
the error occurs early, in drilling on a curve
OS: Windows Vista
Platform: 32-bit
Version: 0.14.3389
Python version: 2.6.2
Qt version: 4.5.2
Coin version: 3.1.0
SoQt version: 1.4.1
OCC version: 6.5.1
mario
the error occurs early, in drilling on a curve
OS: Windows Vista
Platform: 32-bit
Version: 0.14.3389
Python version: 2.6.2
Qt version: 4.5.2
Coin version: 3.1.0
SoQt version: 1.4.1
OCC version: 6.5.1
mario
Maybe you need a special feature, go into Macros_recipes and Code_snippets, Topological_data_scripting.
My macros on Gist.github here complete macros Wiki and forum.
My macros on Gist.github here complete macros Wiki and forum.
Re: Errors In Scale
sometimes when i tried to find a simpler test case, it hit
Code: Select all
<type 'exceptions.Exception'>: Convert_SphereToBSplineSurface
Clone of difference: Convert_SphereToBSplineSurface
Re: Errors In Scale
I'm sorry. I was wrong. Besides there is a Problem in OCCT with non-uniform scaling.
Most problems concerning uniform scaling can be circumvented by using transformShape instead of transfromGeometry.
EDIT:
in DRAWEXE this means using "pscale" instead of "deform"
Most problems concerning uniform scaling can be circumvented by using transformShape instead of transfromGeometry.
EDIT:
in DRAWEXE this means using "pscale" instead of "deform"
Re: Errors In Scale
shoogen wrote:I'm sorry. I was wrong. Besides there is a Problem in OCCT with non-uniform scaling.
Most problems concerning uniform scaling can be circumvented by using transformShape instead of transfromGeometry.
Hi shoogen
in that case are the edges still converted to bsplines? if so, sketcher does not support bsplines so we would still have the limitation that sketches can not be mounted to the face of the scaled object. If just scaling the end result this is not necessarily a big problem of course.
Jim
Re: Errors In Scale
No, they are not converted.jmaustpc wrote:in that case are the edges still converted to bsplines?
http://www.freecadweb.org/tracker/view.php?id=1525
https://github.com/5263/FreeCAD/commit/ ... dd192777f8
Re: Errors In Scale
Merged.