Forum Moderators: nerd Forum Coordinators: nerd
Poser 12 F.A.Q (Last Updated: 2024 Oct 22 2:54 pm)
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
Unfortunately the python scripts that make it possible for Reality and Poser to work together are wrote in a different version of Python than is available in Poser 12. You'll have to talk to the owner of the plug in, if possible, or find someone who can help you fix your script to work in the new Python.
Reality has been released as open source now.
"Dream like you'll live forever. Live like you'll die tomorrow."
Reality works in p11 with Snarlys fix but not in P12
"Dream like you'll live forever. Live like you'll die tomorrow."
So far as I'm aware Reality will not work with Poser 12 due to the move to Python 3. Getting LUX rendering from Poser 12 will likely need someone to pick up the open source BSD code and make it work in Poser 12. Octane was also said, in a recent official webinar, to be coming to Poser 12 - but my guess is it will be subscription if that happens.
Learn the Secrets of Poser 11 and Line-art Filters.
At least on Mac, Reality requires a very very specific build environment, owing to the mind boggling nastiness that is QT. I used to have a VM of that environment, but it was lost on server raid failure. Every attempt to rebuild that environment that would produce a working compile, failed. I gave up on it since LuxRender sort of fell apart, came back together, but with the Mac version being the red-headed stepchild (to be fair, Apple's fault) It was way too much work just to get working, let alone maintaining it with too many major component libraries needing to be "just so" for it to work at all. Worse than a moving target. One working compile a few years ago, and I gave up.
As much as I loved it, once Poser went Cycles (with its own issues) it was a lost cause. If I need Reality, I fire up Poser 11. And marvel at the ease of photorealistic renders. There were some good ideas there; it might be nice if Poser had a better plug-in architecture for modelers (blender) and renderers (cycles, radeon pro). I'm sure the Dev team has nothing but free time to pursue such things.
As for Reality, I would much rather it be able to export a scene for Radeon Pro Render rather than Lux, anyway. And I know Reality is coded such that this is possible (it's essentially agnostic). But QT.... makes me cry just thinking about it.
I decided to have a look into this. I don't have Poser12 yet, and am a Mac user. It seems to me that the Poser version of Reality relies on the Python2 scripts to bridge the divide between Poser and Reality. So... if the Python scripts were updated to Python3 then it might work.
I emailed Paolo to ask his input but then figured I'd look into it a bit myself. This led me to try converting the Python2 to Python3.
These files replace the existing .pyc files (move them somewhere as a backup) then try putting these files in their place.
As I said I don't have Poser12 so can't test myself with Poser 12, but I did test it with my Poser11 installation which unnervingly seemed to still work. So I suspect I am not understanding something fully.
If you try it and it doesn't work, apologies - just copy the original .pyc files back until we can try again.
At this point it looks like Poser11 works fine with the Reality python3 reality scripts - so I suspect that either Poser 11 did have some support for Python3 beyond Python2, or that the specific Python modifications to make these run in Python3 were backward compatible with Python2.
So I decided to install the Poser 12 free trial to test these mods. It appears to me that Snarlygribbly's avfix.pyc may now be the next stumbling block. Because it's compiled I can't try to convert it to Python3. I tried hacking the header version number in a hex editor to no avail :(
Paolo has made Reality open-source, but i don't know enough Python to do anything with it. Code is here...
https://sourceforge.net/p/reality-plugin/code/ci/default/tree/
----------------------------------------------------------------------------------------
The Wisdom of bagginsbill:
"Oh - the manual says that? I have never read the manual - this must be why."Well, I've been looking at this some more. I was able to decompile and modify Snarllygribbly's AVFix so it still does it's thing.
I think the new stumbling block is loading a SharedObject (Reality.so) from the GeometryExporter I'm getting the error:
startup error occurred importing addon Reality : ERROR: module 'Reality' has no attribute 'Scene'
A man of few words, but concise ones lol.at $700+ for a year of Octane they can blow me.
From my (very very small) understanding of Python, a bad magic number error means that the script was compiled for another version of Python. Sadly, only the creator would be able to change it (at least in any ethical and technically legal way), because you compile python specifically so that people can't see and change the code.
- - - - - -
Feel free to call me Ohki!
Poser Pro 11, Poser 12 and Poser 13, Windows 10, Superfly junkie. My units are milimeters.
Persephone (the computer): AMD Ryzen 9 5900x, RTX 3070 GPU, 96gb ram.
Reality was adapted already a while ago and can be found in certain Private Forums, with other Python fixes. Just that they never reached this Place due Intrigues and many Members getting Banned that tried to bring improvements. Just like mentioned above "only the creator would be able to change it(at least in any ethical and technically legal way)." Trying to make any improvements here sets your membership at risk so better do it in Private external Forums.
If it is indeed open source (I wouldn't know), then it would be fine to fix the magic number, of course.
People don't get banned for trying to bring improvements. They get banned for overstepping creator/intellectual rights.
- - - - - -
Feel free to call me Ohki!
Poser Pro 11, Poser 12 and Poser 13, Windows 10, Superfly junkie. My units are milimeters.
Persephone (the computer): AMD Ryzen 9 5900x, RTX 3070 GPU, 96gb ram.
The problem with Python isn't the magic number of compiled files: jumping from python 2.x to 3.x is often easy, often but not always, and some differences may need a huge work while other parts may just need a small "refresh"If you say so !
A little hint, you will need to fix the Flash issue in Reality in order to make it work again, after this step you can fix the codes. "Not just a magic Number" Guess you have enough Pro's here that will get that little magic running again :)
𝒫𝒽𝓎𝓁
(っ◔◡◔)っ
👿 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 ❤️
Afrodite-Ohki posted at 7:06 AM Fri, 3 December 2021 - #4431216
If it is indeed open source (I wouldn't know), then it would be fine to fix the magic number, of course.
https://preta3d.com/reality-now-open-source-software/
Speaking for myself, I enjoyed playing with the plug-in, but I'm much happier now that there's a good physically-based renderer built into Poser so I'm not jumping around between separate tools.
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.
Has anyone gotten this to work with Poser 12?
I tried to install and run this plugin, but I get this error: "An errror occurred importing addon Reality : ERROR: bad magic number in 'Reality': b'x03xf3rn'"
I tried the fix that worked for Poser 11.2 - to no avail.