Cut Pattern Crash

[beboyle]

When I try to define a new wall type, and set the cut pattern hatch, Revit crashes. If I start a new file and try it, doesn't crash, so there must be something wrong with the file I'm working on. Is there any way to audit the file like in ADT?

Brian

[beegee]

There isn't a similar ADT audit function, but you could try purging the file.

Also try loading one of the backups to see if it behaves the same way.

Running journals can sometimes isoslate the problem also. ( Search topics in this forum )

Was this file upgraded from 5.1 to 6.0 ?

[beboyle]

Beegee,

Purging didn't work, found a back up, but it's WAY back, at least half a day's work. I looked up journals, but I don't think I understand the concept though; drop a journal on the icon, then what?

Brian

[beboyle]

Sorry, and no, the file is new in 6.0

BB

[beegee]

Try changing some of the parameters of the bad wall - base and top etc.

Check your levels setup in the bad file also.

Then try placing the wall in other levels.

[FK]

If you go to Settings->Fill Patterns, is there a pattern on the very top of the list beginning with a space or punctuation?

Can you tell me exactly when the crash happens?

[beboyle]

There is a diagonal hatch pattern at the top of the list, with no name (space or blank). The crash happens when I pick a new hatch pattern and choose okay. Here is the error message:

[FK]

Delete the unnamed pattern, there will be no crash. 8)

[beboyle]

Thanks FK...it worked.

Brian

[FK]

This is fixed in 6.1, by the way.

[Scott D Davis]

speaking of 6.1....when can we expect to see it available? Or are you gonna keep teasing us with it?

[gregcashen]

This is fixed in 6.1, by the way.

Yes, I know. ;)

[Steve_Stafford]

Oh come on guys...we know the answer to that already...he can't say...won't say...they'll tie him up and gag him if he does :D

[FK]

Revit releases when it's ready. It's not ready, but it's going good. :wink:

Look at it this way. We set all kinds of deadlines for ourselves. But software engineering is inherently unpredictable. The state of things when plans are made is not the same as the state of things when the deadlines come. As they approach, we monitor the bug database and decide whether there are reasons for postponing things. Since the plans are not public, postponing does not make us look bad. We don't put ourselves under irrational rush to get the new release out. And you don't arrange your plans around a date we may or may not meet.

[Scott D Davis]

Wish I could use that logic with my clients! "You'll get your plans when they are dang good and ready!"

Thanks for all the hard work, Rev-dev team! Looking forward to every release you ever create!

[FK]

That's the difference between hardware and software! You can't slightly update your drawings when the client is three months into construction. :wink:

[gregcashen]

Revit releases when it's ready. It's not ready, but it's going good. :wink:

Look at it this way. We set all kinds of deadlines for ourselves. But software engineering is inherently unpredictable. The state of things when plans are made is not the same as the state of things when the deadlines come.

Hmm... I think I can relate...


gregcashen releases when he's ready. He's not ready, but it's going good. :wink:

Look at it this way. We set all kinds of deadlines for ourselves. But structural engineering is inherently unpredictable. The state of things when planchecks are made is not the same as the state of things when the deadlines come.