Blender 2.79 vs 2.8 - Changing between solid and wireframe mode is slower #62512

New Issue

Carlo Andreacchio · 2019-03-12T22:28:42+01:00

Carlo Andreacchio commented

2019-03-12 22:28:42 +01:00

System Information
Operating system: Ubuntu 18.04
Graphics card: GTX 1080

Blender Version
Broken: 41cb565880

Short description of error
Changing between solid and wireframe mode is slower.

Exact steps for others to reproduce the error
This is an example file, other production files are significantly worse.

Open attached blend file in blender 2.79
press z many times (blender 2.79 keymaps) to toggle back and forth
feel how snappy it is
switch to blender 2.8
press z many times (blender 2.79 keymaps) to toggle back and forth
notice how it lags.

slowdown-2.blend

**System Information** Operating system: Ubuntu 18.04 Graphics card: GTX 1080 **Blender Version** Broken: 41cb5658803bf3b96f18e93c74c6af66ecdb1e83 **Short description of error** Changing between solid and wireframe mode is slower. **Exact steps for others to reproduce the error** This is an example file, other production files are significantly worse. 1. Open attached blend file in blender 2.79 2. press z many times (blender 2.79 keymaps) to toggle back and forth 3. feel how snappy it is 4. switch to blender 2.8 5. press z many times (blender 2.79 keymaps) to toggle back and forth 6. notice how it lags. [slowdown-2.blend](https://archive.blender.org/developer/F6811442/slowdown-2.blend)

Carlo Andreacchio commented

2019-03-12 22:28:42 +01:00

Added subscriber: @candreacchio

blender-admin commented

2019-03-12 22:28:42 +01:00

#62174 was marked as duplicate of this issue

Jacques Lucke commented

2019-03-13 12:01:55 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-03-13 12:01:55 +01:00

Changed status from 'Open' to: 'Archived'

Jacques Lucke closed this issue

2019-03-13 12:01:55 +01:00

Jacques Lucke self-assigned this 2019-03-13 12:01:55 +01:00

Jacques Lucke commented

2019-03-13 12:01:55 +01:00

That is not a bug. Maybe it can be optimized later, but this is outside of the scope of the bug tracker.

Also in this file there are more than 2.000.000.000 vertices. Blender is not really made for these vertex counts...

That is not a bug. Maybe it can be optimized later, but this is outside of the scope of the bug tracker. Also in this file there are more than `2.000.000.000` vertices. Blender is not really made for these vertex counts...

Carlo Andreacchio commented

2019-03-13 22:00:13 +01:00

That is not a bug. Maybe it can be optimized later, but this is outside of the scope of the bug tracker.

That is fine, as long as its registered that it is slower.

Also in this file there are more than 2.000.000.000 vertices. Blender is not really made for these vertex counts...

I would like you to also reconsider other uses of Blender, especially for infrastructure visualization. Our scenes usually span between 5km square to 100km square, with heavily instanced trees. I am comparing performance between 2.79 and 2.8 on real world scenes and that i am then replicating it in test scenes so i can upload and help make blender even better.

2,000,000,000 vertices is a lot yes... but most if not all are instanced and out of view. 2 billion verts is not that much for a production scene, instanced trees (2000 trees at 100,000 per tree) hits this quite easily.

> That is not a bug. Maybe it can be optimized later, but this is outside of the scope of the bug tracker. That is fine, as long as its registered that it is slower. > Also in this file there are more than 2.000.000.000 vertices. Blender is not really made for these vertex counts... I would like you to also reconsider other uses of Blender, especially for infrastructure visualization. Our scenes usually span between 5km square to 100km square, with heavily instanced trees. I am comparing performance between 2.79 and 2.8 on real world scenes and that i am then replicating it in test scenes so i can upload and help make blender even better. 2,000,000,000 vertices is a lot yes... but most if not all are instanced and out of view. 2 billion verts is not that much for a production scene, instanced trees (2000 trees at 100,000 per tree) hits this quite easily.

Carlo Andreacchio commented

2019-03-28 22:38:59 +01:00

Changed status from 'Archived' to: 'Open'

Carlo Andreacchio reopened this issue

2019-03-28 22:38:59 +01:00

Carlo Andreacchio commented

2019-03-28 22:38:59 +01:00

I would like to have this bug revisited. Whilst it may not be important to you, I have tried to work in a production scene for a day, and this was a deal breaker. Having to wait 3 seconds every time I want to switch between the modes breaks the flow of the artist.

This may not be viable for a blender 2.80 release but 2.81 or later should have it looked at.

I would like to have this bug revisited. Whilst it may not be important to you, I have tried to work in a production scene for a day, and this was a deal breaker. Having to wait 3 seconds every time I want to switch between the modes breaks the flow of the artist. This may not be viable for a blender 2.80 release but 2.81 or later should have it looked at.

Brecht Van Lommel commented

2019-04-04 06:02:22 +02:00

Added subscribers: @Leroy-Xie, @fclem, @ZedDB