LuxCoreRender Project wants you!

Discussion related to the Engine functionality, implementations and API.
User avatar
Sharlybg
Supporting Users
Posts: 885
Joined: Mon Dec 04, 2017 10:11 pm
Location: Ivory Coast

Re: LuxCoreRender Project wants you!

Post by Sharlybg » Tue Jul 10, 2018 4:13 pm

Dade wrote:
Tue Jul 10, 2018 1:53 pm
One of the problems of current unit tests for LuxCore is that they far exceed the the max. time available on Travis-CI. Run all of them on an average machine, requires many hours. We would need a dedicate server to run the tests non stop but we are lacking one.

P.S. as end result, even if we have the unit tests we end to never run them :|
B.Y.O.B. wrote:
Mon Jul 09, 2018 9:41 pm
LuxCore has a lot of unit tests and BlendLuxCore only has a few, not sure if you mean those?
We should definitely expand the automated tests in BlendLuxCore, but I think the test framework has to be rewritten first, it's really clunky to use.

When I have time again I want to create a few more example scenes that will be available from the downloads page. With .blend file and LuxCore file fromat.
Don't really understand what the problem here :

1/ Is there urgent need for ready complet 3D scene ? blend file ? do size , complexity and nature matter ?

2/ What are the kind of requirement for theses hypothetic 3D scene ? interior / exterior /simple / complexe

3/ Is it for Developer and User ?

4/ what is the priority 3D scene or Tutorial ?

Believe me just want to understand and wanna help (even if i'm really busy). I can stop investing time and energy in other project and redirect it where it's really matter.
Support LuxCoreRender project with salts and bounties

Portfolio : https://www.behance.net/DRAVIA

User avatar
Dade
Developer
Posts: 1537
Joined: Mon Dec 04, 2017 8:36 pm

Re: LuxCoreRender Project wants you!

Post by Dade » Tue Jul 10, 2018 5:55 pm

Unit tests are an automatic testing procedure usually intended to verify the functional of a single feature (i.e. a single part of the source code). They are particular useful to catch regressions (i.e. bugs introduced with new features). They are supposed to be run at every commit of new source code.

Our problem is the lack of hardware resource to run the procedure (and the lack of man power for further development).
Support LuxCoreRender project with salts and bounties

User avatar
Sharlybg
Supporting Users
Posts: 885
Joined: Mon Dec 04, 2017 10:11 pm
Location: Ivory Coast

Re: LuxCoreRender Project wants you!

Post by Sharlybg » Wed Jul 11, 2018 10:20 pm

Dade wrote:
Tue Jul 10, 2018 5:55 pm
Unit tests are an automatic testing procedure usually intended to verify the functional of a single feature (i.e. a single part of the source code). They are particular useful to catch regressions (i.e. bugs introduced with new features). They are supposed to be run at every commit of new source code.

Our problem is the lack of hardware resource to run the procedure (and the lack of man power for further development).
Ah ok. It is a pretty tough situation. But sometime i wonder if it is not possible to promote luxcore but in real world. What do i mean ?

In countries like yours ( Italia / Deutschland / Russia ....etc) there are great universities where you can maybe find old friends or students that can accept to help an opensource project.

Or i am totally naive ....
Support LuxCoreRender project with salts and bounties

Portfolio : https://www.behance.net/DRAVIA

User avatar
FarbigeWelt
Posts: 362
Joined: Sun Jul 01, 2018 12:07 pm
Location: Switzerland
Contact:

Re: LuxCoreRender Project wants you!

Post by FarbigeWelt » Thu Jul 12, 2018 10:39 pm

B.Y.O.B. wrote:
Mon Jul 09, 2018 9:41 pm
and BlendLuxCore only has a few, not sure if you mean those?
Yes, to get back again to this topic, I did not mean unit tests, I know these are very useful, depending on how you code, you may have test methods for almost every method sometimed even for easy ones. And if there are many dependencies even a unit test for one method can get rather wide and fragile.

What I mean with test cases is closer to a step by step tutorial e.g. installation of luxcorerender blender addon from zip file or with preferences button "update". If different people on different pc setups (amd, Intel, nvidia) and OS versions follow this test case you can get a standardizable feedback from a variant environments. Real world testing is difficult to be replaced by automated scripts.
Microsoft Windows 10 Professional, intel i7 4770K, 32 GB, AMD R9 290x 4 GB, AMD R9 390x 8 GB
Instagrammer, please join #luxcorerender for your renderings.

irregexpr
Posts: 1
Joined: Fri Nov 16, 2018 4:12 am

Re: LuxCoreRender Project wants you!

Post by irregexpr » Mon Nov 19, 2018 2:10 am

Hello,

I'd like to help. I have a fair amount of development experience, and a Macbook. One thing I'm noticing is that there aren't any instructions for building on the mac and the MacOSCompile repo on github is empty. I see there is a mac alpha from september, but I was unable to open the Cornell box test scene with it.

User avatar
Dade
Developer
Posts: 1537
Joined: Mon Dec 04, 2017 8:36 pm

Re: LuxCoreRender Project wants you!

Post by Dade » Mon Nov 19, 2018 8:53 am

irregexpr wrote:
Mon Nov 19, 2018 2:10 am
I'd like to help. I have a fair amount of development experience, and a Macbook. One thing I'm noticing is that there aren't any instructions for building on the mac and the MacOSCompile repo on github is empty. I see there is a mac alpha from september, but I was unable to open the Cornell box test scene with it.
You are welcome, you should talk with Robbrown who is currently developing the MacOS port, the related thread is here: viewtopic.php?f=5&t=58
Support LuxCoreRender project with salts and bounties

robbrown
Developer
Posts: 49
Joined: Mon Sep 03, 2018 1:04 am

Re: LuxCoreRender Project wants you!

Post by robbrown » Tue Nov 20, 2018 5:52 pm

@irregexpr I'll send you a PM with some instructions. I haven't gotten to setting up the MacOSCompile yet, that'll be building scripts and bundling once I have that completed. Currently focused on some test failures trying not to put the cart before the horse.

Post Reply