Bricscad V8
After upgrading to Version 8, our Bricscad users have listed out the following problems. I have reproduced below the points raised by them. Bricscad V8 is installed in Desktop PCs having Windows XP, 3.0 Gz, and 1 GB RAM. 1. Drawing of size more than 10 MB are not opening.2. If copy, paste & trim command is given, the drawing is getting closed automatically 3. No Ref Edit command in Bricscad – 84. While printing dimension position are changed, we are not getting the corresponding co-ordinate points while dimensioning, so its getting less or more of dimension.5. Client / Supplier symbols not getting printed sometimes.6. Files are automatically closed, when working & printing.7. Sometimes when we give the command save, hatch etc it automatically closed and the hourly work becomes totally waste.8. System is getting hung while giving the save & hatch command. Hence the work is getting delay.9. While giving Ref Edit the size of poly line is getting too big automatically.10. If any command is alternately repeated the system is getting hung, the only remedy is to shut down the system11. While working in ISO dimension alignment is not getting correct even the match property is not working.12. Supplier drawing is not opening. If its opens many of the details & text for notes is totally missing.13. Sometimes cursor node point is getting changed while working.14. If we use high configuration RAM also the speed of drawing is getting slow gradually, if we try to work fast.15. While deleting or hatch its show error.16. While printing, the output will be not proper result (Paper size is changing).17. While opening a new file which came from the supplier its shows that the drawing file is corrupt.18. While doing isometric drawing, Dim oblique command do not working and some dimension will be missing / changed.19. We can't use the dimensioning edit command.20. If we give undo command, it will go (undo) some 5 to 6 operations before or some times it will go to the intial stage of the drawing.Any suggestions please.
Comments
-
If the listed issues are entered as support requests we will assign them to analysts who will investigate the issues and provide you with responses.Please specify the full version number of the V8 version you use, it is displayed in the About dialog.Please attach drawings or relevant data for issues that occur with specific drawings or data.Please enter a separate support request per issue to allow for efficient processing: every issue is assigned to the most appropriate analyst, hence a request containing 20 issues is likely to make a very long roundtrip along analysts before answers will come back to you.Thanks for your cooperation,Hans De Backer
0 -
I submitted a support request for 3 - Refedit is missing and will be included in a subsequent revision.On point 7, people don't really work for 1 hour between saves in any computer program, do they?On point 17, opening a drawing which gives a report it is corrupted probably means it is!Just a general point I have found in V7 which might apply to V8 - If I select a lot of entities then issue a command to edit them, the program is likely to crash. Perhaps not the first time, but it probably will soon. Issuing a command first causes no trouble, but extensive pre-selecting is about the only action I find which can cause a crash in Icad.
0 -
This is very interesting. I've been using BricsCad for about 6 weeks (v8), and haven't noticed any of the problems described here. Some of them don't apply to me, of course, and in other cases it may be that I didn't realize that's what's happening. I'll be watching for these things.After reading the comments, I experimented a little, alternating Move and Copy, 5 times each, of over 18,000 entities in a 30 mb file I got from a client, all with no problem.I have had some crashing, but the only pattern that I've noticed is that it often seemed to happen when I zoom out quickly with the wheel after an operation. I got into the habit of saving before zooming out, and zooming out a little slower after an operation, and since then I haven't seen much crashing. Not sure if there's a connection or if my luck is improving.My main problem has been that many of my lisp routines no longer work reliably since I changed from 8.0.11 to 8.0.21, and they often cause the lisp interpreter to stop working. It's possible that the frequent re-starts that I've had to do to get lisp working again are the reason why I'm not seeing much crashing now.
0 -
Concerning selecting a very large dataset and moving/copying/rotating it: we are currently rearchitecting the way the dragged entities are generated in order to make dragging less memory-hungry and avoid crashes or hang-ups caused by out-of-memory situations. This will be improved with priority.
0 -
In defense of the original post, we have been experiencing debilitating issue with v8 as well. Most of which include corruption issues, of which i have submitted numerous examples and support requests.What is frustrating is that not all machines exhibit the same behavior. My machine has no problems whatsoever, and i love V8, but other machines can't open any files, some can't print, some show all kinds of strange behaviors like crashing to the desktop after simple commands, etc. This has rendered our purchase of 10 seats of no use as of yet.I still have faith that the problems will be resolved, but it is still my opinion that v8 was released too soon, it should still be beta.
0 -
We have had several problems with "random features" as well. Then I noticed that using V8, the memory usage on my machine went trough the roof. So I upgraded from 1GB to 2GB on 3 machines to test the theory.Since then the stability of the machines while working with V8 significantly improved.
0