-
1
- #1
hudson888
Mechanical
- Jun 19, 2007
- 2,275
Under certain circumstances it has always been a bugbear that the curves will not render smoothly. For example sometimes you'll see a circle that displays as a hexagon, becoming octagonal as you zoom in and getting gradually smoother. This applies to curves in wireframe, and edges of solids whether shaded or wireframe to a greater or lesser extent. It also seems to be much worse when perspective is turned on.
Cases where it hurts are curves and splines touching or not quite touching by an extremely small amount say 0.001 mm and coming to an intersection or tangency. Sometimes you can measure distances and the answer is zero, but it displays a gap, and others it reports a gap but you can't see where to determine which two of three curves are correct. I find that you can often get an improvement using update display, and usually more so using regenerate work view. But often there seems to be no way or amount of zoom that will make the thing show me enough improvement to be meaningful. Even if you scale the objects by a factor of 1000 you may get the same thing. It only improves when you isolate geometry from the point of interest and then regenerate, so I assume it has something to do with the size of the feature relative to the model that you're displaying.
I guess a typical example would be a line or better still a spline intersecting an arc at a fairly oblique angle, say 10-15 degrees off being tangent. If you subdivide the spline to be two curves as it crosses the arc then reduce the length of one curve such that there is a tiny gap. Now zoom in a try to see whether the end of one or the other curve is touching the arc. I'm darned if I can tell. Worse at extreme zoom it won't let me select to measure I have to zoom out.
The other case is the engine animation. I have got quite good results but with the camera navigation turned on and perspective which seems to automatically engage itself, the wheels and other circular elements appear to have stepped edges even using high quality ray traced rendering. I have tried screwing down the line tolerance, hardware and software rendering and turning off all the accelerator modes under Visualization Performance settings, and I have used two machines with different certified graphics cards. It still won't come out as good as the static version of the same. As long as you don't use a trajectory curve this does not affect you.
We don't have all our licenses switched over to NX-5 so we can't test in later versions. I ran it in NX-3 initially and tried a brief test in NX-4 with no noticeable improvement. I think these two cases are manifestations of the same type of behavior, but would be happy to stand corrected. What if anything have I to change to force it to work, and is it any better in later versions?
Yours Hopefully
Hudson
Cases where it hurts are curves and splines touching or not quite touching by an extremely small amount say 0.001 mm and coming to an intersection or tangency. Sometimes you can measure distances and the answer is zero, but it displays a gap, and others it reports a gap but you can't see where to determine which two of three curves are correct. I find that you can often get an improvement using update display, and usually more so using regenerate work view. But often there seems to be no way or amount of zoom that will make the thing show me enough improvement to be meaningful. Even if you scale the objects by a factor of 1000 you may get the same thing. It only improves when you isolate geometry from the point of interest and then regenerate, so I assume it has something to do with the size of the feature relative to the model that you're displaying.
I guess a typical example would be a line or better still a spline intersecting an arc at a fairly oblique angle, say 10-15 degrees off being tangent. If you subdivide the spline to be two curves as it crosses the arc then reduce the length of one curve such that there is a tiny gap. Now zoom in a try to see whether the end of one or the other curve is touching the arc. I'm darned if I can tell. Worse at extreme zoom it won't let me select to measure I have to zoom out.
The other case is the engine animation. I have got quite good results but with the camera navigation turned on and perspective which seems to automatically engage itself, the wheels and other circular elements appear to have stepped edges even using high quality ray traced rendering. I have tried screwing down the line tolerance, hardware and software rendering and turning off all the accelerator modes under Visualization Performance settings, and I have used two machines with different certified graphics cards. It still won't come out as good as the static version of the same. As long as you don't use a trajectory curve this does not affect you.
We don't have all our licenses switched over to NX-5 so we can't test in later versions. I ran it in NX-3 initially and tried a brief test in NX-4 with no noticeable improvement. I think these two cases are manifestations of the same type of behavior, but would be happy to stand corrected. What if anything have I to change to force it to work, and is it any better in later versions?
Yours Hopefully
Hudson