Results 1 to 5 of 5

Thread: 2015 renderer for 2018

  1. #1

    2015 renderer for 2018

    Bring back the 2015 renderer in 2018 as an optional renderer.

    No, it's not a joke. It's a real request.

    https://forums.newtek.com/showthread...72#post1549372

  2. #2
    Registered User 3dhotshot's Avatar
    Join Date
    Mar 2009
    Location
    Durban
    Posts
    99
    In my opinion I think 2015 is heavily coded on Image based lighting and is close to mimicking real world photography / photorealism
    less calculations more accurate on some instances and 2018 has different algorithm that is now doing more calculation
    type emulation hence using more resources to achieve realism closer to modo render algorithm and octane style output.

    This could be a valid point on some levels as Lightwave 2015 engine is still at the top of most packages in render quality even now,
    and developer should be maybe focusing more on combining octane render into LW core or they could off added the new 2018 PBR engine as separate Render engine inside of LW whilst keeping the 2015 engine as base mode untouched. ( 2 amazing renders but separate )

    Then give the user a second render option to activate the NEW PBR algorthim so not to upset people who would like 2015 output untouched as it was in 2015, but giving them the option to choose between the 2 engine outputs ( 2015 / 2018 )

    who knows what plans are for the future or reasons they have ............
    Last edited by 3dhotshot; 07-26-2018 at 03:19 AM.
    Behance / YouTube AMD 1.9Ghz Dual Potato Core Laptop

  3. #3
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,279
    +1. old render engine with nodes still has its uses

  4. #4

    already posted here >
    https://forums.newtek.com/showthread...derer-for-2018

    +1. old render engine with nodes still has its uses
    agree, however moving forward is important, and the new 2018 Render engine pretty much does just that.
    if anything, it would be smarter to make the 2018 engine optionally work more like the 2015 engine.

    like mentioned in the other thread, you can't simply add the 2015 render engine back, without adding tons of code/time.

    the 3rd and best option, imo, is to continue improving the 2018 render engine.
    Last edited by erikals; 08-11-2018 at 10:59 AM.
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  5. #5
    Super Member JohnMarchant's Avatar
    Join Date
    Mar 2003
    Location
    Murcia, Spain
    Posts
    2,764
    I have to agree with erikals, onwards and upwards. I think its more about how the renderer works in 2018 than having 2015 renderer back. I only really use 2015 for modeling and baking some procedural and node stuff that is not available in 2018. Once thats done and i have the texutres baked its back to 2018 renderer. I would however like some of the options we had with lighting in 2015 back in 2018.

    Oh and if one more person says "oh but its not real world" i will bust a nut, i dont always deal in the real world and the way its supposed to look. Celshading is not real world at all but we use it as well.
    Dell XPS 15
    15.6-inch (3840 x 2160) 4K 282ppi IPS LCD
    Intel i7 7700HQ 2.8GHz
    Windows 10 64Bit
    NVidia GeForce GTX 1050 Ti
    1TB SDD
    32Gb Ram

    LightWave 2018.4

    Very nice Laptop

Bookmarks

Posting Permissions

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