PDF layer mess BUG

[Cris-Ideas]

Hi,

This subject was previously brought up on forum but there is no reply from Autodesk regarding misleading information that this bug was fixed.

Obviously it was NOT.

In short:

Problem is that when exporting drawings to PDF objects are placed on layers that are incorrect. Also there are problems with following appearance overrides on assembly level and using proper DVR when exporting to 3D PDF.

This was brought up for AI 2015. In the meantime there was information given by a member of Autodesk Customer Support Jon Dean that this "is fixed in 2017". (2017 was not relised at that time).

This however turned out this is not true. Nothing is fixed.

Since at some point Autodesk informed that "this is fixed" could someone from Autodesk inform us, users experiencing this "fixed behaviour" when can we expect you to keep your word and fix this, but rally fix so it works, rally works.

I have prepared video showing this behaviour.

Also I have prepared data set you can download form my A360 drive at: http://a360.co/2c1kZgA

Cris.

[Xun.Zhang]

Hi, I will look into it for sure and give update later. Would you mind try another way like Print to PDF? hope it can help you to workaround firstly.

[Cris-Ideas]

Hi

I would not mind at all to try. In fact I was advised to do so several times by Autodesk employees and every time I tried outcome was the same, that is:

There is equal mess in layers if use use export or Save copy as pdf. I have gave this answer every time I was asked.

To pront as pdf you need pdf pronter installed (that I do not think is included in Inventor). Using PDF creator there are no layers inside pdf but pdf get ridiculously big.

So current status for me is that this is just not working.

Cris.

[Xun.Zhang]

Hi Cris,

I am looking into it and just as you've mentioned, it's known for us from Jon. there are two defects were tracked internally, the state shows that the fix most likely go to Inventor 2017 R3, but I can't promise here. please let us know the result once you update Inventor 2017 to R3 when it online in short.

Hope it helps a little bit.

[Cris-Ideas]

Hi,

I must say this is not helping.

Basically same answer "it is fixed in next SP, or relise" I got from Jon quite some time ago.

Couldn't anyone rather than writing "it should be fixed", "I can't promise"  just take a data set I provided and check if it really works in next relise?

Than you could just post " I have checked, problem you show in the video is no longer there, you just need to wait a moment for next SP" ?

This would be much better.

So could you make this small effort and verify in practice whether this is in deed working in next SP, and ensure us and your self that it is in deed working properly, and not was fixed like last time.

Cris.

[Cris-Ideas]

This

was not fixed in AI 2017.R3

[Xun.Zhang]

We are looking into it now.

[LishuangLu]

Hi Cris,

Thanks for reporting this to us! This is indeed a problem and has been existing there for a long time.

We used the same mechanism for PDF export and DWF export, when export to DWF, you could see different sheet is associated with different layers, and each sheet entities will be controlled by its own layers.

But in PDF viewer, all the sheet layers will show up together, so it may lead confusion and mess up when check the visibility of each layer.

And this behavior is existing for a long time, it may take more time for us to investigate the solution, before we provide the solution, would you mind using DWF for export and layer visibility control first? No worry, we will still work on the investigation and fixing for the root of the issue.  

Thanks very much for your support as always!

Regards,

-Lisa

[Cris-Ideas]

Good morning all Autodesk guys and ladies monitoring this forum.

It is yet another day when I come to work and first thing I do is to take care of pending Inventor issues.

Thank you Lisa for illuminating a bit this issue with PDF layer mess.

I was of course not aware about PDF and DWF similarities, because I do not use multi-sheet DWFs, as there are more problems with clients when they are to view them.

But since you brought this up in your post, first thing I did today was to try how it works. And guess what -

There is a problem with layer mess in DWFs also.

So I suppose you should also start to investigate this, and finally fix it so it has some logic in how it works.

I admit in DWFs mess is a lot smaller than in PDFs. Still it is there.

Unfortunately I have to address other issues with inventor I am currently discussing with Autodesk + I have my own work to do, so I am unable to prepare documenting video, and data set right now.

I however invite you to contact me via e-mail, and arrange skype (or other) call to discuss this problems.

I must also make a remark over how long this is taking to fix.

From my experience actions taken by customer support in case of this problem report are highly unsatisfactory and in points ridiculous.

I have reported this issue 3 times. first time for AI 2015.

Two times I was informed that problems I show ARE FIXED in next SP or version. I then asked again customer support to check if in fact problem I have documented is no longer there.

I was then reassured that it was verified and it is fixed.

Well obviously both times I was given this information it was not true.

How do you feel about this way of treating your customers?

I am rather disappointed (not to use other words) that I am not being treated seriously.

Cris.

[LishuangLu]

Hi Cris,

Good morning! And thanks very much for your quick reply and testing.

I guess I didn't catch up the issue in DWF, so I would like to follow up with you via email, here's my email address Lishuang.Lu@autodesk.com.

Feel free to send email to me. Hopefully we could understand your issue thoroughly then get some process in investigation and fixing.

Thanks,

-Lisa

[Cris-Ideas]

Hello everyone,

I have prepared video showing exactly mess with layers in pds and dwf. It uses data set I have provided but for your convenience I also make it available for download:

http://a360.co/2fNq7Z4

(make sure you have sound on)

Cris

[LishuangLu]

Hi Cris,

Thanks for providing the dataset! We have tracked this into our internal bug system, and currently developer is working on the fix. I'm going to validate the fix from developer, if the fix is good, would you like to have a try?

Thanks a lot for your support as always! And please stay tuned for our fix.

Thanks,

-Lisa

[Henry.Huang]

@Cris-Ideas

An article was created for this issue. And if developer team update the incident has any update, the article will update. 

 https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/sfdcarticles/sfdcarticles...

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[Cris-Ideas]

@LishuangLu

Of course I would like to try. I am waiting a long time for that.

Cris.

[Sofia.Xanthopoulou]

Hi @Cris-Ideas,

I just saw that your support case has been closed. As this is a very interesting topic, I'd like all users to be able to benefit from your experience. 

Please, be so kind and publish another post with the outcome of this case and mark it as accepted solution. 

Thank you very much for your input and participation in the forums 

Best regards

[Cris-Ideas]

@Sofia.Xanthopoulou

Hi,

So it seems there is a chance this problem will be fixed in near future as Autodesk managed to prepare update that fixes it (I have tried, it works).

Only thing that is not certain is whether this will be included in next SP or update or not.

So until it is issued we do not know for sure.

Cris.

[Sofia.Xanthopoulou]

This is correct, @Cris-Ideas, I totally agree.

But at this very moment, your last post is the answer (solution). By highlighting it we could spare other users from searching for other solutions. This is their benefit. 

An accepted solution unfortunately is not always what we want to hear - it's just the truth - whether we like it or not  

I am really sorry for the inconvenience 

But let's stay positiv  A new year is coming and another 365 for Autodesk to make customers happy 

Best wishes

[Cris-Ideas · Accepted solution]

Still not Fixed properly!

Although there was  a fix on the way it is not fixing the problem entirely.

So the problem is that layers are duplicated and objects that should go on on layer are in fact on two layers with the same name.

So for this PDF for example "intellectual property.." note goes on different Visible 0 ISO layer than the rest of the visible Objects, and in idw it is obviously on the same layer.

Autodesk :

Is it rally so hard to do things properly?

Is it really to hard to fix it once for all.

And yes I have all the latest updates and SPs installed.

And yes I am still using AI 2017 because had no time to test 2018 and move.

Cris.

[johnsonshiue]

Hi Cris,

How are you doing? I understand it is frustrating to see a given issue not addressed properly. However, it is possible the fix would work in certain cases but not all cases and this case is a different one, though it looks similar. Or, the issue was misunderstood and the issue was not fully fixed. Did you submit a case for this particular issue already? If yes, what is the case ID? Do you have a defect ID that I can follow up on? Could you share the files reproducing the behavior (johnson.shiue@autodesk.com)?

Many thanks!

[Cris-Ideas]

Hi Johnson,

I am pretty busy and had no time to supply new support cases. I have a bunch of them waiting.

Also I must say I feel there was very little outcome from all I had done in the past to brought issues in to Autodesk attention and document bugs I had found.

As for this one, here is a procedure that you can use to reproduce this behaviour :

1) Just make a idw.

2) crater sketch symbol with text. assign this text to be on the Visible layer

3) insert view on to the sheet

4) insert sketch symbol

5) verify if symbol disappears if if you turn off Visible layer

6) export PDF

7) report bug to Autodesk.

9999) wait very long until it is fixed (sorry for that, but that's just how it is)

Hope this helps.

Cris