There was another detail in V18.2.04 : trying to load FAS/VLX file had shown a message box about, but was silently ignored in V18.1 and before. Yes, but as mentioned, only for visualisation inside Blade, no impact to Lisp processing by the Lisp core engine.įor V18.2 we had fixed 1,2 (long-time) defects where native Lisp functions were not 100% compatible Īnd with V18.2.04 one bug was introduced (some notation for double values were not properly recognised) and one change for (repeat) function, which incorrectly accepted double values "I also found that Blade also checks the structure and syntax of all lisp customization and anything that calls AutoCAD specific applications or parts thereof" If Blade is not open, there is no impact at all to Lisp loading + processing - and if Blade is open, it analyses the Lisp file content for the "Resources" and "Functions" panel tabs - but also no impact to Lisp processing. The normal Lisp processing is not affected at all by Blade :-) Not sure what you mean with "is that BricsCad now checks and analyzes all installed lisp customization and I believe menu macros."
My system now loads cleanly and I think faster than ever. I need a small amount of recoding to make a couple routines work again but for the most part I consider Blade a good addition to BricsCad and a great way to force needed housekeeping. Blade is much more than just a lisp IDE, It can find most errors that may have worked in the past but with errors that are no longer acceptable. I then proceeded to reload all custom toolbar menus, lisp, etc. I reverted to loading only the default BricsCad cui, removing everything from On-Start, On-Doc and Appload for a fresh start. What did load in the past weather semantically correct or not may no longer work. I also found that Blade also checks the structure and syntax of all lisp customization and anything that calls AutoCAD specific applications or parts thereof. I have the menu source files but if you only have the cui's, it can be a chore to revise custom menus. I apparently had some remnants from AutoCAD that ran in Version 18.1 but won't in 18.2.04.
BRICSCAD V18 UPGRADE
The upgrade installation does save a backup but what I did not realize is that some customization, particularly partially loaded custom menu cui's need to be reloaded. What I did not realize when upgrading is that BricsCad now checks and analyzes all installed lisp customization and I believe menu macros. It is indeed a welcome addition to BricsCad. If you have an old computer or are still experiencing performance issues with this new update, then you can turn off the hardware acceleration.įor AutoCAD/Civil3D users, open the file ARDNETInitialise.ini, found at the location C:\ProgramData\CSS\ARD\Program Settings.Ĭhange the values for ‘Accel’ and ‘Antialiasing’ from 1 to 0, to turn off hardware acceleration and restart the software.īricsCAD users will find the ARDNETInitialise.I recently upgraded to the latest version, V18.2.04.
BRICSCAD V18 DRIVERS
If you experience performance issues when installing v18.1, then updating your graphics card drivers should resolve the issue. This means that commands like the Vertical Grading Editor, Cross Section Viewer, and Model Viewer will look much better and perform a lot smoother.īefore installing v18.1, it is recommended that you ensure that your graphics card drivers are up to date. Civil Site Design v18.1 will by default make use of your graphics card for all graphical processing.
0 kommentar(er)
