topic Re: ArchiCAD Crashing in Installation & update

ArchiCAD Crashing

Anonymous — Tue, 09 Jul 2024 06:36:36 GMT

Hi.... I'm working in ArchiCAD 10 on a MAC and every time I go to the 3D window the bug reporter pops up and closes down the program. It also just happened as I was creating a section cut. Any ideas of why it might be doing this? Thanks again....

Re: ArchiCAD Crashing

Dwight — Mon, 11 Jun 2007 19:26:42 GMT

Poof, GONE?
Do you have the report turned on?
Of course, it disappears when Archicad crashes so nevermind.

This is most likely a corrupted element.

Use your Mechanic's Mind to eliminate layers or model segments until you isolat it.

Re: ArchiCAD Crashing

Anonymous — Tue, 12 Jun 2007 06:33:04 GMT

Don't forget the binary search procedure. Model half the building. If it crashes model half again of that part. If not model half of the other. Repeat until you have isolated the part. This reduces the selection very fast with a minimum of steps.

Of course you can also use a "smart" binary search. Try to guess which half will be OK. This will save you having to go through excess crashes if you guess right.

Re: ArchiCAD Crashing

stefan — Tue, 12 Jun 2007 06:44:37 GMT

Could be limitations in graphics adapter, RAM or CPU.

Post your specs when asking questions. There is a minimal requirement to run ArchiCAD.

Re: ArchiCAD Crashing

Dwight — Tue, 12 Jun 2007 06:53:48 GMT

I have always preferred the half-of-the-layers at a time method to locate the corrupt element, since it is foolproof.

The lead-up:

Many users also ignore warning messages about corrupted element creation, like overlapping slap bits. These warnings, even if Archicad tries to fix the problem, can be the direct cause of an impossible 3D model.

Re: ArchiCAD Crashing

Anonymous — Tue, 12 Jun 2007 06:57:35 GMT

Dwight wrote:
I have always preferred the half-of-the-layers at a time method to locate the corrupt element, since it is foolproof.

Yep, layers is the simplest way to do it.

Re: ArchiCAD Crashing

Dwight — Tue, 12 Jun 2007 07:03:19 GMT

yup. the simplest.

PS: Slap bits = slab bits.

Re: ArchiCAD Crashing

Anonymous — Thu, 21 Jun 2007 19:21:25 GMT

We are experiencing AC10 locking-up/freezing/crashing..whatever, in 3d mode on our MAC bookpro 2.33ghz Intel Core 2 Duo with 2gb 667 MHz SDRAM.

Any suggestions as to the possible problem?

Re: ArchiCAD Crashing

Anonymous — Thu, 21 Jun 2007 20:03:57 GMT

sham wrote:
We are experiencing AC10 locking-up/freezing/crashing..whatever, in 3d mode on our MAC bookpro 2.33ghz Intel Core 2 Duo with 2gb 667 MHz SDRAM.

Any suggestions as to the possible problem?

Not without more details.

Re: ArchiCAD Crashing

Anonymous — Thu, 21 Jun 2007 20:11:04 GMT

We have recieved these warnings

"Internal error in generator function at line 1119 in the 3D script of file wa_trim_us_10.gsm"

"Library part was not converted properly (w12)"

"Not enough edes in generatrix at line 1119 in the 3D script of file wa_trim_us_10.gsm"

Frankly we dont know what to do when we recieve those warning messages. We hit the continue button and work on. Today we had four crashes.

Please help

Re: ArchiCAD Crashing

Dwight — Thu, 21 Jun 2007 20:24:35 GMT

Swell. Ignore warnings, proceed at peril.

That object is calling a macro. Something is corrupted.

It might be the object should be replaced from a clean library.
It might be an inadvertent bad setting in the object.

If you were a mechanic and this were an old car, you'd systematically test the possibilities by locking out what the problem might be.

It seems like a window trim. Try to do a 3D without showing windows and see.

This is done by using the Filter Elements in 3D command that provides a list of categories to not view.

Re: ArchiCAD Crashing

Anonymous — Thu, 21 Jun 2007 20:39:23 GMT

I can't say whether this relates to your crashing but there seem to be many ways that the wa_trim_us_10.gsm can go wrong (I fixed one last year that broke when the part was used in a profiled wall). I just took a quick look at the script and (as I suspected) it looks like the problem is with your sill settings.

Unfortunately the library parts are too complex to trap for errors in all possible parameter interactions. This macro has almost 4000 lines of code in the 3D script - and it is only putting the trim on the window.

I have been lobbying long and hard with GS to get a handle on this. I am hopeful that we will see some improvements in the near future.

In the meantime try adjusting your sills (or turn them off).

Re: ArchiCAD Crashing

Anonymous — Thu, 21 Jun 2007 21:06:24 GMT

Dwight wrote:
Swell. Ignore warnings, proceed at peril.

That object is calling a macro. Something is corrupted.

It might be the object should be replaced from a clean library.
It might be an inadvertent bad setting in the object.

If you were a mechanic and this were an old car, you'd systematically test the possibilities by locking out what the problem might be.

It seems like a window trim. Try to do a 3D without showing windows and see.

This is done by using the Filter Elements in 3D command that provides a list of categories to not view.

WOW you guys are a bit rough on a newbie!

I will try your sugguestion and report back tomorrow.

Re: ArchiCAD Crashing

Anonymous — Fri, 22 Jun 2007 14:09:28 GMT

Gentlemen

Your recommendation to turn-off the windows appears to have helped.

One question for the experts. Evidently you knew by the error code it was a window. Is there a legend that is available that we should have to diagnosed these problems on our own?

Thanks once again for all your help.

Re: ArchiCAD Crashing

Anonymous — Fri, 22 Jun 2007 14:26:45 GMT

We belive the problem with the windows was due to being units that were modified .

The warning messages did state that certain items had not been "converted".

Does anyone have an idea about window units not being "converted" what does that mean?

Thank you

Re: ArchiCAD Crashing

Dwight — Fri, 22 Jun 2007 21:05:19 GMT

How does one get experience in this area? Old Spouses Tales, i guess: Sort of like knowing that cayenne pepper is good for staunching blood flow in an emergency.

Is there a list of these things? Yes. Just read the entire Archicad Forum archive.

"Converted" may or may not be valid - what it is trying to tell you is that the code doesn't make proper sense. Most likely a bad setting. If not, then an old object.

In the window bit problem, I have had years of difficulty with just those kinds of elements, and after spelunking in the Archicad library files, have learned to interpret the code names. I have geek genes even if my daddy was a motorcycle thug. He must have been trying to disguise his sensitive nature.

Solving these problems is tricky. Sometimes an ordinary user, through intentional or accidental object settings is the first person to discover a problem that makes it all the way through Beta testing. Sort of like after i got my new Volvo and immediately drove it to Mexico and back. Because of the extra mileage, my car was the first one to have the lambdadoodie valve crap out.

But warnings are warnings and a user needs to think like a mechanic to systematically remember what they did just before things went wrong.

Re: ArchiCAD Crashing

Anonymous — Fri, 22 Jun 2007 21:33:09 GMT

Hey Dwight I got your point about how to jump into AC

Thanks

Re: ArchiCAD Crashing

Ralph Wessel — Sat, 23 Jun 2007 10:45:36 GMT

sham wrote:
Does anyone have an idea about window units not being "converted" what does that mean?

"Converting" means using the instructions in the object's 3D script (program) to produce 2D/3D geometry. Most ArchiCAD library parts are dynamic, producing 2D/3D geometry on demand rather than storing a pre-defined shape. If there is a fault in the object's programming, it will fail to 'convert' to a 2D/3D image. The warning message provides you with some clue as to why parts of your project model are not appearing in 3D. Diagnosing the actual cause is another matter

Re: ArchiCAD Crashing

Anonymous — Sat, 23 Jun 2007 11:17:43 GMT

Thanks Ralph for responding...your explanation sounds as good as anything that I have read to date.