Maniphest T69952

Ctrl + Z skipped back about 30 steps with redo doing noting
Closed, Archived
Actions

Assigned To
Richard Antalik (ISS)
Authored By
Elliot Gascoigne (elliotgascoigne)
Sep 16 2019, 4:36 PM
Tags
  • BF Blender
Subscribers
Demeter Dzadik (Mets)
Elliot Gascoigne (elliotgascoigne)
Jacques Lucke (JacquesLucke)
Richard Antalik (ISS)

Description

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30

Blender Version
Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-15 18:34, hash: rBb043bef000e9
Worked: (optional)

Short description of error
after sculpting for a couple of hours using dyntopo I then started making a material with cycles and ambient occlusion nodes and after creating about 20 nodes in the node tree I pressed ctrl z to go back one step blender skipped back to after just sculpting and my material disappeared with nothing happening when I try and redo.

Exact steps for others to reproduce the error
Sculpt using dyntopo with constant detail at about 40, back to layout tab, enable cycles, create environmetn texture with HDRI, create material and input 20 different nodes with ambient occlusion node. Then press Ctrl + z

Related Objects

Event Timeline

Elliot Gascoigne (elliotgascoigne) created this task.Sep 16 2019, 4:36 PM
Jacques Lucke (JacquesLucke) lowered the priority of this task from 90 to 30.Sep 16 2019, 5:21 PM
Jacques Lucke (JacquesLucke) added a subscriber: Jacques Lucke (JacquesLucke).

Couldn't reproduce it yet. Can you try to make it easier for us to reproduce? For example, you could provide a simple file in which we just have to do very few steps to see the issue. The fewer steps, the better.

Elliot Gascoigne (elliotgascoigne) added a comment.Sep 16 2019, 5:57 PM

So I've just been able to reproduce the issue using a simple scene. Here is what is happening: using cycles on GPU rendering - using default cube (bevel edges), enter sculpting tab, enable dyntopo at constant detail at around 40, sculpt a little using any brush, enter layout tab, open a shader editor window, edit the material by placing nodes (any amount) (and I understand that i was editing the default material) then after pressing Ctrl + z it reverts the default material back to it's default state with all the placed nodes removed. I hope this makes a bit more sense, just let me know if you need any more info

Jacques Lucke (JacquesLucke) raised the priority of this task from 30 to 90.Sep 16 2019, 6:02 PM
Demeter Dzadik (Mets) added a subscriber: Demeter Dzadik (Mets).Sep 17 2019, 1:07 AM

Probably this: T68416#751673. Make sure to edit materials in Object mode. :/ As I stated in that thread, imo shader editing needs to be disabled outside of Object mode, but I was ignored D: @Jacques Lucke (JacquesLucke) maybe you can weigh in on this?

Jacques Lucke (JacquesLucke) added a comment.Sep 17 2019, 9:39 AM

That seems to be the same issue indeed. However, now I cannot reproduce it at all, because it's crashing beforehand..

Elliot Gascoigne (elliotgascoigne) added a comment.Sep 17 2019, 11:11 AM

I've just tried to replicate the issue again by just going into the sculpting tab and back into layout, and when you go into the sculpting workspace it changes to sculpt mode, then when you enter the layout workspace it reverts back to object mode, but then adding several nodes and then hitting CTRL + Z it deletes all nodes that you put into the shader editor and goes into sculpt mode. So I was actually in object mode when editing the material

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Jan 11 2020, 2:33 AM
Richard Antalik (ISS) added a subscriber: Richard Antalik (ISS).

I can not reproduce this.

Is this still an issue with latest build? https://builder.blender.org/download/

Richard Antalik (ISS) closed this task as Archived.Jan 19 2020, 11:44 PM
Richard Antalik (ISS) claimed this task.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to close the report