F17 b5 3D Textures Shimmer / Render as black blocks

OS 11.1. but I've had this problem in the past in pref OS and vers of Fusion

FBX 3D object. did quick texture / bump map on them.

when camera moves, random blocks render in 3D objects where texture is missing. varies per frame.

https://www.dropbox.com/s/pzo7ag9hk46f9 ... r.mp4?dl=0

this isn't a new problem, just a great example thats easy to see in this case. I did 3D camera track that looked pretty good, then wanted to insert 3D objects. this is first pass to see how close trackers are, see if things fit before even attempting to get it into the realm of real looking.

S

Try increasing the size of your scene. It might just be inaccuracy from the renderer trying to handle very small floating point numbers. Scale it up by a factor of 10, and it might go away.

Try increasing the size of your scene. It might just be inaccuracy from the renderer trying to handle very small floating point numbers. Scale it up by a factor of 10, and it might go away.

hi ! interesting idea. is there a simple way to scale every up ? or do I need to do something like attach everything to an axis, then scale the axis.

I had a pretty large scene last year, 25,000 wide at least, sky was 2 image planes in the range of 16K ea to cover camera move, I had flickering textures on models on some frames. I cheated and manually painted the bad frames when it was noticeable in FG areas as the quick fix since camera move was locked.

S

Usually if you just add a Transform3D right before the Renderer3D and set the Scale to 10 or 100 that will do the trick. It'll scale the entire scene, so you don't have to worry about keeping things registered. But if you're using World Position or Z auxiliary buffers elsewhere, you'll need to adjust any nodes that are using them because they measure logical 3d units instead of screen-space units (Motion Vectors, Texture coordinates and Normals will be unaffected). Also, Depth of field might need to be adjusted if you're using it, since that's based on the scene units.

Edit: An extremely large scene might also exhibit this problem because floating point accuracy also breaks down at high values. In that case, the solution might be to scale everything down instead of up.

thanks, I'll give that a try and see what happens !

S

using 3D transform from .1 to 100 didn't make a difference., nor did playing around with add or removing the textures, bump map. its more like error with the polys themselves blinking in and out.

S

Next likely possibility, then, is polys that are too close to one another, or even right on top of one another, and the renderer isn't consistently choosing the one that should be in front.

Make sure you have only one copy of the geometry in the scene. If it's connected in two places, or there are duplicate polygons, or if there is are polys simply too close to the visible ones, that can cause artifacts like you're seeing. If the geo is has thin walls—that is, there's another surface just behind the visible one for the interior surface—then turning on Backface Cull might fix it. The polys turned away from the camera won't be considered for rendering, so they can't fight with the exterior ones.

And that'll be the extent of what I know about troubleshooting that kind of render error.

only single models in scene, nothing double stacked or close. the polys flickering are part of main object surface, really nothing special going on. if anything, the models are fairly far away from the camera to line up in the shot, maybe 15K-20k away, then I think scaled down to look about right. I'll try back face cull but usually I find that causes problems rather than fixes them so I tend to leave it on. if this doesn't work, I may render out stills of models and comp them in 2.5D style or go find some buildings from stock pix I can, a appropriate for the purpose, maybe :/

UPDATE : culling backfires fixed it, thanks ! should of tried that first.

S

Glad it worked!

I have often had this sort of problem with models acquired from one of the many model libraries. It depends on what software the model was made in - some modelling packages don't treat front and back faces in the same way and this can result in double sided surfaces with both sides having normals that point the same way.

Usually I have to take the model into a full modelling package to sort this out, or even remodel completely in extreme cases.