Page 2 of 3

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 11:55 am
by FarbigeWelt
B.Y.O.B. wrote: Mon Mar 25, 2019 9:01 am Can you upload the scene?
It shoul be in my first post as 7z File.

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 12:00 pm
by sanjinms
B.Y.O.B. wrote: Mon Mar 25, 2019 11:55 am So you probably ran out of (GPU) memory?
Hmm...I use I7(7th), 16gb of ram and GeForce 1070(8gb vram)

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 12:10 pm
by B.Y.O.B.
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.

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 12:15 pm
by B.Y.O.B.
FarbigeWelt wrote: Mon Mar 25, 2019 11:55 am
B.Y.O.B. wrote: Mon Mar 25, 2019 9:01 am Can you upload the scene?
It shoul be in my first post as 7z File.
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

Posted: Mon Mar 25, 2019 12:17 pm
by sanjinms
B.Y.O.B. wrote: Mon Mar 25, 2019 12:10 pm 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.
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.

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 3:00 pm
by FarbigeWelt
B.Y.O.B. wrote: Mon Mar 25, 2019 12:15 pm Anyway, you can fix the problem by moving the texture in the Z direction (lower left):
😎 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

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 3:02 pm
by B.Y.O.B.
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.

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 4:44 pm
by FarbigeWelt
B.Y.O.B. wrote: Mon Mar 25, 2019 3:02 pm In a fresh scene. in a normal scene.
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.)

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 5:12 pm
by B.Y.O.B.
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?
No, this should also work on materials saved with older versions.

Re: LuxCoreRender v2.2alpha1 released

Posted: Mon Mar 25, 2019 5:31 pm
by pepe
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.