Announcements

Between mid-October and November, the content on AREA will be relocated to the Autodesk Community M&E Hub and the Autodesk Community Gallery. Learn more HERE.

Problems with Civil View in Max Design 2013.

Problems with Civil View in Max Design 2013.

Anonymous
Not applicable
1,848 Views
8 Replies
Message 1 of 9

Problems with Civil View in Max Design 2013.

Anonymous
Not applicable
Fired up Civil view today and was confronted by the following message upon selecting Swept Object Editor.

runtime Error: Not Creatable: Civil_View_Swept_Object

Upon attempting to create a new element, the following message appeared ..

Unknown Property: "total" in undefined.

A quick peruse of the MaxScript listener showed the following.

>> MAXScript Rollout Handler Exception:
-- Runtime error: Not creatable: Civil_View_Swept_Object <<
>> MAXScript Rollout Handler Exception:
-- Runtime error: Not creatable: Civil_View_Swept_Object <<
-- Error occurred in DYNFUNaddSOSelement(); filename: C:\Program Files\Autodesk\3ds Max Design 2013\stdplugs\(CivilView)\CivilViewRollouts.mse; position: 869684; line: 17393
-- Defined in encrypted script
-- called in BUDYNadd.pressed(); filename: C:\Program Files\Autodesk\3ds Max Design 2013\stdplugs\(CivilView)\CivilViewRollouts.mse; position: 970778; line: 19097
-- Defined in encrypted script
>> MAXScript Rollout Handler Exception:
-- Unknown property: "total" in undefined <<

It may be coincidental but I applied PU06 this week.

The last time I used Civil View was before that update.

Has anybody got a clue what's happening. ?
Chris
0 Likes
1,849 Views
8 Replies
Replies (8)
Message 2 of 9

Anonymous
Not applicable
I have the same problem since last week. I did some unistall/re-installation but it didn't worked out.

Please assist.
0 Likes
Message 3 of 9

Anonymous
Not applicable
I'm getting a similar but different error on importing FZP traffic vissim data&colon;

-- Error occurred in i loop; filename: C:\Program Files\Autodesk\3ds Max Design 2013\stdplugs\(CivilView)\dsimImport.mse; position: 36048; line: 751
-- Defined in encrypted script
-- called in BUDYNokok.pressed(); filename: C:\Program Files\Autodesk\3ds Max Design 2013\stdplugs\(CivilView)\dsimImport.mse; position: 39720; line: 808
-- Defined in encrypted script
>> MAXScript Rollout Handler Exception:
-- Runtime error: Not creatable: Civil_View_Traffic_Data_Constraint <<

also installed PU06, but not sure if it was working before that since it had been a while.

Tried re-installing civil view, running repair on max, etc, but didn't work. Next step I guess will be full re-install to see if that helps...

-SJ
0 Likes
Message 4 of 9

Anonymous
Not applicable
I have now completely reinstalled 3DS Max design 2013 and the problem persists....

I'll have to try to escalate..

Rgds

Chris

Edit...

Problem solved by deleting the Civil View Configuration file. Can't for the life of mr remember where it was.. but the folder containing the filewas called enu, A very helpful chap at Autodesk Support located it, deleted it and voila... return of civil-view.

Sorry I can't be more helpful.

Chris
Message 5 of 9

VincentSheehan
Advisor
Advisor
I found the issue.

Delete the "CivilView.ini" file located in the Windows users folder shown below.

C:\Users\yourusername\AppData\Local\Autodesk\3dsMaxDesign\2013 - 64bit\ENU\en-US\plugcfg

You have to unhide the folders and also reselect the Country Kit and Units in Civil View. This worked for me so I hope it helps.

Vincent Sheehan

Sr. Civil Designer
Poly In 3D Blog

Message 6 of 9

Anonymous
Not applicable

I'm having this same issue in Max Design 2014 SP5, but the previous 2 fixes listed above aren't working for me when trying to import FZP files.

 

Anyone have a clue?  I don't recall if I've installed anything new lately, possibly just SP5.

0 Likes
Message 7 of 9

Anonymous
Not applicable
Thanks Vsheehan, That fix worked for me. I was running Max 2014 SP5 and it was spitting out hte same error. We had a couple of other Civil errors last week that this fix worked on as well.

Cheers for the help
John
Message 8 of 9

Anonymous
Not applicable

This fixed it 2016 too! Cheers man - I would never have found that!

Message 9 of 9

Anonymous
Not applicable

Thank you so much, deleting the civilview.ini worked for me as well:) 3DS Max 2016.

0 Likes