Artifacts on PDF problem - Revit 2020

[lasse.juul2KP56]

Hi

Now I'm seriously starting to be concerned that Autodesk is really owned by The-Devil inc...

Got my brand new Microsoft Surface laptop 3 with it's best hardware configuration and yet… My 8 years old heavy Dell Workstation is having flawless performance compared to this(!)

This is not even big and complex models, but i do use the graphic opportunities for all it's Worth.

Issue:

Sometimes the screen just flickers when zooming: theres big "white spots" on the scrren, these wil differ in size and appearence while zooming.

I use cutePDF-writer, and I simlply can't accept that we still have to deal with 3. party software in 2020! It's for the most common an basic task! Take you together Autodesk! It's a shame! A disgrace!!! The only reason I can figure out why it's like this, is that it makes us dependent on problemsolving at least four different Levels: the hardware, the operation system, Revit and the PDF-software. Then Autodesk can just sitt and Wash thier hands doing nothing and blaming everyone else to be the problem. It's a mess!

After more than 20 years I think I've used at least 2 month in just Autodes related software issues. And some of the Things haven't even been solved yet. And probably never will because this Company that heeves zillions of dollars every year only care about their stock-holders

[RobDraw]

This is a user help forum for users to help users.

The complaint department is down the hall to the left.

[pendean]

>>>...Microsoft Surface laptop 3 with it's best hardware configuration and yet… My 8 years old heavy Dell Workstation is having flawless performance compared to this...<<<
>>>...This is not even big and complex models...<<<
>>>... Sometimes the screen just flickers when zooming: theres big "white spots" on the scrren, these wil differ in size and appearence while zooming....<<<

Thanks for the product review and confirmation we all need to stay away from Microsoft's Surface3 with REVIT.

Autodesk Feedback is over here if you want them to post in the REVIT system requirements to specifically list this device as one to avoid https://www.autodesk.com/company/contact-us/product-feedback

[lasse.juul2KP56]

I don’t see any solution in the replies.

If you’re too sensitive or Autodesk-saved to endure any little gasp for air, then go on and don’t reply.

IT’S AN ACTUAL PROBLEM!

And I don’t believe mother-Autodesk should be spared for the users frustration. I’m not pointing fingers on any other than the ones who should be in task. We’ve been more or less Attached to Revit since it has more or less become the industry-standard. I would expect more from a Developer that heaves in zillions every year. The list of essential annoying bugs is still endless.

And issues like the one I’m pointing out, shouldn’t happen in 2020. We’re talking about THE most essential any professional drawing programme should do: make flawless outputs straight out of the Box. It’s frustrating, tiresome and exceptionally time-consuming to be thrown around between Autodesk: Revit, Microsoft: Surface + Win10, Adobe/CutePDF: PDF-writer and Intel: graphic card hardware+software… -Where’s the problem? The thing is none of them seems to take any responsibilities to solve it, they careless and arrogantly just pass the responsibility on to the others.

And in between I can’t do any work other than trying to solve this before I get broken.

So if any if you out there has experienced the problem described in my initially text and as seen in the screendumps and has got a solution, then please share it with the rest of the communities.

[pendean]

Thanks again for re-confirming Microsoft Surface 3s are not appropriate for REVIT users. Your passion is coming through that it fails.

You can make REVIT suggestions to Autodesk yourself here https://forums.autodesk.com/t5/revit-ideas/idb-p/302 and here https://www.autodesk.com/company/contact-us/product-feedback

Thanks again.

[RobDraw]

One person with problems does not make it incompatible. It could very well be a local issue. In order for it to be a compatibility issue, it needs to be repeatable in a completely different environment.