Oscar J wrote:Nice kitchen!

Hey, is it possible to export light layer temperature/RGB values from your exporter yet?

working on it!

*Staying tuned* :) No news because moving my house at the moment and have much to do... like constructing the new kitchen. Using the new exporter works well with basic scenes and light layer under linux: kit1.jpg k2.png k3.jpg I hopefully get my new mac book in march so i can develop/test the expor...

Happy New Year! After some free days with my family i continue working on the new exporter. The UI implementation is nearly finished which means the implementation of all possible parameters are done. The big work will come when to sort,order and rearrange all the knobs and buttons into the right ta...

Sorry for long time no new posting: I am still busy at work but coding still goes on! Currently i have around 80% of the UI finished (implementing parameters, buttons ,knobs and so on). The C++ module for export works but i still fighting with different compilers on different plattforms (windows, li...

uhhh... roundabout three weeks no news?! ;-) here are some signs of life! I am back from holidays and a lot of work is on my desktop... i still coding on the new exporter and do some UI stuff at the moment but at the moment i do not have too much free time for coding. hopefully i have some more news...

Thank you for the input Oscar ;-) The screenshot is just a 'proof of concept' and was done by me to see if the code is working. The whole layout and where to put what is not yet started ;-) The 'clay buttons' was also a test to put elements into existing blender ui parts. Maybe in the future i will ...

the last week i was thinking about the whole 'UI python scripting' stuff and how to avoid using the 'extension framework' python module which is used by blendigo a lot. i don't want to use the framework because it is (afaik) not well maintained at the moment and there is no good documentation availa...

first full export seems to be working :

~11 Mio. Vertices / ~ 11,6 Mio Quads / Export Time: ~39,5sec (instead of 55 secs with blendigo 3) / File size ~668MB

enough for this week ...

progress update 1: "Dear little diary...." :-D the last week was full of surprises. Much surprises coming from boost::python and my rusty c++ coding experiences and i am also was struggling with igmesh format version 3 a little bit and how to pass all the data in 'a good' way to 'the extension' from...

Hi, i wrote already i am trying to do a new (mesh)-exporter as a python extension in C++ for blender. Because this is a complete new approach i am starting this new topic instead to post my progress at the 'blendigo topic'... Until now there is not too much happened: I am still doing some software a...

Hi, after thinking about what to do next i have an idea what i am doing now. First step is a kind of a blendigo re-write. Because there are big changes in the code base i can not guarantee that the code will be compatible to the current blendigo code. We will see (maybe it becomes a fork). i don't k...

crazy and amazing! very nice! btw.: thank you for the shot

Oscar J wrote:Nothing like some good ol' paragliding to clear your mind.

Exactly! like my club mate: http://xc.dhv.de/xc/modules/leonardo/in ... tID=680265 he is now so relaxed after >150km *hohohooho*

hmmmm... maybe,maybe not. who knows .... i think i should free my mind from the current blendigo code and think about a new approach.... will free my mind at the weekend with paragliding and do some 'architecture summit' after the weekend.... maybe i will come with new ideas

So much exciting stuff to code! :-) some words about my progress on blendigo... blendigo is well coded and overall it is done very clever in some way... but ;-) i found some strangeness inside the code (e.g. class handling, duplicated code and so on...) which makes it hard to me to extend blendigo ...