Jump to content

Model matching in msfs?


Recommended Posts

1 hour ago, Quinten Bowman said:

Among the things I don't understand is, when we're talking model matching causing a CTD, which program is crashing? MSFS? vPilot? Potentially either or both?

It can be either, but usually it's the sim crashing, and then sometimes that will also cause vPilot to crash.

1 hour ago, Quinten Bowman said:

To meet that goal, I'm contemplating changing Settings>Performance> Do not display aircraft beyond to "zero", and Maximum aircraft to display to "zero." Aside from not being able to see anyone, anyone know of a reason this won't work?

You only need to set the max aircraft to zero. Doing so will make the max range setting irrelevant. (The max range cannot be set below 1 anyway.)

As to your sim crashing, I'm afraid I have no idea what might be causing that. Does it happen only when you connect to the network and there is an aircraft nearby? Or does it also happen when there is no other traffic near you? If it only happens when there is traffic nearby, is it only when a certain model is used to render that traffic?

Have you tried temporarily removing MegaLiveries?

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to post
Share on other sites
  • Replies 84
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

if the freeware developers create the models and paints then I don't see why not. The issue right now is that the legacy models and paints from FSX P3D do not work with MSFS and thus must be made new.

Dear @Ross Carlson @Matthew Bartels There is an effort already ongoing to bring FLAi models to FS2020, hopefully soon there will be enough out there to start chewing on it! https://forums.fl

Then you'll need to ask them why you're sometimes getting bad model matches.

Posted Images

Frankly, I haven't paid much attention to who else is around. Since they are both early flights, I've specifically chosen to fly out of relatively unpopulated airports (CYLW and KGEG) so that any ignorance I display affects the least number of other users. I was flying towards KSEA and CYVR. It is entirely possible that I got within the standard 40 miles injection radius of another user, triggered model matching, and caused MSFS to crash. That's actually the possibility I'm troubleshooting. But I have 2 data points, which isn't enough to draw conclusions.

For what it's worth, MSFS appears to crash much less often (every 10-12 hours, versus every 30 minutes) when I don't have vPilot attached.

I will remove the megaliveries and see if that changes something. While I don't see how it could be related, I can also try removing A320NX and a A321 that was imported/upgraded from MFSX. It's likely my next flight will be 0300Z, so I won't have anything to report until tomorrow.

As a point of protocol, should I let ATC know I've had crash issues in the flight plan notes? Via voice? Do they get the message that my sim crashed when it happens? Is there a way to let them know what happened when I suddenly drop off radar?

Link to post
Share on other sites
48 minutes ago, Quinten Bowman said:

Is there a way to let them know what happened when I suddenly drop off radar?

If your Pilot Client remains connected while an exception or other error message remains on-screen, you can key up and let them know.  Otherwise, don't worry about it.  If you drop off the scope and don't reappear within a couple minutes, they'll assume you aborted for one reason or another & will move on with their day. 

Cheers,

-R.

fvJfs7z.png

Link to post
Share on other sites

Update, which might be moot, since I see vPilot updated this morning and the new version seems to disable model matching for msfs. But in case this is helpful to someone else, here's what I've learned. 

Last night I was able to complete my first Vatsim flight ever, from KEUG to KGAG, by going into performance and turning maximum aircraft to display to ZERO. There was other Vatsim traffic in the area, but I obviously couldn't see them because I'd turned them off.

Next, I turned aircraft back to 999 and logged in parked at KSEA, because it was busy with other Vatsim pilots. MSFS crashed to desktop within a minute. I get the impression MSFS is crashing because it is receiving information about Vatsim pilots that MSFS can't handle. My suspect is still something about the Megaliveries (currently running all of 11.3).

Testing that, I removed Megaliveries, spawned next to a busy airport, and just sat for a while (defined as more than a couple minutes and until I got bored). No crash.

My current hypothesis is that either there are errors in Megaliveries, which vPilot is dutifully passing on to MSFS, and MSFS can't handle.

I have no idea where or how to start diagnosing Megaliveries.

Link to post
Share on other sites
13 hours ago, Ross Carlson said:

That's not the case. The 2.6.9 update just fixes a bug that was causing some MSFS models to not load correctly.

So this is expected behavior? or something is wrong in my setup?

image.png.b4bbef2f6a5e5635e7284df29778a199.png

Elias Stassinos - Member of CHFD club (Connect-Have Fun-Disconnect)

Link to post
Share on other sites
On 11/13/2020 at 12:37 PM, Quinten Bowman said:

Update, which might be moot, since I see vPilot updated this morning and the new version seems to disable model matching for msfs. But in case this is helpful to someone else, here's what I've learned. 

Last night I was able to complete my first Vatsim flight ever, from KEUG to KGAG, by going into performance and turning maximum aircraft to display to ZERO. There was other Vatsim traffic in the area, but I obviously couldn't see them because I'd turned them off.

Next, I turned aircraft back to 999 and logged in parked at KSEA, because it was busy with other Vatsim pilots. MSFS crashed to desktop within a minute. I get the impression MSFS is crashing because it is receiving information about Vatsim pilots that MSFS can't handle. My suspect is still something about the Megaliveries (currently running all of 11.3).

Testing that, I removed Megaliveries, spawned next to a busy airport, and just sat for a while (defined as more than a couple minutes and until I got bored). No crash.

My current hypothesis is that either there are errors in Megaliveries, which vPilot is dutifully passing on to MSFS, and MSFS can't handle.

I have no idea where or how to start diagnosing Megaliveries.

Thanks, I have been for now actively avoiding customizing any AI model packs - not only because they may be buggy and/or break with every Asobo ubdate - also other aircraft look like a small bunch of pixels grossly overshadowed by their own lights. Except when really, really close which is not common.

I am still looking forward to a modest but reliable VATSIM-optimized livery pack for the Default AI/low-poly models.

 

Edited by Diego Vasquez
Link to post
Share on other sites
  • 2 weeks later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...