OK, alarmist warnings out of the way, I doubt that many people will come across this issue, but everyone needs to be aware, to avoid loss of work/data.

I currently only know that this will reliably crash my macOS Sierra 10.12.6 Poser 11.2.391 system, so confirmation is needed as to whether it affects other versions of Poser and other OS configurations. Please don't test this on an active scene unless you've just saved and confirmed the save is complete!

While editing Poser Preferences>Interface>Shortcuts, I successfully added a shortcut to one of my Python Scripts from the ScriptsMenu hierarchy, without a problem, using a similar key combination to all of the others. However, when I though to try something different, since Poser and the OS itself use a lot of the obvious key combos, I double-clicked another script and when the Shortcut editor dialog came up, I pressed the Fn key on my main keyboard. Poser immediately crashed to desktop in a cloud of bits (nicely tidied into a crash dump in ~/Library/Logs/DiagnosticReports).

Can folks on other setups please confirm this? I have reported this via the current Beta GitLab path, while we eagerly await announcement of the new reporting mechanisms.

Again, please DON'T try this unless you know you've saved your work.

---

My ShareCG Stuff

Verbosity: Profusely promulgating Graham's number epics of complete and utter verbiage by the metric monkey barrel.

The latest build this month) is 11.2.329. MIght be worth trying it. I have it on Mojave and El Capitan.

I have had a problem across multiple installs of Poser, and different PCs, that if you accidently click on a Poser window while it is in the process of doing something the window will go white and Poser will crash. One of the big pluses of Poser 11 for me is the auto save function, although it does mean that once I am happy with a scene and I am sure it is saved I have to go back and deleted the autosave folder otherwise the amount of disk space the autosave folders take up build up.

 

 

I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 -  Ryzen 9 5900HX, with 64 gig ram and 3 TB  storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU .   The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.

I havent seen that, but — running Poser 11.329 on a Mac 10.10 — I've noticed that if I add an external runtime in the middle of a project and then try to go to the Materials window, everything will crash. Been that way since SM introduced 11.

docandraider.com -- the collected cartoons of Doc and Raider

Must be a mac issue. I've hit numerous keys by accident multiple times, never recall it crashing poser. Just tried it again. Still running win7.

I've been running Win10 Pro the past couple of months, and even though I haven't upgraded past 11.2.296, I've never had a problem clicking on the Poser UI while a render is running, it'll just beep at me.

That said, if I'm understanding Hornet correctly, I have seen a render go white if I want to cancel the render for some reason. It doesn't crash, though, if I let it sit and do it's own thing for a while. Then it goes back to rendering, and I can then cancel.

_______________

OK . . . Where's my chocolate?

Butterfly Dezignz

Miss B posted at 1:22PM Fri, 24 January 2020 - #4377562

I've been running Win10 Pro the past couple of months, and even though I haven't upgraded past 11.2.296, I've never had a problem clicking on the Poser UI while a render is running, it'll just beep at me.

That said, if I'm understanding Hornet correctly, I have seen a render go white if I want to cancel the render for some reason. It doesn't crash, though, if I let it sit and do it's own thing for a while. Then it goes back to rendering, and I can then cancel.

If I click on the render screen during a render it ignores the it unless of course on click on cancel. If, on the other hand, I accidently click on say the preview screen while it is loading the a scene from the library the screen will white over. That seems to be a normal response as I have other programs do it as well. The difference with Poser is that the white screen stay for a minute or so and then Poser crashes. It used to do this to me in Poser 2014 and it has been that way on three different computers so the only thing I can think of is it is interacting with another program I have as that is the only thing that would be in common on all the machines.

It happens very rarely these days as I have learnt to be careful and with autosave on in Poser 11 at most I lose about 10 minutes of work plus the annoyance of restarting Poser. I can live with that quite happily, if I was using Poser in the work environment I might have to look deeper but thankfully Poser is just for my fun.

 

 

I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 -  Ryzen 9 5900HX, with 64 gig ram and 3 TB  storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU .   The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.