OSXintel_64bit_ LuxRender-0.9_weekly_april_06_2012

[Synthercat]

LOL! snow leopards indeed!

One week ago I lost the best of my 2 cats but at least I still got a cat purrring (besides my wife! ) when I get home

[jensverwiebe]

updated 26.01.2010

Jens

[jensverwiebe]

BUMP - for the blind

Jens

[jensverwiebe]

Bump for the new OSXintel_64bit_ LuxRender-0.7_weekly_jan_30_2010, see first post.

Jens

[SurfingAlien]

Thank you Jens!

I see you mention a crash on OSX in the changelog... I have Lux (0.6.1) crashing quite often when I save FLMs (but the file is saved before the app quits). Don't mind that much at the moment 'cause it's all about small test files (and I don't even know if I changed the settings in LuxBlend to be able to resume the rendering...); it's probably me and not Lux (I've such a short time to play with it at the moment! ... still have to get the basics), but if you wanna take a look into I can send you the .blend file and the crash report... let me know.

cheers,
Alessandro

[jensverwiebe]

hi Alien

No thx atm, this crash on saving flm looks like a wx-bug to me + it is occuring rare and really not reproducable.
I can save flm 10 times without probs, then it crashes.
Due wx 2.9 is alpha, again let´s ignore this for now and examine the saving in QT GUI when finished.( Or just now with the test app )

In the meantime i recomment to save flm out of a stopped render ( so timers are stopped )

There did not happen so much OSX testing, for i was mostly alone on that, so i have no widely compared between
32bit ( wx 2.8 ) 64bit ( wx 2.9 , btw now in 0.6.1a a good half your evolved again ) and QT.

Any observations about that are very welcome.
Personally i use mostly the 64bit in stress-work and found it mostly rockstable.

Jens

[jensverwiebe]

Bump for weekly ---> OSXintel_64bit_LuxRender-0.7_weekly_feb_05_2010

Jens

[the3dcie]

Thanks a lot for your weekly builds, downloading the new one right now !

However, it's probably due to the nature of those weekly builds (developer previews...) but i have a scene i use to test the render engine which takes 9+ GB of RAM with 0.7_30_Jan_2010 when it takes only 3.5 GB with 0.6.1a !
I haven't tested this new one but i'll do that right now.

In the meantime, is this the way it's supposed to work ?
I have right now "only" 4GB on my iMac and this scene with 0.7 is putting it to its knees !
Too bad actually as 0.7 doesn't seem to suffer the same "overbright HDRI" 0.6.1a is facing.

Sorry, i digress, thanks again for the weekly builds and for the hard work of anyone involved in this marvelous project.


Cheers,
Laurent aka Tartiflette

[jensverwiebe]

Regarding the memory, have no idea atm, there is so much new stuff to observe and i mostly check this all alone ( for OSX ), haven´t
looked for changes in memusage. Will set it on my list of todo´s

So far a small test ( luxball):

17614 LuxRender-0.6.1 jensverwiebe 0,2 9 108,1 MB 184,6 MB 208,7 MB Intel (64-Bit)
17627 LuxRender0.7dev jensverwiebe 0,2 9 134,7 MB 241,7 MB 255,7 MB Intel (64-Bit)

..not much but obvious difference in memory-print.
We will keep this in mind.

Be aware: developer-version is not meant for production, do at your own risk.


Jens

[the3dcie]

Regarding the memory, have no idea atm, there is so much new stuff to observe and i mostly check this all alone, haven´t
looked for changes in memusage. Will set it on my list of todo´s


Jens

Great, thanks a lot for the fast reply !
Regarding the new build, it seems a little bit less than the one from January 30th, but it's still in the 8+ GB area, so still more than 2x the memory footprint of 0.6.1a with the same scene. (well amost the same as one is saved with 0.6.1 exporter while the other is saved with 0.7dev exporter, but you get the idea ! )


Cheers,
Laurent aka Tartiflette