Chief_QA

Not sure why your email was rejected, but we looked into this and it looks like you sent another a few minutes after the first one.  We received that one successfully.  The rejection must have just been a bump in the internets.

In any view that you would like to display other plans, just click on the floor number in the toolbar and it will open that dialog.

You can show multiple plans in one camera view using the reference display.  You can even position them as well.

The only difference between a studio driver and a game ready driver is the internal branching at Nvidia. A game ready driver may not have a hot fix that a previous game ready driver had, it may have come from a different code branch line which did not have the hot fix applied.  The studio drivers are all pulled from main and then tested for stability, if a previous studio driver had a hot fix, all future studio drivers will as well.  Also, the studio drivers are tested more thoroughly and provided to all Nvidia partners to test and respond if there are any issues found.  This is not done with the game ready drivers.  These are the only differences that I am aware of.

It's available in my digital locker now.

13 hours ago, VHampton said:

Anyway, X15 will be arriving at a digital locker near you soon. 
 

Next week for sure! She promised. 

 

Maybe even sooner...

The 528.24 driver looks to be good, no new issues found.

We are currently testing this driver and will let you know.  Unfortunately, the release notes have never listed any of our issues as fixed, our only way of knowing is from our internal contact at Nvidia.

Since you have been installing many different versions of drivers, I would start with a clean install of 526.98 if you haven't done that already and see what that gets you.

The 526.98 11/16/22 Studio driver is the latest driver that is approved to be used, the later drivers have an issue, we are working with Nvidia to resolve this issue.

19 minutes ago, DeLayDesign said:

@ChiefArchitect

This is new...

The software then crashes.

Can you try and rollback to the 526.98 Nvidia Studio Driver and see if that fixes the error?

1 hour ago, GaryOhmer said:

527.56 crashed on me so I went back to 522.25 and it also crashes - seems all of the drivers are crap

You should contact tech support, there may be a setting that fixes it or if we can reproduce the issue then we have a better chance of fixing it.

It looks like Nvidia just released a new version today, 527.56, may be related to the issues in 527.37?  Not sure, we are installing and testing 527.56 now.

Is this what you are looking for?

There is usually an "Upgrade" or "Get New Version" button that you have to click on to get the Public Beta to be displayed and made available.

Windows has that as well, you can have multiple desktops and switch between them.

If you just want your X12 toolbars in X13 you can reset the migration and then when prompted migrate your toolbars over.  To reset the migration just go to Edit>Preferences and go to the Reset Options panel, on this panel there will be a button Reset Migration.  Click it, restart Chief and it will prompt you for the migration, select only the toolbars and that should get you your X12 toolbars into X13.

Edit>Edit Behaviors>Connect CAD Segments  you turned it off.

We recommend using the Nvidia Studio drivers, they are more stable, go through more extensive testing, and are on a scheduled release cycle, plus we get the pre-release builds so we are able to test and provide any feedback to Nvidia, if needed.  We don't evaluate the game ready drivers, they are released randomly and too frequently for us to track.

Actually I think the Rainbow Tool being referred to is this.

2 hours ago, HumbleChief said:

Curious, what "solid state drive" are you seeing and how can you know it's "way below standard?" Not to challenge your knowledge but curious to learn how you can make the diagnosis from the picture posted. Thanks

The SSD is listed in his signature, which is probably where Rene noted it.

I agree, the SSD could easily be upgraded to a 512GB or 1TB, and then just get an RTX card, since you have the AMD already, go for the RX 6000 series.  I have the RX6800xt and it is comparable to the Nvidia RTX 3080, but any of the RX6000 series card would be a tremendous step up from what you currently have.

5 hours ago, Kbird1 said:

 

Any chance this is also causing this Preferences Error I am working on solving with Anne in Tech.Support ?

 

- it only happens on a MAC Laptop with the latest Version installed , and resetting Prefs. and rename the .ini has not helped.

 

It may be the same issue, if this issue only happens on the X13.2 update, but I am not 100% sure.  This one may be unique to your system.

Ok, thanks for the details, it is helpful.

19 minutes ago, SusanC said:

Yes, this MacBook Pro and the other MacBook Pro had each been upgraded to the update for X13 and from Catalina to Big Sur.

The Mac desktop in the office, which is used rarely, we discovered is too old to run Big Sur so it will be replaced with a new Mac desktop.

Which did you do first the update to Chief or the upgrade to Big Sur?

1 minute ago, SusanC said:

In my case the endless loop error messages and subsequent crash happened regardless of what I tried:

1.  I tried opening through the Chief X13 "Open Plan" option that is offered at start up.

2.  I tried opening through my local copies stored on my hard drive by double clicking on the file.

2.  I tried opening through a plan downloaded to my desktop that was not syncing to Google Drive.

3.  I tried opening through Google Drive as I've done for years (and yes, I know that is not the preferred method and I will no longer be working that way - I will be downloading).

4.  My issues started after upgrading to the newer version of X13 and upgrading to Big Sur.  

5.  My error messages referenced Catalina.

6.  Very rarely I could open a plan without issues, but 99% of the time there were errors and crashes.  

7.  Uninstalling X13, rebooting, and installing the older version of X13 has been the solution for my computer and for the other designer in my office.

 

My husband was in software development for many years so I know how challenging it is to fix bugs.   I am incredibly appreciative of all the manpower it took behind the scenes to figure this out - thank you!!

 

 

When you say you upgraded Big Sur, do you mean you upgraded from Catalina to Big Sur or just upgraded Big Sur to 11.5.2?  And was this the case for all of your macs seeing the problem?