Party [ error 319]

[cacciatorino]

This morning modeling doesn't work. all the parts I create, to a verification are damaged.

I restarted both modeling and windows, what else could I control?

 

[cacciatorino]

I solved:
Last time I used modeling, I set the unit of the length in meters and then I forgot to put it back in mmm.

so I was drawing 600 meters long parts and you see that it does not like osd!

 

[Er Presidente]

I solved:
Last time I used modeling, I set the unit of the length in meters and then I forgot to put it back in mmm.

so I was drawing 600 meters long parts and you see that it does not like osd!

Hahaha,
osd's working ball should be 30 meters, by default, if I don't remember badly.
You can change it, but then you lose it precisely down, normally "at least 6".

 

[Superguido]

Maronna,
If you go back to drawing with solidedge I will commission you a job I:wink:

 

[cacciatorino]

Maronna,
If you go back to drawing with solidedge I will commission you a job I:wink:

I don't get it, but if I should take it back next week.

 

[reb_bl]

I solved:
Last time I used modeling, I set the unit of the length in meters and then I forgot to put it back in mmm.

so I was drawing 600 meters long parts and you see that it does not like osd!

hunting, you do Big cars!!! :biggrin:

 

[Shaba]

Hahaha,
osd's working ball should be 30 meters, by default, if I don't remember badly.
You can change it, but then you lose it precisely down, normally "at least 6".

Really?
I'm drawing a 37mt long line
for now he hasn't made any mistakes..

 

[Er Presidente]

Really?
I'm drawing a 37mt long line
for now he hasn't made any mistakes..

I honestly don't remember exactly, maybe it's 100 meters, but the problems were born if for some reason the visualization or operation went out of this sphere at that point the error came out.

the working sphere should be able to calculate, knowing how many maximum decimals can handle osd and knowing that the basic setting of object resolution is six digits, you should be able to know which is the maximum "big" object that osd can handle. if you change the "minimum" resolution to two decimal digits, automatically increases the size of the sphere correspondents "zeri".

 

[maxopus]

I honestly don't remember exactly, maybe it's 100 meters, but the problems were born if for some reason the visualization or operation went out of this sphere at that point the error came out.

the working sphere should be able to calculate, knowing how many maximum decimals can handle osd and knowing that the basic setting of object resolution is six digits, you should be able to know which is the maximum "big" object that osd can handle. if you change the "minimum" resolution to two decimal digits, automatically increases the size of the sphere correspondents "zeri".

less bad that "they bought you", but it would take 118 :biggrin:

 

[Er Presidente]

less bad that "they bought you", but it would take 118 :biggrin:

witty! Look, it's all about cad, the fact that if he doesn't talk doesn't mean he's not there!
:biggrin:

 

[cacciatorino]

witty! Look, it's all about cad, the fact that if he doesn't talk doesn't mean he's not there!
:biggrin:

parasolid reaches 500 meters in default settings.

 

[Er Presidente]

parasolid reaches 500 meters in default settings.

there. ?

 

[maxopus]

witty! Look, it's all about cad, the fact that if he doesn't talk doesn't mean he's not there!
:biggrin:

Not exactly.
I decide the relative and absolute precision, not the size of the model space.

 

[Er Presidente]

Not exactly.
I decide the relative and absolute precision, not the size of the model space.

I am compelled, despite, to dissent deeply and firmly. :smile:
the two things are intimately connected.
It's likely that osd has a smaller sphere than others but, in any case, I can't think of the two variables as disjoining and independent, if I design a skyscraper of 100 mt in "millimeters" I can't have the same precision (absolute) of the model compared to if I'm drawing a small table.
I can use a 100 mt working ball and don't know the problem, but I'll have a lower-generated model accuracy at the same time (e.g. at least 4 instead of at least 6).
certain cads manage the precision of the "clear" model as well as the sphere, others associate each other and you do not realize that changing the one also the other "goes below".

p.s.: I'm starting to get nervous, so, please, let's stop contradicting me!
:biggrin::biggrin:

 

[cacciatorino]

p.s.: I'm starting to get nervous, so, please, let's stop contradicting me!

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/

 

[Er Presidente]

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/

dear you, osd non "derive" from me30, these are fairy tales that put around the commercialoids:smile:

As you see, parachute precision is at least 8 with a 1000-unit ball!
So with a 1000mm ball, you'll have a "less 8" millimeter precision, if you want a 100-metre working ball (100.000 millimeters) you'll always have to use 1000 units that will match each 100 millimeter and then your "millimeter" will automatically be at "less 6".
blocking the "worksphere" is used to help you avoid building different models with "resolution".

 

[maxopus]

I am compelled, despite, to dissent deeply and firmly. :smile:
......
p.s.: I'm starting to get nervous, so, please, let's stop contradicting me!
:biggrin::biggrin:

It's clear to me.
even in pro/e when the model assumes dimensions of two orders of greater size
you need to set a different precision.
It seems to me that it is due to the calculation in mobile comma that stands at the base of all programs.
However, I have never been able to read topics related to the model size setting.
in truth it would be necessary to do a test because I don't think I've ever exceeded 200 meters.
It could also be as you say ... I modify precision and model size come accordingly. I'll let you know.

 

[Er Presidente]

...can also be as you say...

Ohh! a fac'u caxx!


p.s.: I understand, you really want me to get pissed off!
:biggrin:

 

[maxopus]

p.s.: I understand, you really want me to get pissed off!
:biggrin:

But you want to piss yourself off that's what I say. :biggrin:

you can't set the model space, just the precision.
in practice with the default accuracy (0.0012) makes you insert sizes up to 10^6 mm (a cube with 1000 meters on the side).
If you want to make models of higher dimensions you have to change the accuracy.

 

[Er Presidente]

But you want to piss yourself off that's what I say. :biggrin:

you can't set the model space, just the precision.
in practice with the default accuracy (0.0012) makes you insert sizes up to 10^6 mm (a cube with 1000 meters on the side).
If you want to make models of higher dimensions you have to change the accuracy.

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: