I tried that with DM's PromptFantasy.

In my environment, a similar phenomenon occurs when I check "Enable OpenGL Mip Maps". The screenshots are from P13, but the behavior is the same on P11.

I think that is affected by anti-aliasing and denoising by the OpenGL library.

In my environment, when the Pixel Samples value is 100, a threshold value of 0.001 in Poser12 is equivalent to about 0.5 in Poser13, and 0.002 is equivalent to about 0.7. However, that may depend on the Pixel Sample value and scene content.

For that scene I tried, with a threshold value of 0.002, P12 computes about 3000 samples before processing the next bucket. P13 computes all 10000 samples, so it takes a very long time.

* Confirmed by watching the rendering progress bar

I seeked for a threshold value that cuts off the computation at about 3000 samples on P13, and it is about 0.7.

The result is similar quality with slightly faster render times.

Also, "with a threshold value of 0.002, P12 computes up to about 3000 samples" for that scene, so if the Pixel Samples value is 50 or less, P13 renders faster even with a threshold value of 0.002.

I have seen a similar problem on Poser12/Windows 11. Please check the General Preference.

These are the results of the CPU rendering, but the behavior is the same for GPU rendering.

On Windows11, Multi-Device rendering doesn't seem to work properly.
Multiple cards are correctly recognized, but it seems that only one is used in the rendering.

I upgraded to Windows11. I've only upgraded the OS and haven't changed Poser 12.0.703 and NVIDIA driver 472.39.
On Windows11, Multi-Device rendering doesn't seem to work properly.
Multiple cards are correctly recognized, but it seems that only one is used in the rendering.
It worked fine on Windows10 before the upgrade.
Curiously, Poser 11.3.818 works fine on Windows11.
Is it a problem in my environment? Or is it a known issue?

FVerbaas posted at 9:57AM Sat, 16 January 2021 - #4410453

Solution: Try to copy your code to notepad and save from there in a new file.

Thank you for your response.
I created a new script by copying and pasting on Notepad, but the trouble was not solved.

D:\usr\poser\scripts> type test.py         * <- old script
print("!!! test !!!")
import sys
print(sys.version)

D:\usr\poser\scripts>
D:\usr\poser\scripts> type test2.py        * <- new(copied) script
print("!!! test !!!")
import sys
print(sys.version)

D:\usr\poser\scripts>
D:\usr\poser\scripts> fc /b test.py test2.py
Comparing files test.py and TEST2.PY
FC: no differences encountered


D:\usr\poser\scripts>
D:\usr\poser\scripts> certutil -dump test.py
  0000  ...
  0037
    0000  70 72 69 6e 74 28 22 21  21 21 20 74 65 73 74 20   print("!!! test
    0010  21 21 21 22 29 0d 0a 69  6d 70 6f 72 74 20 73 79   !!!")..import sy
    0020  73 0d 0a 70 72 69 6e 74  28 73 79 73 2e 76 65 72   s..print(sys.ver
    0030  73 69 6f 6e 29 0d 0a                               sion)..
CertUtil: -dump command completed successfully.

D:\usr\poser\scripts>

Results (D:\usr\poser\scripts\test2.py)

File "", line 1
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 2-3: truncated uXXXX escape
!!! test !!!
3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)]

Results (D:\poser\scripts\test2.py)

!!! test !!!
3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)]

That seems to be a problem that depends on my environment.
I would like to solve it by using "D:\poser\scripts".

adp001 posted at 6:39AM Sat, 16 January 2021 - #4410436

Same error if you write

print("Something")

Thank you for your response.
I tried as follows.

script

print("!!! test !!!")
import sys
print(sys.version)

Results (D:\usr\poser\scripts\test.py)

File "", line 1
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 2-3: truncated uXXXX escape
!!! test !!!
3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)]

Results (D:\poser\scripts\test.py)

!!! test !!!
3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)]

The results are the same as before.

jadeite123 posted at 7:59AM Thu, 23 April 2020 - #4386616

Poser11.3(Specific module: python27.dll) crashes every time in the following case in my environment:

It may be caused by DSON Importer....

After the clean installation of 11.3.813, python27.dll didn't crash with File-Exit. However, it crashes again after the reinstallation of DSON Importer.

It crashes when deleting a G2F from a scene, and Event Viewer shows the same code(0xc0000005) and the same offset(0x0000000000119a32).

jeffnlkpt2 posted at 10:34AM Sat, 18 April 2020 - #4386467

Any one else having trouble with Poser crashing when trying to delete anything or starting a new project? Mine crashes constantly anymore.

Poser11.3(Specific module: python27.dll) crashes every time in the following case in my environment:

• Trying to close Poser by File-Exit.
• Trying to delete a Genesis/G2F/G2M from a scene.
• Trying to close a scene including Genesis/G2F/G2Ms.