fully broken scenes., by drag an object only the pivot point moves #69853

New Issue

noki paike · 2019-09-13T19:59:07+02:00

noki paike commented

2019-09-13 19:59:07 +02:00

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13417 Core Profile Context 0

Blender Version
Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-13 15:37, hash: 92736a7b75
Worked: the previous build was fine.

on the Gpu intel hd 4000 works perfectly.

Short description of error
On radeon HD 7600 all loaded scenes, fully broken scenes., by drag an object only the pivot point moves.

Edit:

Investigating better, Greace Pencil works well.
It seems that only the mesh, curve and metabal in objects mode are affected by the bug.
In edit mode, the operation of scaling, move, rotate works correctly.

The new tools of rotation, movement and scale in scupt mode also work well.

On the GPU intel HD 4000 works perfectly.

Exact steps for others to reproduce the error
see the video.
https://youtu.be/0j8OdGKJaJc

blender_system_info.txt

blender_debug_output.txt

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13417 Core Profile Context 0 **Blender Version** Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-13 15:37, hash: `92736a7b75` Worked: the previous build was fine. on the Gpu intel hd 4000 works perfectly. **Short description of error** On radeon HD 7600 all loaded scenes, fully broken scenes., by drag an object only the pivot point moves. Edit: Investigating better, Greace Pencil works well. It seems that only the mesh, curve and metabal in objects mode are affected by the bug. In edit mode, the operation of scaling, move, rotate works correctly. The new tools of rotation, movement and scale in scupt mode also work well. On the GPU intel HD 4000 works perfectly. **Exact steps for others to reproduce the error** see the video. https://youtu.be/0j8OdGKJaJc [blender_system_info.txt](https://archive.blender.org/developer/F7746001/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F7746002/blender_debug_output.txt)

noki paike commented

2019-09-13 19:59:07 +02:00

Added subscriber: @nokipaike

Marcin Twarowski commented

2019-09-13 23:03:10 +02:00

Added subscriber: @MarcinTwarowski

Marcin Twarowski commented

2019-09-13 23:03:10 +02:00

Are you sure you don't have this selected?

Are you sure you don't have this selected? ![image.png](https://archive.blender.org/developer/F7746562/image.png)

noki paike commented

2019-09-13 23:50:31 +02:00

In #69853#775692, @MarcinTwarowski wrote:
Are you sure you don't have this selected?

Obviously it's the first thing I checked, no it depends on the GPU Radeon, in fact on the other Intel GPU, it works well ... it's a bug emerged today.

if you see the video, however, you notice the totally destroyed wanderer scene.

> In #69853#775692, @MarcinTwarowski wrote: > Are you sure you don't have this selected? > ![image.png](https://archive.blender.org/developer/F7746562/image.png) Obviously it's the first thing I checked, no it depends on the GPU Radeon, in fact on the other Intel GPU, it works well ... it's a bug emerged today. if you see the video, however, you notice the totally destroyed wanderer scene.

Roger B commented

2019-09-14 00:00:23 +02:00

Added subscriber: @rboxman

Roger B commented

2019-09-14 00:00:23 +02:00

Can you try pulling down from git again. A large eevee refactor was reverted due to some other issues. See if you have better luck after.

noki paike commented

2019-09-14 00:41:45 +02:00

I tested the latest build Blender 2.81 Alpha September 13, 21:35:05 - 1cdfc1d199
with the new rewritten eevee piece (and also the reverted), it seems that the eevee rendering works fine.
the bug is previous, and is probably related to some changes made in transform.c

(probably a glitchworkaround of my gpu or something similar has been interrupted)

in the image rendering of shaders is ok, but is geometrically a mess

I tested the latest build Blender 2.81 Alpha September 13, 21:35:05 - 1cdfc1d199c3 with the new rewritten eevee piece (and also the reverted), it seems that the eevee rendering works fine. the bug is previous, and is probably related to some changes made in transform.c (probably a glitchworkaround of my gpu or something similar has been interrupted) in the image rendering of shaders is ok, but is geometrically a mess ![Screenshot (119).png](https://archive.blender.org/developer/F7746636/Screenshot__119_.png)

noki paike commented

2019-09-14 01:42:32 +02:00

Blender 2.81 Alpha September 13, 23:20:49 - 0547a77536

I just tried this build and the problem disappeared. everything works as well now.

Blender 2.81 Alpha September 13, 23:20:49 - 0547a7753643 I just tried this build and the problem disappeared. everything works as well now.

noki paike commented

2019-09-17 20:06:39 +02:00

Added subscribers: @fclem, @mano-wii

noki paike commented

2019-09-17 20:06:39 +02:00

windows 10 -- Blender 2.81 Alpha September 17, 16:40:11 - 884a385287

bug returned,
now I can confirm, that it's related to this ...

DRW: Refactor to support draw call batching
3a08153d7a

the scenes seem super light but the meshes are a mess.
(see the video in the bugreport)

@fclem , @mano-wii
I believe you know what it is ...
GPU radeon HD 7600 ...

windows 10 -- Blender 2.81 Alpha September 17, 16:40:11 - 884a3852873f **bug returned,** now I can confirm, that it's related to this ... DRW: Refactor to support draw call batching 3a08153d7a84 the scenes seem super light but the meshes are a mess. (see the video in the bugreport) @fclem , @mano-wii I believe you know what it is ... GPU radeon HD 7600 ...

noki paike commented

2019-09-17 20:28:19 +02:00

it seems that blender ignores the pivot points of objects and puts all the meshes in the center of the scene

(ps. it's awesome as blender starts instantly now)

it seems that blender ignores the pivot points of objects and puts all the meshes in the center of the scene ![Screenshot (159).png](https://archive.blender.org/developer/F7753756/Screenshot__159_.png) ![Screenshot (158).png](https://archive.blender.org/developer/F7753755/Screenshot__158_.png) (ps. it's awesome as blender starts instantly now)

Germano Cavalcante self-assigned this 2019-09-17 22:06:12 +02:00

noki paike commented

2019-09-18 14:56:18 +02:00

@mano-wii @fclem

just to give you extra information, destroyed similar meshes also appear on linux, it had never happened before.

(I'm using the lastest mesa-devel drivers)
(R600_DEBUG=nosb ./blender ) no shader backend , slow compilation of shaders but rendering in eevee usually works fine

on linux the scene appears less destroyed, moving objects works.
in wireframe it's ok.

on individual objects, I found similar meshes destroyed on those on windows ... it seems to be related to normal flipped.

on the intel HD 4000 everything works well also on linux, so the problem is limited with the radeon HD

@mano-wii @fclem just to give you extra information, destroyed similar meshes also appear on linux, it had never happened before. > (I'm using the lastest mesa-devel drivers) > (R600_DEBUG=nosb ./blender ) no shader backend , slow compilation of shaders but rendering in eevee usually works fine on linux the scene appears less destroyed, moving objects works. in wireframe it's ok. on individual objects, I found similar meshes destroyed on those on windows ... it seems to be related to normal flipped. ![Schermata del 2019-09-18 14-46-00.png](https://archive.blender.org/developer/F7755531/Schermata_del_2019-09-18_14-46-00.png) ![Schermata del 2019-09-18 14-45-28.png](https://archive.blender.org/developer/F7755528/Schermata_del_2019-09-18_14-45-28.png) ![Schermata del 2019-09-18 14-46-36.png](https://archive.blender.org/developer/F7755529/Schermata_del_2019-09-18_14-46-36.png) on the intel HD 4000 everything works well also on linux, so the problem is limited with the radeon HD

Marcin Twarowski commented

2019-09-18 15:01:48 +02:00

Removed subscriber: @MarcinTwarowski

noki paike commented

2019-09-18 16:57:26 +02:00

Other useful information:
Always on linux, with Radeon hd 7600 if I start blender with GPU workarounds, I get the same identical windows errors : only the pivot points moves, all the messed up meshes in the center of the scene, ruined meshes

Other useful information: Always on linux, with Radeon hd 7600 if I start blender with GPU workarounds, I get the same identical windows errors : only the pivot points moves, all the messed up meshes in the center of the scene, ruined meshes ![Schermata del 2019-09-18 16-43-22.png](https://archive.blender.org/developer/F7755818/Schermata_del_2019-09-18_16-43-22.png)

Germano Cavalcante commented

2019-09-18 17:31:49 +02:00

Changed status from 'Open' to: 'Archived'

Germano Cavalcante closed this issue

2019-09-18 17:31:49 +02:00

Germano Cavalcante commented

2019-09-18 17:31:49 +02:00

I spent yesterday and today investigating.
I fear don't have much to do.
These AMD GPUs have reached a state that requires workarounds to workarounds.
Depending on how many users use and report problems on these cards, I can look into a solution again.
But for now ... archiving :\

I spent yesterday and today investigating. I fear don't have much to do. These AMD GPUs have reached a state that requires workarounds to workarounds. Depending on how many users use and report problems on these cards, I can look into a solution again. But for now ... archiving :\

noki paike commented

2019-09-18 20:30:07 +02:00

this is really a sad news, after more than a year that everything was fine I find myself catapulted back to August 2018 :/

it is obvious that there will not be many that will report the bug, we are not caught in many to do every day beta testing with a laptop of 2014, at least until the official release 2.81 will come out where ordinary people will download the new release, and they will discover the surprise that blender 2.81 is no longer supported for all those machines-GPU until at least 2015-2016. (legacy AMD DAMN drivers, having support opengl 4.6 and not useful to anything.)

now I'm fucked, it's game over for me, for who knows how long, since at the moment I won't be able to afford to change machines, at least with a decent one.

this is really a sad news, after more than a year that everything was fine I find myself catapulted back to August 2018 :/ it is obvious that there will not be many that will report the bug, we are not caught in many to do every day beta testing with a laptop of 2014, at least until the official release 2.81 will come out where ordinary people will download the new release, and they will discover the surprise that blender 2.81 is no longer supported for all those machines-GPU until at least 2015-2016. (legacy AMD DAMN drivers, having support opengl 4.6 and not useful to anything.) now I'm fucked, it's game over for me, for who knows how long, since at the moment I won't be able to afford to change machines, at least with a decent one.

Germano Cavalcante commented

2019-09-18 20:43:24 +02:00

Changed status from 'Archived' to: 'Open'

Germano Cavalcante reopened this issue

2019-09-18 20:43:24 +02:00

Germano Cavalcante commented

2019-09-18 20:43:24 +02:00

I will investigate further.

noki paike commented

2019-09-18 22:14:27 +02:00

Added subscriber: @mareko

noki paike commented

2019-09-18 22:14:27 +02:00

Hello @mareko , I read your comment in this task,#54638 I know you are the official AMD Developer for Opensource Mesa Drivers, and much more ... could you please help us investigate what happens here?
It's been over a year since we hit this weird bug. ...
(this on windows)

I also created a thread on other messes that also happen on linux, with these GPUs, do you really think we need to give up on them? ...
https://devtalk.blender.org/t/amd-r600-mesa-linux-driver-eevee-broken/9294

(Marke's comment on the other task)

AMD guy here.

You need to request the Core profile for older versions of our open source driver. If you don't, you'll get the compatibility profile which is mainly used by legacy applications.

The original plan was to keep the Core profile version at GL 4.5 and the Compatibility profile version at GL 3.0 forever, but we changed our minds and started adding Compatibility profile support last year:
Mesa 18.0: OpenGL 3.0
Mesa 18.1: OpenGL 3.1
Mesa 18.2: OpenGL 4.4
Mesa 18.3: OpenGL 4.5

You are shooting yourselves in the foot by using the Compatibility (default) profile. The Core profile is slightly faster if you are CPU-bound.

Hello @mareko , I read your comment in this task,#54638 I know you are the official AMD Developer for Opensource Mesa Drivers, and much more ... could you please help us investigate what happens here? It's been over a year since we hit this weird bug. ... (this on windows) I also created a thread on other messes that also happen on linux, with these GPUs, do you really think we need to give up on them? ... https://devtalk.blender.org/t/amd-r600-mesa-linux-driver-eevee-broken/9294 (Marke's comment on the other task) > AMD guy here. > > You need to request the Core profile for older versions of our open source driver. If you don't, you'll get the compatibility profile which is mainly used by legacy applications. > > The original plan was to keep the Core profile version at GL 4.5 and the Compatibility profile version at GL 3.0 forever, but we changed our minds and started adding Compatibility profile support last year: > Mesa 18.0: OpenGL 3.0 > Mesa 18.1: OpenGL 3.1 > Mesa 18.2: OpenGL 4.4 > Mesa 18.3: OpenGL 4.5 > > You are shooting yourselves in the foot by using the Compatibility (default) profile. The Core profile is slightly faster if you are CPU-bound.

noki paike commented

2019-09-18 22:52:30 +02:00

@mano-wii maybe it can help

OpenGL capabilities report

The table here shows the features reported for devices with the following GL_RENDERER strings:
AMD Radeon HD 7660G + HD 7600M Dual Graphics
Different driver versions may have different feature sets, and we may have conflicting reports from the same driver version. There is a column for each distinct set of reported features. The column heading gives the short device name, and the set of driver versions with that feature set.

Green cells indicate supported extensions; red cells indicate non-supported extensions. Cells are marked with bold when their value differs from the previous cell in the same row.

https://feedback.wildfiregames.com/report/opengl/

@mano-wii maybe it can help > OpenGL capabilities report > > The table here shows the features reported for devices with the following GL_RENDERER strings: > > AMD Radeon HD 7660G + HD 7600M Dual Graphics > > Different driver versions may have different feature sets, and we may have conflicting reports from the same driver version. There is a column for each distinct set of reported features. The column heading gives the short device name, and the set of driver versions with that feature set. > > Green cells indicate supported extensions; red cells indicate non-supported extensions. Cells are marked with bold when their value differs from the previous cell in the same row. > > > >https://feedback.wildfiregames.com/report/opengl/

Marek Olsak commented

2019-09-19 02:05:18 +02:00

Mesa drivers now support the Compatibility profile on AMD hw starting with the AMD GCN architecture, so you don't need the Core profile anymore.

The r600 driver (for the AMD TeraScale architecture) is too old to receive any support.

Mesa drivers now support the Compatibility profile on AMD hw starting with the AMD GCN architecture, so you don't need the Core profile anymore. The r600 driver (for the AMD TeraScale architecture) is too old to receive any support.

noki paike commented

2019-09-19 02:47:54 +02:00

@mareko Thanks for the reply.

Actually there was a time when on these GPU. the Mesa drives worked well with eevee's blender 2.80 on linux , it continue to work with

R600_DEBUG = nosb

but without speeding up shader compilation, then a change was made in blender and the shader backend stopped working, I'm sure it's something really small and insignificant , some unmanaged API in a standard way, which blew away the management of lights and shadows.

Anyway, I asked for your intervention here, since you are an AMD developer and you know these gpus, if you could give some advice on what happens with windows drivers, if it's a driver bug or something else that destroys geometry. (see the images)

Unfortunately I don't know how to give any other kind of information, I'm just a normal user.
I hope you and the blender devs can have a chat about it.
Thanks.

@mareko Thanks for the reply. Actually there was a time when on these GPU. the Mesa drives worked well with eevee's blender 2.80 on linux , it continue to work with ``` R600_DEBUG = nosb ``` but without speeding up shader compilation, then a change was made in blender and the shader backend stopped working, I'm sure it's something really small and insignificant , some unmanaged API in a standard way, which blew away the management of lights and shadows. Anyway, I asked for your intervention here, since you are an AMD developer and you know these gpus, if you could give some advice on what happens with windows drivers, if it's a driver bug or something else that destroys geometry. (see the images) Unfortunately I don't know how to give any other kind of information, I'm just a normal user. I hope you and the blender devs can have a chat about it. Thanks.

noki paike commented

2019-09-19 08:59:39 +02:00

@mano-wii

I tested all this night, the latest build

  Blender 2.81 Alpha September 18, 23:15:36 - 741d7d60ed90

the situation is less tragic than it seems, I did some tests to try to find situations that recur and find what is broken and dare it works.

in the first video, I was able to find a very simple situation where the mesh goes crazy and i managed to "repair" it and even to break it up by making a "join", here is the video and here is the file. cartel.blend
https://youtu.be/mo5sgl8Xo14
if there are no situations like this file, I can also load objects with millions of polygons and display them correctly.

in the second video I did a sort of navigation to see what happens ... and it's all there! almost, in edit mode, eevee works correctly, it's in object mode that's broken, and switching between the two modes (with all the selected objects) sometimes the scene adjusts ..
some effects work in one mode and not in another, such as the glow ...

https://youtu.be/ILdZxgVxzsQ

@mano-wii I tested all this night, the latest build ``` Blender 2.81 Alpha September 18, 23:15:36 - 741d7d60ed90 ``` the situation is less tragic than it seems, I did some tests to try to find situations that recur and find what is broken and dare it works. in the first video, I was able to find a very simple situation where the mesh goes crazy and i managed to "repair" it and even to break it up by making a "join", here is the video and here is the file. [cartel.blend](https://archive.blender.org/developer/F7757607/cartel.blend) https://youtu.be/mo5sgl8Xo14 if there are no situations like this file, I can also load objects with millions of polygons and display them correctly. in the second video I did a sort of navigation to see what happens ... and it's all there! almost, in edit mode, eevee works correctly, it's in object mode that's broken, and switching between the two modes (with all the selected objects) sometimes the scene adjusts .. some effects work in one mode and not in another, such as the glow ... https://youtu.be/ILdZxgVxzsQ

blender-admin commented

2019-09-19 16:17:50 +02:00

This issue was referenced by d0c772f68b

This issue was referenced by d0c772f68b84267e15630064fc21cc54fc7209f0

Germano Cavalcante commented

2019-09-19 16:18:52 +02:00

Changed status from 'Open' to: 'Resolved'

Germano Cavalcante closed this issue

2019-09-19 16:18:52 +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

fully broken scenes., by drag an object only the pivot point moves #69853