Hi,
I am trying to generate an isometric drawing out of the piping shown in the picture. I know that in this case I probably should create an ortho view instead, but the customer wants isos... What to do...
The green part is generated fine when I try to pinpoint the problem using quick iso. The red part is impossible. The error log is completely clogged up with this message: "WARNING - The count of created skew entities is not correct." So, I guess it's a problem with the angle? When I use "offset angle" before I create the iso it generates. But I have to put in 30 (or so) degrees...
Got any ideas? I can understand that isogen can have difficulties with certain angles but this is ridiculous. By the way, I'm using Plant 3D 2016...
Solved! Go to Solution.
Hi,
I am trying to generate an isometric drawing out of the piping shown in the picture. I know that in this case I probably should create an ortho view instead, but the customer wants isos... What to do...
The green part is generated fine when I try to pinpoint the problem using quick iso. The red part is impossible. The error log is completely clogged up with this message: "WARNING - The count of created skew entities is not correct." So, I guess it's a problem with the angle? When I use "offset angle" before I create the iso it generates. But I have to put in 30 (or so) degrees...
Got any ideas? I can understand that isogen can have difficulties with certain angles but this is ridiculous. By the way, I'm using Plant 3D 2016...
Solved! Go to Solution.
Solved by hean117. Go to Solution.
Can you please upload the PCF file.
Or the 3D drawing and details which project configuration Metric or Imperial.
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
Can you please upload the PCF file.
Or the 3D drawing and details which project configuration Metric or Imperial.
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
PCF file is attached.
As a sidenote I can say that it works like a charm in Plant 2017 with the exact same settings (just migrated the project). The customer wants it in 2016 though...
PCF file is attached.
As a sidenote I can say that it works like a charm in Plant 2017 with the exact same settings (just migrated the project). The customer wants it in 2016 though...
I ran the PCF you attached in both 2016 and 2017 and they look identical.
I ran the PCF you attached in both 2016 and 2017 and they look identical.
Something was wrong in the isoconfig file and I couldn't figure out what. I took a fresh file with the basic Plant settings in it and it worked. Then I had all the fuss with configuring everything again the way I wanted it. Now it works fine!
This is what sucks the hardest with this program. Just put all the controls in the GUI and this won't happen.
Something was wrong in the isoconfig file and I couldn't figure out what. I took a fresh file with the basic Plant settings in it and it worked. Then I had all the fuss with configuring everything again the way I wanted it. Now it works fine!
This is what sucks the hardest with this program. Just put all the controls in the GUI and this won't happen.
Hi
"Just put all the controls in the GUI and this won't happen"
If not already maybe this is something you can add to the Idea Station
Tom
Hi
"Just put all the controls in the GUI and this won't happen"
If not already maybe this is something you can add to the Idea Station
Tom
I don't agree with "put everything on GUI",at least not now.
You see, what make isoconfig.xml so unfriendly is WHER IS THE FXXXXXX MANUAL?? (look at AVEVA PDMS,the manual is too many to see them all)
As my opinion , using xml has its advantage now - very flexible to modify your iso,sometimes even looks like take advantage of programming bug.
If using GUI environment,what we can do is all determined by ADSK programmer. Then we take a look at P3D...well,from 2011 to 2017 ,still need to improve some very basic functions (even thought PDS, PDMS..etc. have already show them what abilities a plant design software should have.)
P3D make me feel like "We sell program first, then using then money to improve it step by step",but if a user can do all the thing on PDMS or other software,WHY SHOULD I CHANGE TO P3D? ( well....I know,I know ,because the owner force us to :[ )
I don't agree with "put everything on GUI",at least not now.
You see, what make isoconfig.xml so unfriendly is WHER IS THE FXXXXXX MANUAL?? (look at AVEVA PDMS,the manual is too many to see them all)
As my opinion , using xml has its advantage now - very flexible to modify your iso,sometimes even looks like take advantage of programming bug.
If using GUI environment,what we can do is all determined by ADSK programmer. Then we take a look at P3D...well,from 2011 to 2017 ,still need to improve some very basic functions (even thought PDS, PDMS..etc. have already show them what abilities a plant design software should have.)
P3D make me feel like "We sell program first, then using then money to improve it step by step",but if a user can do all the thing on PDMS or other software,WHY SHOULD I CHANGE TO P3D? ( well....I know,I know ,because the owner force us to :[ )
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
I apologize for the inappropriate words I used.
I apologize for the inappropriate words I used.
Can't find what you're looking for? Ask the community or share your knowledge.