I'm trying the Vue 4 demo. When I enter a value at numerics dialog, say, 110 for X it changes ramdonly to some other numer. I get 110.011. Here's what I do on a fresh start: 1) Click the Position tab under Numerics Tab (top right of the screen). I have main camera selected. 2)Enter 110 to X and press tab. Cursor moves to next field which is Y. The X field stays as 110. 3) Click the Position tab under Numerics Tab again or change timeline or do something else. When I check the X value again it's now 110.011 What gives?? I get all sorts of random decimals.

That's normal:-) There must be a reason but you have to hope somebody else explains it. :-)Guitta

So it's a bug then ... :(

No, no! If it was a bug, it would not have followed all Vue versions:-). there must be a technical explanation. I hope somebody knows.

You don't get the same error then??

For sure, I have the same since version 2 of Vue:-)

I've pointed this out before. Why it does that I do not know. It's like it calculates or changes something like say your number is in degrees and it changes it to radians or polar for the render engine. I've been pointing it out since version 3 to e-on. I've told them time and again that there is a error occuring in there render engine. If you want proof render a box with 6 sides in the middle of a forest say. The box will not line up perfectly. Near the top the trees will be goofed up. That's just a symptom of a bigger problem but I don't seem or have not been able to explain it to them properly. I've sent them pictures. It's a bug IMHO cause mojoworld and Bryce both don't do that. I probibly added it to what do you want in version 5 but nobody seems to get it. It's a ugly bug and it gets in my way all the time. It probibly shows up other places. It's like the camera is not a small point it's a rectengle or something. I think the reason is caused by what you just noticed the numbers change by themselves and this little error shows up. Like sure on flat single pictures it's no big deal you'll never notice. Try making a complex panorama in it will be next to impossible to get it perfect. If you just have clouds on the top part of your panorama it will hardly be noticable but it you have stuff crossing from one side to the other and to the top like trees or buildings it will be all goofed up. So nobody listened to me and we are still putting up with it. Ya all get it now?????

I actually finally have proof beyond a resonable dought. I made a panorama that shows it perfectly. The box does not line up near the top by over 5 pixels. I dragged the box into photoshop and fixed it manualy. It's goofed counter clockwise by about 5 pixels at the top. That is a lot of error.

I think it's normal if I understand well : If you don't verify what is after the point (unfortunately it's hidden since the case is not enough wide), you think you enter a natural number (i.e. 110), but in fact after the point the precedent value remains : for me it's not a bug; you just have to delete what is after the point ;=) Yves

Numbers do have a way of changing by themselves in Vue but then again it could be stuff that was not deleted at the end and it's important also to hit the enter key after you finished typing and not go clicking on the scene or the new numbers will not stick.

I've seen this "bug" in many 3D softwares...

Each 3D soft' has an internal coordinates system. This system doesn't work with "real" numerical values, but with "abstract" formulas.

When you enter a value in a field, VUE converts it in it's own geometry units. This conversion is never perfect, often VUE has to choose an approximate value...according to the amount of polygons, the center of the 3D space, the amount of separate meshes in the object-group, the object axis, etc... this is why a value of, i.e., "110" will be converted to "110.011".

You can notice the same "bug" in a 2D graphic application : how do you center a 1 pixel object in a 4x4 pixels image ? or how do you resample by 50% a 5x5 pixels image ?

It can be a problem for architecture or engineering 3D modeling, where you need very precise metric value (down to nanometers). But for "artistic" 3D scene creation, it's not a problem. Your eyes can decide if an object is a the right place or not...

:) Eric

I have not sen this type of problem in Max, TrueSpace, LightWave, Bryce, etc. and there is NO reason why it should happen at this level. Floating and double type errors happen way, way deeper. This is not to be mixed up with rotational number changing which is a different matter. Coordinates in 3d space are very much static. Unfortunately it appears to be a genuine bug. Nothing to so with formulae or centering. For 110 I get 110.011 For 120 I get 120.012 For 130 I get 120.013 For 450 I get 450.045 For 1200 I get 120.12 For 56000 I get 56005.6 I do see a pattern. It may be that Eovia programmers have mucked up the transfer from edit control to memory and back.

Ya get my vote. Send it in cause like there is a bug here somewhere. Its in the camera contols also. 90 degees FOV and pointing 90 degrees is not perfect and that little bit of error you found might add up to the 5 pixel rotation that I discovered... I have pictures I could send them in also. I now have proof there is something wrong and it isn't in other programs like you've noticed. Just send them a bug report along with a link to this thread... Hey I found the Boolean bug so anything is possible. That one is now squwished dead BTW. Remember you're using the stupid demo though. I'd try the full version right now but I can't cause I'm rendering in a different program and I can't stop it.

This type of bug of a very basic nature at this late date and version will not reflect well on Vue. I do not think this has to do anything with Vue converting to geometry units. If I use the dials I can get 110.000. Why can't I type the exactly same number? I tried to send a bug report but they do not accept demo versions.