General Category > Anim8or v0.98 Discussion Forum

Anim8or corrupting files

<< < (2/3) > >>

Gregory:

--- Quote from: Raxx on April 29, 2013, 09:23:30 pm ---Ok, I discovered the problem, thanks to the file you shared.

The problem is that you're working on too small of a scale. The height of that letter is maybe half of an Anim8or unit high. That means that in the workspace with how you are zoomed in (according to those attached pictures), each pixel represents an accuracy of a smaller floating point (decimal) value than what Steve programmed Anim8or to handle. So if you click and drag at that scale, Anim8or probably can't pinpoint a precise coordinate at that exact pixel since it's out of it's range, and instead returns gibberish at the very tail end of the x, y, and z coords.

Note also that since the interface only returns three decimal spaces, it's going to show '0' even if it's really 0.00015.

The solution: scale it up! 3D software is vector software, so scale ultimately doesn't matter. If you need true-to-world precision, then instead of setting 1 unit to equal 1 foot or 1 meter, set 1 unit to equal 1 cm and convert to metric if you're not already doing so, or just set 10 units to 1 foot (or whatever...I'm sure you get the point).

If you absolutely have to fix what you've got, open it up in notepad, go into the knots blocks of data, and set all of the Z-Coords to zero.

--- End quote ---

I just opened this page to type pretty much the same thing you just did :)

In the text version of the an8 file, the coordinates go to 5 places but are cut off in the knot dialogue.

An8
knot { (0 -0.01758 -0.10016)

dialogue
0.000  -0.018  -0.100

As for scale, I use 1 unit= 1 meter.  That matches other software native scaling that I use without having to modify the scaling, and the problem is that if I build larger, say at 10m instead of 1m, I still have the problem when I scale the model down for use elsewhere.  I really don't want to have to rescale every model I build outside of its storage version.

Gregory:
Would this be solved by simply making the knot dialogue able to handle 5 decimal places?

Raxx:
Well, I just tinkered around with it a little, and it seems that there may indeed be some sort of true bug or glitch involved. It seems that there's a small "sweet spot", a zoom and window size where it works well, though it seems it starts screwing up eventually after a large of knots have been placed. Then there's the large danger zone where it messes up after the first couple to first several knots. Perhaps it's relative to odd-numbered pixel-wide windows vs even vs too-large vs too big. At this point I think it's safe to say it's a bug, since it just got too complicated to explain rationally just by observation.

I don't think it'd be solved just by enabling 5 decimal places in the dialog box. It'd only grant you an easy way to set the Z to zero after it messes up.

Gregory:
I've been messing around with the scaling and still the best would be for me to be able to keep it at 1 unit = 1 meter.  If only I could set the Snap to Grid at a small measure, like .001 I might be okay, but it won't allow it.

I haven't followed the forums for some time.  Has Steve been on?  Is he going to be updating Anim8or (can I hope for a bug fix on this?)

Gregory:
If we could just have it be locked to Z at zero or whatever the first knot was set at when we uncheck the XYZ box it would be fine, just keep it on that plane.  Or even a feature similar to Flattening a face, moving selected points to one plane.

Navigation

[0] Message Index

[#] Next page

[*] Previous page