CII 2019 - Performance Issues

Posted by: AaronCAD1991

CII 2019 - Performance Issues - 08/22/19 06:26 AM

Hi,

Since the upgrade to Windows 10 - CAESAR seems to be having a few problems.

An issue where crashing would occur when accessing analysis results from the graphic screen was fixed after upgrading from v10 to v11.

However there is still a general lag when moving in and out of the graphics screen, and static analysis takes significantly longer to run than usual.

What could potentially be causing this?
Posted by: Richard Ay

Re: CII 2019 - Performance Issues - 08/22/19 07:52 AM

v.11 (especially the graphics) is faster than v.10.

Please open a Support Request so that Tech Support can see your machine and work to resolve the issue.
Posted by: anubis512

Re: CII 2019 - Performance Issues - 08/23/19 09:18 AM

I'm noticing a couple issues I don't recall seeing before when upgrading to a new version.

When I open a C2 file created in Caesar 2018, it gives me an error about the configuration file if any changes were made. If I try to update the configuration file in the piping input it crashes; I have to close the piping input and update the config file thru the home screen.

Additionally, for models previously run (in 2018), Caesar seems to be sporadically saying "no restraints present in the system" when attempting to view the static results. I simply rerun the analysis and the results come back.
Posted by: Richard Ay

Re: CII 2019 - Performance Issues - 08/24/19 03:39 PM

The c2 configuration file contains the version of the software that created the file. Anytime you access a (data) directory with a configuration file NOT created or updated by the version of c2 that you're running, you will encounter a warning regarding this version difference.

The software should not crash - period. What is crashing, the configuration module or the input module? Do you know how the software was installed on your machine? Missing files or an aborted installation could account for software crashes.

When viewing the static (or dynamic) output we assume that analysis has been run with the same version of the software. You can expect quirky behavior if this assumption is violated - we often change file structure to address improvements and additional data. Version mismatches here can result in the software misreading (or misinterpreting) the data files.

If you continue to have problems, please file an SR so that Tech Support can assist you.