@mcsupersport wrote:The issue of black artifacts was ME1, on a couple areas there were settings in the code that when it saw a AMD gpu it used a setting(I guess you could call it) that is no longer used by AMD chips and as such, things wouldn't draw. (There is a mod on the Nexus to fix this)
As far as newer amd cpus causing issues, not inherently, well at least my Ryzen7 seems to have no issue at all with the game, and I am running a MSI Lightning R9 290X amd gpu and again seems to have no issue.
Now, on my machine the game config utility has no issue running and does exactly what it is supposed to. I am wondering if you issue is a bit deeper or different than common stuff. You may look into reinstalling all the game specific DirectX files from the installer files in the game. You may also want to try swapping the video card you are using to the other one....it is a check to see if you have a bad video card starting. Also check to see if all cables and such are installed and tight. Also, do you happen to have a computer close that the game works fine on?? Maybe you could try copying the files directly from that computer over to the install location, as maybe something such as anti-virus or firewall is interfering???(not likely but hey)
The fact that installing ME2 caused Windows 10 issue also kinda leads to thinking issue is with Windows 10 itself....meaning something corrupted in it....a system check of Win10 may yield something.
Right, so the black artifacts in the past, due to AMD, was for the GPU and only in ME1. Thanks for clearing that up.
Which Ryzen 7 do you run? They are all 8-cores if I'm not mistaken, with AMD's version of HT/Theoretical Threading so it has twice the active "cores" for code execution, ie 16 Threads.
I have, as I mentioned, an intel 6700k with a 1080 sitting next to this current machine. It has had no issues with ME1 or 2. For the sake of it I ran it and it did not give any issues.
Did pull o ut one of my 1080Ti's and swapped them around, removing the SLI bridge etc. No difference, even with only one card plugged in to the PCI-E socket. Did try both 16x Sockets on my motherboard, in case the socket itself was messing up. Cables are nice and snug.
There's no AV or FW active on my system apart from Windows 10's basic system. So most likely not interfering with the program as such.
Nah, Win10 has had that issue since 2013 - some fix it with a forced reboot of PowerShell, others with a recheck/scan of the underlying executive code.. Others with creating a local account. Some fix it with simply logging out and back in.. And others, like me, need to uninstall the last program (Adobe Acrobat Reader, Photoshop, Mozilla Firefox, and now ME2, all mentioned by others).
I did a system scan, nothing wonky (SFC and DISM).
@holger1405 wrote:Lets test something.
Open the msconfig tool, press the windows key and R at the same time > Typ or copy and past "msconfig" (without the quotes) in the new window > enter > under "Start" click on "Advanced Option" > limited the machine to 4 cores > OK > OK > reboot > test.
Test the config utility also, it should run with this settings.
The utility program now works.
Graphical errors persists in-game though.
Just as a notice/addendum: I am running the game through one of your work-arounds, @holger1405, even now when I tried with only 4 executable cores.
I am also telling Origin NOT to update my game, as it wishes, due to the fear that the DLC's may have a finger in on the issue.
If wanted I can uninstall and reinstall the game, no work-around, 4 Cores, and allow Origin to download updates/DLC's - in case this is a possible reason for failures of texture loading/rendering.
Also - depending on my resolution in-game, the distance that Armor and "Objects" textures vanishes/turns black, shifts. Low Resolution will let me get close to objects before they go black, high resolution removes textures once I reach aprox 3 Character-widths.
