It shoul be in my first post as 7z File.
LuxCoreRender v2.2alpha1 released
- FarbigeWelt
- Donor
- Posts: 1046
- Joined: Sun Jul 01, 2018 12:07 pm
- Location: Switzerland
- Contact:
Re: LuxCoreRender v2.2alpha1 released
Light and Word designing Creator - www.farbigewelt.ch - aka quantenkristall || #luxcorerender
MacBook Air with M1
MacBook Air with M1
Re: LuxCoreRender v2.2alpha1 released
A texture of size 7000x5000px needs about 400 MiB of memory (assuming it has 3 channels).
You could check the RAM usage when you try to use it, and check how much your scene needs without this texture.
You could check the RAM usage when you try to use it, and check how much your scene needs without this texture.
Re: LuxCoreRender v2.2alpha1 released
Sorry, my bad, totally forgot that.
Anyway, you can fix the problem by moving the texture in the Z direction (lower left):
Re: LuxCoreRender v2.2alpha1 released
It happens even in startup empty scene even when I turn off openCL in both render settings and Imagepipeline. Of course, only if I using HighRes images.
- FarbigeWelt
- Donor
- Posts: 1046
- Joined: Sun Jul 01, 2018 12:07 pm
- Location: Switzerland
- Contact:
Re: LuxCoreRender v2.2alpha1 released
Thanks for this. I moved the objects away from 0,0,0 but did not think about to do it with local 3d mapping too.
Do you think this could be done internally a check against 0 and if true to move it automatically by a minimal offset? In my opinion the current behaviour of the software is not user friendly in borh cases:
- 3d position of objects
- 3d position of textire mapping
Because in both cases default is 0,0,0.
Regards
Light and Word designing Creator - www.farbigewelt.ch - aka quantenkristall || #luxcorerender
MacBook Air with M1
MacBook Air with M1
Re: LuxCoreRender v2.2alpha1 released
As I said in an earlier post, we already do this internally and I could not reproduce your problem in a fresh scene.
No idea what was wrong in your scene, maybe some excessive scale or something else? Anyway, it already works user-friendly in a normal scene.
No idea what was wrong in your scene, maybe some excessive scale or something else? Anyway, it already works user-friendly in a normal scene.
- FarbigeWelt
- Donor
- Posts: 1046
- Joined: Sun Jul 01, 2018 12:07 pm
- Location: Switzerland
- Contact:
Re: LuxCoreRender v2.2alpha1 released
It is meant to be a freah scene, but I imported materials from 2.2 a0. Maybe this is a reason for the ‚unusual‘ behaviour. Does this mean I have to materialize from scratch for every older scene to use it with version 2.2 alpha1?
If yes, well this is not a big issue. But one have to consider this.
(How ever for mass creation of materials a kind of table based parser would be nice idea.)
Light and Word designing Creator - www.farbigewelt.ch - aka quantenkristall || #luxcorerender
MacBook Air with M1
MacBook Air with M1
Re: LuxCoreRender v2.2alpha1 released
No, this should also work on materials saved with older versions.FarbigeWelt wrote: ↑Mon Mar 25, 2019 4:44 pm It is meant to be a freah scene, but I imported materials from 2.2 a0. Maybe this is a reason for the ‚unusual‘ behaviour. Does this mean I have to materialize from scratch for every older scene to use it with version 2.2 alpha1?
Re: LuxCoreRender v2.2alpha1 released
Any chance for a macos version?
I am contemplating future possibilities.
I guess the best os for blender and luxcore will be linux.
But what are the best price/performance hardware right now?
Edit
An i7 8700k with 32G of ram look like a good option.
I am contemplating future possibilities.
I guess the best os for blender and luxcore will be linux.
But what are the best price/performance hardware right now?
Edit
An i7 8700k with 32G of ram look like a good option.