If you bought this at Daz, is it stable and working for you? I got big problems and want to know if this thing actually works on most systems or not.

It installed correctly after I had removed the read-only attribute from the mainButtons.py (one of PPrPack own scripts) It runs without a problem here on PPrP 4.2 (Win98US)

Thanks for the reply Hein. I had to remove the read only attribute for the mainButtons.py file too plus I had to copy the tcl80.dll to the system folder to get it to even install. (or add its path to the autoexec.bat would also work I read somewhere after searching for the error message I got)

Even after all that, when I run the script it makes my system perform like a Pentium 200 with only 3 lights and a bowl prop. Screen updates take forever if they happen at all (it often crashes) if I move a script window so I can see behind it. Running the script takes down Poser.exe with a c++ runtime error often, the script window turns white and won't leave till I actually click on it somewhere or CAD and shut it down. It's a mess and I don't dare load a big light set (one of the scripts complains none are installed) or a real model.

I have a P4 1.7GHz, 512MB RAM, 30GB free disk space, a common Nvidia TNT2 card running Detonator Drivers and Pro Pack is patched to the latest update on an XP Home system. Rarely does Poser crash otherwise, but with this script, it's every few minutes. The only thing I've gotten to work without crashing before it is done is delete all lights.

I'm wondering if anyone else is having similar problems, is it OS related problem, python, Pro Pack or just my system? Poser is really stable for me unless I run this script, but MK Scripts is kinda flaky at times on my system too. It's only the second set of scripts I've purchased and both have given me some troubles, but this one is so bad to make it unusable.

My Poser Pro Pack executable version is 4.2.1.179, can anyone verify that it is indeed the right version for the 3rd patch? I have the SR3 pdf in the folder and I recall patching it but the file info doesn't tell you what service release it is.

I'm running the scripts on a PIII 500 with 640 MB on Windows 2000. I have not experienced any problems with them.

diana: I'm having similar problems so you're not alone. Now to figure out why? s

Hi again diana, seems to be fixed here, I removed the "read only" attribute from the ProPak pythons scripts (all of them) and it didn't have any affect until after I removed the attribute from all the scripts. Anyway, upon reopening the big "P" all seems well, hope yours is too

There are times PP slows down a little, but 30-40 lights are no problem. The script that tells you there aren't any lights is the Lightworkshop that looks for lights with names as created by the Sky&Bounce workshops , with the aid of the analyzer you can change the naming in existing lightsets, once that's done the Lightworkshop won't complain when you have an "old" lightset loaded when you run that script. I've looked at the MK Scripts, tried them too, they crash Poser 9 times out of 10 here. Apart from that have you contacted Paul Bos to see if he has an idea why?

Thanks for the feedback y'all. I haven't contacted Paul Bos as I read on Daz's site they were supplying tech support for all the stuff at the store now. I am waiting till tomorrow to talk to Daz unless I find a fix here before then.

I'm going to try your tip movida, making copies of each one for safe keeping.

An update, taking the read only attribute off all the scripts did not fix my problem. First time I ran Poser and the light analyser script, renamed my current lights to something like skymain, it froze, the script window went blank white and sat there over my image. I had to close the script and doing so crashed Poser.exe with a C++ runtime error again. I can't even describe how badly the scripts bog my system down. Acts like I have 10 Vicky models in Poser. (and I had only one simple prop)

I get the C++ in Windows XP Pro and Service Pack 3 of Poser Pro. There is for sure a bug some where!

Well, misery loves company, appreciate the input starmkr. I have wondered about XP being a fly in the ointment... it has a lot of software acting quirky.

I'm using WIN2K, maybe it is XP??

Running Win98, the script worked fine under 98SE too.

Hi I was not able to get the installer to work but I can get the scripts to run if I execute them directly so far I have been able to do that with out a problem on a Windows 2000 machine with 256 k of ram (its a portable) and on an Xp desk top 500k of ram If anyone needs something tested with the script let me know and I can try to duplicate the problem on either machine Keith

Keith, did you remove the "readonly" attribute from the mainButtons.py before running the install? I needed that before I could install the scripts.

I'm compiling a letter to Daz this morning to see if they've accrued a quantity of folks with like problems and hopefully a solution. I will get back here if I find a solution if Daz doesn't post here with it first.

Keith, you really ought to install the scripts, I am sure it is one of the two things that gave me a problem with the install. It would make them easier to use. I thank you for your offer of assistance and may take you up on it if no solution is forthcoming.

Hi I did remove the atribute. However since I have the MK scripts installed I get an error that there is no button available to install to Thats why I run the scripts directly. The installer fails if certain buttons are not available. Running the script directly seems to work so far K Keith

I only run the Environment scripts , when I tried to install the MK script I had the "no buttons available" msg. ProPack problem maybe :)

Hi I think its a python problem. For some reason the main button script is limited to 10 buttons. I posted on the python forum a message but no one can figure out how to add more then 10 buttons. So the MK buttons beat the Environment buttons on my system Keith

I read a tip somewhere to use the main buttons only as links to "secondary" pages which hold the buttons for the actual scripts. PCBos does it with these Environment scripts and also with his Radiosity scripts. Entering buttons by hand isn't that much of a problem and is often described in the readme's.

What is PCBOS? Thanks Keith

Paul Bos , the programmer of the script