fully broken scenes., by drag an object only the pivot point moves #69853
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#69853
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Added subscriber: @nokipaike
Added subscriber: @MarcinTwarowski
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.
Added subscriber: @rboxman
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.
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
Blender 2.81 Alpha September 13, 23:20:49 -
0547a77536
I just tried this build and the problem disappeared. everything works as well now.
Added subscribers: @fclem, @mano-wii
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 ...
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)
@mano-wii @fclem
just to give you extra information, destroyed similar meshes also appear on linux, it had never happened before.
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
Removed subscriber: @MarcinTwarowski
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
Changed status from 'Open' to: 'Archived'
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 :\
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.
Changed status from 'Archived' to: 'Open'
I will investigate further.
Added subscriber: @mareko
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)
@mano-wii maybe it can help
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.
@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
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.
@mano-wii
I tested all this night, the latest build
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
This issue was referenced by
d0c772f68b
Changed status from 'Open' to: 'Resolved'