• Posts

  • Joined


81 Excellent

About BrianBeck

Profile Information

  • Gender
  • Interests
    Washington State University. Go Cougs!

Recent Profile Visitors

8996 profile views
  1. 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.
  2. 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.
  3. 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: Thanks
  4. 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.
  5. Hi Brian,

    Yesterday I sent a bug report regarding toolbar problems through the beta reporting facility.

    I just wanted to make sure that process for reporting bugs was still working.

    Did you receive my bug report?


  6. This is a general problem in the latest build of Firefox. You can find one example of a bug report on the issue here: The issue was marked fixed yesterday so hopefully it will be pushed out soon.
  7. 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.
  8. 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
  9. 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?
  10. 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
  11. 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.
  12. 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
  13. 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.
  14. 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.
  15. 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