I’ve encountered a problem when trying to render out a site plan with a camera that is a long way from the site where the fine gaps between decking boards are rendering out strangely. I’ve got some ideas on how to fix this but thought someone could maybe point me in the right direction. I dont often do this kind of project so its a new issue for me.
The purpose of the job was to try and have 1 model for all of still images and then be able to reuse this for the site plan. it hasn’t really worked out this way because with all of the proxy plants on every view crashes (2Gb Ram). So this image is with only a few trees on with the plan to do everything else in separate passes. I preferred the slight amount of perspective from using a camera for the top down view so would prefer to stick to this if possible
Any help with the weird rendering error is most appreciated. What settings would you normally look at changing to solve this problem?
I’ve only recently switched to this but its 1.50.00 and requires a dongle. I’m not sure about what other info you would need? I’m fairly certain that there are newer versions, would this solve the problem and does this issue appear/dissapear depending on the version?
My camera is about 1Km away from the site. Other than this, I’ve got fairly standard settings with Irradiance map/DMC. My secondary ray bias is at 0.001, would this be causing the problem?
I’ve been trying to figure this out myself for a while now and so far i think I can narrow the problem down to the irradiance map settings. normally for a small scene, I can drop the max subdivs down to say -2 or -3 without any problems.
Through testing, I’ve found setting the max subdivs to -1 seems to help a lot but is going to slow this rendering down rediculously.
At the moment im gradually raising certain settings including:
Hsubs from 60 to 80
Interp samples from 30 to 40
Nrm threshold from 0.3 to 0.15
noise threshold from 0.015 to 0.01 and change filter from legacy to Schlick
The problem I have is finding a good balance between all of these things to that the large image will actually render. I could always set the max subdivs for Irradiance mapping to 0 and this would solve the problem…but calculating the lighting is going to take days.
*click* turned on detail enhancement and the problem is instantly solved with all other settings remaining unchanged, even with -6/-3 for irradiance map settings.
I notice bucket rendering is slower but overall this should more than make up for the extra time that it would have taken to calculate with a max subdivision of 0