Included in the drive is the full model and the "testing" model which is where the images come from Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.Ĭreated 31 Jul, 2020 Issue #530 User Matthewv1998
They should be regular Python member variables instead. To me, it looks like neither is the case for many of the members in the LOL file. blend file, or need to be exposed for Blender's operator API. Many of the Properties in these groups should not be properties in the first place: Properties should only be used for variables that either need to be serialized and saved in the. The file properties/lol/LuxCoreOLScene.py contains several PropertyGroups that are used by LOL. Thanks to git, deleted code is never lost. There's a lot of disabled (commented) code - please enable and use, or delete. I would propose to create downscaled versions and only load those into Blender. The main problem seems to be that the thumbnails are 1080x1080 pixels in original size, although they are never shown that large. In my Image Node Preview addon, I can store 100 thumbnails of similar display size in 25.6 MiB. So the asset bar thumbnails need about 1.4 GB of GPU memory, when all of them are loaded. After opening the asset bar and scrolling through all model and material asset once (so all thumbnails were shown), a usage of 1.7 GB is reported.With Blender open, 0.3 GB usage are reported (so Blender uses about 0.1 GB).Created 25 Jul, 2020 Issue #522 User Theverat