Marketplace Ratings not weighted with number of ratings

ISSUE DESCRIPTION

Description of the issue:
The 2024 Marketplace Ratings do not appear to properly weight the quality of the score with the quantity ratings received. An aircraft with two 5.0 ratings is displayed higher than aircraft with 518 ratings that average 4.8. This does not appropriately represent the actual score the aircraft have earned based on how many times the aircraft has been accessed.
This is a change from the 2020 Marketplace.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Every time.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Open Marketplace.
  2. Sort by Best Rating
  3. Observe items with very few ratings are displayed before aircraft with more ratings and a higher aggregate rating.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
[PC Only] Are you using Developer Mode or have you made any changes to it?
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
[PC Only] What GPU (Graphics Card) do you use?
[PC Only] What other relevant PC specs can you share?

MEDIA

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Sorted by Best Rating the Marketplace shows an item with One single 5.0 vote higher than an item with a 4.8 from 520 votes. This is wildly inaccurate and unhelpful.
Select Aircraft > Sort by Best Rating > Observe sort by numerical value instead of a value based on quantity of votes.
any-aircraft livery ui

Thank you for the bug report.

We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.