[Mesa-dev] Please bring back __GL_FSAA_MODE

[Marek Olšák]

Yes, reverting the commit should be enough.

Marek

On Thu, Jan 10, 2019, 5:02 PM Tom Butler <tom at r.je wrote:

> Thanks Marek, what would need to happen to get this enabled again? Will
> simply reverting the commit that took it out work? If so is there any
> chance of getting this put back officially or would I have to manually
> compile the driver each release?
>
> In particular I'm looking to get FSAA working in older games via wine,
> mostly they don't support antialiasing which is a shame because there's
> plenty of GPU power going to waste which could be fixing the jaggles. On
> nvidia __GL_FSAA_MODE works as intended provided you set wine's
> OffScreenRenderingMode to "backbuffer" which slightly impacts performance
> but doesn't matter for older games. I'd love to see the functionality
> return for AMD GPUs.
>
> Kind Regards,
>
> Tom
> On 27/11/2018 22:30, Marek Olšák wrote:
>
> Yes, it could be added back.
>
> Marek
>
> On Tue, Nov 27, 2018 at 3:15 AM Tom Butler <tom at r.je> wrote:
>
>> Hello,
>>
>> I realise this was removed for a reason (
>> https://lists.freedesktop.org/archives/mesa-dev/2014-September/067864.html
>> ) but there are cases where it is useful. In older games that do not
>> support native FSAA being able to force it in the driver is the only way
>> to enable it.
>>
>>
>> A quick google search for AMD linux force msaa shows that I'm not the
>> only one who would like to see this feature return:
>>
>>
>> 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
>>
>> https://bbs.archlinux.org/viewtopic.php?id=225425
>>
>>
>> https://www.reddit.com/r/linux_gaming/comments/671yzm/forcing_antialiasing_with_mesa_radeon_driver/
>>
>> https://github.com/dscharrer/void/blob/master/hacks/forcemsaa.c
>>
>> I understand it does cause issues in some cases but there are times when
>> it is useful. Could it be reintroduced with a more relevant name that
>> implies it shouldn't be used? E.g. GALLIUM_LEGACY_MSAA or
>> GALLIUM_FORCE_MSAA_EXPERIMENTAL. That way it would lower users
>> expectations while still making the option available to try.
>>
>>
>> Kind Regards,
>>
>> Tom Butler
>>
>>
>>
>> _______________________________________________
>> mesa-dev mailing list
>> mesa-dev at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20190110/e09f22b5/attachment.html>