Undo Broke??? 1.30.1

Ehm, is it just me, or does ctrl+z or edit-undo no longer work on objects containing multiple prims?
Problem started after my sim was resetted to 1:30:1

Oh damn, that would be a BAD BAD thing. I'll test it out later when I'm in world.

Aah please no.
Then again it's always been very flaky for me, only works sometimes.

I could be mistaken but aren't keyboard controls part of the your client?

For object and land edits, they send Undo/Redo messages to be handled on the sim

I tried a Ctrl+Z undo on a prim move just now in Kuula running 1.30.1 and had no problem. (O.o)

I had absolutely no idea, until now, that an "undo" function even existed!

/me blushes profusely.

Thanks...that's nice to know

It doesn't seem to work all the time, but it does help sometimes.

The last time this broke it was somehow tied to the main chat thingy. Closing main chat (escape when focused there) would make undo work again.
This may be a new bug and unrelated.

Oh I'll have to try that next time mine doesn't work.
Mine worked fine today.

I was having that problem last night. It would work only while you still had the prim(s) selected. If you went back a few minutes later, it wouldn't work. Very much a suckfest when you are expecting to be able to go ctrl-z and return objects to their last location.

What I noticed so far:

* No difference between 'edit - undo' and ctrl+z
* cannot undo the moving of object that I have no mod rights on

Tested it extensively, own full perm objects work fine.

just confirmed this inworld. undo while moving no mod things is broken.
But... on both Second Life Server 1.30.0.133784 and Second Life Server 1.30.1.135015.

Could you try on a prerolled sim too?
I am using an older emerald viewer, so my mileage may vary.

I looked back(google; second life jira undo) and found us talking about this on a RC client blog post. Something Dessie or Ramzi fixed way back in 1.22(viewer!). Or it never got fixed and we just noticed again.

I've always been able to snap back a selection of prims with undo, today its not working at all.

Oh, undo and no mod haven't been friends in quite a while :/

The regular JIRA site is unavailble right now due to maintenance, but here are some summaries to poke at, maybe they want some votes or something.

http://sljirastats.com/VWR-11105 - "Suggestion for changes to position and rotation of ALL objects to be undone with CTRL-Z"

http://sljirastats.com/VWR-11226 = "Undo fails on shared edit movement of no-modify objects (possibly Linux only)"

http://sljirastats.com/VWR-12359 "Undo Option Greyed out on no mod objects when you need to undo position"

Wow. That shows just how rare it is for me to edit no mod prims. I use undo/redo quite a bit and had completely forgotten about this one.
Thanks bunches for the links, very much appreciated.

@blaze. Are you seeing this for all prims, or just no mod?

I may be late at figuring this(but I got there darn it), perhaps two bugs. The no mod one and new one slipped in today?

May as well get used to it. Like how everyone in SL is learning to set rendermaxnodesize to 8192 to offset linden content breakage they said they would fix and then never did.

tried again today to undo a group link of prims, everything works fine now. even if the prims are no mod, (these are prims I created however). Yesterday was script wacko day I think. even a rez-faux box failed to give me the menu when clicked.

What's that do, Ann?

@Lindal -- Here is the info from a notecard I received on it:

I sent out a notice earlier today regarding a problem that has been introduced in the most recent Second Life Viewer 1.23. This issue causes some prims in highly detailed objects such as jewellery, attachments, some sculpted builds etc. to not be rendered (ie not drawn by your computer). This is because Linden Labs, in their wisdom (!) have set limits on how much detail will be drawn, and rather than letting the user choose where to set this level according to their own preferences/needs have made the default very low. The premise of this change is to reduce lag, and so reduce crashes, but it was made without consultation with residents before or after it's implementation, and without us being able to easily choose whether we want detailed images or fast performance.

More details can be found on the Jira here :---> http://jira.secondlife.com/browse/VWR-13868

If left as it currently is much content will be broken, especially jewellery and detailed attachments, complex sculpted items.

The Workaround
***************

It is possible to manually set your viewer to render more complex objects and, given a graphics card that meets LL's minimum requirements, this should cause little difference to your everyday SLife. With lower-end graphics cards you may wish to increase this only when required (ie. photography, building) and reduce it back down the rest of the time or at times of high lag.

1. Press Ctrl+Alt+D to open up the ADVANCED menu (at the top of your screen, after File, Edit... Help)
2. Open the ADVANCED menu and find DEBUG SETTINGS (4th from the bottom). Clicking this will open a small window with a space to type in it.
3. Type in that window "RenderMaxNodeSize". The default for this is set to 40% (or 4000). Increase this to about 6000 or as high as needed to render all missing prims. I am finding 6000 is adequate with little change in performance.
4. Close the debug settings window.

You may need to play with the value you set this to to optomise it for your computer set-up/graphics card. Remember, you are playing off graphics quality against performance/speed.