Bangalore, India
In one of my earlier posts, you read about the Bricscad user preference poll and the results.
In this post, we bring you the complete list of requests that have been made by Bricscad users in India with status comments and workarounds where applicable.
# 1 : Bigger, more powerful raster engine - Users want the capability to load 200+ MB of image sizes without having Bricscad crawl. Pan, Zoom and other drawing creation, editing functions must work effortlessly even with large images attached. This is especially important in India where many CAD/GIS service providers traditionally work with large satellite imagery.
Status : Support request has been filed with Bricsys. Watch out for Bricscad V12. We hope to see an enhanced, better raster engine.
# 2 : Real-time rendering of 3d model - even when they are manipulated using the Real Time Motion tools. This is one of the most requested, most missed feature in Bricscad by mechanical CAD folks.
Status : Support request has been filed with Bricsys. Watch out for Bricscad V12. We hope there may be some improvement. One of the reasons why AutoCAD offers better real-time rendering response is because the code is optimized for Windows, while Bricscad uses OS-neutral code that must run on Windows, Linux, Mac etc. Performance is a tradeoff?
# 3 : Independent drawing context between multiple drawings - Switching from one drawing document to another causes any active command in the first drawing to get cancelled when a new command is started in the second drawing document. Command line text windows are shared and are not independently provided for each drawing document.
Status : Support request has been filed with Bricsys. Watch out for Bricscad V12. The requirment has been noted by Bricsys.
# 4 : Match properties command - does not work between objects from one drawing to another.
# 5 : Copy & Paste of drawing objects does not work between AutoCAD and Bricscad - AutoCAD objects, when copied and pasted in Bricscad, becomes OLE objects (not desired). It would be nice if Bricscad can recognize AutoCAD objects and paste them as Bricscad entities in the drawing. By the way, AutoCAD does not recognize Bricscad entities either. It would be good if both CAD programs talked to each other.
# 6 : Color Face or Color Edge command does not display dialog box - unlike in AutoCAD. You need to manually type in the color value in Bricscad.
# 7 : The FILTER and TORIENT command are still not available natively in Bricscad.
Workaround: We have, however, implemented these two commands in GeoTools as GT_FILTER and GT_TORIENT and it is available as FREEWARE commands.
# 8 : Support for dynamic blocks - This is available, but only partially in Bricscad. The request for this exists in India, but is not very strong.
Status : Support request has been filed with Bricsys. It is on Bricsys radar and is one of the requests made by the global Bricscad user community as well.
# 9 : Image insert not consistent with AutoCAD - A raster image of pixel size 1075x766 inserted into Bricscad with default parameters acquires a size (drawing units) of 1.0 x 0.7126. In other words, the horizontal dimension becomes 1.0 and the smaller dimension accordingly scaled as per pixel aspect ratio. In AutoCAD, the drawing units size of the image is exactly 1075x766. In other words, 1 pixel becomes 1 drawing unit.
Status : Support request has been filed with Bricsys. We are eagerly waiting for this to be fixed.
# 10 : Command line support for XSOLIDS commands in Bricscad Platinum.
Status : Support request has been filed with Bricsys. This is not a top-priorty request, but would be nice if implemented.
# 11 : Implementation of Indian and ASME codes in the X-Hardware section of Bricscad Platinum.
Status : Support request has been filed with Bricsys. This is not a top-priorty request, but would be nice if implemented.
# 12 : Support for MPOLYGON (from AutoCAD Map) objects in Bricscad.
Status : Support request has been filed with Bricsys. This is not a top-priorty request, but would be nice if implemented.
# 13 : XSolids Array must be associative - when X-Hardware items are used in the array. At the moment, it is not. Only regular solids are associative.
Status : Support request has been filed with Bricsys. Users would love to see this fixed.
# 14 : Pasting an Excel table must appear in Bricscad as a TABLE object.
Status : Support request has been filed with Bricsys. This is an important feature to have which is currently not happening in Bricscad.
# 15 : Undo option in LayOn / LayOff / Offset commands.
Status : Support request has been filed with Bricsys. This is very useful for CAD drafters and in my opinion, it should be an easy fix. I hope Bricsys fixes this quickly.
# 16 : Retain AutoCAD Map Object data when doing an WBLOCK export from Bricscad.
Workaround : Use the GT_WBLOCKBC command of GeoTools and save your object data. This command is part of the FREEWARE commands in GeoTools.
# 17 : CONVERTPOLY command in Bricscad - to convert light -weight to heavy-weight polylines and back.
Workaround : There is a GT_CONVERTPOLY command in GeoTools, which is part of the FREEWARE routines. With this command, you will no longer miss the absence of ConvertPoly in Bricscad.
# 18 : Native support for MLINES, and MLEDIT.
Workaround : You can use the BCADTOOLS FREEWARE routine from Bricsys, which implements the MLINE command. It works very well. However, the MLEDIT command is not yet supported.
Discover Bricscad, discover GeoTools-AutoCAD & GeoTools-Bricscad, discover TechCenter . Brand new ways to work smarter in CAD!!
Comments