Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Multiplayer Model Matching - need your expertise

Featured Replies

There is an element in my conundrum that relates to VR - but I think the expertise I need from you folks is wider than just VR, which is why I post it here.

I've been flying Multiplayer with a colleague (for ease, lets call him Chris) for a while - and it is simply splendid - but there's been a quirk.

Prior to my recent experiments:

- If we were both flying the same aircraft type, I could see Chris's aircraft, along with his chosen livery, correctly and he could see mine.  This was the case both with 'stock' Asobo models and also any 3rd party models that we both have loaded

- However, if we were flying different aircraft, then he could see both his own and mine correctly.  However, while I could see mine correctly, Chris's showed only as the 'default' generic model (lightplane or airliner)

This discrepancy was the case whether we were running in 2D or VR

 

So, I figured, what was the difference between Chris's pc /network set up and mine? :

- my Community file had loads more stuff than his

- my MSFS was running on an SSD; his was running on the boot (C: ) m2

- His original installation was more recent than mine

- my PC is faster (AMD7700X vs his AMD5800X) and my graphics card (4080) higher spec than his (3080Ti)

 

So first step was that I offloaded all out of my Community file except the 3rd party aircraft we both had.  Result:

- no change, in either 2D or VR

Second step, I reloaded MSFS on my separate SSD with its reduced Community File content.  Result:

- no change, in either 2D or VR

Third step, I loaded MSFS onto my m2 (C:) boot drive and stuck with just our common aircraft in the Community File.  Result:

- In 2D  If we both boot up at the same airport, I now see his aircraft correctly, and in his chosen livery  🙂

but

- If I boot up in VR, he is back to the generic 'lightplane or airliner'  🙁

but, weirdly

- If I boot up in 2D and then switch in sim to VR, Chris's aircraft remains correct and in the correct livery even in VR!  And that remains the case whether we subsequently lose visual contact during the flight or not.

 

And throughout, Chris's view of my aircraft is working as it should, whether he is in 2D or VR (and yes, we both use the same VR headset model and version)

 

I know the Model Matching is a bit clunky in MSFS (hence the rise of the very impressive 'M3 Model Matching Utility') - but I don't really understand why my results are so different to Chris's...

 

Anyone know? 

 

 

 

 

Edited by AJZip

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.