Chief Architect Help Database - Article Number: 461
Chief Architect 9.54 Update NotesThe information in this article applies to:
- Chief Architect 9.5
Thursday, July 8, 2004
Following are the update notes for 9.54. These update notes are provided as a service to help you identify if you need a specific update. An average user may or may not have experienced the problems listed in this update. If you have experienced one of these problems we recommend obtaining and installing the update.
Program functionality resolutions:
Sometimes we run into instances where we discover that something that is designed to do a certain thing in the program is not functioning correctly. While we endeavor to thoroughly test the program before each release it is not possible to test every conceivable combination. As these problems are identified we work toward resolving them with program updates. Below is a list of problems that have been identified and resolved in the 9.53 – 9.54 update. We have classified them by several categories to allow you to more quickly determine if you may be experiencing the problem. Keep in mind that many of these only existed in a very specific set of circumstances and may not affect the way the program works for the average user.
While we endeavor to document all solutions there may be problems that have been resolved that are not on this list. Also, if you are using a version of Chief Architect other than the Full version, there may be items that are listed here that do not affect your version.
3D and Render Views
- Resolved a specific problem where parts of walls were missing in 3D views.
- Changed behavior of Garage doors that were placed before building a foundation. Now when the foundation is built, doors in a garage will seek the level of the floor rather than sit on top of the stem wall.
- Resolved a problem where you cannot export an elevation or 3D view as a DXF file in Chief Architect 9.5 Base & Home Designer Pro 6.
- Resolved a problem where corrupt callouts were causing a screen redraw in camera views.
- Resolved a problem where sloping windows would display siding at the top under certain conditions.
- Resolved a problem in a particular plan where cross section cameras lost their section lines.
- Resolved a problem where cabinets placed in 3D views were not getting the correct wall connections.
- Fixed a problem where sunlight was not casting shadows in certain cases with POV.
- Resolved a problem where wall details had invisible framing if created from a template with invisible wall framing.
- Fixed a problem in a particular plan where the default stem wall height was not getting updated.
- Resolved a problem where Suppress Label in Window Defaults is not used in new windows.
- Resolved an issue where soffit labels were selectable. Soffits do not support labels.
- Fixed a problem where door swings in rotated plans did not display correctly.
- Resolved a problem where the Default cabinet label was not displaying correctly.
- Resolved a problem where select same did not work in some cabinet combinations.
- Resolved a problem where stairs could not be reflected about a line.
- Resolved a problem where the default text layer was different between floors.
- Removed an option to set the offset on labels in a schedule, since this never was intended to work this way.
- Resolved a problem where moving a bay or boxed window while the CTRL key was pressed resulted in inconsistent results.
- Resolved a problem where, in certain cases, a curved wall could fail to extend over the platform edge.
- Resolved a problem where Lines drawn on layout page 19 are brown.
- Resolved a problem where rotated text did not display in a layout until the plan was opened.
- Resolved a problem where some dotted lines exported to dwg as dotted and others solid, when exporting from a layout.
Materials Lists and Components
- Resolved a problem where the Materials Polyline does not work for Chief Architect Base version.
- Resolved a problem where the Materials Polyline does not work when you right-click the menu and choose Calculate. It did work when you clicked the icon.
- Resolved an issue where certain items were updated to the master list in the wrong category.
- Resolved a problem with Export Materials List not exporting all the displayed data.
- Resolved a problem where the Use check box was disappearing when an accessory was added in the Cabinet Component dialog.
- Resolved a problem where, when adding several components, not all added components were being retained.
- Resolved a problem where continuous dimensions required a refresh to show correctly after insertion.
- Resolved a problem where Resize About was not updating dimensions properly when wall type changed.
- Resolved a situation where dimensions set to particular layers were not turning off.
- Resolved a problem where terrain does not generate flat inside an elevation region in some cases.
- Resolved a problem in a particular customer plan where it took forever to rebuild terrain.
- Changed the default for new plans to have the flatten building pad unchecked.
- Changed message when saving over a previous version plan to avoid confusion.
- Added a feature to recover from certain situations where plans are corrupted.
Copy Paste Issues
- Resolved a problem in where group select and paste of doors did not correctly paste the door swing.
- Resolved a problem where the default CAD positioning unit was not being retained.
- Resolved a problem where the first floor shows up on plan footprint even though floor 0 is selected.
- Resolved a problem where Error 4206 was produced with 2:45, 3:00, and 3:15pm Sun Angle.
- Resolved an issue where double-clicking a full overview resulted in an error message.
- Resolved a problem where, in a specific set of circumstances, you would receive internal error no. 6865.
Crashes or Assertions
Assertions are placed in the program to flag unexpected events. If these situations do occur, they indicate the program is in a potentially bad state. If you get an assertion, you should always write down the .cpp file and the line number and report it to Chief Architect as soon as possible. Asserts are very specific and, if encountered, allow the programming staff to identify the exact place in the code where the problem is occurring. Along with this information we may request a plan that exhibits the problem or specific set of steps that exhibit the problem. If you discover an assertion and uncover the steps to reproduce the problem, reporting the problem will help make the program better for both you and other users.
Crashes are different than assertions. Hardware failures, driver issues, viruses, anti-virus programs, as well as programming problems, are a few of the reasons that crashes can occur. When we find a reproducible crash that is the result of a problem with Chief, we rank it as the highest priority. From time to time you may experience a seemingly random crash. If you do experience a crash, try to remember what you were doing prior to the crash. If you can reproduce the crash, then report it as soon as possible to the Chief Architect Support Staff so we can determine if the problem is something that can be resolved. Crashes manifest themselves in a variety of ways such as computer shut down, program shutdown, error messages, etc. A specific error message may allow us to determine the exact cause of the crash. Writing down the verbatim message allows us to resolve the problem in a timely manner.
- Fixed a crash that happens in specific plans when you build walls floors and ceilings.
- Resolved a crash after playing a walkthrough.
- Resolved a crash when editing objects in a 3D view.
- Resolved a crash with filleted skylight polylines.
- Resolved several crashes in specific customer plans.
Resolved assertions in the following modules and lines:
- WallTypeDlg.cpp Line: 485
- roomdlg.cpp Line 1575
- devtrans3.ccp Line 330 exp
- GenPlan.cpp Line: 1866
- lists.cpp Line: 1116
- lObject.cpp Line: 523
- lObject.cpp Line 1328
- lObject.ccp Line: 818
- lObject.cpp Line 523
- polylins.cpp Line: 2731
- wall3d.cpp Line 1232
- Symbol.cpp Line: 1284
Last updated on: Jul 01, 2006