0025119: turning off all post processing options reduces but does not eliminate graphics issues on my Radeon 570x GPU iMac 2019 - DEV Arcen

ID	Project	Category		Date Submitted	Last Update

0025119	AI War 2	Graphical Bug		May 29, 2021 3:56 pm	May 29, 2021 5:47 pm

Reporter	abjohnsonzz	Assigned To	Chris_McElligottPark
Status	resolved	Resolution	fixed
Product Version	3.004 Post Processing Options
Fixed in Version	3.005 Radeon Returns

Summary	0025119: turning off all post processing options reduces but does not eliminate graphics issues on my Radeon 570x GPU iMac 2019
Description	With all post-processing off, a new game, going into an unexplored planet usually causes graphical noise. The graphical noise is reduced from the default settings, but is improved enough so that it is possible to tell when the view is shifted to the galaxy view or not. The background noise is retained, but there can be a clear circle corresponding to the planet that is clear, so the hyperplanes and planet names can be seen. I then tried turning off the AA, but this did not change the noise incidence even when starting a new game. The occurrence of the noise does have some quirks. It does not always begin immediately on entering an unexplored planet. There can be a clear interval of a few seconds. On an earlier attempt after which I turned off only some of the post-processing ( the intel noise and two(?) of the bloom controls), I started a new game, went directly to a planet adjacent to the home world. No noise resulted. I waited several minutes with no noise. I then went to the galaxy view and entered a planet 2 hops from the home world and immediately generated noise. The noise with the default settings is much worse. I believe it is a bloom effect. With all the post processing turned off, the noise is like on a UHF tv (yes, I'm old) between broadcast channels, except colored not black and white. The property that makes the game unplayable is that the noise persists after leaving an unexplored planet.
Tags	No tags attached.

Chris_McElligottPark May 29, 2021 5:47 pm administrator ~0061898	New build is out, and if you choose the OpenGL launch option on Steam or GOG (if you don't see that, Exit Steam and restart it), then you should no longer have the issue. Thank you! * OpenGL support, which we removed from Mac OSX a few months ago on our beta branch, has been returned. In almost all circumstances, you should not use this -- Metal will perform better, is more modern, is a better use of RAM, etc. However, because of driver issues with Radeon cards on OSX, at the moment OpenGL will be needed for compatibility purposes with that specific hardware combo. ** Please note that, from now on, Metal is used by default, or you can force it to be used by adding `-force-metal` at the command line. To use OpenGL, you can add `-force-glcore` to do that. There are of course also start options in GOG and on Steam for making this happen without you having to fiddle with the command line.

Date Modified	Username	Field	Change
May 29, 2021 3:56 pm	abjohnsonzz	New Issue
May 29, 2021 4:31 pm	BadgerBadger	Assigned To	=> Chris_McElligottPark
May 29, 2021 4:31 pm	BadgerBadger	Status	new => assigned
May 29, 2021 5:26 pm	Chris_McElligottPark	Relationship added	related to 0024969
May 29, 2021 5:26 pm	Chris_McElligottPark	Relationship added	related to 0024789
May 29, 2021 5:26 pm	Chris_McElligottPark	Relationship added	related to 0024972
May 29, 2021 5:47 pm	Chris_McElligottPark	Status	assigned => resolved
May 29, 2021 5:47 pm	Chris_McElligottPark	Resolution	open => fixed
May 29, 2021 5:47 pm	Chris_McElligottPark	Fixed in Version	=> 3.005 Radeon Returns
May 29, 2021 5:47 pm	Chris_McElligottPark	Note Added: 0061898