[T0M0]

This isn't something with high priority, even roadmap doesn't mention Volumetrics support for GPU,
but when you render ( or preview with FIRE in GPU mode) scene with a volumetric extension applied (constant, VDB) Maxwell Render or Studio will crash.

Would be nicer if message like "Volumetric extension is still not supported in the GPU engine and will be disabled for rendering." will appear than crash

Tested in Maxwell Render 4.0.0.18 on Windows 7 x64.

[luis.hijarrubia]

This isn't something with high priority, even roadmap doesn't mention Volumetrics support for GPU,
but when you render ( or preview with FIRE in GPU mode) scene with a volumetric extension applied (constant, VDB) Maxwell Render or Studio will crash.

Would be nicer if message like "Volumetric extension is still not supported in the GPU engine and will be disabled for rendering." will appear than crash

Tested in Maxwell Render 4.0.0.18 on Windows 7 x64.

Just tested and can't reproduce it. It's true that we don't have a message telling that this extension is not supported, but didn't crash. We just tested with a cube, a volumetric and default sky. Is anything else in your scene?

[T0M0]

Whoa that's interesting

Step-by-step what I did:
- launch Maxwell Studio
- drag'n'drop Maxwell Volumetric to viewport (leave all parameters on default values)
- apply default Custom material
- create and active New Camera
- launch Fire or render (GPU engine) will result to crash
//CPU is working fine, both draft and production engine

I use Titan X (Maxwell architecture) with driver 375.70

Crash log:

Problem Event Name: APPCRASH
Application Name: maxwell.exe
Application Version: 4.0.0.18
Application Timestamp: 589c5d4a
Fault Module Name: mxcommon-x64-v120.dll
Fault Module Version: 4.0.0.18
Fault Module Timestamp: 589c5d3c
Exception Code: c0000005
Exception Offset: 00000000002bdd08
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1051
Additional Information 1: 0939
Additional Information 2: 093984f6bf5cb67aab61be0ea4d66dca
Additional Information 3: b3fd
Additional Information 4: b3fd3bb739afa74c83b9eb47619d798b

[luis.hijarrubia]

Whoa that's interesting

Step-by-step what I did:
- launch Maxwell Studio
- drag'n'drop Maxwell Volumetric to viewport (leave all parameters on default values)
- apply default Custom material
- create and active New Camera
- launch Fire or render (GPU engine) will result to crash
//CPU is working fine, both draft and production engine

I use Titan X (Maxwell architecture) with driver 375.70

Crash log:

Problem Event Name: APPCRASH
Application Name: maxwell.exe
Application Version: 4.0.0.18
Application Timestamp: 589c5d4a
Fault Module Name: mxcommon-x64-v120.dll
Fault Module Version: 4.0.0.18
Fault Module Timestamp: 589c5d3c
Exception Code: c0000005
Exception Offset: 00000000002bdd08
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1051
Additional Information 1: 0939
Additional Information 2: 093984f6bf5cb67aab61be0ea4d66dca
Additional Information 3: b3fd
Additional Information 4: b3fd3bb739afa74c83b9eb47619d798b

Yes following your steps it crashed. It's strange, as we couldn't make it work again as we did before, we tried adding a cube, having no camera, and always crashes, but didn't crash in our test a fre minutes ago.

[luis.hijarrubia]

Well, it seems, that it doesn't crash if you have geometry and the volumetric is the last item.

[T0M0]

Exactly what I wanted to post now

Yes, if there is some geo Maxwell won't crash (also the volumetric won't show in render).

And volumetric can't be at top in object list even there are another objects, it will also cause crash.