♥ PosetteForever ♥

<img src="https://www.posetteforever.com/images/smiles/eusa_clap.gif" alt="" /> <img src="https://www.posetteforever.com/images/smiles/eusa_clap.gif" alt="" /> <img src="https://www.posetteforever.com/images/smiles/eusa_clap.gif" alt="" /> Great tutorial, thanks a lot, VK! <img src="https://www.posetteforever.com/images/smiles/eusa_dance.gif" alt="" />

Yes, Thank you VK! <br /> <br /> {I just took the time to see if the"phi text" method was available to P5 users;... <br /> The manual says: "Figure creators wishing to use the old method should refer to the electronic Poser 3 Advanced Techniques document, which covers the old figure creation method in detail. This document is in PDF format and is included on your Poser 5 content CD in the documentation folder." <br /> It is not on my version of the CD. <img src="https://www.posetteforever.com/images/smiles/rolleyes.gif" alt="" /> } <br /> <br /> { I did however notice a bunch of free content (including morph targets for Don & Judy) that I did not remember were there. :grin:} <br /> <br /> Now having said that;... How can a P5 user make use of this beginner's tutorial? <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

WhooWeee! <br /> <br /> I was able to download the "Poser 3 Advanced techniques" document from eFrontier. <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

Great detail in here! <br /> <br /> So, if I have an existing car model, with pedals that don't move, hoe can I make them move? <br /> <br /> Thanks!

I'm with Goat on this... <br /> I think that I need a "hand-holding type" tutorial on how to rig a car model in P5. <br /> <br /> I looked at already poserized vehicles (The Cobra, The Veepster, a Hummer, and others); but they only helped to confuse me more as to where the bones need to be. <br /> <br /> As for the phi file, whew... I think I understand how to make it; but I am unclear when to make it; or even if I need to make it in P5. <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/eusa_think.gif" alt="" /> <br /> <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

Sorry, I can't help with the Setup room in Poser 5 and later. However, the steps are always the same. <br /> <br /> Maybe it helps when I try to answer your questions. <br /> <br /> @goat4444: <br /> Make the first step: Import the existing car model into Poser (menu "Import > Wavefront OBJ"). <br /> Once you see the car model in Poser, open the Group Editor and check if there is for each pedal a group including only the pedal geometry. <br /> <br /> You always have to start with a properly grouped model. So this is always the first step. Please ask for more information if you don't know how to import the model or how to use the Group Editor. <br /> <br /> If the car model has no groups for the pedals, you need to group the model. This can be done in your modeler or in Poser. If you don't know how to group the model please ask here for more information. <br /> <br /> If your car model has groups for the pedals, you're ready for the next steps: <br /> - Scale the model if necessary. <br /> - Place the model in the Poser scene where you want it to load. <br /> - Adjust reversed normals if necessary. <br /> - Use "Spawn Props" in the Group Editor to create props from the model groups. <br /> - Delete the original car model. <br /> - Export all the props to create the figure obj file. <br /> <br /> If you don't understand these steps, please ask for more information. <br /> <br /> Once you have the figure obj file, you can start to create the .cr2 (rig the model), see below. <br /> <br /> <br /> @Whazizname: <br /> I'm sure there are tutorials how to use the Setup room in Poser 5 or later to rig the model. <br /> <br /> The phi-method is usually much faster (and painless, too). Here's some more information: <br /> <br /> 1. You can create the phi-file at any time. I usually make the phi when I have spawned the props in Poser. This way I can see the exact group names and make sure that all groups are included in the phi. <br /> <br /> 2. Usually, the car rig should be very simple. The simpler the better. You have a root object (the car body), and all parts are attached to the car body (like wheels, doors, pedals, etc.). Because of this, the phi is also very simple. You can use the following code as a template. <br /> <br /> <!-- no smilies start --><div class="code"><div class="code-header" id="codehdr2_161562f1" style="position:relative;">Code: [<a href="download_post.php?post=35048">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_161562f1','code2_161562f1','');ShowHide('codehdr_161562f1','codehdr2_161562f1','')">Hide</a>] [<a href="javascript:void(0)" onclick="select_text('code_161562f1')">Select</a>]</div><div class="code-header" id="codehdr_161562f1" style="position:relative;display:none;">Code: [<a href="download_post.php?post=35048">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_161562f1','code2_161562f1',''); ShowHide('codehdr_161562f1','codehdr2_161562f1','')">Show</a>]</div><div class="code-content" id="code_161562f1" style="position:relative;"><span class="code-row-text">objFile :Runtime:Geometries:cartest.obj <br /> <br /> 1 cargroup yzx <br />    2 wheelgroup xyz <br />    2 doorgroup zxy <br />    2 hoodgroup zyx <br />    2 pedalgroup yxz <br /> <br /> </span></div></div><!-- no smilies end --> <br /> <br /> When you use the template, you insert your group names and add more actors (for the wheels, for example). <br /> <br /> - The "objFile" line: This is a file path using the ":" separator. The line starts with the word "objFile", followed by a space or tab, followed <br /> by ":Runtime", followed by the path to your obj file. Use the exact filename of your obj. The line must end with a return. <br /> <br /> - Write a line (a full line ending with a return) for each actor. <br /> <br /> - Each line starts with the hierarchy level (a number), followed by a space or tab. <br /> <br /> The logic of these numbers is simple: The root actor has number 1. This actor will be the child of actor BODY in the figure. Most objects like humans and cars have a single root actor. However, you can define several root actors, for example two roots for two faerie wings. All actors with number 2 are children of the root actor. These parts are attached to the root actor. <br /> <br /> All actors with a higher number are children of the prior actor with the prior number. For example, a "3" actor is a child of the "2" actor in the latest preceding line: <br /> 2 foo <br /> 3 foochild <br /> 3 foochild2 <br /> 2 goo <br /> 3 goochild <br /> 3 goochild2. <br /> <br /> - Each line lists the exact group name, followed by a space or tab. Spaces are not allowed in the group name, and your obj must not contain groups with spaces. <br /> <br /> - Each line ends with a rotation order flag, followed by a return. The rotation order is for example "xyz". The above template can be used for a car model facing the front camera (the usual setup). <br /> <br /> - Be sure to finish the phi file with a return to make a full line for the last actor. <br /> <br /> - The rotation order is crucial when you make a soft body model, because Poser tries to set up complicated joint parameters for the figure. You don't need these parameters in a car model, so you don't need to care for this stuff. Once you have the .cr2, you load the car figure and simply adjust the origin of the parts. <br /> <br /> However, the rotation order flags in the phi can help to place the origins. Here are the rules: <br /> <br /> The origin of the root actor is always centered in the root actor. The flags in the phi just define the rotation order, that is the order of the rotate channels on the root actor. <br /> <br /> For children of the root actor, the first dimension (axis) defines the major axis of the child. The second and third dimensions define the plane where the child is attached to its parent. When Poser converts the phi, the origin and the end point of the actor are placed at the end points of the major object axis, and centered in the second and third axes. <br /> <br /> For example, the wheels have flags "xyz". The x-axis is the major axis of the wheel, and "yz" define the plane where the wheel is attached to the car. Using this flag, Poser places the origin and end point of the wheels on the x-axis, and in the center of the y and z dimension of the wheel. This is exactly what you want. Remember that this setup can be used when your car geometry faces the front camera.

Likewise, the door actor has flags "zxy". The origin and endpoint of the door is placed at the endpoints of the door in the z-axis, and centered in the xy-plane. <br /> <br /> Poser uses the bounding box of the geometry group to calculate the position of the origin and endpoint. The bounding box is the smallest box enclosing the entire geometry. For example, the hood actor has flags "zyx", the origin is centered in the xy-plane. This is not the hinge point of the hood. So you need to adjust the origin when you have your first .cr2.

The phi-flags also define the rotation order of the actor, that is the order of the rotate channels in the .cr2. You can set up the rotation order in the phi or later in the .cr2. Most actors rotate about one axis (like the doors, hood, pedals, etc.). In this case, the rotation order doesn't matter, maybe you even delete the unused rotate channels from the .cr2. <br /> <br /> The rotation order does matter when the actor uses more than one rotation axis, like the front wheels (to drive and steer). There are two important rules for the order of the rotate channels: <br /> 1. Later rotate channels carry the rotation axis of prior rotate channels. <br /> 2. The middle (second of three) rotate channel can generate "gimbal lock". <br /> <br /> A "later channel" is a channel whose code appears later in the .cr2. The "middle" rotate channel is the channel whose code appears after the first and before the third rotate channel. <br /> <br /> Let's see what this means for the front wheels: We choose the rotation order "xyz". X-rotate revolves the driving wheel. Y-rotate turns the wheel when you are steering. Z-rotate is unused. When you drive and steer, you set both rotations, that is <br /> x-rotate (drive) <br /> y-rotate (steer). <br /> <br /> The subsequent steer channel carries the rotation axis of the prior drive channel. When you steer the wheel, the drive rotation axis is carried and points to a new direction. This is what you want. <br /> <br /> Rule 2 doesn't apply to the front wheels, since we use only 2 rotation axes.

Thank you for your tutorials VK, they are really priceless <img src="https://www.posetteforever.com/images/smiles/notworthy.gif" alt="" /> <img src="https://www.posetteforever.com/images/smiles/notworthy.gif" alt="" /> <img src="https://www.posetteforever.com/images/smiles/notworthy.gif" alt="" />

<img src="https://www.posetteforever.com/images/smiles/thumb.gif" alt="" /> <img src="https://www.posetteforever.com/images/smiles/eusa_clap.gif" alt="" /> <img src="https://www.posetteforever.com/images/smiles/eusa_clap.gif" alt="" /> Thanks a lot, VK <img src="https://www.posetteforever.com/images/smiles/lol.gif" alt="" />

You're welcome. <img src="https://www.posetteforever.com/images/smiles/smile.gif" alt="" />

Thanks again VK. <br /> <br /> I have a few questions: <br /> <br /> 1.) The model I've chosen loads facing away from the camera. How does this alter the tutorial you posted? (I rotated & scaled the model; but when I spawned the props, they were unscaled, and unrotated.) <br /> <br /> 2.) The model I've chosen has multiple "body" parts; should these be grouped together to form one "car body"? <br /> <br /> 3.) (This is related to #2 above.) There were 74 props spawned from the model; some parts need to "work" together.(Tires, wheels, brake rotors, brake calipers,...)Do I need to group the parts that work together before I spawn the props? <br /> <br /> 4.) Are the default OBJ export options ok for this? <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

@ VK; <br /> Please ignore questions 2 & 3. I used the group editor to combine the parts that work together before spawning props. <br /> <br /> I have one additional question though: How do I prevent the brake calipers from rotating as the wheels, rotors & tires roll? <br /> <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

Answer 1: <br /> When the car faces the back camera, the procedure is exactly the same. You can use the same phi setup. For example, the major axis of the wheels is still the x-axis, and the flags in the phi are <br /> 2 wheelgroup xyz <br /> <br /> You need different phi-flags when the car is oriented on the x-axis (facing the right or left camera). <br /> <br /> <br /> Answer 4: <br /> You choose special export options. Uncheck all options, check only "Include body part names in polygon groups".

What was the question ?

Answer 5: <br /> You usually don't need a separate actor (group) for the brake calipers, since the calipers won't move in the car figure. Therefore, the calipers are part of the carbody, and the wheels are a separate actor. <br /> <br /> If your car object has separate caliper groups, include the caliper geometries into the carbody group, and delete the caliper groups: <br /> 1. Open Group Editor. <br /> 2. Select the carbody group in the Group Editor. <br /> 3. Click "Include Group" and select a caliper group. <br /> 4. Repeat for all caliper groups. <br /> 5. Select a caliper group in the Group Editor. Click "Delete Group". Repeat for all caliper groups. <br /> <br /> Caution: Don't delete the wrong group by mistake. And don't forget to delete the caliper groups, otherwise you have two groups including the same geometry. Before you spawn the props, check "Show Multigrouped Faces" in the Group Editor. Poser highlights all faces which are members of more than one group. When you spawn props from an object with multigrouped faces, you get a duplicate of the same geometry. For example, the caliper geometry is included in the carbody part and in the caliper part. <br /> <br /> If your car has a moveable suspension, you group the caliper geometry with the part where the caliper is attached. Of course, the geometry of the suspension should be mechanically consistent. This means, there must be some geometry where the caliper is attached (usually the housing of the bearing). <br /> <br /> When you have different parts which should roll with the wheel, you choose a common parent for all rotating parts. For example, you have an actor "axleFL". When you rotate the wheel, you set exactly one rotate channel of actor "axleFL". All actors which should follow the rotation are children of actor "axleFL". The hierarchy could look like this: <br /> 2 axleFL <br /> 3 brakerotorFL <br /> 3 rimFL <br /> 4 spinnerFL <br /> 4 tireFL <br /> <br /> Now when you rotate "axleFL" all children follow the rotation, that is the brake rotor and the <br /> rim and the children of the rim. <br /> <br /> Usually you don't need a separate tire actor, unless you want to move the tire away from the rim in your car figure. Therefore, you group the rim and the tire and make a single actor "wheel".

The car I've chosen doesn't have a suspension, or axle group. <br /> <br /> The way I understand it is: the front rotors, and calipers need to steer with wheels & tires; and the rotors need to roll (x- rotate?) with wheels & tires. <br /> <br /> So, in this situation, what would you suggest to prevent the front calipers from rolling with the wheel/tire/rotor group? <br /> <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

I thought I should post this image for P5 or newer users following this thread. <br /> <br /> {I left the roof panels in seperate groups because I wanted to be able to make them invisible when desired. I left the spoiler a seperate group; because it's height is adjusted as the vehicle increases speed. I left the engine part in their original groups; because I was unsure of the detail accuracy, and may want to change them in the future.) <br /> <br /> Question 6: <br /> Is it nessesary to put something in the phi file to change the spoiler height; or is it ok to just use the y-trans dial? <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

You're right. You need two separate actors to steer and drive. <br /> <br /> You could try the following rig for the front wheel: <br /> <br /> 2 caliper <br /> 3 brakerotor <br /> 4 wheel <br /> <br /> Use the y-rotate on parent "caliper" to steer. Use the x-rotate on child "brakerotor" to drive. When you steer, the caliper and its children follow the rotation. When you drive, the caliper is fixed. The brakerotor rotates and its child "wheel" follows the rotation (see image). <br /> <br /> Answer 6: <br /> No need to modify the phi. You can use the y-tran dial on the spoiler actor. <br /> <br /> Poser includes translate channels for each actor in the new cr2, but the translate dials are by default hidden (except for the dials on the root actor). When you want to use translate dials in a child actor, you have to open the cr2 in a text editor and edit the "hidden" line in each translate channel you want to access in the dials palette. "hidden 0" display a dial for the channel, "hidden 1" doesn't. <br /> <br /> BTW, your car looks great.

Thanks VK! <br /> <img src="https://www.posetteforever.com/images/smiles/smile.gif" alt="" /> <br /> <br /> That is a clever solution to my rotor problem. <br /> <br /> I might have more questions about the joints. I now have the bones in place.; but I am not having the expected results when adjusting the position. <br /> <br /> But; now I need sleep. <br /> <br /> Thanks again. <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

{I forgot to say, that the car model is not created by me; I just chose it to learn rigging in Poser.} <br /> <br /> It seems as if the "crosshairs" are in the reverse order from those shown in VK's diagrams. {I mean, the green one is at the rear edge of the door, and the red one is at the front edge.} Is this caused by the model originally facing rearward? <br /> <br /> I positioned the "crosshairs" in the Left door to match the diagrams; but when I apply rotation the whole front part of the car bends. I'm unclear about how to control only the desired actor. <br /> <br /> also, the bones seem to be in an incorrect position. The main bone seems to be located near the Right front wheel. <img src="https://www.posetteforever.com/images/smiles/eusa_think.gif" alt="" /> <br /> <br /> {see image.}

A. The reversed door-joint: <br /> This could be caused by the orientation of the geometry. Poser assumes the new figure is facing the front camera which is the default for all Poser humans and animals. <br /> <br /> On the other hand, my simple example car has correct orientations for the door when I have a facing front and a facing back model and create the figure using the same phi-file. It's maybe just a fluke, who knows. <br /> <br /> Of course, you can always correct the joint orientation in the Joint Editor. <br /> <br /> B. Front part bending: <br /> You have to disable (uncheck) the "Bend" option of all actors: <br /> 1. Select an actor. <br /> 2. Open the Info dialog. <br /> 3. Uncheck "Bend". <br /> The Bend option activates the soft-body joint attributes. These attributes define which polygons should be deformed when you bend (rotate) the actor of a skin (an organic figure). Cars are not skins and the joints shouldn't deform the geometry. Therefore you have to uncheck the Bend option. (You should also delete the respective channels in the cr2). <br /> <br /> <br /> C. Origin of the root actor: <br /> I'm not sure whether I understand the bones in your picture. The base of the cone is the origin, the top is the endpoint, right? The large bone from the center to the right front wheel seems to be the origin and endpoint of the root actor "carbody". <br /> <br /> It looks like Poser places the endpoint of actor "carbody" at the origin of the first child (the front wheel on the right "RIMRF" according to the Hierarchy Editor shown). From there, Poser draws a line to the origin of the following children. This would explain the white lines originating at RIMRF and ending at the origin of the remaining children. <br /> <br /> In a car model you usually only need the origin, not the endpoint, of an actor. The origins look OK as far as I can see. <br /> <br /> To fix the endpoint problem (if this is a problem), you could place the endpoint of actor "carbody" at the center of the car, right above the origin of "carbody" (same xz-coordinates of origin and endpoint). <br /> <br /> I don't know if you can edit the endpoints in Poser 5. The Joint Editor of Poser 4 only shows the endpoint of the "goals" (the last children in the hierarchy). To modify the endpoint (in Poser 4), you have to edit the cr2 in a text editor: <br /> 1. Open the cr2 in a text editor. <br /> 2. Find the code of actor "carbody". The code could look like this: <br /> <!-- no smilies start --><div class="code"><div class="code-header" id="codehdr2_195294f5" style="position:relative;">Code: [<a href="download_post.php?post=35095">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_195294f5','code2_195294f5','');ShowHide('codehdr_195294f5','codehdr2_195294f5','')">Hide</a>] [<a href="javascript:void(0)" onclick="select_text('code_195294f5')">Select</a>]</div><div class="code-header" id="codehdr_195294f5" style="position:relative;display:none;">Code: [<a href="download_post.php?post=35095">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_195294f5','code2_195294f5',''); ShowHide('codehdr_195294f5','codehdr2_195294f5','')">Show</a>]</div><div class="code-content" id="code_195294f5" style="position:relative;"><span class="code-row-text"> <br /> actor carbody:1 <br />    { <br />    name    car <br />    on <br />    bend 0 <br />    dynamicsLock        1 <br />    hidden        0 <br />    addToMenu    1 <br />    castsShadow        1 <br />    includeInDepthCue        1 <br />    parent BODY:1 <br />    channels <br />        { <br /> </span></div></div><!-- no smilies end --> <br /> <br /> 3. Scroll down to the end of this actor's code. It looks like this: <br /> <!-- no smilies start --><div class="code"><div class="code-header" id="codehdr2_ab0f6549" style="position:relative;">Code: [<a href="download_post.php?post=35095&item=1">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_ab0f6549','code2_ab0f6549','');ShowHide('codehdr_ab0f6549','codehdr2_ab0f6549','')">Hide</a>] [<a href="javascript:void(0)" onclick="select_text('code_ab0f6549')">Select</a>]</div><div class="code-header" id="codehdr_ab0f6549" style="position:relative;display:none;">Code: [<a href="download_post.php?post=35095&item=1">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_ab0f6549','code2_ab0f6549',''); ShowHide('codehdr_ab0f6549','codehdr2_ab0f6549','')">Show</a>]</div><div class="code-content" id="code_ab0f6549" style="position:relative;"><span class="code-row-text"> <br />        } <br />    endPoint 0.326 0.253 -0.307 <br />    origin 0.332 0.253 0.08 <br />    orientation 0 0 180 <br />    displayOrigin        0 <br />    displayMode USEPARENT <br />    customMaterial    0 <br />    locked 0 <br />    } <br />   <br /> </span></div></div><!-- no smilies end --> <br /> <br /> 4. Edit the "endpoint" line. There are 3 numbers separated by a space. The numbers are the xyz-coordinates of the endpoint. Write the xz-values from the "origin" line into the xz-values of the "endpoint" line. Save and close. <br /> <br /> As far as I can see, the cr2 should work well. If you modify the endpoint of "carbody", post a new picture with the resulting bones. If you get unexpected results with the cr2, post the problems.

In Poser5 the endpoints are controllable with the joint editor. I'll change their positions to match the origins' positions. {I'd done this with the Left door; but the body still bent; so I changed it back. Now that you've explained the bending issue to me, I'll redo it.} <br /> <br /> Thanks again VK! <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/smile.gif" alt="" /> <br /> <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

The cr2 is almost complete. <br /> <br /> Just a few things...: <br /> <br /> The endpoints are not a problem, after bend is unchecked for each part. <br /> <br /> I have been unable to unhide the ytrans dial for the spoiler. I changed the "hidden" from 1 to 0; no success. I then noticed that there were fewer lines in the "groupNode Transform" section; so I added the missing ones to the c2. I again changed the "hidden" value; no success. <br /> Suggestions? <br /> <br /> Also... How do I set limits for the dials? {I mean, so the doors & hood will open only so far...} <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

A. Dial limits: <br /> In the channel code, there is a "min" and a "max" line, like <br /> <br /> <!-- no smilies start --><div class="code"><div class="code-header" id="codehdr2_cccafde5" style="position:relative;">Code: [<a href="download_post.php?post=35101">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_cccafde5','code2_cccafde5','');ShowHide('codehdr_cccafde5','codehdr2_cccafde5','')">Hide</a>] [<a href="javascript:void(0)" onclick="select_text('code_cccafde5')">Select</a>]</div><div class="code-header" id="codehdr_cccafde5" style="position:relative;display:none;">Code: [<a href="download_post.php?post=35101">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_cccafde5','code2_cccafde5',''); ShowHide('codehdr_cccafde5','codehdr2_cccafde5','')">Show</a>]</div><div class="code-content" id="code_cccafde5" style="position:relative;"><span class="code-row-text">rotateY yrot <br />    { <br />    name Open <br />    initValue 0 <br />    hidden 0 <br />    forceLimits 4      <------- set the "forceLimits" flag <br />    min 0       <-------   the minimum value of the dial <br />    max 80       <-------   the maximum value of the dial <br />    trackingScale 1 <br />    keys <br />        { <br />        static  0 <br />        k  0  0 <br />        } <br />    interpStyleLocked 0 <br />    } <br /> </span></div></div><!-- no smilies end --> <br /> <br /> 1. Write your min and max values into the channel code. The minimum value must be smaller than or equal to the maximum value. When your door opens to -80 degrees, you choose <br /> min -80 <br /> max 0 <br /> <br /> When the values are equal or the max value is smaller than min, the dial is locked. <br /> <br /> 2. Write the "forceLimits 4" flag. The default value 0 means the limits are by default disabled. The dial can take any value unless the user activates "Figure > Use Limits". When the "Use Limits" menu is activated, the dial takes only values within the "min" and "max" limits in the channel code. <br /> <br /> A "forceLimits" value other than 0 means the "min" and "max" limits in the channel code are always enabled. The user cannot choose a value beyond the limits. This is what you want. <br /> <br /> <br /> B. Y-tran dial invisible: <br /> I'm not sure what the problem is. Could you post the code of the "groupNode Transform"? Are there any IK-chains in the model? IK-chains, if available, are listed in the Hierarchy Editor. Delete all of them. <br /> <br /> Save a document with the model and open the document in a text editor. Is the y-tran channel in the code? Is the "hidden 0" line set? <br /> <br /> You can send me the cr2 code (without geometry, maps, etc.) so I can take a look at it.

Ah... I forgot about Figure->Force Limits. Limits work now; thanks. <br /> <img src="https://www.posetteforever.com/images/smiles/smile.gif" alt="" /> <br /> <br /> I attached the cr2. I left in the modifcations that I made to the groupNode code; because I was sucsessfl in removing the "taper dial" from the spoiler with it. <br /> <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

I could run the cr2 in Poser 4 with an example geometry (some cubes). The yTran dial of the spoiler is available <br /> and works as expected. Poser 4 strips some of the script when the model loads, but the essential channel code <br /> is the same as the code used by Poser 5. <br /> <br /> The "groupNode" is only used to group dials in the tabs of the dials palette, AFAIK. This parameter does not <br /> affect the channels. It seems as if you have to list the channels in a groupNode when you want to see the dials. <br /> Anyway, the yTran channel was already listed in the groupNode of actor SPOILER. <br /> <br /> I noticed a "SPOILER_jointx" dial on actor "Carbody". Channel "jointX SPOILER_jointx" is usually invisible <br /> (and should be automatically hidden when you open and close the Joint Editor with selected "Carbody"). However, <br /> this shouldn't affect the channels of the spoiler. <br /> <br /> I attach a zip with 3 different cr2's you can test: <br /> <br /> carreratest1.cr2: <br /> This is basically your original cr2. The only difference is a hidden "jointX SPOILER_jointx" channel on actor <br /> "Carbody". The yTran dial on actor "SPOILER" should be available in the dials palette of the spoiler. <br /> <br /> carreratestPo4.cr2: <br /> This is the original cr2 loaded and saved in Poser 4. I used this cr2 for my test. The yTran dial on actor <br /> "SPOILER" is available in the dials palette and works as expected. Note that the "figureResFile" lines point at <br /> :Runtime:Geometries:carrera.obj. And the materials are Poser 4 style, of course. Poser 4 doesn't use the <br /> groupNode code. If all fails, try this cr2. <br /> <br /> carreratestStrip.cr2: <br /> The stripped version of your cr2. I removed the unused code. <br /> There are several channels in each actor used only for joint and geometry deformation: "twistX", "jointY", <br /> "smoothScaleZ" etc. and "taper". These channels bloat the cr2 and are dead code (never used). <br /> There are "weld" commands for each parent and child. "Weld" glues the seams of parents and children. This is <br /> only used when you have a skin with a continuous surface. Car actors are usually not welded, and the code can <br /> be removed. The filesize of the stripped cr2 is about 10% smaller. The more actors you have, the more <br /> overhead you get. The overhead is duplicated in each document which includes the figure.

Thanks VK. <br /> <br /> I intended to remove the bloat; but wanted to get the cr2 working well first. <br /> <br /> <br /> I'll try out the cr2s and get back to you. <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

*stomp* I want this Porsche <img src="https://www.posetteforever.com/images/smiles/lol.gif" alt="" />

To VK; <br /> <br /> I loaded the "carrerateststrip.cr2", directed it to the correct obj, and everything works well. <img src="https://www.posetteforever.com/images/smiles/eusa_clap.gif" alt="" /> <img src="https://www.posetteforever.com/images/smiles/notworthy.gif" alt="" /> <img src="https://www.posetteforever.com/images/smiles/notworthy.gif" alt="" /> <br /> Thank you very much for assistance with this! <br /> <br /> I do have a couple more questions though... <br /> <br /> 1.) Would there be a great size benefit to removing all of the unused dials(scaling for children, zrotate for wheels,...) from the cr2? <br /> <br /> 2.) Could you please explain the much smaller cr2 size of the P4 version? <br /> <br /> {I intend to look into & compare the different versions; but I'm being invaded by friends from out of town. It must be "Spring Break" somewhere in the world... <img src="https://www.posetteforever.com/images/smiles/rolleyes.gif" alt="" /> } <br /> <br /> <br /> To Ahjah; <br /> <br /> I'm glad that I excepted this and the other Hankster automobiles as perks from one of my "testing jobs". I almost didn't; because they were not "poserized"; Now, thanks to VK's tutorial, and assistance... they are (or will be...). <img src="https://www.posetteforever.com/images/smiles/lol.gif" alt="" /> <br /> <br /> <br /> <br /> To Goat; <br /> <br /> If you've been lurking this thread recently, I'm curious to know how your progress is going. <img src="https://www.posetteforever.com/images/smiles/smile.gif" alt="" /> <br /> <br /> I decided that I don't use much Poser animation, so I did not include poseable pedals, and I did not link the turning of the steering wheel to the steering of the tires. I think I will include those with the next auto I poserize; but now I want to spend some time getting aquainted with Apollo Maximus, and Miki 2. <br /> <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

I'm glad to hear that the model is working well. <img src="https://www.posetteforever.com/images/smiles/smile.gif" alt="" /> <br /> <br /> Re filesize: <br /> 1. Removing the unused channels saves about 5% of the (stripped) cr2 filesize. <br /> 2. The big difference between Poser 4 and Poser 5 is the material code: In the <br /> stripped cr2, the channel code is less than 20%, the material definitions are about 80% <br /> of the cr2 (84 KB versus 460 KB).

To VK; <br /> <br /> I noticed that on the Vespa, there are dials in the "body" that control the visiblity of the spare tire, and extra seat. <br /> Would you please explain the procedure for accomplishing that? <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/happy8.gif" alt="" />

The changing parts are "alternate geometry". <br /> <br /> In the figureResFile, the geometry of actors "sparewheel" and "pillion" is a single tiny polygon "p_dummy" inside the Vespa body. The "p_dummy" geometry is invisible. <br /> <br /> <!-- no smilies start --><div class="code"><div class="code-header" id="codehdr2_0b4de475" style="position:relative;">Code: [<a href="download_post.php?post=35207">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_0b4de475','code2_0b4de475','');ShowHide('codehdr_0b4de475','codehdr2_0b4de475','')">Hide</a>] [<a href="javascript:void(0)" onclick="select_text('code_0b4de475')">Select</a>]</div><div class="code-header" id="codehdr_0b4de475" style="position:relative;display:none;">Code: [<a href="download_post.php?post=35207">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_0b4de475','code2_0b4de475',''); ShowHide('codehdr_0b4de475','codehdr2_0b4de475','')">Show</a>]</div><div class="code-content" id="code_0b4de475" style="position:relative;"><span class="code-row-text">actor sparewheel:1 <br />    { <br />    storageOffset 0 0 0 <br />    geomHandlerGeom 13 p_dummy    <---  tiny single polygon <br />    } <br /> actor pillion:1 <br />    { <br />    storageOffset 0 0 0 <br />    geomHandlerGeom 13 p_dummy   <br />    } <br /> </span></div></div><!-- no smilies end --> <br /> <br /> There are extra geometries for the pillion, the spare wheel, and the rack to mount the spare wheel. <br /> <br /> In the respective actors, for example "pillion", there is an "alternateGeom" instruction to load the pillion geometry. There is also a "geomChan" channel which displays a dial to choose the alternate geometry. <br /> <br /> <!-- no smilies start --><div class="code"><div class="code-header" id="codehdr2_a0056012" style="position:relative;">Code: [<a href="download_post.php?post=35207&item=1">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_a0056012','code2_a0056012','');ShowHide('codehdr_a0056012','codehdr2_a0056012','')">Hide</a>] [<a href="javascript:void(0)" onclick="select_text('code_a0056012')">Select</a>]</div><div class="code-header" id="codehdr_a0056012" style="position:relative;display:none;">Code: [<a href="download_post.php?post=35207&item=1">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_a0056012','code2_a0056012',''); ShowHide('codehdr_a0056012','codehdr2_a0056012','')">Show</a>]</div><div class="code-content" id="code_a0056012" style="position:relative;"><span class="code-row-text">actor pillion:1 <br />    { <br />    name    pillion <br />    on <br />    bend 0 <br />    dynamicsLock        0 <br />    hidden        0 <br />    addToMenu    1 <br />    castsShadow        1 <br />    includeInDepthCue        1 <br />    parent vespabody:1 <br />    alternateGeom    pillion <br />        { <br />        name pillion <br />        objFile 1003 :Runtime:Geometries:vspscooter:pillion3.obj    <--- the alternate geometry <br />        } <br />    channels <br />        { <br />        geomChan pillion  <--- choose alternate geometry <br />            { <br />            uniqueInterp <br />            name (pillion) <br />            initValue 0 <br />            hidden 1 <br />            forceLimits 4 <br />            min 0 <br />            max 1 <br />            trackingScale 0.045 <br />            keys <br />                { <br />                static  1 <br />                k  0  0 <br />                } <br />            interpStyleLocked 1 <br />            staticValue 0 <br />            valueOpDeltaAdd   <---   ERC slave code <br />                Figure 1 <br />                BODY:1 <br />                vpvsp3pillion <br />            deltaAddDelta 1.000000 <br />            } <br />        } <br /> </span></div></div><!-- no smilies end --> <br /> <br /> The geomChan channel is an ERC-slave of a master channel in BODY. When you set the master, the geomChan loads and displays the alternate geometry, for example the pillion. <br /> <br /> <!-- no smilies start --><div class="code"><div class="code-header" id="codehdr2_3a199c52" style="position:relative;">Code: [<a href="download_post.php?post=35207&item=2">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_3a199c52','code2_3a199c52','');ShowHide('codehdr_3a199c52','codehdr2_3a199c52','')">Hide</a>] [<a href="javascript:void(0)" onclick="select_text('code_3a199c52')">Select</a>]</div><div class="code-header" id="codehdr_3a199c52" style="position:relative;display:none;">Code: [<a href="download_post.php?post=35207&item=2">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_3a199c52','code2_3a199c52',''); ShowHide('codehdr_3a199c52','codehdr2_3a199c52','')">Show</a>]</div><div class="code-content" id="code_3a199c52" style="position:relative;"><span class="code-row-text">actor BODY: <br />    { <br />        { <br />        valueParm vpvsp3pillion    <--- ERC master <br />            { <br />            name Pillion <br />            initValue 0 <br />            hidden 0 <br />            forceLimits 4 <br />            min 0 <br />            max 1 <br />            trackingScale 2 <br />            keys <br />                { <br />                static  0 <br />                k  0  0 <br />                } <br />            interpStyleLocked 1 <br />            } <br /> </span></div></div><!-- no smilies end --> <br /> <br /> You find more information on alternateGeom and ERC in the ERC tutorial, Chapter 9. <br /> (www.atlantis23.com/erc_download.html).

Just wondering if anyone has had luck making more cars! <br /> <br /> Great tutorial!!

Not me but I'm having some ideas for alternate geometries <img src="https://www.posetteforever.com/images/smiles/lol.gif" alt="" />