Exporter features

arneoog · Post by **arneoog** » Thu Jul 27, 2006 11:37 pm

What kind of features should an exporter have?
We should make a list

arneoog · Post by **arneoog** » Thu Jul 27, 2006 11:38 pm

Here are some:

renderer_settings
width
height
metropolis
large_mutation_prob
max_change
russian_roulette_live_prob
max_depth
bidirectional
strata_width
frame_upload_period
halt_time
logging
image_save_period
save_tonemapped_exr
save_untonemapped_exr

tonemapping
pre_scale
post_scale
colour_correction

u3dreal · Post by **u3dreal** » Fri Jul 28, 2006 1:32 am

Well i think the best thing is to have full control over indigo from
within the exporter. So indigo gets totally integrated.
Plus all the materials should be accesable.

cheers

u3dreal

arneoog · Post by **arneoog** » Fri Jul 28, 2006 1:40 am

Yes, totally!

And therefore we should make a list of what features it needs.
So that everyone can use very much the same functiuons,
regardless of what software they use.

I know you added a "time and date for the sun" option in the Max2Indigo exporter.
That should be on the list.

u3dreal · Post by **u3dreal** » Fri Jul 28, 2006 1:46 am

I get the time / date data from max daylightsystem-.##

cheers

u3dreal

arneoog · Post by **arneoog** » Fri Jul 28, 2006 1:54 am

Could you make a list of the things you know is needed?

u3dreal · Post by **u3dreal** » Fri Jul 28, 2006 3:16 am

Hm i will probably do this when i update my exporter but for
now i'm sitting in munich and i cna do any thing..

cheers

u3dreal

Zom-B · Post by **Zom-B** » Fri Jul 28, 2006 5:05 am

I would like to see the following stuff:

- Shpere & Plane Objekt
- NK-Materials integration with Pre Rendered Preview (see here)
- Export Model as Triangel Set defined in the XML (for easy sharing)
- Tooltips (if the App support this => great for n00bs like me

)

Hope some of this is possible to realize...

gautxori · Post by **gautxori** » Sun Apr 06, 2008 4:43 am

hi,

it seems funny to me (

) that since Jul 2006 there's no continuation on the proposal of keeping a unified interface to export data from 3d modellers to indigo, & to make available to modellers the data of materials, cameras, textures, lights, etc. [EDIT: when v1.0.4 was released there was a short debate on this (see the thread http://www.indigorenderer.com/joomla/fo ... c&start=35)
and perhaps also after this]

i feel there's some command-line app missing that could help unifying this (woops, perhaps this is the indigo SDK?)

dougal2 · Post by **dougal2** » Sun Apr 06, 2008 4:51 am

the multiple independant development of the exporters for different apps, all of which have different interfaces and features is a little bizarre, i agree.

However, given that developing an exporter requires expert knowledge of the modelling application, it'd take too much time and money for a single person to buy every available package, learn its API and construct a unified exporter for all of them.
Add to this the fact that nearly every app uses a different programming language too... a common codebase is not really very practical.

Perhaps the exporter development could have been more unified from the start but I think we're at a point now where re-writing even a single part of a single exporter is a major task.

gautxori · Post by **gautxori** » Sun Apr 06, 2008 8:07 am

yep, i agree that "we're at a point now where re-writing even a single part of a single exporter is a major task". What i'm afraid of is that this could make some "exporters" die (not the developers, the apps

), and indigo could lose a nice chance of being "the most used renderer (and the best) by 3d modelling apps".

Post by **fused** » Mon Apr 07, 2008 11:12 pm

Exporter features

Exporter features

generic "exporter" (interface)?

dougal2

Who is online