Chief_QA

You can now go to your preferences dialog and on the reset options panel there is an option to reset migration if you want to migrate again from X12.

If you want the X13 Real Time Ray Tracing to work for you it would be better to get the AMD RX6000 series card if you want to stay with AMD.

3 hours ago, RL-inc said:

Ed-

I found the option in the screen shot below - "Animate windows when minimizing and maximizing"

It was checked and now I have turned it off- will run with it for a bit this am and see how it goes.

 

I am curious- do you think this is relate to whether or not the library browser is docked or floating?

That is what I am trying to find out, to see if this setting can mitigate this issue on Windows.

Glenn, I don't believe so, I am just trying to determine why some users on Windows don't have this issue at all, just gathering more information is all at this point.

23 minutes ago, RL-inc said:

Continued correspondence with Tech Support-

Reply to CA above followed by tech support response

 

 

"I looked at monitor settings and I am currently at 250%- that said there is no way I can work at 100%- way too small for my old eyes.

In the past I have worked with my library browser floating and had no issues.
I did see on Chief Talk that keeping it docked in the original position can solve the issue but not particularly convenient for me.

Hopefully CA can get this resolved soon.
Please keep me posted on the progress."

 

 

 

"Thanks for your patience. I know it can be quite frustrating. We hope to have a fix in X13 but we won’t know for sure until we get to the public beta and get the software into more hands."

 

 

 

So really no fix for this in the current version?

Has anyone that has dealt with come up with a reasonable solution?

 

I keep my SSA current and will upgrade to X13 when available but what about those that cannot upgrade - they would just be stuck dealing with it?

Doesn't seem right.

 

 

 

Just out of curiosity, do you have this setting On or Off?  It can be found in the Display settings area.

On 2/20/2021 at 11:49 AM, RL-inc said:

Ok just happened again.

Just opened a new layout file and set it up for a job - then drug it to adjacent monitor and original plan screen toolbar tweaked our- see attached screen shot.

 

Has tech support had any luck with this-

Hard to be productive when you have to rebuild toolbars all the time 

 

Do you have any side windows on your secondary monitor?  If so, keep all of your side windows on your primary display, library browser, project browser, etc, this will reduce the chances of having toolbar issues.

View>Toolbars  it is a toggle

I have seen both iterations, I get them all bunched up in the corner like I showed, and when chief is restarted or reset the toolbars then become all on 1 line.

This is what it looked like for me.

6 minutes ago, glennw said:

Ed,

Is it possible that once this happens once, the toolbar configuration is overwritten and this then prevents it from happening again using the same toolbar configuration - and this is why it is hard to duplicate in the same Chief session using the same toolbar configuration?     

Glenn, I don't know at this point yet.  I was also able to reproduce it on my PC, the first time was on a mac.  Both times it happened I was opening a new plan.  My toolbars were locked, I added the layerset and dimension default controls to them, and working in both monitors going back and forth with the side windows floating.  I think the floating side windows is the key, at least for me.  This last time I had just gone into the library browser then went back to the primary monitor did a new plan and bam.

Good news, I got it to happen.  Now if I can just do it again.

11 hours ago, glennw said:

Ed,

I have been playing around a bit and can duplicate the toolbar problem - but only occasionally.

I will keep trying.

This is just a bit of a rave as things come up.

Do we need to move this subject to a different thread or is it OK to continue here?

At one stage I thought the problem maybe related to having an imperial plan opened at the same time as my metric plans - but nothing repeatable.

One thing that I haven't seen mentioned is that the wonky toolbar definitions are saved and remain wonky so that you cannot just change back to the original definition.

One thing that I have noticed is that the toolbars can move around when you have 2 plans open, which use different layer set names, different default dimension names or different default set names. I especially run into this when I open some one else's plan that may have longer names for these items in the dropdown box. A long name can push all the tools along to the right (sometimes off the screen) as you switch from one plan to the other. 

Another thing I noticed after Reseting Toolbars was this tool bar titled Time Tracker.

It contains a couple of Plan View tools that don't work, along with some other tools that look like they don't belong there.

There are duplicate Plan View tools in their own toolbar that do work.

Any ideas?

Glenn, that is very helpful information.  I am planning on looking at this in the afternoon, I have a few more things to get done before I can get to this issue.  We can just use this thread for now.  Are you using the oob toolbars or a custom configuration?

Thanks Glenn,

What I need to start is the exact resolution of each monitor, dpi, scaling, etc.  Then which one is your primary monitor, what windows of chief are running on each monitor, a copy of your toolbars and the layout you have, side windows, which ones are displayed, where are they, docked, floating, then what are you doing when you notice them getting messed up.  Are you sending stuff to layout, are you opening views, anything that can help us help you would be great.  Screen pics are great to give me an idea of your window layout.

I remember this issue well, I reached out to our users on April 28, 2020 requesting more information so we could reproduce the problem in house, and we didn't get any of the details that I was asking for to help us help our users.  I was prepared to set up as similar of a system as I could find, had a dev engineer ready to help troubleshoot, and was ready to fully commit to reproducing the issue.  After no information was provided, I moved on to the next issue on my list.  Any forums I have ever been on when an internal engineer contacts me for additional information I am eager to provide whatever they need to help me out.  If we would have gotten that information we needed back then this issue would most likely have been fixed in that next update.

X12 will run on Big Sur, we are still evaluating whether or not X12 will run on Mac devices that have the M1 chips, the Rosetta translation app is not friendly to OpenGL apps, but we are in the midst of receiving hardware and will test and evaluate.  We will be updating our system requirements when we have completed this evaluation.

Are you running the latest update 22.2.0.54 released on 4/21?

We have been trying to reproduce this in house for a while, is there anything you can provide that will help us determine what the trigger is?  Are you floating certain toolbars and/or side windows? Are you using multiple monitors or only a single monitor? Are your multiple monitors the same resolution?  Is this on a laptop and you use a docking station? What was the last thing you did when you noticed your toolbars were scrambled?  Are you switching between views?  What OS, screen resolution, screen dpi setting, video card, and can we get a copy of your toolbars?

We just released an update to resolve this issue. 

The 21.3.1.1 update is now live.

We are working on a fix and will have an update out as soon as possible.

For his raytrace issue it could be this problem:

The missing DLL was provided in a windows update KB2999226 which may not have been installed on your system or maybe failed to install.  If you run the Visual C++ Redistributable for 2015 found on the Microsoft website it should resolve your problem. 

https://www.microsoft.com/en-us/download/details.aspx?id=48145

 

There is a plethora of information available in this thread that I wished I had located years earlier.  In particular, how various hardware configurations can effect rendering and ray-tracing times in Chief, along with the the importance of a thorough understanding of light sources and their individual impact upon ray tracing.  Somewhere in this thread one of the participants states the value this information has to potential Chief clients and that cannot be understated.  The lack of concrete technical documentation that discusses various processors (i.e. I7-XXX vs Xeons), video cards (i.e. Nvidia GeForce 980m vs Quadro M4000) and how they directly relate to performance within various aspects of Chief Architect was ultimately the deciding factor for me to pursue Revit.  Despite it being more expensive and more complicated, I was able to source the afore mentioned information much more easily. 

 

It is important to know some of the geeky details, such as:

 

-Is a blazing fast processor more important than a top of the line video card?

-Does the amount of memory on the video card directly effect performance in Chief?  

-Does a SSD hard drive vs a mechanical one make a difference if we don't have a ginormous amount of RAM to begin with?

-How many CPU cores/threads can Chief effectively use, and when and where do we benefit from 24 cores vs, say, 8?   (this is the Xeon vs I7 debacle)

-At what point does added RAM no longer truly make a difference in Chief?

-At what point does the bottleneck of the system switch from CPU to GPU and vice versa?

 

 

When someone is building a machine for a very specific purpose it is of upmost importance to them to allocate their funds properly.  I have a feeling many other people like me have found precious little information on the specifics of just how Chief Architect software interacts and utilizes hardware.  It may not be the sexiest of information, but for many (including me) the lack thereof drove me to Revit.

 

Do you have a link for this data?  I went to their website and I didn't find anything like you mentioned at all.  I wouldn't consider "most affordable processor" defining any performance criteria like you mentioned.  All I saw was some old outdated information involving a few laptops and a couple of HP desktop computers.  Nothing covering Windows 10 at all, in fact some of the listings didn't even have Windows 8.1, only Windows 8.  I especially like their Mac solution which is just run Bootcamp, no native solution at all.  Running a directX software based system on a platform designed for OpenGL would not be something I would ever want to do.

Do you know if they perform any OS certification testing like we do?  We are Windows certified for Windows 10 and have been doing this since their certification testing became available.  Our products are also used at Microsoft for their own OS update testing.

I would really like to see this data and how we could improve our system by just recommending a few high end systems or cards and eliminate the freedom of our users to "run what they brung"

Yes it is, you need to request it from our website in the normal fashion, there should be a choice to request either X7 or X8 now.

In X6 it would be better to bring in as a PDF, in X7 we improved the bringing in tabbed formatted text from outside of Chief and you could do live text in X7.