OctaneRender™ 2020.1.2 [superseded by 2020.1.3]

[3dworks]

I am having 2020.1.2 crash on open on my 2010 mac pro (tower) running OSX High Sierra and the latest (not new) nVidia drivers that work on this machine (web driver -387.10.10.10.40.130... CUDA driver 418.163)
Is this the first version that simply will not work with my older setup?

same configuration here, macpro 2010 with gfx 1080, latest updates of nvidia driver 387.10.10.10.40.137 and CUDA driver 410.130.

crash log of standalone:

Code: Select all

Process:               octane [1176]
Path:                  /Applications/OctaneRender Enterprise 2020.1.2.app/Contents/MacOS/octane
Identifier:            com.otoy.octanerender
Version:               2020.1.2 (8.1.2.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           octane [1176]
User ID:               501

Date/Time:             2020-06-12 20:47:08.343 +0200
OS Version:            Mac OS X 10.13.6 (17G13035)
Report Version:        12
Anonymous UUID:        B841C2F9-C67E-C61A-949C-585831F2E43B


Time Awake Since Boot: 1000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [0]

Application Specific Information:
/Applications/OctaneRender Enterprise 2020.1.2.app/Contents/MacOS/octane

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.otoy.octanerender         	0x000000010c171ec2 0x10a50e000 + 29769410
1   dyld                          	0x0000000117ce1ac6 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 420
2   dyld                          	0x0000000117ce1cf6 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
3   dyld                          	0x0000000117cdd218 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 330
4   dyld                          	0x0000000117cdc34e ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 134
5   dyld                          	0x0000000117cdc3e2 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 74
6   dyld                          	0x0000000117ccd567 dyld::initializeMainExecutable() + 196
7   dyld                          	0x0000000117cd2239 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 7242
8   dyld                          	0x0000000117ccc3d4 dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 453
9   dyld                          	0x0000000117ccc1d2 _dyld_start + 54

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x8df07596762000e3  rbx: 0x0000000117d19608  rcx: 0x00007ffee56f1c28  rdx: 0x00007ffee56f1bc0
  rdi: 0x0000000000000001  rsi: 0x00007ffee56f1bb0  rbp: 0x00007ffee56ee5f0  rsp: 0x00007ffee56ee270
   r8: 0x0000000117d18150   r9: 0xffffffff00000000  r10: 0x00007fffb1e4a0c8  r11: 0x00007fffb1e4a0d0
  r12: 0x00000000000001a3  r13: 0x000000000000022d  r14: 0x00007fffb1e3dde8  r15: 0x000000010c171ea0
  rip: 0x000000010c171ec2  rfl: 0x0000000000010202  cr2: 0x000000010c171ea0
  
Logical CPU:     12
Error Code:      0x00000000
Trap Number:     6


Binary Images:
       0x10a50e000 -        0x10dd1dca7 +com.otoy.octanerender (2020.1.2 - 8.1.2.0) <E45D8F32-BF00-3760-913C-791A9B11CF9C> /Applications/OctaneRender Enterprise 2020.1.2.app/Contents/MacOS/octane
       0x1145c5000 -        0x1145d2ffb +CUDA (0) <03A35E39-5908-30EE-B02D-E44A7AA6BB13> /Library/Frameworks/CUDA.framework/Versions/A/CUDA

[mojave]

It seems that some AVX-512 instructions were introduced in both 2020.1.1 and 2020.1.2 executables which will likely cause the issues that some of you are experiencing with machines with older CPUs which do not have support for this extension set.

We will investigate what is causing this and whether we can provide a solution in the next build.

Thank you for your reports.

[funk]

It seems that some AVX-512 instructions were introduced

Thanks for looking into it

[SRCOBB]

I can tell you that the issue, for me at least, is only presenting 2020.1.2, not 2020.1.1

[noldo]

If i connect a mix material with displacement to a base layered material, the dispacement disappear!

Version 2.1.1 is the same.
Version 2.1.0 is ok!

[3dworks]

It seems that some AVX-512 instructions were introduced in both 2020.1.1 and 2020.1.2 executables which will likely cause the issues that some of you are experiencing with machines with older CPUs which do not have support for this extension set.

We will investigate what is causing this and whether we can provide a solution in the next build.

Thank you for your reports.

great thank you!

[CrusaderArts]

Seems that all versions of AMD's Ryzen Processors & most of Intel's processors don't support AVX-512 neither.

I tried this on my Ryzen 9 3900X and I crashed once I started to render.

From my research, only Intel's Extreme Edition CPUs and some Xeon CPUs support AVX-512.

I hope this gets fixed soon.

[useruser]

hello
unfortunately the2020.1.2 SLAVE does not show my RTX 2080Ti card ( 442.92 Studiodriver, Win10 ) it works
with version 2020.1
thanks in advance!

1.jpg

1.2.jpg

[bepeg4d]

Linux seems not affected by the AVX issue, since my old Mac pro is working correctly with 2020.1.2 under Ubuntu 20.4:

8145FB95-E4BF-48CB-8ABD-FFF0D5946824.jpeg

ciao Beppe

[mojave]

Seems that all versions of AMD's Ryzen Processors & most of Intel's processors don't support AVX-512 neither.

I tried this on my Ryzen 9 3900X and I crashed once I started to render.

From my research, only Intel's Extreme Edition CPUs and some Xeon CPUs support AVX-512.

I hope this gets fixed soon.

This does not seem to be the same issue as for others Octane would not start if this would be a problem, would you be able to provide some logs or stack traces at the time this happens?