Here is an update on the issue +.
I have found out there is difference in MI scene rendering depending on the method used for execution.
BTW: this is not the first time such a discrepancy have been discovered.
All is good if you Drag and Drop scene file onto the Batch Renderer executable.
But I hate Drag and Drop and never use it. Instead I have made an .mi file association with IrayStandaloneRenderer.exe
So when I double click scene file and fire up renderer, at least 2 discrepancies could be observed (there might be more):
1. Shadow artifacts are not removed.
2. At the end, when message pops up asking to open file, there is NO button to open a log file.
I did verify that my file association is correct and even if I use "Open With* from context menu and navigate to the executable, it still does render with 2 problems mentioned above.
FT ticket was updated....UPDATE:
Apparently where was an issue with file associations in Windows 10. it was pointing the older version of the Batch Renderer.
And even when I picked the right executable in "Open With", it would revert to the old one on the fly. I LOVE Microsoft!
After cleaning the .mi association in registry and recreating it all is working fine now.
2 Years Ago by