Cadworx 2020 and 2020 R1 isogen batch issues?

Anyone else having issues with continuations showing up properly with 2020 or 2020 R1?

the below pictures show the issues with continuations. neither of them show continuation text. if we wblock out the piping to a new dwg and redrop the line we dont seee the extended continuation graphics circled in red but the cont text still wont populate. when the line is dropped in 2019 the continuation graphics work fine.

I did some Tests, looks like if continuation graphics is set to anything other than 0 the continuation message is not displayed. I logged a support case for feedback, perhaps you could do the same.

Hi Everyone,

Wondering if there has been a fix for the continuation issue? We are about to run ISO's on a project and are still only able to get continuations to work if continuation graphics count is set to 0. Thanks in advance.

Snitker

I believe a fix for that was made available some time ago.

im running 2020 R2 now AND THIS STILL ISNT FIXED! come on Hexagon!

This was fixed in one of the service packs in 2020 R1 already ? Recently did training on 2020 R2 and we used continuation graphics without problems.

Can you check if it reproduces for one of the default styles ? Might be style or model related.

It's listed as being addressed in the 2020R1 HF1 readme.

ill have to check it with the default style but we had hexagon on the phone and confirmed it still not working right.

happens in all styles and various models.



doesnt appear to have been fixed.

see attached pics using ootb isogen style. Cont graphics set from 0 to 3 in order

It works on my installation. Are you perhaps toggling the single PCF checkbox for IGB ?

no not toggling the single pcf radio button

Can you upload your model here? Just a question when moving to R2 did you create a new config file ? in 2020 R2 the setting was renamed to IsogenContinuationGraphicsLevel.

And there lies my biggest complaint... Changing the config files without proper notice or conversion.
We are constantly reusing old models but the undocumented config files changes is causing many many headaches. This goes along with the CPM & CEM blocks where the settings are saved.
Backwards compatibility is possible if you jump through 5 hoops, light yourself on fire, and jump off a high dive. It didn't used to be that way.

Good thing the Whats New explains all of this



Vanman, I don't see that change anywhere in my Dialogs or Imperial.cfg files. My settings still show: IsogenContinuationGraphicsCount=0

Is there something special that needs to be done?

They don't tell you all the fine details.
Case in point is my last TR.
Support noticed my config was the wrong version by looking at the LanguageFile setting.
What was LanguageFile=English.dic is now LanguageFile=English.xaml
No where in the What's New do you see a description of this.

Sorry Guys, looks my one computer had a different language file loaded, so it changes how that setting is displayed in the dialog box. The actual config setting remains unchanged.

That being said though, when upgrading its usually a good idea/workflow to setup a fresh config file from scratch for a new project.

Thanks for confirming, it would be great if they would start putting in ALL changes that affect the users.

I agree it is best to use the config that comes with each version and modify those settings to match your project. Then you can use that one as a default going forward. It saves a lot of confusion down the road and since HCAS doesn't document their changes, you should notice them at that point.

nope we didnt do that, but we cant use R2 due to a POD graphics error and linking back to our excel that spits out data from out line lists. R2 is dead in the water for us now. I will test this out though cutting a new cfg and see if it fixed that

see attached line no. 1703

even with the ootb R2 cfg file the cont graphics set to 2 or 3 look messed up

A quick glance looks like the continuations are working on your model, sort of. Used a setting of 3.

The one problem I did pick up was the continuation on the valve V1738.

I am really not sure why the pipe is not shown dotted and where is it getting supplemental flow arrow from ? Continuation is also shown on the Tee and not at the flange. I am guessing it has something to do with the ubolt and the pipe.

Trey can you try do a convertfromprjdata on those components ?

i did a convertfromprj with no change to that continuation

Trey, I am not sure why this is not working correctly on your model. To my mind it points to something model related, but could be mistaken.

Can you try the test model I created on your side.

Trey, how you are you adding the Isogen Supplemental flow arrows?

I see them appear on the Isos, but I am unable to locate them in the model ?

I moved your model to different coordinates, the supplemental flow arrows are then not shown on the Isos and the continuations from what I can see are coming through correctly.

i fear we mustve had a dirty/corrupt model. ive copied the pipeline to a new sheet, then remodeled the pipe and nipples and its now showing the graphics fine. ill have to see if i can track down how this particular piper made this model. it does appear to be fixed when i remodel this myself in a clean drawing.

Could it have been a model from a previous version? We have recently seen issues with older models being used in a newer version and causing problems, by re-drawing the models the issues were fixed.

I don't recall the exact scenario, but we put the model into a database and had it redraw in a new model and it was better.

You might try running a change spec on the parts so CADWorx redraws the items instead of using the database that doesn't redraw everything.

they were 2020 R1 models but all 2020 CW variants had broken cont graphics when set to 2 or 3. now R2 PODgraphics is messed up and wont let us drop isos into borders that populate data from excel sheets lol. it never ends!

Could always use ISOWorx as an independent and stable option to update your titleblocks. We are adding in some new status tracking functionality and other enhancements that should be available in the next few months.

The PGP problem is a little annoying. An interim workaround is open the models in 2020 R1, run batch isos and then close without saving.