BlendLuxCore Development

Discussion related to the Engine functionality, implementations and API.
User avatar
B.Y.O.B.
Developer
Posts: 3017
Joined: Mon Dec 04, 2017 10:08 pm
Location: Germany
Contact:

Re: BlendLuxCore Development

Post by B.Y.O.B. » Tue Sep 24, 2019 4:05 pm

Yes, the Blender devs removed it.
neo2068 moved the hemi options into the sun light menu, you have to change the sun type to "hemi" to see them.
Support LuxCoreRender project with salts and bounties

Eneen
Posts: 1
Joined: Fri Mar 16, 2018 4:48 pm

Re: BlendLuxCore Development

Post by Eneen » Wed Nov 06, 2019 8:10 am

I'll grab proxy topic...
lacilaci wrote:
Tue Sep 25, 2018 7:06 am
Well random vertices is good enough. As long as they are distributed evenly around the whole volume, not based on mesh density. Which was a problem in first versions of vray proxy display in max afaik. Where, for example, since trees have more polys where leaves are, vertex/cloud display picked those vertices at first so you had to request very big amount of display vertices to see where trunk is placed.
As @lacilaci said problem with point cloud based on vertices is you can't actually see where triangles are, so medium-poly and low-poly objects are just mess and you can't see actual object shape. Besides it requires special rendering and coding. That's why suggested very simple solution from indigo render, where you have proxy linked to mesh, not object. This solution has some neat advantages:
- it doesn't require any coding of proxy display
- it's extremely fast as blender loads only manually decimated mesh, not full one and generating view
- after heavy decimation blender leaves edges on hi-poly objects, this looks really good on trees (screen attached)
- you can precisely decimate original mesh so it can even cast shadows
- you actually see where geometry is so it's way easier to put stuff into scene and avoid collisions
- you can use any geometry like billboarded view of tree using 6 triangles and get proxy display

proxy_display.jpg

This one is still heavy to display (10% of faces), but I keep both meshes inside external blend file so I can generate both original proxy and have decimated one. It requires a bit of work, but considering creation of whole asset it's very little.

Link to github issue: https://github.com/LuxCoreRender/BlendL ... issues/110

User avatar
epilectrolytics
Donor
Posts: 605
Joined: Thu Oct 04, 2018 6:06 am

Re: BlendLuxCore Development

Post by epilectrolytics » Tue Nov 19, 2019 11:31 am

Apparently certain Intel libraries handicap AMD, especially Ryzen Processors by not utilizing certain implemented accelerators.
This pertains also for NumPy. I don't understand anything about coding, but isn't this a part of Blender / LuxCore too?
Some peeps have noticed and develop workarounds (sorry for links in german language):
https://www.computerbase.de/2019-11/mkl ... amd-ryzen/
https://www.pugetsystems.com/labs/hpc/A ... BLAS-1560/
https://www.computerbase.de/forum/threa ... h.1906201/
MBPro 15" 16GB i7-4850HQ GT750M, MacOS 10.13.6 & Win10Pro PC 16GB Ryzen 2700X, 2 x RTX 2070

User avatar
Dade
Developer
Posts: 3402
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: BlendLuxCore Development

Post by Dade » Tue Nov 19, 2019 12:21 pm

epilectrolytics wrote:
Tue Nov 19, 2019 11:31 am
I don't understand anything about coding, but isn't this a part of Blender / LuxCore too?
It is used only by BlendLuxCore to format the exported data in a suitable layout, it is not used by LuxCore and not involved in anyway in the rendering process.
Support LuxCoreRender project with salts and bounties

User avatar
epilectrolytics
Donor
Posts: 605
Joined: Thu Oct 04, 2018 6:06 am

Re: BlendLuxCore Development

Post by epilectrolytics » Tue Nov 19, 2019 1:24 pm

Good to know, thanks! :D
MBPro 15" 16GB i7-4850HQ GT750M, MacOS 10.13.6 & Win10Pro PC 16GB Ryzen 2700X, 2 x RTX 2070

Post Reply