Igors

Hi, Mark Bug, fixed, details here http://www.eias3d.com/forums/showthread.php?tid=66 Thx for the report

Hi, rdm, All More tests are needed. First test: direct light only (no GI) without transmission. Second one: same but with transmission 0.013. If possible - please post and don't worry how they look, it's for testing Thanls

Hi All Agreed too. Except of points 11 and 14, all rest = good UP propositions

Hi Alex, Ian, All One of possible reasons is that corners are made with intersected surfaces (like several crossed planes or cubes). If so - yes, photon maps fail in such places (we need a new feature in EI9 to solve this)

Hi, Christian, All We've no intentions to hide/ignore bugs but any programmer needs to reproduce a situation to fix a problem. In other words we need your project and a small report. (just error description as you wrote + steps to reproduce). Please prepare such sample prj. We'll post more details (about how and where to upload) not momentary but soon. Thanks

Hi again We've confused all, thx for explanations. Ok, after some thinking: technically it's very complex. The details are: - shaders API does not support fonts enumaretation. Although a portion of native code is possible, it would increase shader's chances to be incompatible with next OS vers and/or EI vers; - with network render there is no any guarantee the exactly same font is installed on all slaves; - a procedural cannot be previewed in Texture Dialog, cannot be mapped as a sphere, cylinder etc. Although a shader can provide all these kinds of mapping itself it could not help with interactive feedback; - a procedural should provide sampling and anti-alias itself, so in this case it should do all that Camera does for texture image (and have corresponded options); - memory problems are possible. On render side images are stored in cachePageFile and loaded by parts when necessary. But a procedural can only keep a whole image (drawn text) in RAM. Sorry for a lot of "cons". It's just "this concrete case", we don't want to be "killers of ideas" ;-)

Hola Juanxer Everything is quite understandable, but please explain us WHY do you persistenly call this feature as "simple"? :-) The actual Mr.Font is a solid piece of code (yes, not near perfect). There is a big difference in "PS draws" (pixes) and "draw 3D" (model in hand). What extra functionality is required?