Good day
I have this tiny issue that is really driving me up the hill
Every time i smooth a face, and render it, it comes out facated.
The drawing is 30 mb, and when i spool it take another 6 to 7 minutes to see if it is doing that.My questytions
Why is vray breaking up smooth faces (yes i can explode, but i dont want to explode all my symbold ect, vray 1 did not do that)
Is there an update that fixes this.
Please, its really urgent and i dont want to bomb the whole drawing.
It start out right when you start your model, nothing wrong but as the drawing gets bigger and tests are done, changes are made…when you end up doing your final render you realize that all the smooth edges are facated, re smoothing will not help, exploding and re grouping helps, but with a bit of a struggle.
It this the cause of a memory issue?
If so, why doesn’t it notify, hey you’re running low on memory, it will still render, but with facated faces.
No answer within 2 hours of you posting a question which you already know the answer to and your response is “This is a terrible website.” The only terrible thing I’m seeing is your attitude in your second post here.
Maybe if you learned how to use forums before compaining about them you might get a quicker response- your subject title doesn’t explain what your problem is, just that you need “HELP!!!”.
Well said Jackson. Hond, I dont know the answer to your question, I generally dont use smooth faces when rendering with VR4SU, I always do my material editing in the VR material editor.
I’ve only ever seen the smooth surfaces bug a few times and found it easy to work around by exploding, unsmoothing the exploded geometry, grouping it again and aplying smoothing. As I’ve only had to this 1 minute process maybe 3 or 4 times in 6 months I’ve not found it to be much of an inconvenience. Sure I’d like to see it fixed, but anything which I can work around so easily is pretty low priority for me. I’m sure if Google got their act together it could be fixed at its root (along with a dozen other SU plugin and VfSU problems).
Kwist, what length of parse times are you seeing? I was seeing >15 minutes for an SU model of around 30k faces, but since I started running Mattieu Noblet’s Remove CG Mat ruby script before rendering will parse in about a minute. Are you not seeing such a similar improvement with that script?
I experience this problem all the time when I use the Profile Builder plugin. It’s a real pain, because if I explode the group containing the geometry Profile Builder won’t recognize it.
And this website has been pretty terrible after they updated it, the navigation and organisation is horrible. While it initially looks more flashy than the old one, the old one was very easy to navigate.
Though, it seems that the original poster meant it was a terrible website because no-one instantly replied, and that’s just expecting too much. While it might appear so some times, people aren’t chained to the computer constantly looking at the forum. Food and sleep is required as well.
The reason why the faces break up is because a material is applied to the group and not the face individual
If you make the group default material and make the faces the color or texture you want, it will come right. Heard it from someone