I can't seem to manually plant obj pointers in the cr2's and have them work using the ProPack. I tried to have the cr2 call up the ball prop with the standard pointer lines: prop:1 storageOffset 0 0 0 objFile 00 :Runtime:Geometries:props:ball.obj If anyone can sucessuflly call up props using the PP like we can do without it. Would you please let me know? And tell me how you did it. I can't get it to work myself. remote accessing obj files is a major thing to lose. ScottA

Oops. typed it wrong there. that should read: prop ball:1 storageOffset 0 0 0 objFile 00 :Runtime:Geometries:props:ball.obj Any idea why this won't work anymore?

hey tommorows black monday at the cl head q lol! there seems to be 2 more problems im hearing about also 3ds wont accept custom textures and when you try to export or import certain props obj etc the pp locks up and greys out the control i hope i dont have this muck trouble with lw

I think you forgot a space in the code. It should look like this: objFileGeom 0 0 :Runtime:Geometries:props:ball.obj

Tried it. Didn't work. Thanks anyway. Have you tried this using the PP Jeff? You've done a lot of this remote calling obj files. And I'm kinda new at it. I might be doing something wrong. ScottA

Usually the PP will take the external OBJ call, combine it with the base OBJ and that gets saved in the folder with the CR2. What you're using there is for PP2s, I think the code is slightly different for a CR2: objFileGeom :Runtime:Geometries:props:ball.obj Without the storage offset line as well.

Nope. Still doesn't work. It only seems to work if you put the Delta's in the cr2 file. Of course. There's only one way to generate those. And that's use Poser without the PP. Doh! No remote .obj calling is working for me. No matter what I try. ScottA

I will test the Pro Pack in LightWave see what happens there.

I have this in my Tuxedo Posette figure:-
actor hip:3 { storageOffset 0 0 0 objFileGeom 0 0 :Runtime:Geometries:PhilC:tuxPosette_hip.obj }
Created before the Propack was issued she opens fine in the update. Re-saving to the library does not re-write the geometry. At least not in my version. :)

PhilC You missed the point and it is simple. Poser4 keeps geometries in the CR2 with no need for seperate geometry files. If they forgot to do that in the pro pack then they screwed alot of people and will have alot of proplems. Not to mention put people out of business, accept for the Beta Testers. Then it will be the Pro POB I dont know If what I am seeing is true but I will tomorrow.

If one of you guys could do me a favor I could find out for sure weather it's me or the PP. What I need you to do is put a remote obj call for the ball prop into the P4nude woman cr2 file. And make sure the ball shows up in the scene. Then e-mail me that cr2 file at: scotta@rochester.rr.com So I can open it and see if it works for me. If it does. I'll be able to study the cr2 file and see how you did it. Thanks for the help. ScottA

OK Scott, email on its way.
The font? Oh I just strike the keys a little harder:)

Imager- Here's Phil's secret. It's all in the wrist... actually in the HTML code. You can learn more about these tricks at the HTML and Web Scripting Forum... ## (I intentionally made it NOT load to show you the font...

Oops- the # sign didn't do what I expected (make it not load). I guess I better head over there too...

Good thing I am not writing and posting Python Scripts...

Just remember, if you play with the HTML in your message, make sure to close your tags!

Thanks for sending me that file Phil. I found out what I was doing wrong right away thanks to having that file for a refrence. I didn't have the ball listed in the "addchild" section of the cr2. I added it. And it worked fine. Can't Blame the Propack for this one folks. Just my stupidity ;-) By the way. Here's something that happened that was weird. When I added your working cr2 file to the same library where my not working test file was. MY TEST FILE WORKED!!!!!!!!! Somehow. It used the info from your cr2 to make mine work. Figure that one out! Pretty strange huh? I love this stuff. Thanks for the help Phil. ScottA

Does everyone notice the "Preview Post" button we have now? If you use that you can catch your HTML mistakes before you actually post.

Yikes! The more I hear about the ProPack the more I'm glad I haven't bought it yet. I'm hearing nothing but negative reports about it. So far, I've only heard complaints and nothing positive. Is there anything good about it? Melanie

Melanie, If you read this thread carefully you'll see that the problem Scott was having had nothing to do with the Pro Pack or bugs. -JH.

It's pretty typical to hear us bring up the problems Melanie. We go looking for them ;-) The people here really push Poser to it's limits. So we always find a few problems. Luckily. That benefits everyone else. Because CuriouLabs sees it. And trys to remedy it for us. Positive things: 1.)flash output is fantastic 2.)viewpoint output looks very interesting 3.)The plug-ins work. But need a little more updating 4.)new file system is much easier and logical 5.)four views is wonderfull 6.)Python scripts will be a cool thing in the future 7.)quick figure creating and editable rotation orders The most positive thing is that they are committed to fixing all the litle problems. And I'm sure they will. They always take care of us. ScottA

Can you tell I'm not an english major ;-)

Hey, I'm gonna get Russ to remove that "Post Reply" button if everyone doesn't start using the Preview button soon ;-)

Oh man. I'm sorry jeff. It's hard to develope new habits. ScottA

Yeah, I know. I keep forgetting about it myself.

How about a forum on using the Post Reply features? We could even have Python scripts write our posts for us, based upon pre-determined character profiles. That way we could get more sleep and work done and totally automate Renderosity...

LOL

Now that the HTML cat is out of the bag will the Forum become just another graffiti wall?

I have installed the PPP and have no problems. Did I miss something?