Fri, Apr 19, 9:06 PM CDT

Welcome to the Poser 12 Forum

Forum Moderators: nerd, donnena Forum Coordinators: nerd

Poser 12 F.A.Q (Last Updated: 2024 Apr 18 2:45 am)



Welcome to the Poser Forums! Need help with these versions, advice on upgrading? Etc...you've arrived at the right place!


Looking for Poser Tutorials? Find those HERE



Subject: Poser 12 crosstalk with my Poser Pro 11


RazBurried ( ) posted Fri, 13 November 2020 at 5:19 PM · edited Fri, 19 April 2024 at 7:39 PM

Every time now when I launch Poser 12 i Get this error message "An errror occurred importing addon dson : ERROR: DLL load failed: The specified module could not be found.

An errror occurred importing addon Reality : ERROR: bad magic number in 'Reality': b'x03xf3rn'

An errror occurred importing addon Reality : ERROR: bad magic number in 'Reality': b'x03xf3rn'"

Those Script are installed in Poser Pro 11 and not in Poser 12. Does it mean I have to uninstall Pro 11? Thanks


hborre ( ) posted Fri, 13 November 2020 at 6:41 PM

You should not have to uninstall P11. Are you sharing the main P11 runtime with P12?


RazBurried ( ) posted Sat, 14 November 2020 at 3:09 AM

Yes I am, My Runtime directory is in D:/Users/Public/Doc../P12 And my Python script are in: D/Programs/ ....P11 Why would P12 try to get Python script in P11? Just find that a little strange.


hborre ( ) posted Sat, 14 November 2020 at 7:56 AM

That is peculiar. I only share my Poser 11 content runtime with P12, not the main runtime. I've had such crosstalk problems in the past with runtime folders from older Poser versions. However, the runtimes were associated with the main folders which contained the troublesome scripts, ergo those scripts had to be either moved or deleted.


randym77 ( ) posted Sat, 14 November 2020 at 11:48 AM

I've gotten similar messages (not about DSON, because that's not installed, but with other Python scripts).

I think it's because I attached my Poser 11 runtime to Poser 12. Didn't have any error messages until I did that.


hborre ( ) posted Sat, 14 November 2020 at 12:31 PM

That is exactly my suspicion, shared Python Scripts from linked primary runtimes. It confuses the hell out of Poser and flags errors. My guess if you have content in the primary runtime, transfer them to a shared folder and unlink the primary from the Library.


randym77 ( ) posted Sat, 14 November 2020 at 3:05 PM

Someone told me that the "bad magic number" error message means the version of Python is wrong.

So I don't think Poser is confused. I think the errors are because Poser 11 uses an older version of Python than Poser 12.

For the moment, I am just putting up with the error messages, because it's less annoying than opening my old Poser scenes and getting a ton of "missing whatever" error messages.


Y-Phil ( ) posted Sun, 15 November 2020 at 1:40 PM

I've got the feeling that to use dson, one must stay with P11 just the time to make the import, and then to use it within P12. Dson is written with python2.7 max in mind, a version of python that has been kept really longer than originally planned. Can't even decompile it, since it's a weird extension and Easy Decompiler can't handle it.

PhYl.


Win10 on i7 8700K@4.3Ghz, 64Gb, Asus TUF Gaming RTX 4070 OC Edition, 2x 2Tb ssd + 6+4Tb hd  + 1x 8Tb hd + 1 10T NAS, Poser 11, Poser 12  and now Poser 13 


Snarlygribbly ( ) posted Sun, 15 November 2020 at 1:51 PM

Dson is a Poser 'addon', a special kind of script that is automatically loaded if it is present in any linked runtime. Reality is another. Addons are found in this folder (of any runtime): Runtime Python addons

If it is a compiled file (*.pyc), then it needs to have been compiled with the same version of Python under which you are now trying to run it.

If you don't want an addon to run when you load Poser, then remove its folder from the 'addons' folder of the linked runtime. If you want, you can put all the addons in a separate runtime which contains nothing but the addons. That way you can link Poser 11 to that runtime, but not Poser 12.

Free stuff @ https://poser.cobrablade.net/


Y-Phil ( ) posted Sun, 15 November 2020 at 1:57 PM

Snarlygribbly posted at 1:56PM Sun, 15 November 2020 - #4404739

Dson is a Poser 'addon', a special kind of script that is automatically loaded if it is present in any linked runtime. Reality is another. Addons are found in this folder (of any runtime): Runtime Python addons

If it is a compiled file (*.pyc), then it needs to have been compiled with the same version of Python under which you are now trying to run it.

If you don't want an addon to run when you load Poser, then remove its folder from the 'addons' folder of the linked runtime. If you want, you can put all the addons in a separate runtime which contains nothing but the addons. That way you can link Poser 11 to that runtime, but not Poser 12.

In my case, the python file is a *.pyd"

PhYl.


Win10 on i7 8700K@4.3Ghz, 64Gb, Asus TUF Gaming RTX 4070 OC Edition, 2x 2Tb ssd + 6+4Tb hd  + 1x 8Tb hd + 1 10T NAS, Poser 11, Poser 12  and now Poser 13 


structure ( ) posted Thu, 19 November 2020 at 9:58 AM
Forum Coordinator

If you edit the poser_12 poser addon file - you should be able to stop Dson from being loaded.

you should find these lines in your poseraddon.py

for runtimePath in poser.Libraries():
    _loadAddons(runtimePath)

try something like this:

for runtimePath in poser.Libraries(): 
    if not runtimePath == "path to runtime containing Dson":
         _loadAddons(runtimePath)

Locked Out


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.