Smn842

The response I got from the support case a month back was to manually edit the wall and the issue would be looked into. Manually editing is fine but stops auto rebuild so not ideal. Today I chased up to find out if this issue has been confirmed/logged as a bug given the X10 official release version still has the same problem. The response was to request the plan in X9 format which I provided a month ago when I raised the case and specifically stated it was still in X9 format. This makes it appear this hasn't even been reviewed to date. I raised another compatibility issue when I upgraded from X8 to X9 that also yielded nothing other than a workaround and was never fixed. I work in software development and appreciate that some regression bugs will never get fixed, but lack of feedback (request for more info, not reproducible, confirmed bug ID etc) and not appearing to read clear case notes doesn't do much to make users keep reporting issues. I do hope I've just had bad luck with my two support tickets to date.

Even as a hobby user I find the door frame and sill issues annoying. Also the lack of inset control which I didn't find an easy workaround for (makes modelling UK style construction very difficult). I did try playing around with using tiny sections of a different wall type but it got very messy to maintain especially with working around a visible wall cavity in some cases.

I just ensure the 'Drawing Unit' on the '3D' section of the 'Symbol Specification' dialog is set to the correct unit during symbol import (check 'Show Advanced Options' on 'Import 3D symbol' dialog) and that solves the problem. You can use the bounding box sizes on the sizing section to ensure the unit is correct if not sure of the source scale. Once imported the drawing unit is read only. The bounding box is just for correcting where the effective edge is for placement etc. I am only a hobby user so there may be ways to adjust after import but this works for me.

Yes I noticed that bit of gutter which wasn't there in X8/X9. They're all auto built roof planes and the walls have no manual adjustments so it should work as is.

I am a software developer so completely agree with the sentiment, but with my end user hat on it all takes time ;-) I'll report it. Thanks.

For my first look at X10 I tried opening an existing X9 plan and the previously correct roof and auto built walls now have a gap: Anyone else reported this type of issue for the current X10 beta? If not I'll sort out a cut down plan for CA support to have a look at to see if its a bug or problem with my plan.

Using two mice is a good, but with one of them being a 3D SpaceMouse its even better in my opinion, and it even works while modal dialogs are displaying. I am not a professional user, but even with my limited use I couldn't imagine using Chief without one.

I second the suggestion on a larger PCIe SSD as Chief does a lot of file I/O in the background and 256GB doesn't go far (only 238GB in real GB terms) . A drop on the graphics card to even a GTX 1080 should allow that and its also quicker to upgrade a graphics card than the boot drive. The general system performance increase of PCIe SSD even compared to SATA SSD is significant.

What setting do you have for Preferences, Edit, Marquee Selection? Just wondering if its the default "Select Intersected Objects" and each time you've copied some object you accidentally copied other items as well so it increased as you progressed. If that's the case then one of the other marquee selection options may be better for your workflow as its harder to over select.

It could just be that the 3D causes many more redraws so performance will be slower than the bigger movements that result from a normal mouse. On my PC with a good graphics card both are very smooth. However there is a fairly long standing performance issue that if you have a 2D plan view open on the same floor that the 3D view mouse is showing then performance is greatly impacted if both views are visible (two monitors or tiled view on one) . It appears Chief is recalculating/drawing the 2D plan for each movement on the 3D mouse. At first I thought this was due to the mouse indicator on the plan but even disabling that doesn't fix it so it looks like Chief is just refreshing/calculating something it shouldn't (I've reported this a couple of times) This workaround is to change floor level so the 2D and 3D view are on different levels. This is best done on the 2D plan as changing the 3D view floor appears to affect showing lights on floors that are different to the floor level shown.

There is no direct import which was a pain for me recently as I needed to convert almost 100 manufacturer radiator symbols for use in Chief. In the end I installed Revit trial and used that to export the symbols to DWG and imported those into Chief which was a bit tedious to say the least! I thought about using a GUI automation tool for the import part but sadly the manufacturer symbols I was using had some minor issues (seems all too common) so I needed to adjust during import.

We don't spend all our time complaining even though a few changes would make our lives so much easier I've used Chief and Home Designer before that to model several existing homes and interiors are certainly less affected by those construction limitations. The main challenge is so much library content is sized differently or lacking European items but at least they can be created/modified as required. There are also just a few places where metric units haven't been implemented fully or correctly but nothing major.

I've had this kind of problem with a few applications over the years and I've ended up creating automisation scripts (AutoIt/custom app) to work through the files. The last time I did this I converted almost 10k files but it relies on not needing manual updates for each file. It's a shame that vendors don't always consider valid use cases for files in older formats.

Not sure if this is related but ever since I moved to x9 I've had a number of exceptions in Chief when working with active layer display options. Usually when I am just toggling layer visibility. Once an exception occurs they become more frequent until restarting Chief. Even with the latest 19.3.0.49 I still get this and although restarting Chief fixes it on a few occasions it has corrupted something in the plan.

Thanks all. It's good that any potential file format changes would be incremental so no loss of existing work done in v9.

Has there been a statement about whether the file formats for X9 beta are now fixed? I see some posts about people using X9 for real work so not sure what the situation is as many betas allow for breaking changes and I could test it more for bugs making real updates rather than just experimenting.

With the recent release of Intel Kaby Lake CPUs this is worth getting over Skylake CPUs for those going the desktop quad core route. Each step brings a little more performance at the same clock speed and in this case the i7-7700K is also faster clocked out of the box than the i7-6700K. I am waiting on the enthusiast very of Kaby Lake CPUs (probably 6 or 8 core) as for me that's the best compromise between the fastest desktop CPU per core speeds but only 4 cores and lots of slower cores on the Xeons which only come into their own when ray tracing.

Let's hope these aren't all the best X9 features! At least faster undo/redo is welcome as that is painful to use on complex plans.

One other tip not related to the SpaceMouse itself, but something you may notice when using one as it makes is so easy to move through the 3D views: If you use multiple monitors or a tiled window view and notice any slowdown with your 3D view as you move then ensure the plan and floor with the camera symbol on is not visible. It's not enough to just hide the camera indicator by layer (and disabling always showing the symbol) you need to be on another floor of the plan of not have the plan window visible at all. It appears having the plan the camera was placed on is causing extra re-calculations for the plan. I often place full cameras on an attic floor to avoid this issue as the speed difference can be significant on complex plans.

I've just encountered this issue with Miele appliances and the cut out. Any idea on when that will be fixed? Thanks.

I had that sleep issue on a GTX790 on Win 10 and that needed a driver update and firmware update. Have you still got X7 installed to compare? There have been three Win10 versions since release as it keeps upgrading itself in a way that previous versions of Windows didn't and this adds another variable to the mix.

Just tried it here with several combinations across three screens and had no issues. I do this quite a lot generally and its been fine on v18.3.1.2 x64 Do you get this with an empty or simple plan and default 3D view settings?