cool. thanks.

change log looks good..
I won't be able to test til Thursday but thanks a bunch for making it an extension!

Changelog: * Added ground to new sky model. that works out ok.. definitely better than the defined black cutoff... might be neat if we could raise or lower the horizon level (but i haven't really thought that through at all :D ) * Added SunSkyControl for changing the sun/sky in realtime. couldn't fi...

here's the version with a solid lampshade. enjoy


[i remembered to purge this time ..no need for mat3.. ]
mat0 will be for the lamp shade..
mat1 = fixture
mat2 = light bulb

no trouble at all.. I already have it drawn that way..
I'm on a bus right now though
ill upload it once I get back to a computer.

I'm not questioning about the design: when I export it as an external mesh Indigo freezes and then reports an error :D that thing is a mess.. i can't even import the .3ds into sketchup and then export to indigo without it crashing.. maybe a bug but i dunno.. i redrew it in rhino..a quick redraw but...

use style's endpoints to see if model's sides are made with a sigle line-side or not... if check redraw it. yay! that does in fact fix it.. and fredo happens to have a nifty little ruby that will take care of all the lonely vertices in a model.. the example .skp i posted actually has 27(!) of them....

snorky wrote: ...
is this the error?

yeah, that's it.. i wonder how this can be dealt with in sketchup or skindigo because in sketchup, we don't have those triangles and all the faces appear to be coplanar.

what exactly did you do to fix the model? (did you do something in sketchup or in indigo?)

This is proving to be a difficult issue to resolve. I found that if I made the geometry a component and made sure the axis was not at the world origin, the problem was resolved. Can anyone confirm? (at least it might be a workaround until the bug is fixed) yeah, that worked for me after a couple of...

^ yeah, i guess you're right.. i am getting the visual update so that's cool.
the non_resetting clock was scaring me though :D

i've seen this behavior in the last few builds : i don't think the 'Update Image' button is working anymore.. I used to be able to click it and the image would update visually and the 'next image update in' clock would also reset itself.. previously, if i had a render going overnight, in the morning...

I would suggest to rather make the scene the correct scale, than to try and fix it by making the camera tiny - this is because other materials (like glass) expect the world to be in units of metres (it looks here like centimetres). nah, it's probably properly scaled.. you can't (easily) draw small ...

Whaat wrote:I appreciate the error reports guys but I really need a SKP file for testing. I have not been able to reproduce this bug myself.

here's a .skp with the trouble area isolated.. render as is and you'll see the error..
thanks

SU on mac doesn't have the 1024 limit.. i think it's more like 2048.. Is this really a platform dependent limit? I only read about the 1024 px until today... you know, now that i think about it, think this was changed in su8 (or was it 7?) there's now a pref for 'use maximum texture size' which i b...

in the skindigo render settings under 'camera', choose autofocus and select a smaller aperture (higher value).. something in the f/16 - f/128 range then click apply.. you might have your default settings saved with the shallow dof so you might want to do a 'save defaults' with the small aperture and...