I sometimes open a second instance of VCP 7 because every once in a while, simply clicking on certain meshes will blow up VCP and VCP regrettably does not have the coveted save-on-crash quality/feature that Word Perfect of 1993-ish. To be fair to VCP 7, I think these crashes/sudden implosions occur when I've hit or exceeded 500MB of RAM due to my file's size. When the file is small, I don't think implosions happen when I touch meshes or try to check properties.

I want to open a second instance for several reasons:

-- sometimes, I do something that takes down VCP 7 and VCP 7 never, EVER remembers the MRU for the crashed session, which might be hours or days on since the MRU update. So, opening a 2nd instance in order to test something possibly dodgy is almost a MUST for me, since only the impaled instance dies.

-- sometimes I want to make edits in a reference drawing copy in a second instance of VCP and then simply copy and paste it into my primary instance of VCP 7, to the layer of choice. It obviously is a nice clean way to get a load of geometry onto the correct layer without having to to a bunch of "tree climbing" and branch +/-. I do not suggest that Beta/Trial copies running as read-only or no-saving versions do this, but if B/T copies are in a valid trial, it might be nice to permit it in case anyone testing a live project needs convincing to come to the Punch! Party.

Since there is the possibility and actuality for VCP to crash on occasion, especially if opening only ONE instance is done for copy/paste reasons, but the production and reference copies both push VCP to using maybe 80% or 90% of the available RAM, it would be highly useful to have copy & paste functionality between two or more REGISTERED, LICENSED copies of VCP.

It is infuriating when an OS owner dictates an edict that apps will not be allowed same-host, multi-instance runs. There are very valid reasons, for example, the implosion/vertical canal impalement that happens when an app crashes. It's a whole lot less stressful when the experimental copy's app instance goes cataleptic and very, very rage-inducing when the production copy dies due to one errant, memory-bounds-exceeding curiosity click.

Fortunately, for the past 3 days, VCP 7 did not not collapse underneath my sessions. It runs really well, and when I'm on a roll in VCP, i will gleefully ignore friends and plaintiff calls to go clubbing. VCP is at times, more often than not, so enthralling that despite occasional stress, I'd spend 3 days in VCP rather than going out.

I have, however, during the past 5 days, taken out my pen and paper and written down about 25 or 26 WISH LIST items for "VCP 8". Some are about outstanding issues, some are about previous wish-list items that never made it, and some are new possible capabilities that I think will benefit all.

Sometimes, I feel that a merging of VCP into Shark might free up resources to quash some issues and introduce new, welcome features. I'm not a programmer, so I marvel and tip my virtual hat to anyone who can program. It's is nothing short of amazing what programmers go through to give us polished apps. I sometimes wonder how they even make money since labor must be between 45% to 55% of most companies' budgets.

But, despite some nagging issues with VCP 7, I still recommend it when talk of live, color, 3D modeling arises. I can do fairly easily in VCP stuff that drives me bonkers in ACAD and Rhino. VCP's live 3D editing and nice default color settings sold me like a firefly buzzing lights. The default colors and perspective are something I never customized much since I'm quite happy as it ships.

But, about copy/paste... I posted 1 or 2 other similarly-themed (c/p) comments today, where new product (VCP/Shark) features could exploit this for Win or Mac users.