46 replies to this topic

[Bartjuan]

Z.

 

If I drag the material over the wall. I get the mapping/color size issue, if I try to undo after that, I get the undo error.

However, like you say, if - after dragging the new material over the wall, I then create a new object, move it, etc. , I can undo just fine.

With the exception that the material error is never "undone"  but it does not give me an error dialog.

 

I have not tried rebooting my system after this started. I can see if that changes anything.....

 

[edit]

 

Upon REBOOT i am no longer ale to reproduce the Undo Error

Edited by Bartjuan, 24 February 2016 - 04:38 PM.

[Alan Cooper]

When undos stopped working for me yesterday using FormZ Free, I was not doing any modelling changes. The operations involved at that time were set view, panning and zooming, dimensioning, altering visability of layers, isolating and revealing, grouping briefly and ungrouping, unlock and lock groups. Normally I can use undo after having temporarily placed some dimensions, but on that occasion I couldn't which makes me think the cause may be more random rather than related to material mapping.

[Tech]

Gentlemen,

 

It sounds like you may  be having a problem with your scratch disk where the Undos are stored.  First, have you ever had any problems with the Undos shortly after rebooting your computer, or does this only happen after an extended time of working?  And how frequently do you typically reboot your computer?   (In general, we would recommend rebooting at least a few times a week.  If you typically go for longer periods of time between reboots, try rebooting daily and see if that affects the issue.)

 

Next, what are your Preference: Scratch Disk settings?  In general we recommend using the System Defaults, but if you are having trouble with this, make a new folder on your Desktop or Documents, and set this as your Scratch Disk.  Once set, relaunch formZ and continue working.  Does that affect the problem?

[Bartjuan]

Z,

 

My recollection is that I only have issues after working for some time.

I'd say I reboot once or twice a week. I'll try this first, full shutdown every night.

Scratch disk is set to system default.  

 

Bart

[Alan Cooper]

I doubt this undo problem is connected to the location of the scrap file because I just did 3 presses of my undo shortcut, but it was upon the fourth click that the error message popped up. I think if there are groups involved it presents more of a challenge for the undo operation. Screen shot of the one that just happened here. Modify split and union operations were involved recently.

Attached Thumbnails

• 

[Karin]

I am also having the "undo no longer working" problem and have no idea why. 
Backtracking to find the cause is kind of difficult without Undo...

 

[Tech]

Gentlemen,

 

It sounds like you may  be having a problem with your scratch disk where the Undos are stored.  First, have you ever had any problems with the Undos shortly after rebooting your computer, or does this only happen after an extended time of working?  And how frequently do you typically reboot your computer?   (In general, we would recommend rebooting at least a few times a week.  If you typically go for longer periods of time between reboots, try rebooting daily and see if that affects the issue.)

 

Next, what are your Preference: Scratch Disk settings?  In general we recommend using the System Defaults, but if you are having trouble with this, make a new folder on your Desktop or Documents, and set this as your Scratch Disk.  Once set, relaunch formZ and continue working.  Does that affect the problem?

 

Hi Karin,

 

Sorry you are having trouble.  If you can answer the above questions, and / or have any further clues, please let us know.

 

It is very odd that there are a large handful of people who have encountered this, but no one has been able to determine a pattern.  Perhaps taking a few quick notes when it does occur of the last few things you did when you encounter this, and then restarting and trying those steps again will help determine the cause?

 

If we can reproduce the problem here, then we can get it corrected, but it is difficult to do anything when we don't know where to start...