Revit 2018 print crash

[Anonymous]

Hi there,

I have an annoying problem. I have a batch print tool which workes fine up to Revit 2017. Now, in Revit 2018 the same tool Crashes 😞

The problem is, it can't be debugged.

I print several PDFs after each other. 

SOme settings are done and after the command:

_mPrintMgr.SubmitPrint();

the pdf is created. Then the code runs over everything again to make the second pdf, and after the command:

_mPrintMgr.SubmitPrint();

A windows message "Revit has stopped working" appears and Revit is closed without any further messages of saves.

Does anyone experience the same problems or Is there something changed with the printmanager in Revit 2018 ?

[matthew_taylor]

Hi Remy,

I've found bugs with DWF and DWG, so I'm not altogether surprised. I think there's been multi-thread tinkering going on behind the scenes.

You don't have something that takes the focus from Revit while printing, do you? (I've reported bugs about this while exporting DWG/DWF.)

Have you looked in the Journal to see if there are hints as to the origin of the issue?

Edit: Oh, and can you create a minimum reproducible solution? I'll test at my end.

[jeremytammik]

Dear Remy,

Thank you for your report.

Sorry to hear about the problem.

That sounds annoying indeed.

Yes, as Matt suggests, please submit a reproducible case for him and the devteam to analyse:

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

Thank you!

Best regards,

Jeremy

[Anonymous]

I am doing nothing special. (Just take the first revit plot sample code from the net and try it in Revit 2018).

I have a collection of sheets I want to plot. I loop over them and fill the CurrentCiewSheetSet method with 1 sheet at the time.

foreach(View plotview in mytoplotviews)

{

 ViewSet _mViewSet = new ViewSet();

  _mViewSet.Insert(plotview);

_mViewSheetSetting.CurrentViewSheetSet.Views = _mViewSet;
_mViewSheetSetting.Save();
_mPrintMgr.SelectNewPrintDriver("printername");
if (!_trans.HasStarted()) _trans.Start("Set profile");
_mPrintSetup.SettingName = "plotprofilename";
_mPrintMgr.PrintToFileName = "pdfname";
if (_trans.HasStarted()) _trans.Commit();
if (File.Exists(_mPrintMgr.PrintToFileName)) File.Delete(_mPrintMgr.PrintToFileName);
 _mPrintMgr.SubmitPrint();
}

This code workes fine in Revit 2010,2011,2012,2013,2014,2015,2016,2017 BUT apparently the rules have been changed in Revit 2018 😞

What happens in Revit 2018 is, the first PDF is made, then in the second loop on the  _mPrintMgr.SubmitPrint(); line, a windows message saying "Revit has stopped working" appears and that's the end of revit. In debug mode I have set a breakpoint, but it never comes there. Revit just crashes.

[jeremytammik]

Dear Remy,

Thank you, perfect.

Please package that code snippet as a macro in a minimal sample document to produce a reproducible case for the development team to analyse:

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

Please understand that they are not capable of browsing the Internet or implementing Revit add-ins or macros.

They work in a completely different development environment.

The only way for us to communicate the details of the problem to them is via a reproducible case.

Thank you for your understanding and cooperation.

Cheers,

Jeremy

[cprice]

We've also reported this as part of the Revit Preview Beta about a month ago.  We've been advised Autodesk are looking into it this week.  But I've spoken to many app developers dealing with the Revit Print/Export API and all are experiencing the same instability.  Autodesk advises it seems to be more prevalent with Windows 10.

In terms of our business case:

• Impact on your application: unable to support Revit 2018
• The number of users affected: thousands
• The potential revenue impact to you: at least $5000/month that it isn't resolved
• The potential revenue impact to Autodesk: Debugging time and resolution/rollout of bug fix.
• Realistic timescale over which a fix would help you: ASAP

[matthew_taylor]

I have to agree with @cprice with regards to the gravity of the situation.

Let's not forget the wasted paper after bad print settings have been used, and the wasted time walking to the printer and back each time.

So far we collectively have issues with DWF/DWG/Paper printing/exporting. Revit 2018.1 can't come soon enough.

To save us having to collectively create a known bug list, I hope Autodesk implement my latest idea:

https://forums.autodesk.com/t5/revit-ideas/known-bug-list/idi-p/7079586

It kinda fits with Autodesk's new policy about openness, don't you think?

[matthew_taylor]

Noted in comments below https://forums.autodesk.com/t5/revit-ideas/known-bug-list/idc-p/7119086#M8547.

[Anonymous]

Guys,

I am facing same issue while printing revit crash 2018. Do you all get any solution?

[cprice]

This was resolved with the Revit 2018.0.2 update.

[Anonymous]

Thank you,

This get resolved