BrianBeck

Para-CAD. I think I can reproduce the issue you are seeing, but I don't see a difference between X18 and X17. In watching your video I can see the problem only occurs after you reselect the dimension and then immediately try to move it with a second click and drag. If your dimension is already selected and you just move it by dragging the move handle the problem doesn't happen. The selection of the dimension and then immediate click to drag is being translated as a double click since it is two clicks on the same object within a very short amount of time. You are also using left click for both clicks. Personally I have been in a habit for a long time of always selecting objects in Chief using right-click, this saves a significant amount of keystrokes in the long run, I think a lot of other users might also do this. I only mention that to partially explain why others are not seeing this, since right to select then left click to drag will not cause a double click action. One simple way to resolve this is to decrease the double click time. By default this is 5 in windows. I reduced it to 1 and then I couldn't reproduce the issue, and I was still able to easily get a normal double click to work. These settings are under Accessibility>Mouse in Windows. I think someone posted an image of this earlier in this thread.

Perry, I looked up your report. I told you to turn off the auto scroll feature because of the issue with the screen jumping in plan views. My guess is if you turn it back on you can no longer reproduce the issue. This is not related in anyway to what Joe is describing with errant double clicking occurring.

I believe the issue you reported had to do with using saved plan views that had the Remember Zoom feature turned on causing the view to scroll incorrectly if the new Auto-Scroll feature was turned on. This issue is resolved in the build you currently have. I don't see any reports relating to errant double clicking occuring.

Has it? Where? If a corded mouse works, this is most likely related to something with the Logitech settings or driver. We have not been able to reproduce this issue, I and a large portion of team are using Logitech mice everyday. I have however on multiple occasions seen the Logitech driver get completely broken when it updates in the background which then causes a variety of issues. Sometimes this can be resolved by just relaunching the Logi software after update(you won't know it updated since it happens silently in the background), in other cases I have had to do a full uninstall of the Logi software and then reinstall it to get it the mouse to work correctly. Given you started seeing this recently and we haven't released any changes to Chief, this seems like a likely culprit. If you are not using the custom button functionality that the software provides you can uninstall it since it isn't doing anything but causing problems in that case. Another troubleshooting step you can take is to try and temporarily disable the software. It doesn't look like they provide an easy way to do this, so you would probably have to kill the task via task manager.

We are aware of this issue. You are more likely to see the problem if you have the "Open Dialogs to the Last Panel Visited" preference turned on. The problem occurs after switching panels in a dialog. If after changing panels an edit field happens to be highlighted/focused then you won't be able to type directly.

This should be resolved now. Go ahead and try again and you should now be able to deactivate your license.

It's actually because Auto Roof Returns are turned on for the walls in the Fireplace, as well as a bunch of other walls in the plan where it probably doesn't need to be on. The fireplace walls are the ones causing the slowness though. If you select them and turn off Auto Roof Returns the plan is no longer slow to build 3D.

There is an issue with mirror reflections in legacy PBR(no-ray tracing) in the 26.1 release. This will be fixed in the upcoming 26.2 update.

To be clear, changing sample count will not effect the original issue reported in this post, as the issue only occurs in cases where Ray Tracing is not being used. Sample count is only used when Ray Tracing is supported. You can use a lower sample count now in X15 because we have added a Denoising option that will denoise and clean up the scene once the max sample count is hit. Make sure you have the Cap Live Samples and Denoise When Complete checkboxes checked in order to make use of the new features.

Thanks Chief ID. I took a look at the your plan and was able to reproduce the issue. The problem is caused by the Sun Follows Camera setting. So for now if you turn that setting off your views should work at the same speed as X14. We will look into the cause of the issue in X15 and hopefully get it fixed in a future update. For others that read this, the problem only effects PBR views on systems that do not support ray tracing.

That is an older Quadro card that doesn't support ray tracing, so I don't think making Scott's suggested change will have much of an effect. My guess is if something go slower it will be on all cards and not just this one. We have not seen any issues like this up to this point, so there is also the possibility that something your plan is causing the slowness. So if you could send this plan into us, preferably the X14 version of the plan we can take a look and see if we can discover and reason why the performance has decreased. You can send it in to support here: https://support.chiefarchitect.com/ Thanks

This error is not related to the error in the original post and is unlikely to be resolved by any changes to your drivers. In almost all cases when we have seen this error it is reproducible when following a specific set of steps. The error normally is displayed when closing 3D views, but is likely caused by something done while in the view. Please contact technical support with the steps you are taking when you see this error. Please include the plan file and any saved cameras that you were using as the camera settings could also have an effect. You may also want to start a separate thread about this since as I mentioned this is a different error and not related to the message the original poster asked about.

This is a general problem in the latest build of Firefox. You can find one example of a bug report on the issue here: https://bugzilla.mozilla.org/show_bug.cgi?id=1773907 The issue was marked fixed yesterday so hopefully it will be pushed out soon.

Joe, I have not been able to reproduce this in my simple test cases. Please make sure to send an example of the issue you are having into tech support. Solver, I believe you will need to draw the regions accurately to the corner to see them miter at the corners. In your image the region is extended beyond the corner.

This problem is not related to the recent Chief update. We have tracked this issue down to an Optional Windows update labeled KB5011543. You can uninstall this update and the problem will go away. To uninstall the update: In Start Menu, type "Control Panel" then press Enter In the Control Panel: Click on Programs Then Click on View Installed Updates Scroll down to the Microsoft Windows Section Find the update that says KB5011543(It will likely be at the top) Select it Click the Uninstall Update bottom at the top of the page

Do you see this same problem if you do not have a PBR with ray tracing view open in another tab as you do in the video?

Amanda, Open Preferences and on the Render Panel check the option under Troubleshooting called Manage GPU Residency. This should hopefully allow you to print the entire layout. If not please contact Technical Support with the plan and layout file and we can look into it further. Thanks

It is being used in your Dormer defaults. If you change the wall type there to something else you will be able to delete it.

Scott, Try using any browser that is not Safari and it should look much better. Safari doesn't support the modern version of WebGL which is used for rendering the scene in 3D Viewer. This is why the anti aliasing isn't working. Thanks

It looks like the issue has to do with the width of the Material column. Yours is extremely large and this is preventing the resizing of the dialog. The size of the column could be the result of the issue Rob mentioned which existed in the Public Beta but has since been fixed. You can resolve this issue but either resizing the material column back down to a reasonable size if possible or the other option is to go to Preferences and on the Reset Options panel click Reset Dialog Sizes.

Looks like there is a new feature that came as part of the upgrade that removes followers who have had no activity on the forums for over year. We could change the timeout or set it to never, but I think the current default of 1 year seems reasonable.

You just need to reset the FTH which clears the list of flagged applications which will result in Chief running much faster. Paste this command into a command prompt that is running as admin to reset the list: Rundll32.exe fthsvc.dll,FthSysprepSpecialize

If you are getting the Fault Tolerant Heap(FTH) message then Chief will run very very slowly until you have reset the FTH. Take a look at this article for help resolving the issue: https://www.chiefarchitect.com/support/article/KB-03114/message-windows-fault-tolerant-heap-fth-has-been-enabled-for-this-application.html

Mick, A quick google search indicates those error codes have to do with a permissions issue either with the Windows Temp folder or the c:\Windows\Installer folder. I would do search on those msi error codes and try a couple of the suggested fixes.