At what level is the Mapping process "remembering" the mappings?

Hi Cory Pattak,

This is stored at both the device level and in the show file as it is shared across the network in a multi-console system. You are correct that the intent is to not need to remap fixtures every time when your inventory is likely unchanged. To clear the mappings, press the reset button in the importer then remap your fixtures as desired.

thanks. Nick Gonsman and I were discussing this offline as well. As you open different files or create blank new fies, there is a real inconsistency to what mappings are remembered, which ones are forgotten, and which mappings Eos tries to make on your behalf that aren't even necc in your import file. I can provide a screen recording with details if you are interested. Regardless, I think it should be a high priority to try and clean up this behavior and make it more consistent because it's currently leading to a lot of extra clicking and mapping and resetting etc as one moves between files and performs various import functions.

thanks. Nick Gonsman and I were discussing this offline as well. As you open different files or create blank new fies, there is a real inconsistency to what mappings are remembered, which ones are forgotten, and which mappings Eos tries to make on your behalf that aren't even necc in your import file. I can provide a screen recording with details if you are interested. Regardless, I think it should be a high priority to try and clean up this behavior and make it more consistent because it's currently leading to a lot of extra clicking and mapping and resetting etc as one moves between files and performs various import functions.

for some reason it's not letting me attach an image, but here is an example of how this process can be so confusing.

https://www.dropbox.com/s/vx9w9b3l4xlfgrz/Import.jpg?dl=0

[Moderator added image]

The same fixtures are showing up in both the linked and unlinked columns. The only solution is to reset and link them all again, which can be tedious if you've recently done it and expect the linkings to be remembered. 

That is confusing. Could you PM me the show files and .A3D files you are seeing that with?

i will try, the behavior is so inconsistent, it's hard to replicate it.

Hi Cory,

Looks like this is due to the device mapping being case sensitive and the symbol names changing from upper case to title case.

I've filed a request for the future for those mappings to be matched case insensitively.

how odd, because the cases never changed on my end. They've always been the same in the "Int Type" field in VW that is being imported to Eos. I never changed anything to be all CAPS, but it seems Eos did, and then didn't recognize the same fixtures when they were being imported again later.