Page 1 of 5 123 ... LastLast
Results 1 to 20 of 82
  1. #1
    Member J_the_Ninja's Avatar
    Join Date
    Sep 2010
    Location
    Portland, OR, USA
    Posts
    1,062

    LuxRender 1.2 Released!

    EDIT: v1.2.1 is out. It's at the same download page:

    ________________

    Download link: http://www.luxrender.net/en_GB/standalone

    Official release notes: http://www.luxrender.net/forum/viewt...p=92975#p92975

    Originally Posted by jeanphi
    Hi all,


    Here we are again with a new stable release of LuxRender featuring lots of bug fixes. You are strongly advised to upgrade to this 1.2 version due to the huge improvements in the correctness of the renders in this release. See below for the list of improvements.
    Many thanks to all the developers involved in this development cycle, this is going to be a strong base to add the next features like full GPU acceleration. If you have questions, do ask them in our forums, and if you find bugs or want to suggest improvements, do so in our bug tracker so that they don't get forgotten..


    The splash screen has been changed to the one submitted by Piita for the v1.0 contest, it finished almost at a draw with the winner, congratulations to him.


    Packages or installers for most platforms have been made available from our downloads page. Some exporters have been packaged in the installers depending on the platform, otherwise you'll be able to get them from the download page or the repositories.


    Changes since v1.2RC1:
    - fix a memory leak in the GUI
    - fix display of .flm statistics
    - fix rendering artefacts when the scene is very small
    - fix for incorrect rendering of environment lights with large black areas
    - fix for severe regression introduced in bidirectional rendering when optimizing dispersion code
    - fix a long standing bug in bidirectional which made renders with bidirectional appear darker than with path
    - fix lots of issues with hybrid path rendering, it should now match normal path rendering
    - fix wavelength mutation in metropolis
    - fix for image filters having a width less than 0.5
    - removed the annoying message box when loading a queue file
    - fix display of negative numbers in statistics
    - lots of fixes for SLG3


    Other changes since v1.1:
    - hybrid rendering modes are now available even on non OpenCL builds
    - SLG bidirectional implementation with vertex merging or hybrid mode
    - fixes to SLG sun light
    - fixes to bounding boxes causing instances objects to sometime disappear or be clipped
    - tile rendering with SLG
    - more advanced GPU memory management with SLG
    - SLG core is now a library
    - port of some more Lux features to SLG core
    - user driven sampling and noise aware sampling (still experimental with bidir and metropolis combination)
    - all scenes rendered are now added to the queue so you don't have to choose between single render and batch rendering
    - improved queue handling
    - fix dispersion using SPPM rendering
    - new woven cloth material
    - WARNING: backward compatibility break: the displacement direction when using loop subdivision has been reversed to match general expectations and to be consistent with microdisplacement or bump mapping
    - improved dispersion handling with path and bidir
    - much faster bloom filter
    - fix a memory leak that could be dramatic when using hybrid rendering
    - fix for projector light not applying transforms correctly


    In LuxBlend25 since v1.2RC1:
    - improved smoke support including fire (with path integrator)
    - fix for lights in dupligroups
    - many tweaks to sanitize the UI and improve usability
    - adapt to Blender 2.66
    - proper export of render layer visibility (NOTE: first render layer only)
    - proper motion blur export (motion blur from drivers, constraints, parents, etc should "just work")
    - material preview improvements (should render out faster)
    - metaballs export


    In LuxBlend25 other changes since v1.1:
    - improved preview
    - add new LuxRender features
    - be compatible with Blender 2.65 (not backward compatible)
    - primitive proxy support to allow exporting of more LuxRender native shapes like spheres, cylinders, ...


    ---------------------------


    Source Code


    People who want to download the source code can download the v12 tag files of our HG source code repository here:
    Lux: http://src.luxrender.net/lux/file/ee0b9ff73d62
    LuxRays: http://src.luxrender.net/luxrays/file/475fbf15f0ca


    LuxBlend (2.66): http://src.luxrender.net/luxblend25/file/3b84c4d3f009


    ---------------------------


    Cheers,


    Jeanphi
    If you've been having glitches with the material panel in 2.66, this should fix those. Happy rendering!
    Last edited by J_the_Ninja; 18-Mar-13 at 15:42.



  2. #2
    Member ohsnapitsjoel's Avatar
    Join Date
    Nov 2010
    Location
    Cincinnati
    Posts
    1,513
    yay! cool, thanks to the devs!
    Joel's Artventures in Digital Media
    My Blender addons - some may be useful to you, others probably won't
    I use too many emoticons.



  3. #3
    Member Ace Dragon's Avatar
    Join Date
    Feb 2006
    Location
    Wichita Kansas (USA)
    Posts
    21,337
    Seems like the Luxrender development is going well as far as features and light simulation is concerned.

    Though what concerns me is that there's still a number of WIP threads on the Luxrender forums where it's around the artist struggling to get clean renders with parts of an image rather than getting excellent results and proceeding to add more to it. It really does seem like that there's some people who give the impression that you need to fiddle with the settings and/or fight with the engine before you get something that really stands out.

    Of course I've seen plenty of clean images, but the majority of them are built simply to play with the light physics rather than create a full environment. (ie. making an image catering to Lux's strong points).
    Sweet Dragon dreams, lovely Dragon kisses, gorgeous Dragon hugs. How sweet would life be to romp with Dragons, teasing you with their fire and you being in their games, perhaps they can even turn you into one as well.
    Need Cycles materials / node setups: Get them here



  4. #4
    Member Kemmler's Avatar
    Join Date
    Mar 2007
    Location
    USA
    Posts
    1,038
    That's true, but that's an issue with most engines AFAIK. Cycles certainly has that problem.



  5. #5
    Member
    Join Date
    Apr 2012
    Location
    Australia
    Posts
    411
    Luxrender can be hard to use but you need to read the manual/wiki and at least try and experiment/understand for yourself.


    Some people have the sort of opinion that it's a light simulator and for that reason everything should be built to real and expect it to work, IE "I can throw anything at it and it will come through clean after 6 hours".

    No, actually though you've really got to think what you're doing as much if not more than any other renderer.
    You can't make layers behind layers of glass with dispersion enabled behind another layer of frosted glass, stick a 1000 triangle light behind that and expect it to produce acceptable results in acceptable time.

    Relative to other "simpler" (subjective) renderers, Lux struggles with glass surfaces, IMO this is a source of a lot of noisy renders.

    Eventually when VCM starts being integrated we might see a big change. Not only by being able to more effectively sample glass and diffuse materials at same time, but afaik the mode should be a more robust/versatile default in comparison with bidirectional. Currently it is, as you say, often necessary to tweak/fight the render method and settings to fit the scene, or to build the scene with the render method in mind which is of-course not fun for new users.



  6. #6
    Member J_the_Ninja's Avatar
    Join Date
    Sep 2010
    Location
    Portland, OR, USA
    Posts
    1,062
    Originally Posted by Rhys View Post
    Some people have the sort of opinion that it's a light simulator and for that reason everything should be built to real and expect it to work, IE "I can throw anything at it and it will come through clean after 6 hours".

    No, actually though you've really got to think what you're doing as much if not more than any other renderer.
    You can't make layers behind layers of glass with dispersion enabled behind another layer of frosted glass, stick a 1000 triangle light behind that and expect it to produce acceptable results in acceptable time.
    This sort of thing is by the far the biggest culprit of people struggling with Lux, and it's also where the 5 day long renders come from. An engine like Lux makes people think the old rendering/comp maxim of "It doesn't have to BE right, it has to LOOK right" no longer applies. That's not true, an unbiased renderer is just another tool to make things look right without so much fiddling with arbitrary properties. When designing a render engine, there's a balance between "fast, but takes work to get good results" and "gets good results, but takes work to do it quickly. A physical/unbiased renderer shoves that slider as far as it will go towards the latter.

    If you want fast results out of them, you need to pay attention to what exactly you are throwing at it: Do you really need bounce light from the sun off the floor to illuminate this room, or can you shove a fill area light behind the camera? Is multiple scattering on that candle that takes up 35 pixels REALLY necessary? If you disable dispersion on this, is anyone going to actually notice? Can you fake that sunbeam in post? Is the 10000x5000 HDRI REALLY necessary, or can you just replace the background later?



  7. #7
    Member Carrozza's Avatar
    Join Date
    Feb 2008
    Location
    Italy
    Posts
    1,229
    Clever comments, Rhys and J_the_Ninja.
    But, starting from the fact that a good faking knowledge does help, would you still advise Luxrender over Cycles?
    I'm not trying to flame or anything, I'm just a curious hobbyist user trying to get te most out of his limited spare time.
    Thanks for any hint, and keep up the good work Lux team!



  8. #8
    Member
    Join Date
    Feb 2012
    Posts
    1,791
    Those are totaly diffrent engines.

    generaly it is like that.

    luxrender - can give some awesome images but you it will take a lot of time to render and setup materials etc lights.
    cycles - if faster but you have to know exacly what you are doing, it is more flexible as well.
    vray - cost quite a while for that price you can make cycles buying hardware incredible fast. Or you can buy the best rendering engine on market
    Last edited by Kramon; 25-Feb-13 at 06:49.



  9. #9
    Originally Posted by Carrozza View Post
    But, starting from the fact that a good faking knowledge does help, would you still advise Luxrender over Cycles?
    Would you advise a SUV over a sedan car? Without knowing more, you can't answer. They fit different purpose, each one has its strengths and weaknesses.
    Regarding the LuxRender UI for materials, I hope that things will be able to improve with the opening of the nodes API in Blender.



  10. #10
    Originally Posted by Kramon View Post
    luxrender - can give some awesome images but you it will take a lot of time to render and setup materials etc lights.
    cycles - if faster but you have to know exacly what you are doing, it is more flexible as well.
    yafaray - cost quite a while for that price you can make cycles buying hardware incredible fast. Or you can buy the best rendering engine on market
    I'd say Cycles is much more tightly integrated within Blender and has a wider support of Blender features while LuxRender has more advanced rendering algorithms and is much more focused on physical correctness. Regarding speed, it's not a clear cut, there are many scenes that would render faster with LuxRender than Cycles, it all depends on the setup, and Lux will soon have a full GPU renderer.
    I think you typed yafaray but had something else in mind because yafaray is free and open source too.



  11. #11
    Member Carrozza's Avatar
    Join Date
    Feb 2008
    Location
    Italy
    Posts
    1,229
    Originally Posted by jeanphi_ View Post
    Would you advise a SUV over a sedan car? Without knowing more, you can't answer. They fit different purpose, each one has its strengths and weaknesses.
    Regarding the LuxRender UI for materials, I hope that things will be able to improve with the opening of the nodes API in Blender.
    What the different purposes? Animation for Cycles VS still pictures for LuxRender?
    OK, let's talk about still pictures alone: could you please try to summarize the strenghts and weaknesses of the two?
    Thanks in advance for your help!



  12. #12
    Member
    Join Date
    Feb 2012
    Posts
    1,791
    Originally Posted by jeanphi_ View Post
    I'd say Cycles is much more tightly integrated within Blender and has a wider support of Blender features while LuxRender has more advanced rendering algorithms and is much more focused on physical correctness. Regarding speed, it's not a clear cut, there are many scenes that would render faster with LuxRender than Cycles, it all depends on the setup, and Lux will soon have a full GPU renderer.
    I think you typed yafaray but had something else in mind because yafaray is free and open source too.

    damn i mean vray..



  13. #13
    Just look at my previous post. LuxRender will give you a result comparable to a picture taken of the setup in real life and it has a set of very powerful algorithms to do so. Cycles will make special effects easier, it allows to cheat with completely unrealistic lighting situations. That might or might not be what you want.
    When using LuxRender you need to have the mindset of a photographer in real life (with some added possibilities), with Cycles you can keep the mindset of a more traditional 3D CG artist.
    Both are great tools in my opinion, they are both quite versatile and I think you really need to see by yourself which one best suits your needs.



  14. #14
    Member
    Join Date
    Feb 2012
    Posts
    1,791
    Originally Posted by jeanphi_ View Post
    Just look at my previous post. LuxRender will give you a result comparable to a picture taken of the setup in real life and it has a set of very powerful algorithms to do so. Cycles will make special effects easier, it allows to cheat with completely unrealistic lighting situations. That might or might not be what you want.
    When using LuxRender you need to have the mindset of a photographer in real life (with some added possibilities), with Cycles you can keep the mindset of a more traditional 3D CG artist.
    Both are great tools in my opinion, they are both quite versatile and I think you really need to see by yourself which one best suits your needs.
    i like luxrender because i made some works in it. It is as you say easy to setup. i am waiting for nodes.. or some new way of creating materials because now it is quite bad...



  15. #15
    Member Carrozza's Avatar
    Join Date
    Feb 2008
    Location
    Italy
    Posts
    1,229
    Fair enough: I don't have the knowledge nor the time to become a photographer, so I guess it's a better bet to try and understand Cycles and cheat my way to a decent - whilst not physically accurate - picture.
    Just to be understood, the main purpose I use Blender for is to make some architectural visualization shots, mainly interiors.
    Cheers!



  16. #16
    Member NinthJake's Avatar
    Join Date
    May 2009
    Location
    Sweden
    Posts
    1,928
    Originally Posted by Kramon View Post
    vray - cost quite a while for that price you can make cycles buying hardware incredible fast. Or you can buy the best rendering engine on market
    Though just as with Cycles and Luxrender you have to know exactly what you are doing to get a good result with Vray, which is why really good Vray users are so valuable on the market.

    I don't think that any render engine is just "jump-in-and-go" friendly. You gotta know which settings to use or you will have to wait forever to get good results or settle with less quality, and that is true for all renderers.

    To the Luxrender team:
    Congratulations on the new release!

    This one looks amazing just as all the other releases, will take some time to play with it as soon as I can



  17. #17
    Member Carrozza's Avatar
    Join Date
    Feb 2008
    Location
    Italy
    Posts
    1,229
    About Vray, I have to say that I demoed it once, and found it really, really impressive: might not be perfect, but the most "jump-in-and-go" rendering engine I can think of.



  18. #18
    Member NinthJake's Avatar
    Join Date
    May 2009
    Location
    Sweden
    Posts
    1,928
    I use Vray often and you gotta try to render more complex scenes before you can say that it is "jump-in-and-go" friendly. If you don't have the right settings when rendering a high-resolution image with a lot of complex materials and light portals and other tricks you will watch Valve release the third installment of all their games before your render is finished (in other words, the world will end before it's done)

    Even if you are just rendering an extremely simple scene with Vray (a monkey head in a box) you can set up the render settings so that it renders a really fast clay render but add one simple texture to the ground and it will immediately take 4x longer to render if you don't adjust the settings accordingly. Now I'm not claiming to be a professional Vray user or anything (far from it), I am reading the manual almost daily and I still learn something new all the time, I probably haven't even explored 20% of the vast ocean that is Vray.

    I got to say that Cycles is probably the most user-friendly render engine I have ever used and the one I would personally say is the easiest to learn



  19. #19
    Member
    Join Date
    Apr 2012
    Location
    Australia
    Posts
    411
    Luxrender vs cycles, I would consider it a workflow choice.
    They both can make good stuff but have very different way about it.



  20. #20
    Member daveleitz's Avatar
    Join Date
    Feb 2011
    Location
    Alabama
    Posts
    260
    Great! Downloading now!

    I'm glad that memory leak got fixed. I look forward to being able to use material nodes for Luxrender in the future. As for Cycles vs. Lux? Why not both! Both keep getting better. I mostly use Cycles right now, but I still spend some time learning and testing Lux too. It's the best of both worlds.



Page 1 of 5 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •