• This forum is the machine-generated translation of www.cad3d.it/forum1 - the Italian design community. Several terms are not translated correctly.

Party [ error 319]

  • Thread starter Thread starter cacciatorino
  • Start date Start date
Here!

1.2 x 10 "at least 3", and arrive at the kilometer, if you want the "less 6" you have to go down to the "ten to 3" (a sphere of one meter).

p.s.: I don't want "insister", but the parachute seems to get better.
:biggrin:
Aspè that I am ageing and losing references (i.e., I use parashyper, he never loses them) :biggrin:

What do you mean the parachute gets better?
 
Aspè that I am ageing and losing references (i.e., I use parashyper, he never loses them) :biggrin:

What do you mean the parachute gets better?
that with a one meter ball comes to "less 8" instead of "less 6".
 
I asked for lumens on the American forum if, as soon as they answer me saying that actually parasolid is the far better product on the market I get resentful.
 
I was answered by the "dad" of himself (what honor!) :smile:

says that if you use the measuring unit always and anyway the meter, and that the unit that is set by the user only serves for the user interface, and is not considered in the calculations of the cad.

The workspace is a 500-metre radius ball, and apparently it's "hard-coded" in the software (you can't exceed). But in the next version there are improvements on this aspect, in order to better interface with the world of civil engineering.
 
I was answered by the "dad" of himself (what honor!) :smile:

says that if you use the measuring unit always and anyway the meter, and that the unit that is set by the user only serves for the user interface, and is not considered in the calculations of the cad.

The workspace is a 500-metre radius ball, and apparently it's "hard-coded" in the software (you can't exceed). But in the next version there are improvements on this aspect, in order to better interface with the world of civil engineering.
You know it's hard coded?
and that the millimeters are meters in reality?
2-0 for me:
 
I was answered by the "dad" of himself (what honor!) :smile:

says that if you use the measuring unit always and anyway the meter, and that the unit that is set by the user only serves for the user interface, and is not considered in the calculations of the cad.

The workspace is a 500-metre radius ball, and apparently it's "hard-coded" in the software (you can't exceed). But in the next version there are improvements on this aspect, in order to better interface with the world of civil engineering.
You know it's hard coded?
and that the millimeters are meters in reality?
2-0 for me:
means that the variable of the resolution of the piece is independent and adapts to the size. I don't think it's possible to model a 500-metre piece with a resolution at "less 8" otherwise it would be in contrast to the limits declared by parasolid.

that caxxo means "millimeters are meters?":biggrin:
 
I was answered by the "dad" of himself (what honor!) :smile:

...
and of course he answered you directly "he"! With that question, you made the walls of the whole building tremble!
You will see that "merdon" will come out of this thread!
:biggrin:
 
...
says that if you use the measuring unit always and anyway the meter, and that the unit that is set by the user only serves for the user interface, and is not considered in the calculations of the cad.
Caxxate...
The workspace is a 500-metre radius ball, and apparently it's "hard-coded" in the software (you can't exceed). But in the next version there are improvements on this aspect, in order to better interface with the world of civil engineering.
improvements...but look a little! and think that up to "birds" did not even exist in the list of possible hypotheses of thought. . .
:biggrin:
 
means that the variable of the resolution of the piece is independent and adapts to the size. I don't think it's possible to model a 500-metre piece with a resolution at "less 8" otherwise it would be in contrast to the limits declared by parasolid.
from what I understand, parasolid has a precision of 10^-8, and the max length of 1000, that is to say that it manages a numerical value of 11 digits (999,0001). and does not use any mobile comma, as it does pro/e. I read that this mobile comma pro/e causes many problems when exporting to step or iges (receiving issues), always from the American forum:
http://www.proesite.com/accuracy.htmthe user who reports the link says that the same ptc recommends to use absolute and not relative accuracy, if you are planning to export to step or iges.
 
means that the variable of the resolution of the piece is independent and adapts to the size. I don't think it's possible to model a 500-metre piece with a resolution at "less 8" otherwise it would be in contrast to the limits declared by parasolid.

that caxxo means "millimeters are meters?":biggrin:
You can't stand today. :-)
means that even if you work in mm the unit is always the meter... so the precision in mm is at -5... or not?
in pro/e you can set relative and absolute precision but, you will soon unwind it as you have transplanted the kernel. :-)
 
from what I understand, parasolid has a precision of 10^-8, and the max length of 1000, that is to say that it manages a numerical value of 11 digits (999,0001). and does not use any mobile comma, as it does pro/e. I read that this mobile comma pro/e causes many problems when exporting to step or iges (receiving issues), always from the American forum:
http://www.proesite.com/accuracy.htmthe user who reports the link says that the same ptc recommends to use absolute and not relative accuracy, if you are planning to export to step or iges.
Can you smell it?
:biggrin:
 
from what I understand, he has a precision of 10^-8, and the max length of 1000, that is to say that it manages a numerical value of 11 digits (999,00000001). and does not use any mobile comma, as it does pro/e. I read that this mobile comma pro/e causes many problems when exporting to step or iges (receiving issues), always from the American forum:
http://www.proesite.com/accuracy.htmthe user who reports the link says that the same ptc recommends to use absolute and not relative accuracy, if you are planning to export to step or iges.
the problem exists if you work badly and have to do with very small surfaces that converge near the fittings and who has a different cad uses a different precision.
Just that whoever receives the file signals it to you, modifies accuracy and sends it back.
in standard modeling and lamiere this "problem" is not there.
 
Since modeling is a me30 program, developed on unix machines 40 years ago, I wouldn't be surprised if you actually work 8 bits emulated to 64 to make customers happy, and so more accurate can not be. :biggrin:

parasolid by default works with 10^-8 precision, and can work with 1000 size models as max (500 per side compared to origin).
http://www.techsoft3d.com/getting-started/parasolid/accuracy-of-parasolid-models/
sincerely not.... I think I missed something...
Let's start again, if parasolid declares that with a precision at -8 you have 1000 units of maximum size, a cube of 500 meters and with a precision at -8 (millimeters) you can't do it, test.
It's clear that you can have a 500-metre space and model accuracy at -8, but it's very dangerous.
If you want to avoid trouble, you have two roads, or you have the "space" and connect it to the resolution of the model (cocreate) or do the reverse, free the space and adapt the model (pro/e). every choice to his pros and his cons.
leave the fixed space "at maximum" and do not control the resolution of the model is very dangerous, try to make two cubes from 1 mm to 500 meters away from each other and see.
see means succeeding in making a connection that is at least one "less" compared to the cube size (or smaller to the limit of the system). Because even the empty space must be calculated if, if it really works like this, it will be filled with hope. :biggrin:
 
Because even the empty space must be calculated if, if it really works like this, it will be filled with hope. :biggrin:
I faithfully report what I found on the American forum, in response to my post:
hunter:
i'm discussing about an interesting question with some collegues.

what is the relation between workspace wideness and modeling precision?

i have found a doc where it is stated that parasolid uses a precision of 10^-8 and a workspace of 1000 (+/- 500 around the origin). does it mean that i can model a sphere of 500 meters of diameters and 10^-5 mm of precision?

and when i use "mm" as default unit in se, does it mean that i can model a cube of 1000 mm (1 meter) of edge? or when i use "mm", it assumes "meters"? or the se default unit does not affect "parasolid" modelization facts and it is just a question for the user interface?

the other collegues are supporters of pro/e (10^-6) and cocreate (10^-6), so it seems that se wins!

father of himself, in answer to me:
the "units" in solid edge as you say are just an interface for the user.
the base unit in solid edge (as most other systems) is meters. so yes,
beyond a 500m sphere things will get strange.

ps> some interesting stuff coming in st5 to allow "dicing" of
multi-kilometer terrain models to better match up with the solid edge
philosophy.

other user, answering me:

when i studied it a few years ago there were lots of problems within
pro/e and with imports and exports because of the inaccurate geometry.

pro/e makes it more complicated with their "relative accuracy". it is a
ratio of the size of the model tot he smallest edge. this is one reason
it is hard to import pro/e geometry into other cad packages that use a
fixed precision. the small missalgnments it allows show up as gaps and
means that surfaces can not be turned into solid bodies. it can also
mean that on a very large part you can not create a very small feature
like a round.
http://www.proesite.com/accuracy.htm

if, in response other user:
quite right. when we built solid edge, we had looked at our previous
system ems which allowed you to change accuracy and we looked at pro/e
which used a model-size relative approach and decided both of those were
fraught with peril. i believe our decision has proven right over the
years and led to good stability and repeatability, including file
exchange.
I understand that I'm asking the bear if his wine is good, but hearing the opinion of highly competent technicians is always interesting.
 
a curiosity, but if you can "model" according to a set?
I'll explain, it might be that if you build a different sphere, independent, when you're modeling the single model and another one just to handle the axieme, so you could avoid hitting at the same time in the two limits.
 
a curiosity, but if you can "model" according to a set?
I'll explain, it might be that if you build a different sphere, independent, when you're modeling the single model and another one just to handle the axieme, so you could avoid hitting at the same time in the two limits.
I do not think I have understood well, however to test if (v20 32 bit) I have created two cylinders d20 l 50 (millimeters) with a single extrusion, whose centers are at distance 499.000 mm from the origin of the axes. then I picked up the edges with radius r=1 and did it without any hesitation. So much to prove, I changed the r=0.1 connection, and here too, no problem. if instead I bring the distance between the centers to 520.000 (beyond the theoretical limit) the feature still appears in the tree of the model but the visualization graphics fails.

I attach the step of the part to 499,000*2=998000 mm. Unfortunately on this pc I have no osd so I can not see how he would behave to do this job.
 

Attachments

I do not think I have understood well, however to test if (v20 32 bit) I have created two cylinders d20 l 50 (millimeters) with a single extrusion, whose centers are at distance 499.000 mm from the origin of the axes. then I picked up the edges with radius r=1 and did it without any hesitation. So much to prove, I changed the r=0.1 connection, and here too, no problem. if instead I bring the distance between the centers to 520.000 (beyond the theoretical limit) the feature still appears in the tree of the model but the visualization graphics fails.
with the same cylinders with swx you get to 499996 then signals error in the sketch saying that "the sketch has not been updated because you would create an invalid geometry, for example a line of length 0"
if I design only a line with half-carry in the origin I can quote from the origin to an extreme up to the mvalue of
5000000001108855999999...(periodic)
500000.00000001108856 fails

I'm pretty frank. in my work I will never get to need a clutter of the "machine" next to the kilometer :smile:
 
Hell for me this limit is a big problem!!!!:confused:
having to model the stars trek spaceships, being the ncc-1701e sovereign class 685 meters long how do I solve??? ? :biggrin::biggrin::
 

Forum statistics

Threads
44,997
Messages
339,767
Members
4
Latest member
ibt

Members online

No members online now.
Back
Top