Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

Model Matching Issue


1275389
 Share

Recommended Posts

1275389
Posted
Posted

Evening all,

Over the past few days, I've been fine tuning my model matching rules (through VMRGenerator) to add/remove unwanted models.

I came across a major carrier that simply had no models for two specific aircraft. These were AAL's A319/A321 as a result of being so "new" to the fleet.

I found FAIB's A319 and A321 and installed both of them with the appropriate American livery.

 

I successfully setup the A319's model, tested it, and it appeared as a properly matched model should.

I installed and setup the A321's model following its appropriate instructions and it's simply not working. I don't know whether the aircraft is broken or if I did something wrong in the model matching rules (which I highly doubt as it tries to match the model as shown in the vPilot debug menu).

 

Here's the debug console's output:

[00:37:10.169] Model matching rule sets reloaded
[00:37:12.056] Aircraft discovered: AAL725 - requesting CAPS, sending CAPS, requesting aircraft info
[00:37:12.459] Received capabilities list from: AAL725 - MODELDESC=1:ATCINFO=1
[00:37:12.460] Model match result - Callsign: AAL725 - TypeCode: A321 - ModelName: FAIB Airbus A321-200 SL IAE American Airlines - Rule Set: C:\Users\Josh\Docomeents\vPilot Files\Model Matching Rule Sets\AI Matching Rules Generated.vmr - Priority: 1 - P[Mod - Happy Thoughts]: 1
[00:37:17.212] Aircraft added to sim: AAL725
[00:37:17.256] SimConnect error: Failed to create aircraft AAL725 using model "FAIB Airbus A321-200 SL IAE American Airlines". This usually means you have vPilot configured wrong! Specifically, it means that you have downloaded model matching rule sets without having the actual AI models installed in your flight simulator! Read the vPilot model matching docomeentation for details. vPilot will try to create the aircraft with a different model.
[00:37:17.265] Aircraft deleted - Callsign: AAL725 - Reason: MissingModel
[00:37:21.983] Aircraft discovered: AAL725 - requesting CAPS, sending CAPS, requesting aircraft info
[00:37:22.498] Received capabilities list from: AAL725 - MODELDESC=1:ATCINFO=1
[00:37:22.502] Model match result - Callsign: AAL725 - TypeCode: A321 - ModelName: FAIB Airbus A319-100 SL CFM American Airlines - Rule Set: C:\Users\Josh\Docomeents\vPilot Files\Model Matching Rule Sets\AI Matching Rules Generated.vmr - Priority: 1 - P[Mod - Happy Thoughts]: 2

 

Right now it's forcing any AAL A321 to become an AAL A319 and I really don't know why. I haven't encountered this error with any other model.

Anyone have any ideas what's going on here?

Regards,

Josh

Link to comment
Share on other sites

Bradley Grafelman
Posted
Posted

Can you post the contents of the aircraft.cfg file which contains the "FAIB Airbus A321-200 SL IAE American Airlines" model? (You might just want to paste it into pastebin and post the link here based on how large the file is.)

Link to comment
Share on other sites

1275389
Posted
Posted

Now that I posted it, I know what the exact issue is.

Looks like I forgot to change the "fltsim.X" to "fltsim.0"

 

Here's the paste (I prefer pastie over pastebin haha): aircraft.cfg

Link to comment
Share on other sites

  • Board of Governors
Don Desfosse
Posted
Posted

Yep, that would do it!

Don Desfosse
Vice President, Operations

Link to comment
Share on other sites

1275389
Posted
Posted

Is there any way I can force a model on an aircraft to test certain model matching rules? I know you can test all, but can you test one specific one at a time?

Link to comment
Share on other sites

1275389
Posted
Posted

I remember that I actually got the model working two days ago, but encountered something weird, so I re-installed it (and forgot the .X).

I fixed that and now am back to my first problem...this.

Link to comment
Share on other sites

Johnathan Lee
Posted
Posted

I had the black aircraft and iirc it was related to dx10.(where the particular aircraft was not dx10 compatible). going back to dx9 solved that.

 

I have no idea why the nose of the plane is kissing the tarmac though.

 

/regards

vafs_status.php?cs=FDX3590&c=1
Link to comment
Share on other sites

1275389
Posted
Posted

The ground kissing should have to do with whether the sim thinks the model has gears/if they are down.

 

It's particularly strange because the A319 counterpart by the same author works perfectly.

Link to comment
Share on other sites

1275389
Posted
Posted

Anyone else have ideas on what's wrong here?

Link to comment
Share on other sites

  • Board of Governors
Don Desfosse
Posted
Posted

Did you ensure DirectX 10 is NOT selected?

Don Desfosse
Vice President, Operations

Link to comment
Share on other sites

1275389
Posted
Posted

DX10 preview right? It isn't

Link to comment
Share on other sites

  • Board of Governors
Don Desfosse
Posted
Posted

Correct. OK. That was the only thing I can remember that would trigger black aircraft.

Don Desfosse
Vice President, Operations

Link to comment
Share on other sites

Bradley Grafelman
Posted
Posted

Didn't one of the shadow options on the Aircraft tab also tend to cause issues? If I had to guess, it was the "Aircraft casts shadows on itself" one.

Link to comment
Share on other sites

1275389
Posted
Posted

Not checked either. Tested out a few settings and it had no effect on the weird plane

Link to comment
Share on other sites

1275389
Posted
Posted

Installed the FS9 A321, model appears properly, texture doesn't

Link to comment
Share on other sites

 Share