Startup crash under certain conditions

[rkmcswain]

Civil 3D 2013, SP1.

Set STARTUP to 2, and make sure the Sheet Set Manager palette is visible.

Close Civil 3D, then restart it.

It should open in a zero-document state, with the SSM palette visible.

Now open a sheet set, and double click on a sheet in the SSM to open it.

When I do this, I get four "Unhandled Exception" dialogs in a row, then C3D disappears (crashes!)

Can anyone else repeat this? TIA.

[Alfred.NESWADBA]

Hi,

sorry, confirmed ;(

Win7x64, Civil3D 2013 x64 SP1 German

- alfred -

[neilyj666]

Yes - same here.....

[rkmcswain]

Thanks for the confirmation.

At least I know it's not just me.

Kind of defeats the purpose of STARTUP=2 unfortunately...

[rkmcswain]

Apparently, they already know about it. Just received this reply via Subscription support.

Thank you for your update. I was able to replicate the issue with your steps and then after performing a research found that this issue is already in the hand of the development. It seems that the issue happens if there is no other drawing open. 

The ticket number is xxxxxxxxxxxx and is linked to this case.  Per process I will be closing this case out, but please know this is on the front side of support.  Behind the scenes this will remain active and further investigated by our development team here for future consideration in updates and product releases.  To further help compel the need for this functionality fix, please navigate to the link below to submit this feedback.  This will go to the project manager of the product and he in turn will bring this to the quarterly product review /discussion with the development team for further consideration on top of these efforts above.  This is a great tool and can help build further momentum in pushing this request through.

[neilyj666]

I can't help feeling a bit cynical about the priority they give bugs such as this, seems it's easier to introduce something new and in the process break an existing feature....

We'll no doubt see the importance of this issue in the 2014 release when it'll be fixed and they won't have broken anything that already works...