I just bought Ultimate Traffic Live in preparation for Cross the Pond as my WOAI was just barely working with v4, I know it is not meant to be used with it but what other choice did I have before hearing about UTLive? Anyway, I just installed it and hopped on Vatsim real quick to test it out in observer mode, and I found that the models were represented the exact same way as WOAI, so I went into the settings and unchecked WOAI from vPilot, and still the same thing. I did some digging and found that there were some xml edits I had to make, and still nothing. I can easily tell there is a big step I'm forgetting but I just can't seem to find out.

15 minutes ago, seaniez said:

I just bought Ultimate Traffic Live in preparation for Cross the Pond as my WOAI was just barely working with v4, I know it is not meant to be used with it but what other choice did I have before hearing about UTLive? Anyway, I just installed it and hopped on Vatsim real quick to test it out in observer mode, and I found that the models were represented the exact same way as WOAI, so I went into the settings and unchecked WOAI from vPilot, and still the same thing. I did some digging and found that there were some xml edits I had to make, and still nothing. I can easily tell there is a big step I'm forgetting but I just can't seem to find out.

Is UTlive showing up in vpilot as a checkbox option for model matching? Not sure about the xml edits. I have no issues at all without doing that

Make sure you have an entry in your ProgramData/Lockheed Martin/Prepar3d/Simobjects.cfg  that references the UTLive aircraft folder.  Go to your SimObjects folder in your main P3D installation and check whether the UT Aircraft folder matches what you had in your SimObjects.cfg entry.

You shouldn't have to muck about with .xml entries to get a model matching set purely for vPilot.  All you need is an AI Aircraft folder which is referecned in your simobjects .cfg.   vPilot is smart enough to figure out the rest.   I use VMR Generator to create a custom model matching rule set and then add it via the Custom Model Matching option in vPilot.