BrianBeck

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.

Game controllers are not currently supported on Mac so the option to use them will not appear in the menus.

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.

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

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.

Likely your preferences in X9 are different from X10 in regards to which CODEC is being used to create the walk through videos. Take a look at this support article for more information on getting and using a different CODEC. https://www.chiefarchitect.com/support/article/KB-00076/specifying-what-video-codecs-to-use-for-walkthroughs.html

The same issue reported in this thread about exported images would have also occurred for any walkthroughs recorded using the Physically Based rendering technique.

We have just released a patch(20.2.1.1) to resolve this issue. Thank you for your patience.

We are not aware an issue where the software doesn't run on the Macbook pro. We are aware on a issue where the rendering on some MacBook pros is not functioning correctly, and we are attempting to see if we can resolve it. Is this the issue you are having? If not please contact our support team.

Are any of you still able to produce the "white out" issue in the latest 20.1 update? We were able to reproduce and resolve in the update at least one case of this occurring in the Beta based on a report sent in by a user.

David, Creating a General Material with a low roughness and a higher specular value should give you a very reflective surface in 20.1. Altering the roughness and specular values should give you the control needed to get results similar if not the same as X9. Have you been able to test this out? If you are still getting undesirable results in this area please submit a plan to tech support so we can look into the issue further. Thanks

See attached image. Make sure use backdrop is checked for the rendering technique you're using.

PBR will not function in any way if you turn off Global Illumination. Has Mick mentioned this should never be toggled unless you are troubleshooting an issue with technical support. I would also suggest you uncheck texture compression, leaving this checked will cause 3D views to take longer to generate. If you are still having issue after doing this I would suggest contacting our Tech Support team and troubleshooting the issue further with them.

We are aware of an issue that is occurring on older (7-10 year old) ATI cards that causes the ambient occlusion to generate incorrectly as shown in the original images. We are looking into seeing what we can do to resolve this. For now the best workaround as you have already discovered is to turn off the Ambient Occlusion on these cards.

We have recently seen quite a few cases of this issue occurring across all versions of Chief old and new. In all cases so far the only common thread is that all of the users have been running Mcafee virus scan on their systems. We have been working to try to contact Mcafee and reproduce the issue so they can get it resolved. So far however we have not been able to reproduce the problem internally so if you are having this issue please contact our support team with any and all information you can recall on how you reproduced the issue. https://support.chiefarchitect.com The support team will also gather some additional system data from you that will be helpful to us when trying to resolve the problem. Thanks

We have been able to reproduce the issue when using the Windows menu to change between tabs and we are looking into it. For now I would suggest clicking the tabs to activate them. Thanks

Perry, What browser and browser version are you using? We have been able to reproduce the issue in the latest version of the Microsoft Edge browser. Could not reproduce the issue in the latest versions of any of the other common browsers though. Thanks.

For anyone reading this we strongly advise you do not do this. This will not actually resolve the issue although it may prevent the error. You will not get the features of the X9 ray tracer, you will be using the old X8 technology. This is however a good troubleshooting step that may help us try and track down why this issue is occurring on some machines. The actual problem is likely related to the error message posted in the prior post. We are looking into the issue.

Both of these are false. Bloom will have no effect on the what you are seeing. The blurry lines Perry refers are only an issue on live views on a layout page so that would not be the problem here. I am pretty sure you are referring to the ambient occlusion as Chopsaw mentioned. Another thing you might want to try is to check the 'Edge Smoothing when Idle" in the activate camera specification dialog. This will smooth out and sharpen all the edges once the camera stops moving.

We have just added embed code to our Sharing tool in the management interface for both the 360 panorama and 3D Viewer. To use it just click Make Public, click the Share button, then click on the Embed tab to see the code you will need to copy and paste into your website. You will also see there is an option for ChiefTalk. Just paste that link into your post and the viewer will automatically be loaded.

To anybody reading this do not ever do this! It will not in any way improve performance, it will in almost all cases make Chief slower. These preferences are only for troubleshooting purposes to help us try and track down what may be the cause of user rendering related issues. If toggling any these checkboxes out of their default state fixes a problem we would want to know about so we can fix the root cause.

The staff link is only for the ChiefTalk staff/admins. Not all Chief employees want to be listed here or will be. The reasoning per the developers of the forum software for the member list being removed is that this was not a common feature on any common online social community(facebook,twitter..etc do not have list of members) and a use case could not be provided to the developers of the software for why it was needed when search was available. Were you really ever scrolling through pages and pages of members looking for one specific member?

Looks like the member list was removed from the new version. You can go here for something very similar or just use the member search tool https://chieftalk.chiefarchitect.com/search/?type=core_members

We have so far not been able to reproduce any of these issues. We did however research the issue and discovered a flaw that we believed could have caused this problem. A fix was put in for that problem late last week. If you are still seeing this problem could any of you please describe in detail what exactly is happening? For example how much time is passing from when you start to post to when you click post. What browser are you using? Do you see any errors when you attempt to post? The issue above will definitely cause the described problem. If you are logging in and out of your Chief Architect account in different browser tabs while you are attempting to post it is almost guaranteed that a problem will occur. I would suggest that if you have altered your login state while ChiefTalk was open that you refresh the ChiefTalk page prior to attempting to post as this should make sure you are correctly logged in to the site. Thanks

Steve, We have seen this in the past, I think in X7 but are not aware of any issues currently in X8. Previously certain changes to render settings would cause this on certain machines. I have not been able to reproduce the issue on any of our test machines when making the those changes in X8. Could you either post or contact support with the following information: In Edit>Preferences send screenshots of the Render panel and the Video Card Status panel. This information should help us troubleshoot this further. Thanks.