This workstation has dual 3090s on windows 10, but behavior is consistent across multiple machines, including some single 3090 and dual 4090 machines. That driver (552.22 Studio) is the one I'm currently on. Here's the scene file, thanks for the help!

Running into a problem (bug?) that has cropped up sometime between 2023.1.0.2 and 2023.1.3. I used to be able to render 20 million point instances with relative ease, and now the system runs out of system memory and fails. I have built an example scene for those that are interested.

Error on the ...

Copy that. Thanks for digging into it!

Any update on this? Forcing full reloads when the scene gets to be heavier (and consequently slow to reload) basically makes the renderer useless for lighting any serious work. Would be good to know if we should expect a plugin update soon or look for alternatives for heavier scenes. Thanks!

One more note here: I just realized if you hold onto the light handle after beginning a drag without releasing while the IPR refreshes, then once it finally refreshes you can can drag the light around interactively until you release it.

Oh, and it's probably worth mentioning that sometimes this happens with a far lower point counts (around 1M), but the high point count almost always triggers it. Thanks for looking into it!

Sorry if this has been covered already, but is this considered a stable production release? I'm confused by having alpha and production in the same title!

Here ya go. It's just a high poly sphere with some noise on it, copied to the points on a grid. The more your crank up the grid subdivs, the more spheres get copied and the greater the chances of the reload problem getting tripped. Here, around 15M polys consistently tripped the problem, causing the ...

Nearly a year later, checking back in on this one. The IPR still randomly reloads the entire scene on every light move once the poly count gets to some millionish number. I'd like to reiterate that if this is not something otoy is interested in fixing, then please open source the plugin so we can ...

Oh wow. Yeah this is a massive workflow issue, would be great to get this implemented.