Since Poser 12 I have the possibilty to use the Optix Geforce RTX renderer and everything was fine (and superfast compared with ordinary GPU rendering) until recently : now, after a few renders it just gives up, first only after having finished a part of the render, then completely. All you get is a grey or black image. You need to restart Poser to get it back working. Worse, it seems to bug some of the Poser files too, once a file failed a render, it will always fail. I wonder what causes this bug.

---

I have moved this to the Poser 12 forum since it is a Poser 12 issue

The Artistic Cat

I would suggest reporting the bug so the developers have record of it and can work on it.

Sunfire's Creations

If you look in the log, do you have this error?

SuperFly: OptiX CUDA error CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]), line 690

Symptoms as you describe. The render stops partway through, the remainder just goes black. If you do another render, it fails immediately and is all black. The original frame that caused it will always generate the same error; subsequent frames or other scenes may work if you restart Poser.

I was getting that a lot but it has been reduced in 12.500. Before, any frame that caused the error would never work with GPU rendering (Optix or not). Starting in 12.500, those frames now work in Superfly as long as I don't use Optix. That's a big improvement because rendering without Optix only takes twice as long, whereas CPU rendering is more like 10x. (I was originally having to reboot, too, but now restarting Poser is enough.) There are also fewer scenes that cause the error.

If you aren't already on 12.500, definitely update to that version.

Do report it though. They need example scenes that generate the error in order to troubleshoot it. It's very hard to fix an error if you can't cause it to occur on the test machines.

I am going to report the problem, too. From what I can guess, this seems related to Cycles2: I have a vic4, with a double setup: one with PoserSurface (no errors) and one with Cycles (crashed on rtx), the hair is based on PoserSurface

No hair, no problems, with hair and character on PoserSurface: no problems as well.

𝒫𝒽𝓎𝓁

---

(っ◔◡◔)っ

👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
👿 Mac Mini M2, Sequoia 15.2, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️

It's just not very predictable. I can have two frames of the same scene, same figures, same shaders, but one works and one doesn't. The pose matters. Maybe has to do with intersections/collision or something like that.

ChromeStar posted at 4:23PM Mon, 19 July 2021 - #4423488

It's just not very predictable. I can have two frames of the same scene, same figures, same shaders, but one works and one doesn't. The pose matters. Maybe has to do with intersections/collision or something like that.

Aha... Pretty much what I was thinking, too

𝒫𝒽𝓎𝓁

---

(っ◔◡◔)っ

👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gamng, Asus Tuf Gaming RTX 4070 OC Edition, 1 TB SSD, 6+4+8TB HD
👿 Mac Mini M2, Sequoia 15.2, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️

I've been getting this same CUDA error at random for a few months. I've already reported my issue. My specific problem sometimes only shows up after working on a scene for a day or more then I add a single prop and all hell breaks loose and all I get is render crashes from that prop. Sometimes changing the mats on the prop will fix it and sometimes it does not. I've gotten the crash with my free super shader and other times it renders just fine. It's very hard to pin down what is happening.

W10, Ryzen 5 1600x, 16Gb,RTX2060Super+GTX980, PP11, 11.3.740