Thomas de Groot wrote:
> I have made a small list of features I would like to see implemented in a 
> future version of Poseray. These features are derived from cases met in the 
> use of Poseray, in combination with Poser and/or external modellers.
> 
> 
> 
> 1 Naming a POV-Ray export of merged meshes
PoseRay exports the mesh by default by material. PoseRay does keep the 
groups and materials separate when merging a mesh by adding a number at 
the end of the material or group name if it already exists. I could 
create a higher level entity (object) for each mesh read. That way the 
merged meshes could be kept separate with their own materials. Like this 
for 3 meshes with 2, 4 and 3 materials respectively:

//in the geometry file...
#declare object1=
union{
object(object1_material1 material{material1} hollow}
object(object1_material2 material{material2} hollow}
}

#declare object2=
union{
object(object2_material4 material{material3} hollow}
object(object2_material5 material{material4} hollow}
object(object2_material6 material{material5} hollow}
object(object2_material6 material{material6} hollow}
}

#declare object3=
union{
object(object3_material7 material{material7} hollow}
object(object3_material8 material{material8} hollow}
object(object3_material9 material{material9} hollow}
}


//in the scene file...
object{object1}
object{object2}
object{object3}

if only a mesh is exported then the exported files would look as they do 
now. For those wondering why hollow is because it allows media to work 
inside the mesh.


> 
> 2 Saving uv transformations in the Materials section

I will look into the U and V scale, offset and mirror for image_map 
entries in the Poser materials. I have Poser 6 so I cannot test it for 
later versions but I doubt it will change.

> 
> 3 Showing (and using) the origin of the object in the Preview window
> 

Relatively easy to do and could be toggled.

Post a reply to this message

"FlyerX" <fly### [at] yahoocom> schreef in bericht 
news:4adadc9b@news.povray.org...

> PoseRay exports the mesh by default by material. PoseRay does keep the 
> groups and materials separate when merging a mesh by adding a number at 
> the end of the material or group name if it already exists. I could create 
> a higher level entity (object) for each mesh read. That way the merged 
> meshes could be kept separate with their own materials. Like this for 3 
> meshes with 2, 4 and 3 materials respectively:

Yes, that would answer my question to satisfaction.

>
> I will look into the U and V scale, offset and mirror for image_map 
> entries in the Poser materials. I have Poser 6 so I cannot test it for 
> later versions but I doubt it will change.

I think those have not changed. I have Poser 8 so I can test it for you.


>> 3 Showing (and using) the origin of the object in the Preview window
>
> Relatively easy to do and could be toggled.

Thank you! Neat!

Thomas

Post a reply to this message

"Stephen" <mca### [at] aolDOTcom> schreef in bericht 
news:4adadc7f$1@news.povray.org...
> I support your wish list, Thomas. I hope that you have submitted it to 
> FlyerX :-)

Well, FlyerX found it here already :-)
I wanted to post the list here so that people could comment and/or add their 
own wishes (if any).

>
> Your second point is interesting. I have been complaining that Bishop3D 
> actually imports the complete PoseRay generated meshes into the scene. 
> While Moray uses the UDO in the scene and the full mesh and materials are 
> only included. One advantage of this is, in B3D, that you can edit the 
> mesh materials directly and it is saved in the Bishop3D file for 
> exporting.

In that regard, Moray is lacking in functionality, but we knew that already 
:-)  Moray 4.0 will overcome all that ;-)
My motives in my second point are: first the possibility to transform the uv 
one way or another: basically in Poser and export those settings to Poseray 
and beyond; secondarily, doing this in Poseray and save those 
transformations in the settings mtl file; as a last resort doing 
transformations directly into the POV-Ray material file which is much less 
elegant although giving similar results. The first and second options are my 
favourite ones
and need some further implementation in Poseray to become powerful tools.

Thomas

Post a reply to this message

FlyerX schrieb:
> Thomas de Groot wrote:
>> I have made a small list of features I would like to see implemented 
>> in a future version of Poseray. These features are derived from cases 
>> met in the use of Poseray, in combination with Poser and/or external 
>> modellers.
>>
>>
>>
>> 1 Naming a POV-Ray export of merged meshes

I would like to add to this request:

 From what I see, the output file names are generated from the input 
file names as well, and therefore do depend on the oder in which meshes 
are added to the merger.


Another thing:

For me, it would often be desirable to export geometry only, and keep 
the material export "unharmed", so I can change the pose of a figure 
without having to re-do all the changes to the materials again. (I 
prefer to edit them after export.)

Post a reply to this message

clipka wrote:
> FlyerX schrieb:
>> Thomas de Groot wrote:
>>> I have made a small list of features I would like to see implemented 
>>> in a future version of Poseray. These features are derived from cases 
>>> met in the use of Poseray, in combination with Poser and/or external 
>>> modellers.
>>>
>>>
>>>
>>> 1 Naming a POV-Ray export of merged meshes
> 
> I would like to add to this request:
> 
>  From what I see, the output file names are generated from the input 
> file names as well, and therefore do depend on the oder in which meshes 
> are added to the merger.
> 
> 
> Another thing:
> 
> For me, it would often be desirable to export geometry only, and keep 
> the material export "unharmed", so I can change the pose of a figure 
> without having to re-do all the changes to the materials again. (I 
> prefer to edit them after export.)

I have received a couple of messages recently about the lack of control 
on the names for the POV scene. I will implement the names and flags for 
the exported POV files. I removed this from an earlier version because 
of clutter.

FlyerX

Post a reply to this message

FlyerX wrote:

>> Another thing:
>>
>> For me, it would often be desirable to export geometry only, and keep 
>> the material export "unharmed", so I can change the pose of a figure 
>> without having to re-do all the changes to the materials again. (I 
>> prefer to edit them after export.)
> 
> I have received a couple of messages recently about the lack of control 
> on the names for the POV scene. I will implement the names and flags for 
> the exported POV files. I removed this from an earlier version because 
> of clutter.
> 
> FlyerX

Hi FlyerX,
	Unrelated but could you make an option to remove the confirmation popup 
asking if you are sure that you really want to close when you ask 
PoseRay to exit?
It is a very small thing but I find it quite irritating :)


-- 

Best Regards,
	Stephen

Post a reply to this message

Stephen wrote:
> FlyerX wrote:
> 
>>> Another thing:
>>>
>>> For me, it would often be desirable to export geometry only, and keep 
>>> the material export "unharmed", so I can change the pose of a figure 
>>> without having to re-do all the changes to the materials again. (I 
>>> prefer to edit them after export.)
>>
>> I have received a couple of messages recently about the lack of 
>> control on the names for the POV scene. I will implement the names and 
>> flags for the exported POV files. I removed this from an earlier 
>> version because of clutter.
>>
>> FlyerX
> 
> Hi FlyerX,
>     Unrelated but could you make an option to remove the confirmation 
> popup asking if you are sure that you really want to close when you ask 
> PoseRay to exit?
> It is a very small thing but I find it quite irritating :)
> 
> 

I put that in because I lost many scenes by closing the program by 
mistake while thinking I was closing another window. Not a problem... I 
can put that optional.

FlyerX

Post a reply to this message

If, when saving a figure to POV-Ray, one changes the file name, this name 
should also be changed accordingly at the declared figure name, within the 
xxx_POV_geom.inc.

Thus, an original Poser figure *Beggar*, saved under the file name: 
Beggar2_POV_geom.inc

should contain:

//Model assembly from the meshes
#declare Beggar2_=
union {
.....
}

instead of:

//Model assembly from the meshes
#declare Beggar_=
union {
.....
}

as happens under the present version of Poseray.

Thomas

Post a reply to this message

Thomas de Groot schrieb:
> If, when saving a figure to POV-Ray, one changes the file name, this name 
> should also be changed accordingly at the declared figure name, within the 
> xxx_POV_geom.inc.
> 
> Thus, an original Poser figure *Beggar*, saved under the file name: 
> Beggar2_POV_geom.inc
> 
> should contain:
> 
> //Model assembly from the meshes
> #declare Beggar2_=
> union {
> .....
> }
> 
> instead of:
> 
> //Model assembly from the meshes
> #declare Beggar_=
> union {
> .....
> }
> 
> as happens under the present version of Poseray.

Why? It only complicates matters; for instance, if you want to use 
different include files for different frames of an animation, having the 
same figure carry the same name is of an advantage.

If it is about getting two figures of same base name in a single scene, 
it may be easier, too, as in:

#declare MyFigures = array[10];
#local i = 1;
#while (i <= 10)
   #include concat("Beggar", str(i,0,0), "_POV_geom.inc");
   #declare MyFigures[i-1] = object { Beggar_ }
   #local i = i + 1;
#end

Post a reply to this message

"clipka" <ano### [at] anonymousorg> schreef in bericht 
news:4aef52aa@news.povray.org...

> Why? It only complicates matters; for instance, if you want to use 
> different include files for different frames of an animation, having the 
> same figure carry the same name is of an advantage.
>
> If it is about getting two figures of same base name in a single scene, it 
> may be easier, too, as in:
>
> #declare MyFigures = array[10];
> #local i = 1;
> #while (i <= 10)
>   #include concat("Beggar", str(i,0,0), "_POV_geom.inc");
>   #declare MyFigures[i-1] = object { Beggar_ }
>   #local i = i + 1;
> #end

Well, it seems inconsistent to me. If I change the name of the file for one 
reason or another (for instance because I changed the materials but want to 
keep the original too at the same time), I expect the name of the figure to 
change too in order to avoid inconsistencies and confusion later in the POV 
scene.

Your example is of course also valid, so maybe this change should be 
optional.

Thomas

Post a reply to this message