202,798 users have contributed to 43,310 threads and 259,520 posts.
In the past 24 hours, we have 6 new thread(s), 31 new post(s) and 66 new user(s).
When importing an instance into VEP, if the imported instance includes a channel that uses MIR as an insert, the current VEP/MIR project changes to the venue of that imported channel/instance. This means that the importing instances functionality is impractical when using MIR.
The preferred behaviour would be that the imported channel/instance is instead loaded into the current MIR venue. And if multiple venues are being used, load the channel(s) into the first venue.
@JBuck said:
When importing an instance into VEP, if the imported instance includes a channel that uses MIR as an insert, the current VEP/MIR project changes to the venue of that imported channel/instance. This means that the importing instances functionality is impractical when using MIR.
The preferred behaviour would be that the imported channel/instance is instead loaded into the current MIR venue. And if multiple venues are being used, load the channel(s) into the first venue.
In MIR Pro 3D, click on the "Block Incoming Engine Data" icon before importing your instance.
@daviddln said:
In MIR Pro 3D, click on the "Block Incoming Engine Data" icon before importing your instance.
Exactly.
For more complex import scenarios where you want to retain both the original and the imported Venue, please use MIR 3D's so-called "Venue Presets", which are available in the Preset Manager (F7).
