Slow Isogen

[Anonymous]

I have a problem with P3D isogen when I link it to an excel spreadsheet using LDT Setup.  I do this to bring piping design conditions in from a master line list. I have setup two styles, one that is linked to the file and one that is not.  If I run an Iso on the same line number using both setups the one that is linked to the excel takes at least 20 times longer than when not linked.  I have pulled the line list off of the server so everything is running local.

Any advice is appreciated.

[Anonymous]

I have a problem with P3D isogen when I link it to an excel spreadsheet using LDT Setup.  I do this to bring piping design conditions in from a master line list. I have setup two styles, one that is linked to the file and one that is not.  If I run an Iso on the same line number using both setups the one that is linked to the excel takes at least 20 times longer than when not linked.  I have pulled the line list off of the server so everything is running local.

Any advice is appreciated.

[h_eger]

I tested with P3D 2018_
without LDT, P3D for 11 pipelines.

Iso Creation start time : 31.07.2018 10:36:49
Iso Creation finish time: 31.07.2018 10:46:54
Duration                : 00:10:04

with LDT, P3D for the same 11 pipelines.

Iso Creation start time : 31.07.2018 10:56:29
Iso Creation finish time: 31.07.2018 11:01:54
Duration                : 00:05:25

in my LDT file (as * .xls) 23 attributes are anchored for information in the head of Iso.

with LDT almost 50% faster.
I can not understand the problems

Hardware:

[h_eger]

I tested with P3D 2018_
without LDT, P3D for 11 pipelines.

Iso Creation start time : 31.07.2018 10:36:49
Iso Creation finish time: 31.07.2018 10:46:54
Duration                : 00:10:04

with LDT, P3D for the same 11 pipelines.

Iso Creation start time : 31.07.2018 10:56:29
Iso Creation finish time: 31.07.2018 11:01:54
Duration                : 00:05:25

in my LDT file (as * .xls) 23 attributes are anchored for information in the head of Iso.

with LDT almost 50% faster.
I can not understand the problems

Hardware:

[Anonymous]

any other ideas on this I have a line that generates in 4 mins not linked to the excel file and when linked to the excel file it takes almost 1/2hr.  It is not a hardware issue we are running top of line computers with tons of RAM, solid stat hard drives NVidia G force graphics cards.

[Anonymous]

any other ideas on this I have a line that generates in 4 mins not linked to the excel file and when linked to the excel file it takes almost 1/2hr.  It is not a hardware issue we are running top of line computers with tons of RAM, solid stat hard drives NVidia G force graphics cards.

[quentin.contreras]

@Anonymous I came across this Autodesk Network Article, Performance problems after running isometrics with LDT in Plant 3D. Might be related to the issue you are seeing?

[quentin.contreras]

@Anonymous I came across this Autodesk Network Article, Performance problems after running isometrics with LDT in Plant 3D. Might be related to the issue you are seeing?

[Anonymous]

I have the same issue with LDT files. Have had the issue since 2014 version.

I have also tried XLS and XLSX file types and there was no difference between them.

Not using LDT - Duration : 00:00:27

Using LDT - Duration : 00:00:15 (in iso log file) + 2:44 (using stopwatch) for the dialog box to disappear.

I have attached our LDT file. It has other lookup tables etc that autocompletes cells but I doubt that is the issue.

Does anyone that doesn't have this issue able to share their LDT?

It is like it opens excel in the background for every field instead of once to read it all.

Thanks

[Anonymous]

I have the same issue with LDT files. Have had the issue since 2014 version.

I have also tried XLS and XLSX file types and there was no difference between them.

Not using LDT - Duration : 00:00:27

Using LDT - Duration : 00:00:15 (in iso log file) + 2:44 (using stopwatch) for the dialog box to disappear.

I have attached our LDT file. It has other lookup tables etc that autocompletes cells but I doubt that is the issue.

Does anyone that doesn't have this issue able to share their LDT?

It is like it opens excel in the background for every field instead of once to read it all.

Thanks

[DGRL]

Same issue here

With LTD is freaking slow 

Just use LISP to fill in the data

LSP is 100 times faster

[DGRL]

Same issue here

With LTD is freaking slow 

Just use LISP to fill in the data

LSP is 100 times faster

[Anonymous]

Any chance you could share your LISP? Or is it heavily influenced by your title block?

[Anonymous]

Any chance you could share your LISP? Or is it heavily influenced by your title block?

[DGRL]

My lsp is still in development stage 

All you need is a template that includes ATTDEFS and 1 excell file with the data 

[DGRL]

My lsp is still in development stage 

All you need is a template that includes ATTDEFS and 1 excell file with the data 

[PatrickByrne]

I posted similar problem a couple of months ago. From what we can see it appears to be starting and closing Excel for each attribute. It is unworkable in the present form, it would be good if they changed from an Excel to a CSV file.

What we do now is use excel to create a script file.

We have our LDT file with all the information. Firstly we produce our Isometrics then get a file list and use Vlookup in Excel to get the info. We then copy/paste this information into another Excel file which produces the script file.

Next open drawing in the folder and run the scrip file, it now opens each drawing and fills in the title block.

Sounds complicated but the attached picture should help.

[PatrickByrne]

I posted similar problem a couple of months ago. From what we can see it appears to be starting and closing Excel for each attribute. It is unworkable in the present form, it would be good if they changed from an Excel to a CSV file.

What we do now is use excel to create a script file.

We have our LDT file with all the information. Firstly we produce our Isometrics then get a file list and use Vlookup in Excel to get the info. We then copy/paste this information into another Excel file which produces the script file.

Next open drawing in the folder and run the scrip file, it now opens each drawing and fills in the title block.

Sounds complicated but the attached picture should help.

[Anonymous]

Thanks all for the feedback its good to know I am not the only one having this problem.  Using Lisp and scripts is all great options, but it would be nice if Autodesk would get their crap together and fix this problem.  I had to modify my "C:\Program Files\Autodesk\AutoCAD 2016\PLNT3D\PnPIso.exe.config" to allow Iso time to not time out after 30 mins because some of my lines take 40-50 mins to produce and some not at all.

I Guess it is time to go back to CADworx

[Anonymous]

Thanks all for the feedback its good to know I am not the only one having this problem.  Using Lisp and scripts is all great options, but it would be nice if Autodesk would get their crap together and fix this problem.  I had to modify my "C:\Program Files\Autodesk\AutoCAD 2016\PLNT3D\PnPIso.exe.config" to allow Iso time to not time out after 30 mins because some of my lines take 40-50 mins to produce and some not at all.

I Guess it is time to go back to CADworx

[DGRL]

@Anonymous

If it takes 40 to 50 min to generate then you have a misconfigured system 
Ar eyou working in the cloud?

On networtks?

Local?

How is excel installed?
Do you have .net framework 2.0 and 3.5 also installed?

I know LDT is slow but 45 min avarage is not normal

[DGRL]

@Anonymous

If it takes 40 to 50 min to generate then you have a misconfigured system 
Ar eyou working in the cloud?

On networtks?

Local?

How is excel installed?
Do you have .net framework 2.0 and 3.5 also installed?

I know LDT is slow but 45 min avarage is not normal

[JameseeT3KVM]

Same issues here. More than twice as long with LDT file. 

Anyone logged a support ticket for this one yet? Just curious. 

Thanks!

[JameseeT3KVM]

Same issues here. More than twice as long with LDT file. 

Anyone logged a support ticket for this one yet? Just curious. 

Thanks!

[Anonymous]

everything is local, the model the excel file nothing is over WAN in fact I even turned off my network connection to test and had the same result.  I currently have NET framework 4.o installed.

[Anonymous]

everything is local, the model the excel file nothing is over WAN in fact I even turned off my network connection to test and had the same result.  I currently have NET framework 4.o installed.

[DGRL]

You might wanna try to install the whole .net framework family 

3.5 incl 2.0 anf for Plant 3D 2016 4.6 for 2017 and 2018 4.7 i thought 

Please refere to the install instructions for the specific version of .net that fits your version of p3d

[DGRL]

You might wanna try to install the whole .net framework family 

3.5 incl 2.0 anf for Plant 3D 2016 4.6 for 2017 and 2018 4.7 i thought 

Please refere to the install instructions for the specific version of .net that fits your version of p3d

[Anonymous]

The Plant 3D installer automatically installs NET Framework. I just checked to make sure and mine at least has the latest for what is needed for what version I'm using (2018).

It doesn't allow you to install older versions either and the latest is backwards compatible with all previous versions (so it says).

I just did a test looking at the task manager on the details tab and the PID (process ID) for excel changes 48 times for me, which is the same amount of columns I have in my LDT file. This means it is opening and closing excel every time it reads a field. This is what causes the slow down. This can only be fixed by Autodesk, if only they were listening...

[Anonymous]

The Plant 3D installer automatically installs NET Framework. I just checked to make sure and mine at least has the latest for what is needed for what version I'm using (2018).

It doesn't allow you to install older versions either and the latest is backwards compatible with all previous versions (so it says).

I just did a test looking at the task manager on the details tab and the PID (process ID) for excel changes 48 times for me, which is the same amount of columns I have in my LDT file. This means it is opening and closing excel every time it reads a field. This is what causes the slow down. This can only be fixed by Autodesk, if only they were listening...

[DGRL]

@Anonymous

Only thing i can advise from this point on is to use LISP instead of LDT.

This should be a lot faster.

[DGRL]

@Anonymous

Only thing i can advise from this point on is to use LISP instead of LDT.

This should be a lot faster.