<div dir="ltr"><div>Yes, it could be added back.</div><div><br></div><div>Marek<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 27, 2018 at 3:15 AM Tom Butler <<a href="mailto:tom@r.je">tom@r.je</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I realise this was removed for a reason ( <br>
<a href="https://lists.freedesktop.org/archives/mesa-dev/2014-September/067864.html" rel="noreferrer" target="_blank">https://lists.freedesktop.org/archives/mesa-dev/2014-September/067864.html</a> <br>
) but there are cases where it is useful. In older games that do not <br>
support native FSAA being able to force it in the driver is the only way <br>
to enable it.<br>
<br>
<br>
A quick google search for AMD linux force msaa shows that I'm not the <br>
only one who would like to see this feature return:<br>
<br>
<a href="https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/1024166-radeon-eqaa-anti-aliasing-support-merged-to-mesa-18-2?p=1024185#post1024185" rel="noreferrer" target="_blank">https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/1024166-radeon-eqaa-anti-aliasing-support-merged-to-mesa-18-2?p=1024185#post1024185</a><br>
<br>
<a href="https://bbs.archlinux.org/viewtopic.php?id=225425" rel="noreferrer" target="_blank">https://bbs.archlinux.org/viewtopic.php?id=225425</a><br>
<br>
<a href="https://www.reddit.com/r/linux_gaming/comments/671yzm/forcing_antialiasing_with_mesa_radeon_driver/" rel="noreferrer" target="_blank">https://www.reddit.com/r/linux_gaming/comments/671yzm/forcing_antialiasing_with_mesa_radeon_driver/</a><br>
<br>
<a href="https://github.com/dscharrer/void/blob/master/hacks/forcemsaa.c" rel="noreferrer" target="_blank">https://github.com/dscharrer/void/blob/master/hacks/forcemsaa.c</a><br>
<br>
I understand it does cause issues in some cases but there are times when <br>
it is useful. Could it be reintroduced with a more relevant name that <br>
implies it shouldn't be used? E.g. GALLIUM_LEGACY_MSAA or <br>
GALLIUM_FORCE_MSAA_EXPERIMENTAL. That way it would lower users <br>
expectations while still making the option available to try.<br>
<br>
<br>
Kind Regards,<br>
<br>
Tom Butler<br>
<br>
<br>
<br>
_______________________________________________<br>
mesa-dev mailing list<br>
<a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
</blockquote></div>