Upcoming LDCad 1.7 Beta 1

[N. W. Perry]

This is one of those situations that was never an issue in the pre scripting era of the program.

I will try to improve it, but this really shows the need of a whole new core loading system (LDCad 2.0).

Here's another funny side effect: if I apply some mutation to a type 1 line, then comment it out, the comment will have greater decimal precision than the real type 1 line (i.e., 8 places rather than 6). I can go back and forth like this until I quit and re-launch, then the lower precision is "baked in".

I think I understand why this is from prior experience, but it's important to note that the script is acting on the lines as LDCad sees them internally, not the literal source lines that will be written to the file.

Editing to add: I'm still getting a fairly consistent crash after using my script. It's not immediate, but it does seem to accompany closing a file and/or the application, and only ever happens when I've been using the script.

Says it's a Wine problem, but I'll attach the log in case anyone can make sense of it:

  backtrace.txt (Size: 6.63 KB / Downloads: 2)