WOAI Model matching

[Will Stone 1253625]

Hello everyone

 

I finally decided to start flying online again and saw the latest software to have is VPilot. After reading about the mishaps with IVAO model mapping I decided to go the route of WOAI. Saw a good tutorial online and follow the instructions as required.

 

i logged into VPilot and sat at a gate in EGKK and EGLL. I saw some planes worked (e.g. BA A318 and SAS 737) but others didn't. In fact another BA A318 came up as the default FSX A321, how do I stop this as more were coming up as the default A321 than the correct liverie/model.

 

Oh and I didn't install the individual packs, I went on Avsim and got that package installer program.

 

Cheers

[Don Desfosse]

To answer the specific question, we'd have to know a lot of information. First things that come to mind: do you have a WoAI BAW A318 installed? Do you have a model matching ruleset active that contains a BAW A318? What actual aircraft type (NOT what they filed in their flight plan!) did the pilot flying the A318 log in as? If they logged in incorrectly (e.g. using FSInn and logged in as an aircraft type ZZZZ), you won't see them correctly, and it's their fault.

[Will Stone 1253625]

Well to install WOAI I followed a tutorial on youtube ( https://www.youtube.com/watch?v=Bsg4QmJwBrc ), some aircraft work, I know that last night a EZY A318 showed up as fine but another aircraft with same livery didn't work. Which I found strange.

 

I did some trouble shooting earlier in VPilot, I logged some aircraft that didn't show up and went on VATSpy to see how they were registered. I will list the Flight No and Aircraft Type as shown in VATSpy.

• 
  BEE615 - DH8D/L
  G-CIXD - C182/G
  TCX56AX - H/B752/L
  BEE733 - E190/Q
  BAW78HM - A319
  

Each of those show up as just the default A321 aircraft. Is there any better software to get for the model matching other than WOAI, or is there another way to do WOAI? I want to fly on-line but not when I'm flying with 100s of A321s!

[Bradley Grafelman]

What did vPilot's debug window show as far as the decisions being made for model matching? Can you show us some examples of of rules from your model matching rule sets that you think should have been a match but apparently weren't?

[Will Stone 1253625]

how would I do that, sorry quite new to this!

[Ned Hamilton 1215492]

I'm new at this too but I just installed a bunch of WOA models and know a little about troubleshooting.

 

One thing to do is invoke the .debug command inside vPilot it will tell you some more.

 

Look in your model matching rule .vmr files. You should have lines that look like this

Those two lines would match two of your aircraft.

One life saver I have found is to use VMRGenerator to make the matching rules rather than rely on the vPilot ones for WOA models.

 

There are a lot of very helpful folks on this forum.

[Will Stone 1253625]

I have installed and ran the VMR Generator, hopefully this works. from what people here have said and what I found on-line I think it is also down to how people select their aircraft. if they don't select the correct aircraft it wont work if I'm correct, it'll just show a A320.

 

It would be interesting to see if aircraft I see as defaults are the same as others.

[Will Stone 1253625]

Just checked the Model Match Rule Set files - results below:

Flybe DH8D

 

 

BAW A318

 

 

 

 

I'm presume this is all correct?

[Bradley Grafelman]

Seems correct. Are you getting any SimConnect errors in red text (followed by a beep) in the main vPilot window? That would mean that vPilot is matching those rules and attempting to use those models, but FSX is reporting an error when it loads the model with the given name.

 

If not, I would first verify that the rule set file is actually loaded into vPilot (i.e. it appears under the "Downloaded Rule Sets" column on the Model Matching tab in the configuration menu).

 

Lastly, yes, model matching largely relies on pilots inputting correct ICAO aircraft type codes into the correct location of their pilot client. You can use the debug menu (just type ".debug" into vPilot's main window where you'd normally send text and press enter) to view information about nearby aircraft - just click the Aircraft tab and select an aircraft. See if the "Type Code" value on the right is sensible (e.g. "DH8D" versus "DHC-8-400 DASH 8").

 

If you see this happening again, you might also open up the debug menu and capture the debug messages (from the "Messages" tab) and paste them here - they might give more insight as to why you're ultimately seeing the white Airbus.

[Will Stone 1253625]

I did get one error on the VPilot box, it said the TXC*** (can't remember the call sign) B757 couldn't be matched. But tithed than this message there were no orders.

Perhaps it is just a case of people typing in the wrong aircraft type then, I will wait for it to reoccur tonight and try to capture the info.

 

Thank you everyone for the [Mod - Happy Thoughts]istance so far! It's been really helpful!

[Will Stone 1253625]

TCX Sorry, not TXC.

[Ross Carlson]

vPilot will NOT show an error when an aircraft cannot be matched. In that case it will just fall back to your default model (such as the A321) and use that. It will only show an error if it finds a match and FSX throws an error when vPilot tells FSX to create the aircraft. This usually means that you have a model matching rule that refers to a model that you don't actually have installed in FSX.