Yes, I'm not seeing any problems with macOS 13.0.1 that weren't already present in Poser under macOS 12 and macOS 11

I have one report that Poser 12 does work in Monterey, though there are some possible issues with multiple monitors and their arrangement causing Poser crashes. That appeared to be resolved by resetting the monitor arrangement to what Poser was previously using, if I understand correctly.

Poser has for quite some time had issues with multiple monitors and following changes in their arrangement (connect/disconnect, move within viewport, etc.) when Poser windows had been saved via memory dot or UI layout on those secondary monitors. They tend to get dumped back on the main display as a failsafe catchall, which can be annoying at times.

In any case, it seems that Poser 12 is mainly compatible, with the above exceptions noted.

I have a new mac on the way, which I expect to ship with Monterey. I will confirm Poser 12 myself unless I can find someone else who's already upgraded.
Both my current machines are running Big Sur, but they are 2011 and 2013 legacy hardware, so need the Open Core Legacy Patcher to run that.

Yup! You got it. the crash prevented Poser from deleting its single-instance lock file, so it finds that whenever you try to start it up again and stops loading.

Poser 12 will not exhibit this problem, since it actually checks the lock file, which contains the process number of the running Poser instance, and ignores it (deletes and replaces it) if it doesn't match an actual running process. Poser 11 hasn't had that fix added, so you'll have to remove the lock file by hand.

The file lives in ~/Library/Group Containers/F6C5GMLRY9.poser/Poser/11 and will be called "Poser-11" (or Poser/12/Poser-12 in the case of Poser 12 for builds after 12.0.203) Where "F6C5GMLRY9.poser" is a global identifier of a software vendor registered with Apple, so it should be identical on all macOS systems later than macOS Sierra, IIRC.

If you can't see the Library folder in your home directory, use the Finder>Go menu and type in Library, or search for "macOS show hidden folders".

Hope this helps :-)

Hmmm. I wish I could help.

I have one 2013 iMac on Catalina that won't run Big Sur and one 2011 iMac on Sierra, that won't go past High Sierra (which I tested on an external HDD). Mojave and beyond are right out because that iMac's AMD GPU doesn't support Metal, so it's a dead end except for running Poser 12 in Windows 10 under Parallels Desktop VM, which it does without a hiccough (Windows update issues aside ).

Those iMacs are still worthy windows machines, even if Poser 12 won't run on them natively. I read that M1 Macs also work really well as Windows machines with Virtual Machines. Lots of levels of code translation happening there, which they appear to be specifically optimised for.

Neither supports GPU Renders (too old, and the 2013 with NVidia GPU only has 1GB VRAM).

Apple need to hurry up and release their Apple Silicon 27" iMacs, which probably won't happen until late this year.

I do see that M1 Macs will support Octane X, so that's a pleasant prospect for future rendering.

I hear one of the P12 testers was using High Sierra until a few months ago, but is now on Catalina. I was hoping to get confirmation that P12 would run under Mojave, but it's still not worth it for me on the 2011 iMac as lack of Metal support will break macOS to the point of unusability, I hear.

Nice! :-)

I wouldn't go so far as to say "incompatible" with dual monitor setups. I have two iMacs with that configuration, and nothing about Poser stops it working with that, it's just that some room switching from Poser 11 times seemed to ignore the dual monitors and place windows on the primary. The workaround has been to use memory dots with your preferred configuration. Sometimes those need to be applied twice to get the windows distributed as desired on both monitors, which is frustrating, but not a showstopper.

When other priorities have been dealt with, it will be worth pushing for that to get solved finally. :-)

I have recently requested the feature for Python to determine the currently selected parameter, since it gets highlighted in the Animation Palette, and determines which parameter is shown in Graph palettes set to follow selection.

No indication of when, or if that request will be accepted, but there is hope.

Unless Poser provides that level of UI and Python API integration, the most straightforward (not easiest) method would be to create a GUI tool that presents a checkbox list of the current actor's parameters for the user to select to have their values reset to initValue (default). To speed up that operation, scripts can have shortcut keys assigned to them in the General Preferences. So a key-combination to open the tool, multiple clicks or drag selection to identify parameters for reset, then press Return or click OK to apply.

Lots of older python scripts made use of TkInter for their GUI programming, which has always been notoriously broken on macs. Those which switched to wxPython worked better, but still had significant issues unless designed or modified to work on both platforms. Poser Python on Windows also received updates that did not propagate to mac Poser Python until Poser 12, where both platforms now run Python 3.7.9 and wxPython 4.1 (Phoenix).

They're a lot closer in their codebase, now, but there are still gotchas in the GUI implementations for each OS. Mostly, things can work with tweaking.

Can confirm the same multi-version parallel Poser execution on macOS. I can't speak for simultaneous renders, though. I've never had a supported GPU, so each Poser instance would have to share the CPU. That's bound to be more efficient letting them run sequentially, though.

Just so you know, there were a slew of reasons which prompted the Poser 12 refresh to remain with Python 3.7.9, rather than go for 3.8 or 3.9. Not least of which is it's the last version which has support for some legacy modules that Apple has not yet seen fit to purge from their OS releases, yet. For example, the macpath module, which deals with the old classic OS 9 style HFS paths: Drive:Folder:subfolder:filename with colon separators gets deprecated in Python 3.7, (yet remains usable) but actually removed from the Python 3.8 distribution. No big loss, you might say, but it is the original file path specification that Poser was built on, and poser files still contain as valid, cross-platform syntax. Worry about forward or backslashes? Ditch them and use colons in Poser. everyone in the same boat, and Poser resolves them when talking to the OS.

time.clock() goes away, as well as other bits and pieces that have been made use of in Python 2.7 scripts for ages.

Not only would the current struggle to get legacy Python2 scripts updated to Python3 be more of an issue than just syntax changes, but some algorithms would have to use different function calls in place of those which have been removed.

@Tim while most Poser users may not appreciate the benefits of replacing the rusted out steam engine under the hood with something newer, those of use who regularly bruise our foreheads against its limitations trying to build user interfaces for new Poser addons and utilities, are thankful beyond words for this effort from Bondware and the dev team.

Given the flaming wreckage that the end of Flash wrought, Poser could easily have been in the same situation with unsupportable Python2 and broken widgets. Thank you!

Yup. Repl on Slck.

Multiple monitor support has been a bugbear for Poser on MacOS since before SmithMicro's acquisition. There was a time, in PoserPro2014, when it worked just fine, remembering which monitor a Poser child window was placed on, and restoring them next time Poser started.

Then it was decided that for safety's sake (my assumption), since some folks had second monitors that were not always attached, that dialogs and child windows needed to open on the main display, rather than just be forced to remain within the currently available, multi-monitor viewport (not always a rectangle, if monitors have different resolutions or are arranged with vertical and horizontal offsets). That way you'd be safe if you went somewhere with your laptop and left the external monitor behind.

The problem was, that Poser would then randomly ignore the saved locations of windows. If Apple can cope with addition and removal of monitors, without losing windows into the off-screen limbo, then Poser certainly should be able to, also.

Practically, though, when enough of the higher priorities for Poser functionality have been addressed, this will get looked at again. It's certainly on my list of squeaky wheels to be greased ;-)

Oh, and the best way to get issues addressed and raise the awareness and priority of their need to be fixed is to report them on: Poser Support Centre (My spelling ;-) )

For any mac users with Poser 10 or Poser Pro 2014 who've skipped to the end of this thread without reading the whole lot, I'll reiterate the process of restoring access to your library runtimes since Flash Player has exited the building.

• Exit Poser (This is very important, as Poser will overwrite your preferences file when it exits, wasting your time)
• In the Finder, open a new Finder window; From the File menu, choose New Finder Window (or press ⌘N)
• With the new finder window selected, from the Go menu, choose Go To Folder... (or press ⇧⌘G)
• In the "Go to the folder:" dialog, type "~/Library" without the double-quotes, and click Go (this is required as a user's Library folder is normally hidden).
• Within the "~/Library" folder, navigate to "Application Support/Poser/10" for Poser 10 or "Application Support/Poser Pro/10" for Poser Pro 2014.
• In that folder, you will find a file called "Poser Prefs". Select the file and from the File menu, choose Duplicate (or press ⌘D). This will create "Poser Prefs copy", a backup.
• Select "Poser Prefs" again, and from the file menu choose Open With..., and then TextEdit (or your preferred text editor) from the dropdown menu.
• When TextEdit opens, make sure the Poser Prefs window is selected, then from the Edit>Find menu, choose Find... (or press ⌘F) and type LIBRARY_IS_AIR into the Search box and press return.
• Double-click on the "0" following the selection and type the digit 1
• Save the Poser Prefs file.
• If you chose to IGNORE the warning to Quit Poser beforehand, Quit it NOW and save the Poser Prefs file again, making sure it still shows "LIBRARY_IS_AIR 1".
• Quit TextEdit (or whichever text editor you used.
• Launch Poser 10 or Poser Pro 2014.
• The Poser Library app should also launch. Its window is unfortunately not dockable within Poser's interface, since it's a separate app, but it has all the functionality, including drag and drop into Poser.

NOTES:

• When Poser 10/PPro2014 launches, you may not see the library palette. If not, from the Window menu, choose Libraries, which will launch the Poser Library app.

• When the Poser Library starts, you may see something similar to this:

• Simply click Continue and the SSL Certificate dialog will go away.