Page 21 of 22

Re: Mac OS

Posted: Sun Feb 03, 2019 5:57 pm
by robbrown
Those are some nice compile times, maybe I should put my older smaller ATI Card back in. :lol:

Getting really tempted to ditch the Nvidia or stuff it in a Linux box with how Mojave and driver support aren’t happening.

Re: Mac OS, openCl

Posted: Sun Feb 03, 2019 6:25 pm
by FarbigeWelt
epilectrolytics wrote: Sun Feb 03, 2019 7:40 am Next try: Probably It's the 1GB GPU Ram vs 24GB CPU Ram that's causing the weird results of the former test.
Splonk! Bad guessed again. :lol:

902 kSps GPU openCL and CPU together
293 kSps GPU openCL only
688 kSps CPU only

Do you see the openCL values? They should be about 2 to 3 times the listed speed according to LuxMark.

geekbench 4
HD 5750 (1.0 TFLOPS SP 32 bit, theoretical :lol: )
17.3 Gflops SFFT (fast fourier transformation, 32 MB input buffer operating in 16 KB chunks)
core i7 870 55.5 Gflops SP 32 bit (multi core), 18.4 Gflops SP (single core)
19.0 Gflops SFFT (multi core), 4.70 Gflops SFFT (single core)

Speed of this graphic card depends probably much on task complexity.

Re: Mac OS

Posted: Sun Feb 03, 2019 8:39 pm
by Dade
Rob, we added Intel Oidn as new dependency, it is available like Embree from Intel https://openimagedenoise.github.io/downloads.html for MacOS so I hope it should be too much trouble.

Re: Mac OS

Posted: Mon Feb 04, 2019 3:00 am
by robbrown
Sounds good, just figured out my hotel charges by the day for WiFi and I’m here for 2 weeks. So may be getting creative with internet for cloning repos.

Re: Mac OS, openCl

Posted: Mon Feb 04, 2019 12:28 pm
by epilectrolytics
FarbigeWelt wrote: Sun Feb 03, 2019 6:25 pmSplonk! Bad guessed again. :lol:
OMG how could Epilectrolytics' distant diagnostics ever get this dismally defunct??
:shock: :oops: :lol:
I'll gonna spare us another try, also this doesn't belong in the developer section and you have already opened a new benchmark thread,
see ya!

Re: Mac OS, openCl

Posted: Mon Feb 04, 2019 1:29 pm
by FarbigeWelt
epilectrolytics wrote: Mon Feb 04, 2019 12:28 pmThis doesn't belong in the developer section and you have already opened a new benchmark thread,
see ya!
Sure, I partly.agree with you, was one reason to open the benchmark thread as a generic topic.

I provided these results as feedback for the reliability of LuxCoreBlender 2.1 plugin on OS X; but also because I think there is something wrong with its openCL implementation that would need development ressources.

Re: Mac OS, openCl

Posted: Mon Feb 04, 2019 1:45 pm
by epilectrolytics
FarbigeWelt wrote: Mon Feb 04, 2019 1:29 pmI think there is something wrong with its openCL implementation that would need development ressources.
That's very probably Apple's faulty OCL drivers which will never be fixed due to deprecation.
Everything else than a Metal transition is just wasted effort.

It's already a miracle that Rob is still providing OCL builds while everyone else, including Blender, has already given up.

Re: Mac OS

Posted: Sun Feb 10, 2019 7:53 pm
by robbrown
Ha ha, yeah the OpenCL deprecation makes me sad. Cool that it sort of works though. Lux or something else, I suspect I have Metal experience in my future. :lol:

I do now have hotel internet, sadly haven't been here much, might be able to get started with Intel Oidn this week if time permits.

Re: Mac OS

Posted: Wed Jul 17, 2019 4:22 pm
by tomi-vanek
I am trying to build the LuxCore for Mac with script ./scripts/azurepipeline/linux/build.sh in project LuxCore. Build fails - Intel Oidn is missing.

I suspect that Intel Oidn lib is missing in https://github.com/LuxCoreRender/MacOSC ... les.tar.gz, that is built from the project MacOSCompileDeps.

Re: Mac OS

Posted: Wed Jul 17, 2019 5:49 pm
by Dade
tomi-vanek wrote: Wed Jul 17, 2019 4:22 pm I am trying to build the LuxCore for Mac with script ./scripts/azurepipeline/linux/build.sh in project LuxCore. Build fails - Intel Oidn is missing.

I suspect that Intel Oidn lib is missing in https://github.com/LuxCoreRender/MacOSC ... les.tar.gz, that is built from the project MacOSCompileDeps.
It is very likely too miss, we are lacking a MacOS maintainer so the scripts have never been updated with the last required libraries.