Peer_Review wrote:
What they are saying good sir is; If you would be so kind as to give us a little information about your computer then we could lend a hand. It is understood that you are correctly placing the files in ME:A's directory and that is what is causing the problem. So it is some other variable messing with things. So lets get you fixed up shall we?
Fist up, what are you specs, Do you run SLI or Crossfire, and what resolution are you playing at? If you have Nvidia what is PhysX setting set to. Have you tried changing that to CPU? Also if on Nvidia have you changed anything with Nvidia inspector or in Manage 3D settings. If you have, reset them to default then tweak them again once we get everything sorted. If On an AMD GPU have you changed any tessellation settings, or have any global settings overridden? If so set them back to default for the time being.
Next; {This would be the most likely cause of problems) Are you running any other overlays that could interfere (Geforce Experience, Rivatuner standalone or one that came with Afterburner or EVGA PrecisionX. If so Is it set to hook into the framebuffer or viewport? Is Origin's overlay enabled? If so try and disable it. Are there any other overlays Razer, ASUS ROG etc... Remember this fix is not a memory hack like the other. It is hooking into DirectX itself. This is a very common method used by many different utlities and they might be clashing. Are you using SweetFX, Reshade, or any other shader suite? If so which one and what version # is it. Do you have DXtory, or Fraps running. Do you have the Steam version of Display Fusion? If so have you made any changes to the viewport that overrides your display driver's?
3rd: Do you have an overclock on your GPU. Frostbite can have issues with certain overclocks set to various speeds. For example on my system If I set the core clock to 96 {a multiple of 12) it is fine, but 100 will quickly throw a dxgi device removed error. Nvidia cards have also historically favored Multiples of 13. AMD cards never were sensitive to those things (For me at least, though I've not owned any AMD cards since 7970 ghz ed. so that may not be the case still). Yet the game engine might not like certain numbers. Perhaps dial it back a little if you have an aggressive overclock. Ideally you should remove it until you get this working then re enable it. That goes for any tweaks really.
4th: What display driver are you on? The newest one for your platform, What version of Windows are you on? If on Windows 10 do you have the creators update?
5th: Are you passing any commands to the game at launch? Either via the launch commands dialogue in Origin, or adding them to target for a shortcut. How about a User.cfg file in the ME:A directory to tweak things like motion blur, readaheadlimit, or tessellation? If so remove any launch commands or user.cfg files for now.
6th:Have you started Modding the game yet? There is already a basic toolkit out by Warranty Voider, and mods have already appeared the Nexus. Or have you yourself changed any game variables with it?
7th:Have you tried using the repair game function on Origin? If not give that a whirl.
8th:Do you have a legit copy or the game, or are you using a cracked version? There's nothing to be done if you don't have a legit version. (Not an accusation, just covering all bases.)
Now these are the type of thing we need to know to help you. None of us know them through voodoo, burning bushes, or sorcery and so forth. Help us help you, and please try not to be obstinate about it good sir. There is a limited set of things (read: Zero) we can do without having your computer in front of us. I do understand being irritated about not being able to play the game properly. Especially if you are (Like most of us I would guess) a huge fan of Bioware games; and have been waiting in anxiousness for a couple years to get our hands on a new Mass Effect game. One with loot and item drops, && crafting like an actual RPG again no less.
So with all that said, hit us with some answers so you can get back to Pathfinding already.
Thank you for actually trying to offer some real help, much appreciated.
specs: 6700k, fury x, 16gb ram, 1tb ssd
havent changed anything in Radeon Settings for MEA.
i use MSI afterburner and RTSS. have tried disabling both, no change. Origin overlay disabled. Not using sweetFX or Reshade, no FRAPS etc. tried turning off ReLive as well.
no GPU overclock.
do not have Windows Creator update, current build is 14393. most recent AMD driver.
no launch commands. have tried repairing twice now, no such luck. also not using a custom user.cfg
no mods.
i have a legit copy of the game, bought on Origin.
I apologize for being an asshat, but that first response to my initial request for help was a bit grating as it literally parroted back what I first posted.
Thank you again for offering to help. I am using the FWS fix atm, and that working fine-ish, the black bars arent too distracting. Would be nice to get this better fix working tho. I have spent a lot of time now trying to troubleshoot it myself, bit frustrated that nothing seems to work.
Login
FAQ
Search
Members
