LuxRender 0.9-dev Windows build of 04-03-2012

[syndaryl]

Clearly I Did Something Wrong. Help?

Yeah, you didn't use 2.62 offical

With bmesh and other breaking api changes in the dev builds, I suggest you stick with the official for now.

Heh, for a while there the advice was the opposite: stop using the official and grab the latest from Graphical

Turns out a factory reset fixed it. This is my confusedly-grateful face I'm now cautiously setting up my defaults again to see if I can identify what made it go pear shaped - it might just be something old lurking in my settings that it was cranky about, or a conflict with another plugin. *shrug*

[SATtva]

There are only about 1 GiB out of 2 GiB RAM used so I think that's not the problem.

Is that a memory usage during scene loading, and Lux crashes before it's able to start rendering threads? This may mean 1 Gb is only used at scene parsing stage, but when Lux tries to allocate memory for SQBVH structure, it gets killed by the OS due to requesting more than available. Btw, does this happens under 64- or 32-bit OS?

If my assumptions are incorrect, you can report a bug in this thread. Uploading a minimalistic test scene which demonstrates the problem will help greatly.

[HoloFan]

I have tested it on two different machines (one 4 Gig/ Win 7 64-bit and one 2 Gig/Win 8 32bit) and the limit which is handled correctly is a resolution of 18. In that case the memory isn't anywhere near to full. So I posted in the other thread a short description and an example file.

Thanks for your help.

[SLKabaker]

Are there going to be any more Weekly Builds? It has been a month since the last. I am having serious problems with the Build from March 04, 2012. Especially those problems that were referenced in this thread. I know that the source has been updated, but for those of us who do not have the "tools" to compile the source in to a binary, it would be nice to have an updated build. Please let us know if the weeklies are no longer going to be published or if there is going to be a new release cycle (eg. Monthly, etc.)? Thank you.

[SATtva]

Sorry for the delay. We usually try to adhere to the weekly schedule, but can sometimes postpone the new builds due to real life/work interference or source instability (which is quite rare). Bidir still have some minor issues after light strategies introduction, but not a big deal. SQBVH is fixed indeed, no more missing polygons. I'll post Linux weeklies in a couple of days; i think Lord Crc will comment on Windows ones soon.

[Lord Crc]

Indeed, I was waiting to see if jeanphi had a fix handy for bidir, and got distracted by Real Life. I'll merge the new statistics stuff today and put up a weekly.

[jeanphi]

Hi,

Unfortunately not yet. I haven't had much time to work on it, so I'm planning to revert my latest code reorganization while keeping the new direct light sampling changes and pack things up for a RC.

Jeanphi

[Meelis]

Hi

My PC CPU has: MMX, SSE (1, 2, 3, 3S), EM64T

What's better for me from this 2 ?
LuxRender_CVS_20120304_64bit_NoOpenCL.exe
LuxRender_CVS_20120304_32bit_SSE2_NoOpenCL.exe

EDIT, forget it, i take 64bit

[SATtva]

jeanphi, that would be great!

Meelis, Lord's 64-bit builds already have SSE2 support if i'm not mistaken.

[SLKabaker]

I saw what jensverwiebe posted in the OSXIntel Weekly Forum about waiting another week or two. Is there anyway to get a current build for Windows 64Bit with OpenCL? It has been over a month already and these are weeklies, night RTMs. It is understood that they are "unfinished." However, I am unable to use LuxRender, completely! I keep having issues where it is either missing Polygons (Triangles) or LuxRender will Crash and/or both! This is happening with all my Renders. I completely understand Life getting busy and time flying but another two weeks where I cannot render at all - especially where the problem I am having has been fixed in the current source, seems like "torture!" Please post an updated build sooner, I beg of you. Thank you...