Known Bug List

[matthew_taylor]

I'm vetting Revit 2018 right now.

So far, I've found a bug with the UI (User Interface), and three with the API (Application Programming Interface).

It would be great if Autodesk had a public list of bugs! (Don't show security related bugs...)

That way we can:

1. Not waste time reporting bugs again.
2. Make an educated decision about using the latest version.
3. Be aware of limitations.
4. Have an idea when a bug will be fixed.
5. Minimise testing time.

This is a no-brainer. It helps everyone.

Thanks for reading. (And your up-vote!)

p.s. The bugs I have found with Revit 2018 so far (all have been reported):

• UI: Click editing of Multiline Text parameters doesn't work. (Due to be fixed in version 2018.1) (Workaround is to edit in Properties palette.)
• API: Starting a Windows Explorer process when batch creating DWF. (Causes 'save recovery file?' crash.)
• API: Starting a Windows Explorer process when batch creating DWG. (Causes 'save recovery file?' crash.)
• API: Unknown bug when batch creating individual DWG files. (Causes 'save recovery file?' crash.)
• API: Not actually a bug, but undocumented new behaviour...Undocumented new exception when using PromptForNewFamilyInstance: See here.

[matthew_taylor]

• API: IndependentTag.Create causes exception when the only loaded tag family was loaded via the API.

[matthew_taylor]

• API: Duplicating a linear dimension style produces wrong result. To quote @Anonymous "dimensionType.Duplicate("NewType") now returns a dimension with a name "SecretInternalLinAngDimStyle..." instead of NewType" (http://thebuildingcoder.typepad.com/blog/2017/04/whats-new-in-the-revit-2018-api.html#comment-3331378631) No reproducible case submitted yet.
• API: Batch print to printer using printManager.SubmitPrint. (Courtesy of @Anonymous.) https://forums.autodesk.com/t5/revit-api-forum/revit-2018-print-crash/m-p/7079572/highlight/true#M22793 No reproducible case submitted yet.

[jeremytammik]

Thank you very much for the constructive suggestion and all the work you put in so far assembling and maintaining this!

[matthew_taylor]

Thanks @jeremytammik. I think I'll add a post to the other (non-API) Revit forums. I'm hoping people will add their own items!

[dzanta]

current bug found and under investigation (Pick Line tool does not function properly)...

https://knowledge.autodesk.com/community/screencast/8ea8320f-a1d6-44a2-a590-4220cf3c1cf1

[matthew_taylor]

API: Document.Import for DWG. (Courtesy of @AnatolyCEL.) https://forums.autodesk.com/t5/revit-api-forum/error-in-revit-2018-dwg-import/m-p/7120427

[matthew_taylor]

@Discussion_Admin This is a legitimate 'Revit Idea', that is doubling as a list for known bugs. Please move it back to the 'Revit Ideas' section. Any questions, please see @jeremytammik.

[mikako_harada]

Hi Matt, 

Jeremy pointed me to this discussion.  First, thank you for raising good point.  How to track issues has been a topic that we as support team discuss every once in a while. We certainly want to improve it.  Our moving more toward forum and fostering community based as oppose to using DevHelp Online in a closed system, for example, has certainly  opened up visibility to some degree (if not in a convenient form). 

I don't have a good solution to answer in exhaustive way.  But I will bring this to support team and discuss.  

In a mean time, just as an idea, how about making one Revit API forum post and titled "Known Change Request", and make the post "float" at the top.     And the community will keep adding the issue when they encounter one.  Each will be a short summary with link pointing to a separate post discussing the detail. This way, the community can check back the known report.

What do you think?  Do you think it's worth a try?      

[matthew_taylor]

Hi Mikako,

Thanks for your message. (Thanks @jeremytammik!)

I do think that is a good idea, though I was kind of hoping for a more holistic approach. That is, the whole of Revit, not just the API.

Perhaps one at the top of the Arch Forum, one on the Collaboration forum, and one at the top of the API forum?

I think there needs to be a list of items with a status and (Revit) version for each.

As an 'in the future' item, perhaps the internal Autodesk system could have a checkbox to make a description public, and each week the database is dumped to a webpage? This sort of thing would save Autodesk customers hours and hours. (I just got an Autodesk Enterprise Priority email about re-work. This idea would save a *lot* of re-work!)

Let's be honest, I think it'll be a work in progress, but what's important is that a start is made. So, YES! Yes, please.

Thank you.

[matthew_taylor]

Hi @mikako_harada,

Is there any news on this?

A general FYI:

These items have been fixed in the Revit 2018.0.2 patch/hotfix. (I believe you'll also need to apply the license server hotfix discussed here.)

• API: Starting a Windows Explorer process when batch creating DWF. (Causes 'save recovery file?' crash.)
• API: Starting a Windows Explorer process when batch creating DWG. (Causes 'save recovery file?' crash.)
• API: Unknown bug when batch creating individual DWG files. (Causes 'save recovery file?' crash.)

[Anonymous]

I hate to cross-post but only just found this thread.

The following seems to be an undocumented fix to prior (incorrect?) behavior relating to View3D CropBox property:

https://forums.autodesk.com/t5/revit-api-forum/setting-cropbox-for-a-3d-view-with-revit-2018/td-p/71...

[c_hanschen]

Can anyone provide a update on the problems of batch printing and exporting in Revit 2018??

I think every one with batch functionality printing/exporting in Revit 2018 is encountering the same problems (Revit Crashes)

I found this update:

Autodesk Revit 2018.0.2 Hot Fix

It seems to handle some of these problems, no more Revit Crashes for me, but now it is showing this message some where along the batch:

Attempted to read or write protected memory. this is often an indication that other memory is corrupt.

(this message does not appear with same project in Revit 2017)

Does anyone here tried this hotfix in relation to these problems?

Does anyone has this same error message?

Revit does not crash, but the code has stopped, some where along the batch, not always at the same point.

Hoping for more info on the status of these issues.

Chris Hanschen

LKSVDD architecten Enschede

The Netherlands

[matthew_taylor]

Hi,
Did you apply the licensing update? I hear that was part of the solution.
See http://thebuildingcoder.typepad.com/blog/2017/05/hotfix-resolves-export-and-print-issue.html

[c_hanschen]

I first applied only the bug fix.

After that I had the other error, not all the times, but more than once.

After that I applied the license update .

Not sure if I had the error after that.

I will give it a during test, later this day or tomorrow, with more than 1 project and a lot of files.

I will keep you updated!

Thanks for your reply.

Chris

[c_hanschen]

*** NOT SOLVED ***

I tried 2 projects:

project #1 small project. no linked files

Run: 8 sheets to PDF, 8 sheets to DWG and 8 sheets to DXF

I runned it 2 times, no problems

project #2Bigger project, linked Files

Run: 4 sheets to PDF, 2 books PDF of 5 and 42 sheets, 4 sheets to DWG, 4 sheets to DXF

I runned it 2 times:

First time: No problem

second time: "Attempted to read or write protected memory. this is often an indication that other memory is corrupt."

The problems are not completely solved!

It's the same project, the same compiled dll, the same set of sheets and export options, when you run it a lot of time, you can wait for it to crash.

By the way:

on this page: http://thebuildingcoder.typepad.com/blog/2017/05/hotfix-resolves-export-and-print-issue.html 

the following errors are mentioned :

• 12894987 Revit crashes when exporting / printing Sheets via API while a modal dialog is open
• REVIT-112607 Revit crashes when exporting / printing Sheets via API while a modal dialog is open -- 12894987

These errors are not new in Revit 2018..!!!!

Also Revit 2017 crashes when printing AND exporting (same Run) from behind a modal form.

(No debug-able error, Revit Crash)

I asked questions about this in this topic:

https://forums.autodesk.com/t5/revit-api-forum/background-processes-monitoring-or-checking/m-p/71274...

BobbyC.Jones asked me this question: 

"How are you launching your 'tasks', from code behind in a dialog box?"

@matthew_taylor, you probably remember this topic of last week, you participated also.

And yes, that was the problem in Revit 2017, I rewrote my code, the dialog (UI) is closed first, than all the prints and exports are made. problem 'solved'.

So if this is mentioned as a bug for 2018, my conclusion is: Revit 2017 still has the same problems.

read more on my previous topic, it was solved there by taking time brakes between prints & exports, this sounds like the same threading/memory problems.

If somebody of Autodesk is working on a new bug fix for this issues, I will be willing to test is. (don't know if that is good English, but you will understand  )

Chris Hanschen

LKSVDD architecten Enschede

The Netherlands

[jeremytammik]

Dear Chris,

I passed on your message to the development team, and their response is the same as always: we need a reproducible case.

http://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

Can you provide one, please, for me to pass on to them?

Thankk you!

Cheers,

Jeremy

[c_hanschen]

@jeremytammik, thanks for your response.

Yes, I will provide this information for you, but it will be later on this day.

In this case, do you need the full 'Visual studio solution'?

Or can it be a compliled dll and addin-file?

Chris Hanschen

LKSVDD Architecten Enschede

The Netherlands

[jeremytammik]

Full solution for debugging. Better still, a Revit project with a built-in macro... however, I expect that would be too much to ask? And maybe not even possible technically?

Thank you!

Cheers,

Jeremy

[matthew_taylor]

Hi @c_hanschen,

Good updates.

I wonder what sort of PDF export you are doing? As in, what driver?

The driver I use has a post-print event that I had to subscribe to in order to happily tell Revit to progress to the next PDF.

I've not had any trouble with DWG in Revit 2017. I'm interested to see your VS solution to see if there's any impact on my macros!