• Posts

  • Joined

  • Last visited


62 Excellent

About BrianBeck

Profile Information

  • Gender
  • Interests
    Washington State University. Go Cougs!

Recent Profile Visitors

4793 profile views
  1. 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
  2. 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?
  3. 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
  4. 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.
  5. 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
  6. 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.
  7. 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.
  8. 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
  9. 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:
  10. 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.
  11. To be clear Gamepads can be connected to the mac but they are not supported when using Chief on the mac. There are technical and performance related issues that prevent their use on the mac currently. Gamepads are currently only supported in Chief on Windows.
  12. Game controllers are not currently supported on Mac so the option to use them will not appear in the menus.
  13. Larry, The problem in your video looks like an issue caused by older Nvidia drivers. Try going to the Nvidia website and downloading the latest Nvidia driver. This should solve the problem.
  14. Scott, I can confirm this issue. The plan view drawing of the foundation cutout is drawing too large. It is including the jamb width. The dimensions and 3D should still be correct though. The issue should be resolved for the official release of X11. Thanks
  15. Take a look on the Render panel in your Preferences dialog. The Codec for walkthrough recordings is likely set to IYUV. This will result in the large files you describe. If you look at your X9 preferences my guess would be you are using the XVID codec which is what we recommend. Change X10 to use XVID and it should resolve the issue.