Hello everyone.
In update 2023.2.2 I have problems with Render for imported FBX objects. This was not happening on the same PC with 2022 versions on the same model.
When you have a close up view the RENDER start to show streaky textures and problems. I can’t produce videos like this.
I have tried changing FBX source, enabling, disabling all options but nothing corrects the error. Does anyone know why the problem is occurring?
I attach sample images. Best regards.
These look like they could potentially be normals issues. When you imported did you let UE create normals and tangents itself or did you preserve what the model had?
I just speculating, but did you tried the models with blank material? Maybe you accusing the fbx but the real culprit is hiding inside the material.
Thank you very much for your answers.
I am attaching GIF images so you can see what is going on.
First test:
Same FBX, with PATH TRACER in TwinMotion 2023.2.2:
It is observed that the RENDER comes out very bad, with many lines.
Next Test:
Same FBX, with PATH TRACER in TwinMotion 2022.2.3:
It is observed that the RENDER does work well.
I attach this link with the FBX, the GIFS and the model in TwinMotion 2022.2.3, so that you can open it in version 2023.2.2 and see if it is only in my PC that fails.
Thank you very much.
Best regards
Hi, the same thing happened to me when I linked a Revit project with direct link to Twinmotion, and the truth is I don’t know why that happened, the fact is that I had several projects linked in the same file (from Revit) and it What I had to do to solve it was change the base file that I originally had linked to twin, that is, I took another of the files I had and converted it into the base file,…unfortunately everything was moved to time to link it with twin (the twin objects were moved) I had to rearrange them and those lines were no longer visible, I hope my experience is of some use to you and you can solve it
Hello, Thank you very much for your help. I have not been able to solve it yet. I think it is a software situation rather than mine. Hopefully in some next update they can fix it. Is there any way to report these bugs to TwinMotion developers?
