Noticed a strange behaviour that is causing me headaches:
When modifying a model (deleting a face per instance) and want to undo afterwards, I have to hit the Undo menu item many times (sometimes up to 10 times or more) before I can actually get the face back, with all items in the undo stacks as “Undo properties”, although I have done nothing more than deleting the face.
This is not systematic but occurs regularly in models where some VRay materials have been applied.
Anyone else noticed that issue?
Best regards,
Thibaut
2hD Architecture Workshop
My Config:
SketchUp Pro 2019 19.1.173
V-Ray for SketchUp 4.00.02 (build 97144)
V-Ray NeUI Version 2.1.3
MacOS 10.14.5 on MacBook Pro 13 (Late 2013)
I’m having this same problem. Under the Edit-undo menu, it reads ‘‘Undo V-ray properties’’, and I cant seem to make it far back enough to undo anything in the sketchup scene.
Bug confirmed. This bug is affecting all machines in our office, running V-Ray Next for Sketchup Hotfix 1 Edu on Sketchup Pro 2019 on Windows 10.
This is a nasty bug, because it silently hijacks the Sketchup undo stack. V-Ray Next effectively breaks Sketchup’s undo stack, by repeatedly spamming it with dozens of nonsense actions. These undo stack entries are several discrete commits not initiated by the user. They are triggered by standard modelling operations that should have nothing to do with the parts of V-Ray exposed to the end user. Moreover, V-Ray Next is spamming Sketchup’s undo stack even though V-Ray has not even been launched in the current modelling session.
Apparently, the only way of making Sketchup’s undo stack workable again is to disable the V-Ray extension in Sketchup’s Extension manager. So, in order to be able to do standard 3D modelling work including undo, our office has disabled V-Ray Next.
Dear Chaos Group - fixing this bug is worth releasing a Hotfix 2.
Would you please squash this workflow-breaking bug now?
I’m afraid there is no simple way to implement a solution for this particular behavior.
Will make sure to post an update in this forum thread the moment our dev team makes some progress or manages to deliver a workaround.
Hey yall,
Just wanted to give a fresh ‘+1’ for getting this bug resolved. I think it is a pretty major one…a stone-cold workflow killer for me. I would personally want to see this bug fixed before any new features are added to Vray. I mean, come on…UNDO is broke…? I about to the point where I’m thinking of keeping Vray disabled/unloaded until I run into something I can render with Enscape and absolutely have to use Vray.
Hi! The same problem. Thought for current new update of Vray this will be solved. But not yet. Support team, when are you going finally to fix it? How long users have to be ignored? You just confirm you see the problem exist and no more actions from you.
“Undo” is a basic function mostly used in a working process and you make us do not use it properly because of your technical process. What is next? Later we will not be able simply to run Vray at all and you will only notify us you confirm it? Chaosgroup team, we are waiting for your reply and actions.
The major cases of this behavior are identified by the dev team. Creating materials or activating the V-Ray scene may prevent the reversal of prior SketchUp actions. Will post again as soon as we can offer a viable solution!
Also want to thank everyone for voicing out your concerns over this issue! Its priority has been raised accordingly.
Has this issue been resolved for Sketchup? I made a post earlier today about this exact issue in Rhino 5. Luckily, Rhino retains thousands of commands, but still, it has completely disrupted my workflow as well.
Hi @Peter.Chaushev can the priority of this issue be raised even higher? We’re getting more and more reports of people having their workflow disrupted by this issue. Not only does the undo stack get clogged up by the ‘updating properties’ command, but also the process of updating those properties is taking quite a while, making SketchUp time out for a bit, depending on the model size, this might be quite a long while.
I have been experiencing this issue for considerable time. I hoped upgrading to SketchUp 2020 and the associated VRay update would fix the issue, but it hasn’t been addressed in your latest release.
To give some perspective, every time I make a single “mistake” in my model, I have to close that model without saving in order to get back to the state prior to the mistake. If I haven’t saved my model for a few minutes, that means also loosing all my other “non mistake” changes. At the moment I have to uninstall my VRay extension, and reenable it explicitly to do any rendering (again, opening and closing models and Sketchup)We’re professionals, and so all this costs us time and money.
This is quite a significant defect, which you are aware of and can reproduce. I appreciate it may be difficult to fix, but it is a “Class One Defect” that needs to be at the top of someones list. According to your post in October, the priority had been raised, but 3+ months and one patch later, the issue is still in the system.
We’re subscribers, which means we actively choose to spend money on rendering software. We do this to get features and professional support. There is plenty of £0/$0 software out there, but we pay you guys to give us the support we need to run our business. We know you all love the recurring revenue you get from the subscription model, but the the other side to the coin is that year on year the user chooses where to spend their subscription dollar.
Please provide us with an update on this issue, along with an estimated time for resolution. It can be done - just imagine your CEO has just called you to ask.
With the release of update 2 (v4.20.01) on Feb 18th the following fixes were introduced:
- applying material to object faces prior to activating V-Ray is now undoable
- quickly tweaking any material property slider in the Asset Editor no longer causes issues
- creating a material no longer prevents undoing prior actions
This does not yet completely resolve the problem. Changes to V-Ray material parameters still log extra actions in the SketchUp Undo stack. A solution for this is currently prioritized.
Thank you all for your comments!
If you are able to reproduce this consistently, could you please share the model with us (support@chaosgroup.com) and / or provide a step-by-step description how to reproduce the behavior?
Additionally, are you using any 3rd party plugins for modeling?
Here’s the announcement thread where you can see the most important changes listed:
The Undo should work in a much more reliable way now.
I’m afraid that we might never make it perfect since the number of things we have control over in SU is limited.
Please give this build a try and let me know what you think.
“I’m afraid that we might never make it perfect since the number of things we have control over in SU is limited.” Could you please explain why? Why you and Trimble can’t communicate in order to fix all the conflicts exists? We (users) could vote if need, if they don’t let you do something you need. And what for this current nightly build release. Did you note that now we’ve got a problem with “Redo” function, it doesn’t work, I can undo actions and can’t redo them.
This is a slightly oversimplified explanation but:
SketchUp Ruby API:
- Any change made to the SketchUp model using the Ruby api will add to the undo stack.
- Changes can be grouped into “operations”
- Operations can be merged into whatever change is at the top of the undo stack. These are called “transparent operations”.
- There is no way to inspect the undo stack
- Observer events are not refined enough to be able to track the undo stack state
As for our integration, we have one key requirement:
Any change to a vray asset requires its change to be serialized to the model. The reason we want to serialize to the model to to allow users to copy/paste/save materials and components components and have them include their properties. Unfortunately we currently handle a material undo as just a change to the material causing us to update our asset and re-serialize (adding to the undo stack and breaking reado).
There is still room for improvement on our side but we’re limmited by what the current SketchUp API exposes.
Discussions about the SketchUp API improvements/limitations/bugs are public and vibrant. Undo stack headaches affect many extension developers. It is likely we’ll be emphasising the importance of the undo stack over the coming months.
We’re aware of this problem but to be honest I was under the impression that this was not new. I will discuss it with our QA team.
To be clear, it is not that redo doesn’t work. It is that undoing a material change will cause us to re-serialize and add to the stack (making a redo not possible).
