Renderosity Forums / MarketPlace Showcase
Welcome to the MarketPlace Showcase Forum
Forum Moderators: Staff
MarketPlace Showcase F.A.Q (Last Updated: 2024 Nov 08 7:09 am)
Subject: Loading files into Poser from external windows apps.
tromnek, I have it installed per the readme and it appears to function very well with PBoost. I used P3DO to view the pose file, right clicked on a pose and it applied correctly. This was done using PPP. It worked fine with clothing also. The only thing I ran into with the script is I have to shut it down before I can close Poser. Thanks for the gift.
I must remember to remember what it was I had to remember.
Yes, you need to shut down the server daemon (prpcd.py) before closing Poser. I keep forgetting to document that (sorry). Leave the 'Enable multi-tasking python script mode' UNCHECKED for greatest compatibility. This will allow you to run additional python scripts while the server daemon is running, but the most recently run script will 'block' all the others until it is closed. The multi-tasking mode will allow multiple additional scripts to run simultaniously so you can switch between them. The requires that the additional scripts be written in a specific coding style and that they encapsalate all their code and variables inside their application class. You kinda need to be an object oriented programmer to understand this. So to be safe, leave the 'Enable multi-tasking python script mode' UNCHECKED. I'll try and explain all this better on the web page when I get a chance.
I tried running the autoconform with the muti-task unchecked and it didn't work. I haven't tried with some of my other favorites but I see your point. Another interesting point: the script can be accessed through the Python Panel, which you probably knew already.
I must remember to remember what it was I had to remember.
Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=2159729
Ok. This is an interesting situation I haven't considered. However, it is working as it should. I assume you are using the second autoconform posted, the one that conforms clothing when it's loaded. I also assume you are loading the clothing thru the server daemon. Here's what is happening. With the 'Enable multi-tasking ...' UNCHECKED, autoconform is blocking all other (previously loaded) python scripts, including the server daemon. Thus, when you load the clothing thru the server daemon, it doesn't load until you exit autoconform (unblocking the server daemon). With 'Enable multi-tasking ...' CHECKED, all scripts (including the server daemon) run, thus the clothing is loaded and autoconform does it's thing. Fortunately, duckmango has written autoconform.py in a style that functions well in multi-tasking mode.btw.
duckmango is working on a new version, I think it sets morph dials while it conforms (see the attached link). Though I haven't checked out.
Message edited on: 05/23/2005 19:38
It was written by duckmango. 9/15/2004 . Look through the Python forum archive. Don't know if it's still around. The only thing I've noticed when the script is running the shortcut keys don't function. For example trying to turn the color picker on...ctrl+C...doesn't work but the icon will. The copy/paste function may also be affected. Haven't tried with the muti-tasking function on since these aren't scripts.
I must remember to remember what it was I had to remember.
I just checked this in Poser 6. You probably have the server daemon's window selected (it has focus) and it will take all keyboard input (as it should).
You can select Poser's document window (or any other Poser thingy), then the server daemon will lose focus and Poser will take all keyboard input.
I typically run the server daemon minimized to the task bar. In this configuration Poser will have focus and take all keyboard input. The server daemon will still function properly in this configuation and it won't be taking up space on your screen. Poser is also a little more responsive this way.
Message edited on: 05/23/2005 22:00
Now that worked:) I brought in a prop via script then clicked on the command bar and now the keyboard shortcuts function. I did find one thing though, I cannot use the Delete key to delete an obj from the scene.
Message edited on: 05/24/2005 10:13
I must remember to remember what it was I had to remember.
Another interesting observation: It appears the script cannot handle a missing texture error. I loaded a prop from the Poser library without realizing I had deleted the texture for it and after getting the "Find Texture" msg box Poser froze. I tried to close the script but it wouldn't let me. Finally I got the Poser encountered an unusal request error and crashed.
I must remember to remember what it was I had to remember.
What version of poser are you running? I delete objects all the time without problems. (missing textures) This hasn't been a problem for me. In fact I was running the autoconform script and had a number of missing textures and everything went fine. What version of poser are you using? I'll do some more testing.
I'm using PPP with all the latest sp's. I haven't been able to confirm whether P3DO has anything to do with this. I'm using Ver 1.65. I know it's not the latest but I like the AWK better on this version than 1.7. another thing I have to look at again is, I use the Python Panel to initialize the script and may close it to get it out of the way. Let me try both ways and I'll get back.
I must remember to remember what it was I had to remember.
I have not been able to duplicate the delete issue. Here's what I just tested: Started PPP Used File>Run Python Script Opened P3DO and brought in three props in succession. Key board shortcuts worked and I was able to delete items by selecting and using the Delete key close the script closed PPP Closed P3DO Started PPP Used the Python Pallet to start the script Kept the Pallet open/closed Opened P3DO and brought in three props in succession. Key board shortcuts worked and I was able to delete items by selecting and using the Delete key close the script closed PPP Closed P3DO
I must remember to remember what it was I had to remember.
hmmm. I don't have Poser ProPack so I can't test it in that version specifically. We haven't received any issues or complaints from the people using this stuff with ProPack. ProPack uses a different version of Python, however the GUI interface (Tk/Tcl) is the same version as Poser 5 and Poser 6. All anomalies during developement have been due to the GUI and I test the code outside of Poser in Python 1.52 which is what is shipped in Poser ProPack to ensure Python syntax compatability. So I doubt it is a ProPack issue. Also, nobody who tested this stuff using ProPack reported any problems. Does the P3dO 1.65 have the PoserPython Plug-In or are you using the 'Send To' method? I doubt it is a P3dO issue. External applications (in this case P3dO) are almost completely isolated (de-coupled) from Poser. The issue you experienced may be a sequence of events that uncovered a bug in my code or a situation I haven't anticipated. Let me know if it happens again and/or have any other ideas. thanks.
I'm using the send to method you suggested. The pro version of P3DO has a mention of python but I haven't invesigated it. Ever since I posted my observations I've been trying to duplicate my steps that may have caused the lock outs. So far, zilch. It doesn't happen every time. If I ever get any solid information that I know you should be able to duplicate I'll certainly pass it along. It's a great script and a big help on massive packages.
I must remember to remember what it was I had to remember.
Both the free and pro versions of P3dO have the same poserpython plug-in avaliable. I'll check with Yarp from SenoSoft and see if it's supported in version 1.65 The plug-in offer two big advantages over 'Send To'. First it saves some navagation after the right-click because it has an 'Open with Poser' on the initial context menu. Although it only saves one step, it really does make it more convenient. The other is that if you run P3dO in the mode where it shows only one icon per .rsr/.pz2 pair, it will only send the .pz2 file to the server daemon. This way the server daemon will not flash the warning message about the .rsr (or .png) file not being supported. (have you gotten that warning?) I've kinda assumed that people using P3dO would be using the plugin.
Here's something interesting. When I run the script under P6 I don't encounter any problems. No, I haven't gotten that warning, the way P3DO displays for me it shows if it's a cr2, pz2 etc. Off to Seno and see what's new that I'm not up to date on. PS. thanks for putting up with me.
I must remember to remember what it was I had to remember.
The PoserPython plugin was first released with P3dO 1.7.5 (last december's version). I'm affraid PoserPyhton will not show the popup "Open with Poser" command on previous P3dO's (this was a 1.7.5 new feature), so it is far less interesting. Generally speaking plugins can run on any P3dO version, but since newer features (like the popup menu) can't activate on older P3dOs it is recommended to upgrade the plugins pack when you upgrade P3dO. As Tromnek stated, PoserPython is a free plugin. It's just a wrapper around tromnek's work which makes the core of the plugin. btw nickedshield I would be interested to know why you don't like newest AWK (please don't answer on this thread, let's talk about prpc here and not p3do - you can contact me on the private messaging)
Yarp - author of P3DO Organizer for Poser
OK. When I'm thinking clearly I'll do that. Back to something I'm probably doing wrong. As I mentioned. I have P3DO 176 installed along with all of the plug ins. Moved the receiver py to my PP python addscripts folder per the help file. Started PP and initialized the receiver script. Then I initialized the prpc script. I used the open wirth poser function from p3do to load the Daz Eagle. Checked the function of the keyboard shortcuts, sluggish but finally worked. Again used the open with poser funtion to load a mat. got carried away and made a complete scene. Went to close Poser and knew I had to shut down prpc first. I tried to shut down the receiver but got an error that two scripts were running and the program would crash. OK. I shut down prpc but when I tried to shut down the receiver the whole thing froze. Finally I had to use the task manager to shut it down. As I said, I probably did something wrong.
I must remember to remember what it was I had to remember.
Run either the prpcd.py or poserpythonreceiver.py, not both. I should make this clear on my web page. Running both would make the system very sluggish and unpredictable. I thought I had stuff setup so you couldn't run two versions at the same time. I'll check into that. They are basically the same server daemon. The poserpythonreceiver.py script has the 'multi-tasking' option disabled. Since you need this option enabled to run the autoconform.py script, you should run prpcd.py The warning message you got was meant to tell you to close all other python scripts before closing prpcd.py. If you had closed poserpythonreceiver first, it probably would have shutdown gracefully. I'll try and make that message clearer in the future. Thanks for the clear and detailed feedback. It takes alot of the guesswork out of replying and debugging.
Sure, this is something we should make clear in the help file, not to run 2 receiver/listener scripts at the same time. Since there are troubles another posssibility would be to use the prpcd.py even from P3dO (I just renamed it for clarity purpose). But there's the problem of the secure and other version - 2 scripts left so the risk is still there.
Yarp - author of P3DO Organizer for Poser
Something new for this mornings discussion: After only using the prpc script and p3do's open with poser command everything is running smooth. It could be that prpc really didn't like something in the earlier version of p3do. These two apps sure makes it considerably easier to locate and load items, especially when I use a lot of foliage.
I must remember to remember what it was I had to remember.
Thank you. Now you see why I was somewhat concerned about the color picker and translate keyboard shortcuts working. Try to position the foliage with the translate tool active and all you have is the wonderful red outline. Hard to figure where they go.
I must remember to remember what it was I had to remember.
Yes, I have done it a few times just to test the concept. However the version that I have out to the public will not. For security reasons, the public version will only accept a connection from the 'loopback' network interface (127.0.0.1). Also, the current version of P3dO only sends filenames to the loopback interface. If you know python you could edit the server daeomon (prpc.py) to allow other connections. You can use the 'snd2sock.exe' program I supply to send to the filename to other ip addresses. IM me if you need help.
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.
Attached Link: http://www.mort.net/users/krm/dist/poser/prpc
Here is a method for loading files into Poser from any windows application that supports the right-click 'Send To' context menu (windows explorer, P3dO explorer, ...). This works really really well with P3dO Explorer.Included is a module to filter pose (pz2) files so you can filter the pose file to selected body parts (partial pose files on the fly).
The webpage is a little large (100Kb) because of a few screenshots.