Corruption in Default Scene Primitive #54583

New Issue

Roy Rennie · 2018-04-12T18:03:13+02:00

Roy Rennie commented

2018-04-12 18:03:13 +02:00

System Information
Win 10
NVIDIA Titan X Pascal
(DxDiag.txt attached with detailed config)

Blender Version
Broken: 2.79b (22-03-2018)

Short description of error
The default scene displays corruption on opening the app. This behaviour has persisted despite several reinstallations. All settings are at factory defaults.
Intersect (Boolean) operations do not work. Either the selected object disappears and is reduced to an origin with no dimensions or there is an error stating that no intersections are found, despite the two objects clearly overlapping. Difference and Intersect result in the object selected disappearing. Union results in the error message. The operation has worked twice, the second time produced erratic results on the geometry which was not expected.

Update 14/04 : The corruption is now present in a model I have created, rendering the app almost unusable. I have now attached a video of the behaviour. It 'seems' related to the UI as there is also corruption in the menus and interface. As mentioned this is a fresh install with factory default settings and has repeated across different installs. I will try a previous version to see if the behaviour is present.

I have tested prior versions, this behaviour started in V2.60. V2.59 works fine, in fact it is a lot smoother than more recent versions. Interestingly the experimental V2.80 build works fine as well, and looks a lot better. So this issue ranges from versions 2.60 - 2.79.

Exact steps for others to reproduce the error
For the first point, open the app and click past the spash screen. Then simply rotate the camera and/or press tab to enter edit mode.
For the second, using the default cube scene, duplicate the cube, move it to 1:1:1 so that a corner overlaps, then use Intersect (Boolean) - Ctrl F from Edit Mode, pick option from menu. The selected cube is reduced to an origin.

I've attached two screenshots, the default blend file and DxDiag file.

Many thanks,

Roy

bug.blend

DxDiag.txt

BlenderCapture.mp4

**System Information** Win 10 NVIDIA Titan X Pascal (DxDiag.txt attached with detailed config) **Blender Version** Broken: 2.79b (22-03-2018) **Short description of error** The default scene displays corruption on opening the app. This behaviour has persisted despite several reinstallations. All settings are at factory defaults. Intersect (Boolean) operations do not work. Either the selected object disappears and is reduced to an origin with no dimensions or there is an error stating that no intersections are found, despite the two objects clearly overlapping. Difference and Intersect result in the object selected disappearing. Union results in the error message. The operation has worked twice, the second time produced erratic results on the geometry which was not expected. Update 14/04 : The corruption is now present in a model I have created, rendering the app almost unusable. I have now attached a video of the behaviour. It 'seems' related to the UI as there is also corruption in the menus and interface. As mentioned this is a fresh install with factory default settings and has repeated across different installs. I will try a previous version to see if the behaviour is present. I have tested prior versions, this behaviour started in V2.60. V2.59 works fine, in fact it is a lot smoother than more recent versions. Interestingly the experimental V2.80 build works fine as well, and looks a lot better. So this issue ranges from versions 2.60 - 2.79. **Exact steps for others to reproduce the error** For the first point, open the app and click past the spash screen. Then simply rotate the camera and/or press tab to enter edit mode. For the second, using the default cube scene, duplicate the cube, move it to 1:1:1 so that a corner overlaps, then use Intersect (Boolean) - Ctrl F from Edit Mode, pick option from menu. The selected cube is reduced to an origin. I've attached two screenshots, the default blend file and DxDiag file. Many thanks, Roy [bug.blend](https://archive.blender.org/developer/F2670418/bug.blend) ![BlenderBug.png](https://archive.blender.org/developer/F2670419/BlenderBug.png) ![BlenderBug2.png](https://archive.blender.org/developer/F2670421/BlenderBug2.png) [DxDiag.txt](https://archive.blender.org/developer/F2670423/DxDiag.txt) [BlenderCapture.mp4](https://archive.blender.org/developer/F2686591/BlenderCapture.mp4)

Roy Rennie commented

2018-04-12 18:03:13 +02:00

Added subscriber: @vahndaar

Philipp Oeser commented

2018-04-18 12:22:11 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2018-04-18 12:22:11 +02:00

Dont have issues in your provided .blend
Think there are two issues to solve here:

Boolean usage: the boolean operator works with selected/unselected geometry (in your case I think you have to join your objects first). See the manual
graphics glitches:

 Are these NVidia drivers from [[ http:*www.nvidia.com/Download/index.aspx | http:*www.nvidia.com/Download/index.aspx ]]? (Sorry, could make this up from DxDiag due to version numbers in there...) Have you tried different versions?

Its highly likely that this bug is specific to your hardware/driver configuration. These kinds of display issues are often caused by OpenGL driver bugs.
While its possible a software error in Blender, its worth checking if this functions correctly...

After upgrading graphics card drivers.
On a different system (with different hardware/drivers).
Using a Software OpenGL renderer... On MS-Windows: Download this dll and copying it so its located in the same directory as 'blender.exe' and run Blender normally.

If this is a driver bug, or we can't link to this to an error in Blender's code, the report may be closed as a driver error, so please help us determine whether this is a bug in Blender or not.

Marking as incomplete until we have these questions out of the way...

Dont have issues in your provided .blend Think there are two issues to solve here: - Boolean usage: the boolean operator works with selected/unselected geometry (in your case I think you have to join your objects first). See [the manual ](https://docs.blender.org/manual/en/dev/modeling/meshes/editing/faces.html#intersect-boolean) - graphics glitches: ``` Are these NVidia drivers from [[ http:*www.nvidia.com/Download/index.aspx | http:*www.nvidia.com/Download/index.aspx ]]? (Sorry, could make this up from DxDiag due to version numbers in there...) Have you tried different versions? ``` Its highly likely that this bug is specific to your hardware/driver configuration. These kinds of display issues are often caused by OpenGL driver bugs. While its possible a software error in Blender, its worth checking if this functions correctly... - After upgrading graphics card drivers. - On a different system (with different hardware/drivers). - Using a Software OpenGL renderer... On MS-Windows: Download [this dll ](http://download.blender.org/ftp/sergey/softwaregl/win64/opengl32.dll) and copying it so its located in the same directory as 'blender.exe' and run Blender normally. If this is a driver bug, or we can't link to this to an error in Blender's code, the report may be closed as a driver error, so please help us determine whether this is a bug in Blender or not. Marking as incomplete until we have these questions out of the way...

Vuk Gardašević commented

2018-04-28 10:10:32 +02:00

Added subscriber: @VukGardasevic

Vuk Gardašević commented

2018-04-28 10:10:32 +02:00

Changed status from 'Open' to: 'Archived'

Vuk Gardašević closed this issue

2018-04-28 10:10:32 +02:00

Vuk Gardašević self-assigned this 2018-04-28 10:10:32 +02:00

Vuk Gardašević commented

2018-04-28 10:10:32 +02:00

More than a week passed without a reply.

Due to the tracker policy, archiving until the required additional information / data is provided.

More than a week passed without a reply. Due to the tracker policy, archiving until the required additional information / data is provided.

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

Corruption in Default Scene Primitive #54583