Hi, I would have a problem with the IR, this is the second time that happens to me on a file, and both in the previous file that in this one I’m working on suddenly the IR has stopped working, in practice it opens the window but not the rendering, does not stretch between parsing scene and preparing geometry.
I do not know absolutamnete where i intervene, and for what reason this happens, someone has solutions?
thank you
P.S. the version is the beta 1 core 1.7
Is this happening every time with this file? If so, Can you share the scene file? Chaos
Unfortunately I can not post full images, nor files of some of my work, however I noticed that exporting everything to another file works again.
With the boredom of having to recreate all the multipass.
another question, there is no rescue of the multipass setting?
I also have problem with IR. After reboot of C4D the problem doesn’t resolve. 1523726919_test.zip filename of a bug report.
I looked at your scene and had zero problems with the IR, Started instantly. Had a plugin missing error though, not sure what you’re using on the scene, my guesses are that might be causing the IR loop. Does the IR start if you click and hold the mouse somewhere?
I see that you have some lamp hierarchies. Did you use lamps from the library? If so, those might be the cause depending on your version.(they use xpresso)
It is a plane and corona light in cloner
And what is the plugin/s used in the scene?
Roommaker, but i converted all to polygons.
Sometimes I have the same problem when importing .obj. It helps me copy everything to a new scene..
And also corona tool, drop to floor,magic solo
Thanks, That seems to be the problem with making the IR loop. Although you said you had converted it, There was a “spares” group with the roommaker tags on it. I deleted that group and the IR starts.
So was there the problem in roomaker ?
Why don’t you try it?
I’ve got the same problem with the latest Corona build. I am using an Xpresso setup aswell, but i need to keep it. Is there any way to solve that bug?
If i delete the Xpresso Tag, it works. But thats obviously not the solution i’m searching for. 
Hi everyone. This is unfortunately not easily solvable. What some Xpresso scripts are doing is modifying the scene all the time, which causes the IR to restart. There’s no way to find out, whether the object really changed than checking all its data, which could be very slow. Another way to solve this would be creating a special tag that will mark an object for this special calculation. Or, alternatively, there could be a special IR mode, where you’d have to refresh it manually.
Yes, neither of these is ideal, but that’s just the way C4D is wired at the moment. Let me know what you guys think about the aforementioned solutions.
Both solutions sound reasonable and nice. 
Thanks.
The second solution is just like firing up the normal render(i know it’s not exactly the same, but still no big difference to the user)
The first would be a bit too complicated for the average C4D user. (“I think of a man. And I take away reason and accountability”)
First find the object that causes a problem and then add a special tag, then run IR in a special mode. It’s a lot easier to complain in the forums.
I’d be for an IR “safe mode” that adds this special tag (hidden) to all objects.