Sun, Jan 5, 5:46 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 03 1:41 pm)



Subject: Some questions on how to parent a light to a poser prop...


McGyver13 ( ) posted Thu, 14 October 2010 at 12:06 PM · edited Thu, 28 November 2024 at 10:09 PM

file_460319.jpg

 Hello. This is my first time asking a question here, some of you who visit DAZ3D's forums might know me as lordvicore (Ooooooh... that guy,eh...) over there.  I tend to write a lot and ask long questions, but I'm really trying to be as concise as possible. So on to the questions...

What I want to do: Make a Prop(which I have already created)have a light(or lights) parented to it so that it can be used as a smart prop, which will only require the user to click it's icon to load it.
This is for a BIG architectural freebie model I made and I want it to contain some lighting.

The problem:
I'm trying to follow a tutorial by Webtigress (or N8Dreams) "How to light Poser props" 
http://www.sharecg.com/v/25791/PDF-Tutorial/How-to-Light-Poser-Props?interstitial_displayed=Yes
What I want to do is (as the tutorial says I can) is to Parent a light to a poser prop by altering the .pp2 to include the .lt2 data. Only problem is that despite several attempts, it won't work. I've tried several variations of the methods described but they don't work either. I searched the web for other tutorials but that yielded a lot of nothing.

I'm guessing that I'm missing something, or placing something in the wrong spot... 

Rather than describe the tutorial, I figured I'd try and illustrate what I'm talking about using some screen captures...

The first is of My unaltered LT2 file, the second image shows the PP2... I'm guessing that proper(exact) placement of the copied data is real important and I'm really not clear if I'm on target... Just to be clear, I think the tutorial is great, I just think I may not be interpreting it correctly.
(so thanks Webtigress... or N8Dreams for the tutorial it is very helpful).
Anyway thank you in advance for any suggestions or advice you may have.

-Edit I don't see a way to post more than one picture per post... 
This set up is different from other forums I visit... I'll post The PP2 image right after this(a new post)....


McGyver13 ( ) posted Thu, 14 October 2010 at 12:06 PM · edited Thu, 14 October 2010 at 12:10 PM

file_460320.jpg

 The PP2 image...

By the way I hope the way I illustrated this is not confusing... some people get real PISSED when you use lots of lines and colors...
anyway, thanks again...


lesbentley ( ) posted Thu, 14 October 2010 at 7:35 PM

file_460356.TXT

You will have to excuse me, because I have been in the  pub most of the night, and after I came back from the pub we drank two bottles of wine. So my grasp on the subject, or even reality as a whole, is not very strong at the moment. So the health warning here is that what follows may be the incomprehensible ravings of drunken imbecile.
  1. Yes.
  2. Yes.
  3. Yes, you  can paste the lt2 data here. It is not really significant where you a paste it, so long as it respects the brackets.
  4. Yes.

What I usually do myself when adding a light to a prop, is to parent the light to the prop, then save a pz3 (scene). I then construct a pp2 template like so:

{

version
    {
    number 3
    }

[added code goes under this line]

}

I then Copy & Paste the relevant parts of the code from the pz3 to my pp2 template. There are three parts of the pz3 that need to be copped. Of course, only copying the relevant parts. The declaration section near the start of the file. The definition section which contains the channels and other stuff, and the 'doc' section.

There are actually some if's and's and but's that need to be added , but I'm in not any condition to do that at the moment. A good tip is to edit the names of the light and shadow cam to give them  unique internal names, so that ne names do not conflict with names that may already exist in a scent that you will load the pp2 into.

The attached file is a Poser box prop with a light parented to it. You will need to loose the ".TXT" part of the file extension. Because Poser increments the names of successive instances of props, this will only work for the first instance of the box loaded into the scene. To have it work for multiple instances of the prop, you would have to implement it as a cr2.


McGyver13 ( ) posted Fri, 15 October 2010 at 8:37 PM

file_460381.jpg

Thank you lesbently, "the incomprehensible ravings of a drunken imbecile" this was not!  I've found some of my best thinking and writing has come about in the company of my old friend Rum... Of course probably only I think so...  Anyway, I wanted you to know that with your assistance I was able to get this to work! The sample .pp2 was a great idea and using it, I was immediately able to see what my mistake was... I had been copying and pasting the very last bracket from the bottom of the .lt2 into the .pp2.  I tried several variations of what I thought the tutorial was suggesting and I thought that was one of them(the not pasting the last bracket scenario)... I probably should of had some rum first,things would have probably seemed clearer then. Although I try to save my alcohol these days for when I use Blender... eases the mental trauma a bit... that and I actually think I've learned something each time. I haven't, but I laugh a lot. I think thats the important part. Anyway- THANK YOU!! -Vic. PS... I figured I'd show you what it was that  I lit up... It needs a lot more tweaking, but it is supposed to be a beacon light of some sort... sort of like a light house. It is located at the top of the complex in the insert. The whole thing is pretty big.


lesbentley ( ) posted Sat, 16 October 2010 at 6:07 PM

Glad to see you got it working.


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.