Enable Sniper for FNA catalog, part 1

[flibitijibibo]

I'll be making a ton of requests over the next year or so (~70 in total I think), but here are some that should work today:

• Super Hexagon (221640)
• FEZ (224760)
• The Dishwasher: Vampire Smile (268990)
• Salt & Sanctuary (283640)
• Charlie Murder (405290)
• Streets of Rage 4 (985890)
• TMNT: Shredder's Revenge (1361510)

One other question: Is it possible to enable access to Sniper for an appid in the compatibility tools dropdown without necessarily setting it by default? If so I can probably just send the complete list of appids now, but the above make the best use of it as of writing.

Thanks in advance!

[TTimo]

Developers can use -compat-disable-filtering to force a (possibly completely incompatible) SLR. Obviously we don't recommend this for users.

We can map specific branches to sniper. Is this something you want to do for the games above, or should we set them to sniper by default right away? Do you have another set of titles that we should apply a branch specific mapping for?

Since I don't do those edits directly but pass them on to someone else, I'd like to minimize the amount of back and forth.

[flibitijibibo]

Since we have the filtering flag let's hold off entirely for now - going to just check against all the titles I still maintain, should have the complete list of appids this week!

[smcv]

Is it possible to enable access to Sniper for an appid in the compatibility tools dropdown without necessarily setting it by default?

The reason why you can't do this without a developer-oriented override is:

The design assumption is that either you compiled your game in a scout SDK targeting scout, or you compiled your game in a sniper SDK targeting sniper.

If you compiled in scout, then running it in sniper is probably wrong, because sniper doesn't provide all of the obsolete library SONAMEs that scout has (e.g. no GTK 2).

Conversely, if you compiled it in sniper, then running it in scout is probably equally wrong, because the minimum API/ABI that we can guarantee to provide is more than a decade old and is probably missing functions that you want to call.

We don't really optimize for the case of titles that were compiled in scout, sniper, or some other build environment entirely, and accidentally or intentionally use such a small subset of the runtime's available API/ABI that they happen to work equally well in either scout or sniper.