Doug_Park

The icons folder is for the recent files list on the task bar.

While this is safe with regard to files that Chief saves. This may create problems with other applications that may rely on temporary files not getting deleted. However, if an application is doing that I would regard that as a badly written application. So while I think what you are doing is likely safe be aware that it might create unexpected problems with other applications.

Edit Area will stretch many things.

Not sure what is going on. It is possible that you chose the 32 bit instead of 64 bit executable. Or maybe the executable you are running is in a different directory. Maybe a reboot of the computer is needed. You will need to relaunch Chief after you make the change.

Check which annotation set you have active when you create your text. It may be that the Rich Text you created was done using an annotation set designed for a different scale. You should look through the text styles in defaults and become familiar with what is there. Also become familiar with the annotation sets that are there and which text styles are being used. You can set up your leader line to use Simple Text if you want in Preferences>Appearance>Text.

Make sure you navigate to the correct file location of the version of Chief you are running. You may have it set for a different install of Chief.

The print dialog is set up so that you can print or reprint any pages that you want. The page numbering as Joey suggests is usually very important to keep the same. The common use cases that I can think of are: 1) I make a change on a particular page and only need to reprint it. I still want it numbered the same not as page 1. 2) I print several pages but one of them comes out bad because of a printer malfunction. 3) The ink cartridge ran out of ink and I need to reprint from that page to the end. I really don't want it to come out renumbered starting at page 1. There may be others.

Crashing trying to record a video and crashing when saving suggests a disk problem. 1) Verify that you disk isn't full. You should be getting an error message if this is the case. If not then let us know. 2) Run chkdsk to verify the integrity of the device. 3) Check for malware. There may be other causes and I'm not ruling out a problem with Chief.

You can also create a room polyline, then convert it to a material polyline. Using Concentric resize you should be able to quickly get it to include the sheet rock.

More than likely the delay you are seeing is due to recording information for undo. You can verify this by turning undo off temporarily. If that isn't the problem then the rest of this won't help you. Undo settings are in Preferences>General. Our current implementation of undo saves a copy of the file on disk. By default in the temporary files folder. This is normally pretty fast, except for very large plans. However there are several things that can cause this to be slow. 1) There are an excessive number of files in your temporary files folder. I consider this a bug in Windows because on all other operating systems temporary files are truly temporary and will get cleaned up automatically. But in Windows you will need to do this manually. I suggest cleaning up your temporary files. This is best done right after a system reboot before you launch any other applications. 2) Disk fragmentation could be an issue. With modern versions of Windows this is supposed to be done automatically, but there are several things that could cause the defragmentation not to run so running it manually may be useful. If it is already defragmented then it should run fast. 3) Some sort of disk problem could be in play. So running chkdsk would make some sense. Finally, if you have an SSD drive you could set the preferences in Chief to put the undo files on that drive. Beyond that there are a couple of other options with undo. 1) Turn undo off. I don't recommend this. 2) Set up an undo timeout to something like 100 milliseconds. This will make it so that if you are working very quickly the undo state won't get saved until you pause. This would have the effect of skipping multiple things you have done, but you can still undo.

It makes sense to me to allow what Perry is asking for. If we did this we probably would allow for things to be combined for the less complicated cases as we do now so you wouldn't have to use the option. I've also thought that it would make sense to allow creation of unlimited levels below 1.

I would zoom in on the location that the dimensions are locating and turn on all layers. Dimensions always hook to something. In some cases if an object disappears in an unexpected way the dimension will drop a point marker so as not to unexpectedly disappear. If that was the case then simply delete the marker.

I looked at the PDF you posted and it appears to show exactly the same measurements that your plan shows. I'm not clear as to what the issue is.

That looks like an interesting place to ride. I'm not a very good climber so those mountains look very difficult to me. This year I'm going to ride in RAGBRAI which should be interesting. I've never done it before.

I did some timing on my laptop. With the 3D pattern layer on and with a 3D perspective vector over view. I did a rebuild 3D it took 18 seconds. I turned off the pattern layer and did the same thing and it took 12 seconds. So on my machine pattern generation accounts for about 6 seconds of the total time. I got similar results in the standard view although it appears to be slightly slower, probably due to having shadows turned on. Just under 12 seconds of the total time is in building the 3D model. The 3D model doesn't need to be rebuilt all the time, but on the first camera view it will always need to be rebuilt. When objects are edited the affected objects wil require rebuilding of 3D. For walls this can affect many objects as they interact with adjacent walls, roofs, and platforms so the expense of editing a wall in 3D can be large depending on the model.

Nice joke. Thanks for the humor.

The model is complex. Over 700,000 surfaces in 3D. Lots of patterns, but I don't think they are the main culprit. I was initially seeing very slow draw times in 3D. I turned off reflections in mirrors and shadows and then got reasonable performance. Sluggish, but not unexpected for such a complex model.

You have show lower floors checked. Your roofs are on the first floor, so when you go to the second floor they are shown.

Slowness opening the print dialog should have been fixed in the latest update. We are aware of a crash on Mac running Yosemite using the trackpad that crept into the latest update, but other than that it appears to be a lot more stable. We are fast tracking a fix for the Mac track pad crash. If you are having reproducible crashes it would probably be a good idea to get with support to narrow down the cause as it is not what we are typically seeing.

Most of our support team uses Mac Minis. They are reasonably powerful, especially the newer ones. Our goal since releasing X6 on the Mac is to support all Mac hardware. So far we seem to be doing OK, but there have been a few glitches with certain graphics drivers that have taken us some time to work around. I use an older MacBook Air from time to time which is a lot less powerful than the latest crop of Mac Minis. It performs well but I wouldn't want to do production work on it due to the small screen. For most simple designs this should be fairly adequate. Even the most powerful hardware can be less than adequate for very complex models. You may find that for more complex designs that you will need to wait a bit longer for results, but for a budget concious person the mini is a good option. If you are doing production work I would recommend something more powerful as it would likely pay for itself in improved productivity.

What target DPI did you choose on your PDF? A low DPI could cause problems that I would imagine would look something like that.

Certainly the primary reason for defragmenting a drive (seek time) is not an issue with SSD drives. However, there is still a data structure that needs to be traversed for each frament of a file so in theory there would be minor improvements. On my systems I have noticed some minor improvments when defragmenting an SSD. But in theory they don't need to be defragmeneted as frequently. Undo is a slow part of the program. We have been doing some work behind the scenes to get to a faster and reliable undo. The case where it is significantly slower in X7 is concerning. Since undo leverages the same code as our file save it is possible that slower saving and slow undo/redo may be related. Making this faster has been a goal of mine ever since I first made it work reliably many versions ago. Unfortunatey, the internal design of Chief did not start out in a way that made the logical ways of implmenting undo easy. We looked briefly at this for X7 but determined that for our release time frame it wasn't feasible. I can't promise anything for X8, but we do view this as a high priority. I am still puzzled by the slow save that Perry is having when saving. There is a bit of overhead for standard views that we didn't have in X6, which makes some operations faster in X7 as Perry demonstrated in his last video. I want to get to the bottom of these issues. I suspect that there isn't a single cause of the slowness. I looked briefly at the Material dialog. In my case it seemed like opening the library material dialog in X6 was significantly slower than in X7. And in the video it appears that the combined material dialog in X7 opens at about the same speed as the library material dialog opened. Having the two dialogs combined suffers from some slight extra overhead on open. There are at least some minor benefits of having both available, but we should probably look into how we can speed up the initial opening of the dialog. The undo case in X7 there are some differences in what you have open. It appears that you have a 3D view open in X7 but not in X6 which would make a difference as 3D data would need to be regenerated. Also, you have a toolbar floating in front of the view in X7 and not in X6 which probably doesn't affect the performance by much, but it might. It is tough to set up identical conditions for comparison as many things can affect the performance.

I think what you want is the join roof tool. The configuration that I think you are talking about should be something that can be auto generated in many cases, but not knowing the specifics of your design makes it hard to speculate.

While it is true that SSD read/write cycling can wear out in theory quicker than a hard disk. Under normal use, including occasional defragmentation, this translates into something like 10 years or more of useful life. This is a concern for a data center using SSD drives for servers but for the average consumer the drive will likely last longer than a typical hard disk. One manual defrag shouldn't hurt and in general nightly defrags should not be an issue. Of course a good backup is always a good idea.

The alternate behavior provides a grid copy. (2D array of objects.) The secondary spacing applies to the spacing when you drag out perpendicular to the first row of objects you created.