"Floating point division by zero" in Structural Module

[Anonymous]

Hi,

When I attempt to run the influence surface generator or analyze the structure, I am getting a "Floating point division by zero"  error.

This is with 2016 service pack 3. In the past, I had an issue with a similar error on 2014, and it was fixed by changing graphics card settings. In this case, it is on a laptop with integrated Intel graphics only.

Is there a fix for this problem?

[Anonymous]

Hi,

When I attempt to run the influence surface generator or analyze the structure, I am getting a "Floating point division by zero"  error.

This is with 2016 service pack 3. In the past, I had an issue with a similar error on 2014, and it was fixed by changing graphics card settings. In this case, it is on a laptop with integrated Intel graphics only.

Is there a fix for this problem?

[david.geeves]

Hi David,

I'm not sure what would be causing this so it would be best if I had a look at your data files to see if I could reproduce it.  It doesn't sound like the graphics card issue that you say you experienced with 2014 and I haven't had any other reports that this occurs when trying to analyse a structure/run the load optimization.

If you attach the project data file (with any linked beam or section files if appropriate) to a reply to this post I will see if I can spot anything obvious.

Kind regards

[david.geeves]

Hi David,

I'm not sure what would be causing this so it would be best if I had a look at your data files to see if I could reproduce it.  It doesn't sound like the graphics card issue that you say you experienced with 2014 and I haven't had any other reports that this occurs when trying to analyse a structure/run the load optimization.

If you attach the project data file (with any linked beam or section files if appropriate) to a reply to this post I will see if I can spot anything obvious.

Kind regards

[Anonymous]

Thanks David,

I've attached the model.

[Anonymous]

Thanks David,

I've attached the model.

[david.geeves · Accepted solution]

Hi David,

I notice that you are running version 2016.1 (the original 2016  version) in which there were a few issues with linked beams that may be causing this.  I would seriously consider applying the latest patch to the 2016 version which corrects these issues.  To get around this problem you can embed the linked beams into the project data file (this needs to be done one at a time with 2016.1 but can be done all at once from the first patch onwards).

            

You can work with the embedded beams in the same way as in the separate files and this gives huge advantages when transferring load from the analysis.  If you really want to work with separate beams files then you can relink them again.

If you are going to apply a patch I suggest you apply patch #3 which will give you 2016.4.  Also note that the latest version is 2017.

I hope this helps

Kind regard

Dave Geeves

[david.geeves · Accepted solution]

Hi David,

I notice that you are running version 2016.1 (the original 2016  version) in which there were a few issues with linked beams that may be causing this.  I would seriously consider applying the latest patch to the 2016 version which corrects these issues.  To get around this problem you can embed the linked beams into the project data file (this needs to be done one at a time with 2016.1 but can be done all at once from the first patch onwards).

            

You can work with the embedded beams in the same way as in the separate files and this gives huge advantages when transferring load from the analysis.  If you really want to work with separate beams files then you can relink them again.

If you are going to apply a patch I suggest you apply patch #3 which will give you 2016.4.  Also note that the latest version is 2017.

I hope this helps

Kind regard

Dave Geeves

[Anonymous]

Thanks David, that has worked perfectly.

[Anonymous]

Thanks David, that has worked perfectly.

[Anonymous]

Thanks David, that has worked perfectly.

[Anonymous]

Thanks David, that has worked perfectly.