HumbleChief

I had a very bad crash https://chieftalk.chiefarchitect.com/index.php?/topic/9255-first-major-crash-with-new-182042-update/ that removed an entire floor of some fairly complex work. My archive files saved the file and I know what happened but I'm still using X8 as that's the first crash I've had in a very very long time. As Glenn says above if you wait until there are absolutely no issues all you will do is wait.

Interesting Joe, thanks for the confirmation and the tip. The error wasn't really the problem as I've seen it before, but the effect of deleting an entire floor of hard work freaked me out a bit. Thank goodness for the archives.

Will when I get time - leaving for an appointment.

I was able to duplicate it by copying and pasting a window schedule from one CAD detail to another. Got the message below and Chief crashed. Simple to avoid by just creating another, new window schedule but I've copied and pasted schedules before with no problems.

...not sure if it has anything to do with the update or with this particular file but I got a warning message - unable to save this file etc. etc. and Chief would no longer respond. I closed Chief, re-opened and the file I was working on no longer had the (very complex) second floor and all the detail, cabinets etc. were missing from the first floor - it just deleted an entire floor and blew up another. I was able to retrieve an archive and the file looks OK but the original file is toast - just sayin'.

Running fine here.

Interesting article Graham, thanks for posting that. If one were willing to build their own system that seems like a great way to go.

...my experience in California...

Thanks Graham

Curious about which you prefer. I used Live Views in the earlier releases and had some problems and have never returned. I now use plot lines with shadows, no color, sun set to follow camera. How about you?

If there is no vertical surface like a wall Chief will create the p solid at the plane of the Camera itself - look there first.

Alan's advice is good but i'm still trying to figure that out after 15 years of using Chief. I can find them more easily now that I have learned where to look but it still frustrates me. If you create a p solid in elevation it will usually be created up against the nearest vertical surface, or at the camera itself if Chief can't figure out where it should go. Then it needs to be located in plan view to sit in its proper location. I've had p solids created that were simply impossible to find with my meager brain and skill set so I draw them over - a lot. Really think this needs some work for future releases.

Thanks Graham, are you still happy with One Drive?

Question for the 'One Drive' users. Does it allow sending a link to a file that can be opened by someone who does not have One Drive similar to DropBox? When files are too large I send DropBox links to clients and they can open them even without a DropBox account, does One Drive work the same? Or it it necessary to have One Drive account to open links? I'm asking because I think I am paying 9.99 a month for a TB of storage in Dropbox without any Office apps and the Office 365 offer seems pretty compelling. Thanks

Good question - curious too.

True that.

Had GREAT success with DRIVE until it stopped synching automatically. I would have to go t the app menu and 'start' DRIVE to get it to synch. It was a known problem on the forums etc. Still use it with a builder/client but don't depend on it any more.

Yeah I understand Joe, just baffled by it. Thanks again for your help! I'm off to bed.

Got the short one to work the other showed an evaluation error. Tried Eric's dbx. but still wouldn't evaluate. Really Chief why did you bother with this? And set your users up for failure? Still curious.

Sometimes I just feel stupid when I use Chief Architect, no other way to put it.

I don't doubt your analysis is correct Joe. I use macros so seldom that I don't seem to need them but when I do I think your package would be worth many times the amount you charge. I'm posting a video showing my ineptness even with the simple macro solutions you gave me.

I knew you'd have some useful help Joe and I appreciate it greatly but why should I need anyone's help for such a simple task? What do you think they were thinking when they included this 'feature'? Did you ever talk to Dermot about such things? It's just so bizarre to me. Do you have a theory? And thanks again.

EXACTLY what you get out of the box. Just really strange thinking.

...and make it unusable out of the box? Seriously. Why? Can anyone answer that question? Chief? SEVEN decimal places? Seriously? Who made that decision? And why isn't there a clear, easy to understand article on how to round to various, actually usable, decimal places? Truly stumped here. I don't use macros much but need them occasionally for specific projects and tonight I was using them to show the area of Poly Lines for a site plan and add the %area% macro and it resolves to SEVEN decimal places. So, so frustrating. So I scour the forums and the internet to find a clue and of course Joe has some very helpful information that is unfortunately unfathomable to the every day user. So I've wasted an hour trying to figure out how to get a simple poly line label to resolve to 0 decimal places - with absolutely no help from Chief help files or on line articles. So what was the reason to include this 'feature' when it is completely unusable without re-writing the macro? Anyone? EDIT: And why seven decimal places? Genuinely curious. Why not 12? 15? Or a usable 2 and let the macro guys get to 7 if need be but where in Chief, anywhere, for any reason would you need seven decimal place accuracy? Just a really strange mind set that I simply don't understand.

Not the same problem Bryce but similar reliability issues with Drive. I have Win 7.