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.

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.

Oh. I forgot to mention. This stuff should run fine from either 'File>Run Python Script' or the Python Pallet. I've been running it mostly from the pallet.

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.

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 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

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

(oops, deleted the wrong post, and I forgot what I had said, sorry).

I'll try and find autoconform and test it.

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 know of Pboost, but never used it. Please post back to let me know if it works.

Attached Link: http://www.mort.net/users/krm/dist/poser/prpc

I like to organize stuff just like you want to. There are few issues doing this with Poser that make it difficult/impossible. One is that Poser's library interface will only show you the standard library folders (then any folder below them). Also it filters what files it shows you based on the folder (Figures folder will only show you cr2 and crz files). Another issue is that obj and texture files are often reference relative to the current runtime folder. You will need to hand edit some files to make absolute paths for them. I have a method to load Poser content using external windows apps (windows explorer, P3dO explorer). It takes care of the first issue, but I still need to keep many textures and obj files in the runtime structure. (see attached link) Using this method I now create a folder (i still keep it in the runtime structure) for each of my characters that holds the base cr2 file for the character, pz2 files for morphs, hr2 for it's hair, and some of their favorite clothes, props and poses. This method also allows window's shortcuts (.lnk files). So I actually create shortcuts to the above mentioned content. This doesn't really help with backing up. Only with organization and a single point of access. I've seen some stuff on backing up all files referenced in a scene file (pz3). I think SenoSoft's P3dO Explorer is working on plugin along those lines.

Thanks, I was hoping it would. I'm waiting on a physical shipment. I have one more change to the client module registration protocol before I move it out of beta. Python is not bad. The nice thing about it is that you can program 'Top down', 'Proceedural' or 'Object Oriented'. It's also easy to migrate a program from top-down to procedural and procedural to oop. So you can program it however you are comfortable for a particular task. It's real handy for programming little utilities and the 'regular expressions' make text processing really easy.

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12390&Form.ShowMessage=2159729

For the clothing morph settings check this thread. I don't know anything about the 'Make Art' thingy.

Another neat thing that this stuff allows is dereferencing of windows shortcuts (.lnk). I started creating sub-directories for each of my characters that has;

01baseM3withExpressions.lnk
02headmorph.pz2
02bodymorph.pz2
03materials.pz2
04hair.lnk
06M3tunic.lnk

I can select all those files in explorer (or P3dO) then sendem all to poser. While poser is loading them all, I can navagate to another directory and find the next things I want to use.