Override map_type in config script.

you might try emailing sjeiti, since we know already that he understands this stuff. i had completely forgotten about the new command line stuff, since i dont use it at all. so, try sjeiti or maybe someone else will come along that knows this.

Thanks for the replies.

Yes I understand that would be the way to modify the filter description (filter.ffxml in my original post) to output separate maps but it not very efficent if I am doing multiple iterations of (tweak in ff - render in ff - export to maya - render in maya).

Let me outline the two workflows again ( hopefully clearer), maybe I am missing something obvious.

Current workfow ( slow).

Tweak filter (filter.ffxml) in FF
For each map I want to output
Duplicate preset. specify map type and update preset (slow part)
Render with commandline renderer with config.xml
Render in Maya.
Goto Tweak filter.

More efficient workflow ( if possible)

Setup multiple <Task> entries in config.xml to specify different map_type (possible?)

Tweak filter (filter.ffxml) in FF
Render with commandline renderer with config.xml (outputing multiple maps)
Render in Maya.
Goto Tweak filter.


The second method would mean much more simple, efficient development. It does depend on being able to override the map_type variable in the config.xml <Task> section

Any pearls of wisdom?

Cheers
Mike

Quote
You can create many presets per single filter, and set the batch renderer to render all these presets in a row.

Hi,

I have the same problem as bigdog. The command line tool is "limited" because you need to create one preset per map type. Actually, in Filter forge you can decide to create a different map for the same preset using the Filter>Render maps menu. But with the command line tool you can't do the same choice: create one preset per map is not user friendly.

I think bigdog is asking to have a feature like:

<Task>
<Image value="" width="300" height="400" />
<Selection value="" />
<Result path="D:\Images\Wood.bmp" />
<Filter value="filters\Library_284-1.ffxml" />
<Preset value="0">
<Map type="0" />
<Map type="1" />
<Map type="2" />
</Preset>
</Task>

Another reason to use this is with multiple presets per texture, you can't guarantee someone that the different presets per map will be for the same 3D texture. If one setting is changed in one preset (bump for example), it will be a bad 3D texture. But with the same preset creating different maps, you have the guarantee the maps will be coherent for the same 3D texture.