Yes, but with caveats.
For the CAD manager facing a legacy crisis, it is worth its weight in gold. Recovering a single proprietary routine that controls your HVAC calculations or steel detailing can save weeks of rewriting.
For the hobbyist or casual user: Avoid. Most free "new" tools are malware traps. Hackers love to disguise keyloggers as VLX decompilers because they target engineers with admin rights.
The moment of truth is opening the resulting .lsp file. I tested three distinct scenarios:
The Good: For scenarios 1 and 2, the results were shockingly good. The "New" engine does an excellent job of retaining variable names (where not stripped by the original compiler) and reconstructing the logical flow. The indentation was surprisingly clean, unlike the "spaghetti code" often spat out by older disassemblers. It successfully extracted embedded DCL files and reconstructed them into their own separate files, which saves hours of manual resource extraction.
The "Deep Recovery" Feature:
I toggled the "Deep Recovery" option for the obfuscated files. This feature attempts to trace the execution flow to rebuild the logic structure rather than just translating instructions linearly. It worked miracles on a heavily nested cond statement that usually confuses decompilers. However, it did struggle with highly protected files that utilized string encryption. While it recovered the logic, the string literals remained as hex-coded messes, requiring manual translation on my part. This is a minor gripe, as recovering the logic is the hardest part.
For nearly 20 years, decompiling VLX was difficult. Tools existed, but they were outdated (from the AutoCAD 2004–2008 era) and produced unusable "spaghetti code" full of (setq @@ 1) variable names. They failed on modern VLX files using ActiveX or Visual LISP extensions.
When migrating from AutoCAD to BricsCAD or ZwCAD, some VLX functions behave differently. The new decompiler allows you to convert the logic into a universal LISP format that works cross-platform.
A standout feature that distinguishes "VLX Decompiler New" from the pack is its handling of mixed resources. Many VLX files are essentially ZIP archives containing FAS files, DCL resources, and sometimes even DLL wrappers. The tool acts as a two-in-one extractor and decompiler. It cleanly separates these resources into folders, allowing you to see the full anatomy of the package. This is invaluable for security auditing—checking that a downloaded routine isn't loading malicious DLLs in the background.
Yes, but with caveats.
For the CAD manager facing a legacy crisis, it is worth its weight in gold. Recovering a single proprietary routine that controls your HVAC calculations or steel detailing can save weeks of rewriting.
For the hobbyist or casual user: Avoid. Most free "new" tools are malware traps. Hackers love to disguise keyloggers as VLX decompilers because they target engineers with admin rights. vlx decompiler new
The moment of truth is opening the resulting .lsp file. I tested three distinct scenarios:
The Good: For scenarios 1 and 2, the results were shockingly good. The "New" engine does an excellent job of retaining variable names (where not stripped by the original compiler) and reconstructing the logical flow. The indentation was surprisingly clean, unlike the "spaghetti code" often spat out by older disassemblers. It successfully extracted embedded DCL files and reconstructed them into their own separate files, which saves hours of manual resource extraction. Yes, but with caveats
The "Deep Recovery" Feature:
I toggled the "Deep Recovery" option for the obfuscated files. This feature attempts to trace the execution flow to rebuild the logic structure rather than just translating instructions linearly. It worked miracles on a heavily nested cond statement that usually confuses decompilers. However, it did struggle with highly protected files that utilized string encryption. While it recovered the logic, the string literals remained as hex-coded messes, requiring manual translation on my part. This is a minor gripe, as recovering the logic is the hardest part.
For nearly 20 years, decompiling VLX was difficult. Tools existed, but they were outdated (from the AutoCAD 2004–2008 era) and produced unusable "spaghetti code" full of (setq @@ 1) variable names. They failed on modern VLX files using ActiveX or Visual LISP extensions. The Good: For scenarios 1 and 2, the
When migrating from AutoCAD to BricsCAD or ZwCAD, some VLX functions behave differently. The new decompiler allows you to convert the logic into a universal LISP format that works cross-platform.
A standout feature that distinguishes "VLX Decompiler New" from the pack is its handling of mixed resources. Many VLX files are essentially ZIP archives containing FAS files, DCL resources, and sometimes even DLL wrappers. The tool acts as a two-in-one extractor and decompiler. It cleanly separates these resources into folders, allowing you to see the full anatomy of the package. This is invaluable for security auditing—checking that a downloaded routine isn't loading malicious DLLs in the background.