sergio777 opened this issue on Aug 05, 2021 ยท 39 posts
Y-Phil posted Sat, 21 August 2021 at 6:08 AM
OK, I'm going to express a few thoughts...
I've been a developer since at least september, 1987. A good online friend, who is actually selling G8/G8.1 based characters on Rendo, is trying hard to come back to one of his first loves: Poser. And he told me one day something I had completely forgotten: CuriousLab invented the Material room, and the concept of linking nodes to build up Materials. And it was with... Poser4? Poser5? I don't remember, Bu since them, it has been such a fantastic idea that many other "big" programs copied the idea: 3DS-Max, C4D, Blender, etc...
What I mean is that I've got a real feeling that this part of Poser is really at the point, and crashes are probably the result of some external interference...
Why? Because I know for sure that I can use my Windows for up to 5-6 days in a row, without rebooting, using 1 , 2 sometimes 3 instances of a Java-based, resource hungry program: PyCharm, which I use to develop on an Intel-NUC in my local network.
Most of the time, since one of the last Windows corrections, Poser 12 has stopped being sluggish. Most of the time, but not always. Launch a function/program 1000x with exactly the context will yield the same response. If something changes in the context, it can yield another response, including a crash...
And that's what I experienced last week: 3x on 2 days: a crash, once in the Mat room, and two in the Poses room.
And I know two circumstances in which Poser can crash:
And last week, the 3 times Poser crashed, it wasn't the case, but it was more or less sluggish. Specifically in one of the scene that contains a 2k hdri, a pool, and 16 Vic4's. Poser is able to manage and to render all this in one shot, I know it. One of the crashes I experienced was: Poser was terribly sluggish, and I lost patience. Unfortunately, instead of selecting another part using the parts selector in the Mats room (upper-right corner), my moved my mouse too fast, and the hierarchy window understood that it had to move whatever character/prop under something else => crash.
I've filed a ticket about these 3 crashes, and with the dev I'm in contact with, we came to think of a bad external influence. Now, I'm trying to understand what.
Besides this, we could soon have a new update of Poser, in which the OptiX-based renders could be corrected... Yay...
๐ซ๐ฝ๐๐
(ใฃโโกโ)ใฃ
๐ฟ 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, Sonoma 14.6.1, 16GB, 500GB SSD
๐ฟ Nas 10TB
๐ฟ Poser 13 and soon 14 โค๏ธ