Add a chip and or device field to the rating template

[joshandersn]

A field to specify what the tested game was run on
i.e. Chip: M2 Pro Device: Macbook Pro
Status: [[#status]] | Last Tested: [[#date]] | Chip: [[#chip]] | Device: [[#device]] | Installs: [[#installs]] | Opens: [[#opens]]

This info is very helpful when it comes to gauging performance of high end software

[mattmaniak]

Also I would go even further listing chips a game was tested and their RAM capacity, like:

• M2 Pro: 16, 32 GB;
• M3: 16 GB;

It will be helpful for setting the minimum requirements, like a chip performance or memory size.

[hahayupgit]

I think these kinds of additions are good and I agree that they're very useful for the docs, however it does open a broader conversation about how test results should be handled on the pages.

I don't think that putting Chips, Devices, and Device Details on the main docs is useful for what the main test portion is trying to do. As there will be no compatibility errors between different M-Series chips or Ram sizes (right now), the only thing that will change will be performance of the games.

There should probably be something similar to what ProtonDB does, where user reports can be found under a dropdown or scrollable list of sorts at the bottom of the page, and the average of all scores/most recent scores can be found at the top of the page. This can help a user gauge the actual performance of the game to their device if they want to, yet keeping the relevant information of "does it work" as the first thing they see.

Issue is, this would likely require scripting/databasing of sorts to easily add user tests and display the averages, and would require a rework of the current pages and potentially the site as a whole. Considering we have some amazing devs in this community, I don't think its something that's far-fetched, however it's also not something that's on the current roadmap.

That being said, there could be a much simpler solution that I'm not thinking of. This is just my idea for the site. Keep the compatibility as the first thing a user sees in a simple, easy to read way, and add device details and actual performance numbers near the bottom of the page for those who are more interested in that.