Displacement > True crash blender in this file #49324

New Issue

YAFU · 2016-09-11T16:56:15+02:00

YAFU commented

2016-09-11 16:56:15 +02:00

System Information
Kubuntu Linux 14.04, GTX 960

Blender Version
Broken: 2.78 from buildbot ( 96f28f9 )

Short description of error
This problem is related to this 'asphalt.blend' test file from this user:
https://blenderartists.org/forum/showthread.php?396697-Cycles-new-microdisplacement-build-and-testing&p=3097111&viewfull=1#post3097111

asphalt.blend
It seems that 'Ffrima' does not reported yet, so I do the report.
Blender crash when you change Displacement to True

Exact steps for others to reproduce the error
Open 'asphalt.blend' file and change Bump to True in Displacement.

**System Information** Kubuntu Linux 14.04, GTX 960 **Blender Version** Broken: 2.78 from buildbot ( 96f28f9 ) **Short description of error** This problem is related to this 'asphalt.blend' test file from this user: https://blenderartists.org/forum/showthread.php?396697-Cycles-new-microdisplacement-build-and-testing&p=3097111&viewfull=1#post3097111 [asphalt.blend](https://archive.blender.org/developer/F357895/asphalt.blend) It seems that 'Ffrima' does not reported yet, so I do the report. Blender crash when you change Displacement to True **Exact steps for others to reproduce the error** Open 'asphalt.blend' file and change Bump to True in Displacement.

YAFU commented

2016-09-11 16:56:15 +02:00

Changed status to: 'Open'

YAFU commented

2016-09-11 16:56:15 +02:00

Added subscriber: @YAFU

Sergey Sharybin commented

2016-09-12 17:21:28 +02:00

Added subscribers: @MaiLavelle, @brecht, @Sergey

Sergey Sharybin commented

2016-09-12 17:21:28 +02:00

Settings used for musgrave texture are quite insane, they are causing some floating point overflows, resulting in really nasty (inf, nan, fltmax) positions for vertices. This confuses BVH builder a lot.

Not sure what would be a real solution here. On the one hand BVH could become more robust perhaps (binning of such a number wouldn't be fun tho) or maybe we should clamp displacement, or maybe we should clamp node settings..

@brecht, @MaiLavelle any ideas here?

Settings used for musgrave texture are quite insane, they are causing some floating point overflows, resulting in really nasty (inf, nan, fltmax) positions for vertices. This confuses BVH builder a lot. Not sure what would be a real solution here. On the one hand BVH could become more robust perhaps (binning of such a number wouldn't be fun tho) or maybe we should clamp displacement, or maybe we should clamp node settings.. @brecht, @MaiLavelle any ideas here?

Mai Lavelle commented

2016-09-12 19:33:46 +02:00

I don't think its good that the node produces such results, but maybe this could be fixed by skipping displacement of vertices when the displacement is inf/nan?

Brecht Van Lommel commented

2016-09-13 23:59:14 +02:00

Definitely reject non-finite displacements. Fixing texture node(s) would be nice too, though I think we have to be robust to such values coming from the node system.

Mai Lavelle was assigned by Aaron Carlisle

2017-04-17 05:36:11 +02:00

blender-admin commented

2017-05-15 15:44:09 +02:00

This issue was referenced by blender/cycles@59b8b9a0b8

This issue was referenced by blender/cycles@59b8b9a0b8d1b619831f7cec691105b1d6ce4b0d

blender-admin commented

2017-05-15 15:44:09 +02:00

This issue was referenced by ef8ad66aa2

This issue was referenced by ef8ad66aa2d25f414822871f61ece54b0d5a6931

Sergey Sharybin commented

2017-05-15 15:45:41 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2017-05-15 15:45:41 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Displacement > True crash blender in this file #49324