Not that anyone asked for my opinion but I do feel like you all are taking the wrong approach in saying “it’s never going to work”.
You took the time to post about it here, take the extra 2 minutes to upload a rhino file of the the specific object(s) repeating the poor printing behavior, share your system info via System Info command and then hopefully the developers, with enough user examples, can nail down exactly what causes some of the issues you are seeing… (sometimes only one user sample is needed)
It’s obviously not failing as code, you can see in your snip 99% of it is working, just your one column or whatever that is went wild.
User examples, contributions, and patience will only help the developers help us, the users, by making better code that handles more edge cases. Sometimes that takes awhile, sometimes it’s fast.
I too have felt the frustrations of using Technical Vector print while in production work and having it not working as I expected while on deadlines and under pressure of specific deliverables.
But… like all things new, it takes time to iron out the kinks sometimes.
Far sightedly, real-time vector display mode and vector printing via Technical/Pen/Fake2d etc. has been a long standing wish in this community (from what I have seen), now that it’s finally here let’s help make it better because, as you point out, it’s a critical feature that is here to stay. We all need vector output for one reason or another. Having that output be real-time and dynamic and not needing to rely on the Make2D of old is really a great step forward.
Finding an edge case and “giving up” on a feature ever becoming anything just doesn’t help anybody win…
Please contribute a file and some info. No one can efficiently debug something by looking at a screenshot. By only talking at, and not sharing anything like a file, you are essentially guaranteeing it won’t be fixed, doing a disservice to yourself and others that would also like to see these changes/fixes made.
That’s all
happy Rhino’ing! 