[no subject]

So if in your new scene the particle ID is not the same ( for a =
mysterious reason in your case ) the instanced objects can't be the =
same.
I've got the feeling that there is a bug when you export a model with =
some clouds. sometime it breaks the ptypes, sometime not.=20

The best thing is to stay away from this particle system !


--=20
Guillaume Laforge
freelance TD | cg Artist
my blog ! http://vol2blog.blogspot.com/=20



On 1/17/07, Bernard Lebel <3dbernard(at)gmail.com> wrote:

Hello,

I'd like to know what's the particle type ID doing.


I have this problem. I created a bunch of particle clouds, each having
a ptype. Those ptype all use instancing.

Particle clouds, instance groups and instantiated geometry are all=20
under a model. When I open the scene, no problem. When I export a
model and re-import it, everything is still there, except that
particle clouds are using the wrong instances. The ptypes are
connected to the right clouds, the groups are referenced by the same=20
ptypes, but yet particles are interchanged.

The only difference I could find was the ptype ID has changed (what
was 6 is now 0, for example). Can this be an explanation?


Thanks
Bernard
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in =
body:
unsubscribe xsi






------_=_NextPart_001_01C73A51.B2C38B72
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40";>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 (at)font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
(at)page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The PTypeID shouldn&#8217;t matter, =
the
only place where it touches instances is to disambiguate their names at =
render
time. I don&#8217;t think the particle IDs get reordered on load, unless
something happened with the emission.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Did the items in the instance group =
become
re-arranged for some reason? Set the explorer to view things in =
&#8220;Creation
Order&#8221; and use the re-order tool to get back what you had, if =
that&#8217;s
the case.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>=A0- =
=BD<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>guillaume laforge<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 17-Jan-07 10:45<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">XSI(at)Softimage.COM</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: TypeID =
(Particle) of
PType and mixed up instances</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>From Halfdan =
some post
ago : </span></font><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>instance_index =3D ( particle_id * =
23827 )
% nb_instances<br>
<br>
So if in your new scene the particle ID is not the same ( for a =
mysterious
reason in your case ) the instanced objects can't be the same.<br>
I've got the feeling that there is a bug when you export a model with =
some
clouds. sometime it breaks the ptypes, sometime not. <br>
<br>
The best thing is to stay away from this particle system !<br>
<br>
</span></font><br>
-- <br>
Guillaume Laforge<br>
freelance TD | cg Artist<br>
my blog ! <a =
href=3D"http://vol2blog.blogspot.com/";>http://vol2blog.blogspot.com/</a>
<br>
<br>
<o:p></o:p></p>

<div>

<p class=3DMsoNormal><span class=3Dgmailquote><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>On 1/17/07, <b><span =
style=3D'font-weight:bold'>Bernard
Lebel</span></b> &lt;<a =
href=3D"mailto:3dbernard(at)gmail.com">3dbernard(at)gmail.com</a>&gt;
wrote:</span></font></span><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hello,<br>
<br>
I'd like to know what's the particle type ID doing.<br>
<br>
<br>
I have this problem. I created a bunch of particle clouds, each =
having<br>
a ptype. Those ptype all use instancing.<br>
<br>
Particle clouds, instance groups and instantiated geometry are all <br>
under a model. When I open the scene, no problem. When I export a<br>
model and re-import it, everything is still there, except that<br>
particle clouds are using the wrong instances. The ptypes are<br>
connected to the right clouds, the groups are referenced by the same =
<br>
ptypes, but yet particles are interchanged.<br>
<br>
The only difference I could find was the ptype ID has changed (what<br>
was 6 is now 0, for example). Can this be an explanation?<br>
<br>
<br>
Thanks<br>
Bernard<br>
---<br>
Unsubscribe? Mail <a =
href=3D"mailto:Majordomo(at)Softimage.COM">Majordomo(at)Softimage.COM</a>
with the following text in body:<br>
unsubscribe xsi<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
<br clear=3Dall>
<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C73A51.B2C38B72--
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.