Ok !! Thanks to both of you (Soory for the translation !!)

if you select open and un-check "always ..." still has the problem ? usually this appears when MIME setup is wrong

I took a look in the model.options list, and nothing there looks promising (I didn't expect it to, since what you want aren't really model options. If I have a chance, I'll do some more checking tomorrow, but I don't expect positive results...

You are right, It destroys my faces... well it splits them into triangles but they stay planar... so I just have to delete the created lines manually. I can live with that But the bad thing is that rounding coordinates does not solve the problem I have... It seems to be a known bug! It happens with complex models when you often change the axes with the axis tool. I need some way to re-align edges to the axes (even their start and end-points are (almost) exactly on one axis, they are not recognised so)

thanks also remus!!

Observers.... I've never used these tools... I will try Thank you Rick !

Thanks! Meanwhile, I am collecting the suggestions...

Thank you Alex.

thanks Fred06! I'll try that!

Basically, the paths work like this: The camera will be set up at each vertex on the camera path. So, if you have 23 edges in the path curve, there will be 24 camera positions (one per vertex). If the target path has the same number of vertices as the camera path, the target will be at each vertex. Otherwise, the target point will be interpolated along the path so that there are the same number of target points as camera points. For example, if the target path had only 3 edges (4 vertices), the whole path length would be divided mathematically into 23 equal segment lengths, and the target points would be set at equal distances along the 3 edges. Hope that makes sense...

Lapx, that is great. That is what I want. By the way I just bought today the subdivide & smooth script. Haven't had the time to experiment with it yet. With best regards PRSS

Still trying...

Let's see theses links http://www.crai.archi.fr/RubyLibraryDepot/Ruby/Newest_scripts.html try to find : Lens_correction.rb ( thanks to the author) or with an external program ( to perform before using SketchUp ) http://research.graphicon.ru/image-processing/gml-image-undistorter-2.html or this one ( but limited in use ) http://www.epaperpress.com/ptlens/ MALAISE friendly

Thank you Terry for sharing theses plugins New ideas may come from theses curves

Ahh.. and there's no way to hack it together? Doesn't LightUp do kind off the same thing in flight mode? (I'm not sure as I've never used it before though). Thank you!

Just tried it and no problem, http://smustard.com/ Mike

Cool, thanks!

@adamb said: @jorgensen said: Is the light included when one export as AVI ? Exporting movies from LightUp sounds like a useful feature for a future version though. Its all very well you guys coming up with great ideas to improve LightUp, but I'm the one that has to write the code! Anyhow, its done. For the retail version of LightUp you can now press Shift+return in Tourtool mode and it will save frame sequences in realtime which you can crunch down into a movie with Cinepac/mencoder or whatever. Also fixed a bug in the current demo of LightUp (v1.1c) that prevented looping Animation working while in Tourtool, so that will be in the next release (v1.2a) Adam

Fortunately Smustard has the MySmustard plugin to help one track updates to their scripts, to me this already works like a validation system of sorts, kinda moot as a pure validation system for Smustard ATM since you get the scripts from Smustard in the first place. It's the idea that counts, a master data register of the scripts out there and SU checks it (MD5 checksums verification on the server database would help) everytime it starts up, maybe even report new scripts and analyse them in a kind of SAFE MODE before running them. I suppose it doesn't help people much that use SU offline, thus some kind of encrypted database file (with the MD5 checksums) distributed with SU for validation purposes would probably help as well. Should be easily updatable and probably wouldn't be a space hog.

Documentation error. Page.layers should logically return an array of layer objects rather than the layers parent object, and it does. Just one of those cut-paste-forgot-to-edit errors, most likely.