Here is some interior that I am wrapping up. I have some burned areas on the walls, next to the ceiling, but overall I am happy.
Sorry for the double post. The posts are taking 30 seconds and then I get an error (Error while saving content: SyntaxError: Unexpected token E in JSON at position 1). When I try again, the same thing happens, but it seems that the post is posting anyway.
2 Hours for this seem long for your monster machine. I take it we’re talking 4K here. Don’t you have a 1080Ti to try this on with GPU? (and Next Beta3)
Yes, 4k. cycled back down to the stable release until iToo can update their beta. Yes, I have a 1080ti and every time I try GPU I get errors, so I stopped trying. I figure that I’ll have to build it knowing I’ll be using my GPU and right now I only have the one.
I found that when I start a new scene and use GPU from the beginning, all is well. The old VMPP materials for example is NOT compatible with GPU, however sigers’ new XSMP is compatible with (excluding the metal materials).
However, if I switch an old project to GPu for testing, I too get erros all over the place, mostly related to old free siger textures. Once I remove those all is good.
For this particular scene, you could get away with not using any forestpack for a test. I do realize however you have multiple projects going at one time which make it more complicated to test things if you have to install/uninstall software
Yep, the Siger shaders are my issue, too, so it is good that they have fixed that. They should make a converter script to get rid of that proprietary stuff for older scenes. iToo said this week, so maybe I’ll try something soon.
Seems it wants to use the new AI OptiX denoiser. That AI denoiser still needs some “training” as far I remember. Can’t you just use the default denoiser instead?
NVidia is working on an updated version of their denoiser that should take care of the “out of memory” errors.
Best regards,
Vlado
Is it a driver I need or do I wait for the next V-Ray update? I’ll just turn it off for now.
These are proof that working hard doesn’t make an awesome image. Render times are through the roof and I can’t figure out why, so that is part of the reason they are not coming together. I spent a day troubleshooting why my render times are 6+ hours for 4k stills and I came up with nothing. They are not bad, but I am not going to win any friends with them.
Just commenting on that hdri issue.
was it a dome or a rect light with an hdri? Cause that surely wouldn’t make a big difference in render times if used like a portal, no?
The render times with a V-Ray Sun/Sky or an HDRI were the same. I used an HDRI in a V-Ray dome light. I am reworking these now.
Looking Good. What did you change?
I just tweaked things. The render times were still 3-4 hours, so I haven’t gotten that sorted out.
Tell you what, the Microsoft Spring Update really messed with my computer. I think it is video because not even PS is working right. It’ll all fix itself over time, but I don’t remember a time in history were software updates have cause such inconveniences.
True. They are rushing those updates. Crazy times.
those high render times with vray next?
Yes, but it is probably me and not V-Ray NEXT. However, I just opened an exterior with 3.6 render times of 2 hours took 14 hours with V-Ray NEXT. Now, having said that, Windows Spring Update also happened during the same time frame. I just got a new Windows update, so we’ll see if something fixes itself.
ahh report back and lets see what happens, your not the first person i heard it from actually but from what i see online things should be only faster not slower
Hi Bobby, i see depth of field in your image, is that cause the slow rendering time? may be…