Error Mess: Cannot DEL transformation ??

[Dave Jochum]

5 minutes before a client is due in my office I find what I think is a duplicate slab in the section window. I delete it, and without saving (so I could just undo if necessary), view the model in 3D to make sure I didn't just trash something I wanted. (I was unsure, because in plan, selecting all did not show a duped slab.) As the 3D window script is running I get about 20 error messages like the one attached, but with different line numbers referenced. I went to undo, but it was greyed out. Just my luck I guess that an autosave had just taken place. It obviously refers to casement windows, none of which I touched in deleting the slab. Can a GDL guru out there tell me what this means and how to fix it?

TIA

[Dave Jochum]

Hi gang--For some reason this thread was not coming up when I clicked "View Posts Since Last Log-in", so didn't realize this discussion was continuing. I feel like I'm in some weird magnetic field that causes everything I use to act wacky.

Anyway, neither Link nor Mathew found anything wrong with my file. I decided to update AC on my PowerBook to see if the problem would go away. It didn't help. The error message seems to be coming up everytime I build/rebuild the 3D window, but only occasionally if I open the parameter setting window for various windows in my model. So I'm finding it impossible to locate a "good" window to syringe & eyedropper parameters to a "bad" window.

I guess I'll have to delete AC and reinstall AC from scratch. I have to start from the CD (v1). Do you guys think I should update with the build 2256 updater (with the problems being reported by others) or the v1+? Also, will simply trashing my current AC folder leave any file remnants that will cause problems when installing v1?

Thanks as always.

[Anonymous]

One final thing before you reinstall. (I can't remember if this was already suggested.)

Have you tried loading a different copy of the same library?

[Dave Jochum]

Matthew wrote:
One final thing before you reinstall. (I can't remember if this was already suggested.)

Have you tried loading a different copy of the same library?

No, but since the problem occurs on my PowerBook also, which has a separate copy of both AC and the library, I can't see it solving the problem. I'm totally baffled how this could occur on my two machines (I haven't worked on my PB since well before this glitch arose) and yet neither you nor Link had a problem with my file. What the bleep is goin' on?

[Dave Jochum]

All right. I'm at my wit's end. I trashed AC and reinstalled from the CD, then updated to v2. After a few crashes due to Theo's D&WB (I updated to 8_92 and all is fine now) I got up and running with build 2256. I still have the same error messages every time I build/rebuild the 3D window. Nobody else can reproduce the errors with my file.

Any more ideas? (hopefully before I slit my wrists--or a client does it for me!)

[Dave Jochum]

Djordje wrote:
Dave, did you delete the library cache?

Djordje, I'm not certain what you mean by this. In the Library Manager | Library Cache Settings... dialogue box one can clear the http cache, which does not help.

I've also looked for cache files on my drive, but found none associated with GS or AC. Am I having a senior moment?

[Erika Epstein]

Dave,
I think Djordje is referring to temp and cache per
http://tr.graphisoftus.com/ ARTICLE #699 by Jeffry C of US tech support.

A number of us on both platforms are finding it quite helpful to resolve problems AC is having.

[Dave Jochum]

Erika wrote:
I think Djordje is referring to temp and cache per
http://tr.graphisoftus.com/ ARTICLE #699

Thanks, Erika. Unfortunately, this did not fix it either.

[Anonymous]

I've seen similar things before. I think you have a parameter set in one of your objects that causes this error. The key is to isolate and identify the offending object(s).

I usually marquee half of the model and then half of the the half that still gave me the error. When you find the offending object, either figure out which parameter is causing the problem or delete the object and replace it.

This has worked a few times for me and several times for clients.

[Daniel Lindahl]

Dave

I just thought of a simple GDL workaround to try as a fix for your problem.

It seems your window is trying to delete (reverse) more transformations than have occurred so far in the 3D GDL script. This can easily happen with sloppy scripting and having conditional transformations in a script, such as: IF a=b THEN ADDx 5
ADD, MUL, ROT, and XFORM are all coordinate transformations, and DEL 5 reverses the last 5 transformations. If there have only been 4 transformations in the script so far (and with conditional transformations it is easy to lose count!) you will get the error message you see every time the 3D of the object is executed.

Now for the fix:

Open the window object for script editing. Go to the top of the 3D script, and insert the following line:
ADDx 0

This inserts a dummy transformation (moving the origin a distance of zero in the x direction).
You can do this a number of times, just to add as many dummy transformations as are needed for the script not to run out of transformations to delete.

From the list of error messages you posted a while back it looks to me like you have 15 windows of that type in the project, in three different configurations. If that is right, then the error message came up twice for each window, and you would only need 2 lines of dummy transformations in the window script.

Another issue is that when you have opened and resaved the altered object you must save it with the same name in order for it to update in your project, so to be safe you might want to save the unedited object AS a different name in order to have a backup of the object that you can save back if your editing didn't fix it.

I am not sure what the procedure would be for getting the edited object back into the PLA library if that is what you are using. Maybe someone else here can help with that one.

HTH

[Daniel Lindahl]

Matthew wrote:
Of course it's possible, just VERY unlikely. Transformations are rarely (if ever) driven by user parameters.

Matthew

Transformations are often conditional and driven by user parameters.
For instance the number of times the origin is moved to insert a glazing bar (muntin) in a window is determined by a loop that is driven by the grid size in the user parameters. Good scripting needs to also make the DEL lines conditional in the same way, to take the right number of steps back.