Author Topic: Transition Hiccups  (Read 828 times)

0 Members and 1 Guest are viewing this topic.

Master_Shake

  • Swamp Rat
  • Posts: 1447
Transition Hiccups
« on: February 08, 2018, 10:03:55 AM »
Just recently got our AutoDesk renewal and these cumulative 5% increases for the maintenance plan are going to kill our budget in no time.

When your company transitioned to BricsCAD, what hiccups or hurdles did you face and how did you remedy them?

MP

  • Seagull
  • Posts: 17461
Re: Transition Hiccups
« Reply #1 on: February 08, 2018, 10:05:34 AM »
*subscribed*
\|// Set goal. Experiment tirelessly until
|Oo| practice has become expertise.  Loop.
|- | LinkedIn | Dropbox

Cider

  • Newt
  • Posts: 60
Re: Transition Hiccups
« Reply #2 on: February 12, 2018, 04:29:05 AM »
It ran without major problems in our environment (Electrical 2D-planning, lots of block-inserting and
many attributes with data).

We started to use Bricscad with V9, for first tests we used V7+8. Transition ran smooth but slow
(50 Users) because we also introduced heavy customization (LISP + OpenDCL) during this time.
Bricscad-support was great from the beginning, we had troubles using OpenDCL which they fixed from V8
to V9 if i recall correctly. A near show-stopper was the absence of a bmp-printer,
our IT-Departement fixed that for us. The lack of the possibility to create dynamic blocks is no problem for us.

Right now we have 70+ Users, customization now also uses C# and we evaluate the BIM-Module which looks,
though very basic at the time, promising.
due to budget cuts, the lights at the end od the tunnel willbe turne d off.   

Win10 , Bricscad 10-18