Thx DoomsdayRenderer and luuckyy
I think my wishlist was a bit mistakable... sorry
The things I was talking about would only affect the povray export.
Quote:
- an editor for global_settings (something like the object data editor)
|
I meant the global settings in the povray file header, the possibility to add more #include, #define lines and to insert radiosity data.
Data that is added in the export above the camera{} function.
Quote:
- an editor for objects which cant be added to the main union{},
like fog, sky_sphere and rainbow
|
I just thought about a small textfield where data can be entered, which will be added directly below the camera{} function in the povray export.
Quote:
AFAIK a texture is always a part of a material description.
That means that you can't have a texture mapped to your surface(s) without a material applied to your surface(s) (and AFAIK you can't have a model with no material at all).
If your problem is with the material color maybe mixing with the texture colors, then just use a completely white (255,255,255) material.
|
I completely agree
, I meant something different,
the problem is, that povray cant use Layered textures and a texture_map for the same object. Here s an example:
Code:
union { // <- this is the main union
// object box
union {
// OBJECT DATA
texture { ac3d_col_1 } // <- here adds ac3d automatically a texture (1. Layer)
// Here follows data which has been added to the object property dialog (Would be 2. layer),
texture{
gradient <1,1,1>
texture_map{ // does work only if first texture (ac3d_col_1) is removed
[0.1 First_T]
[0.9 Second_T]
}
}
}
// rotate and scale
}
Would be really great if those features could be implemented in ac3d.