Widescreen Gaming Forum

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.

oxide7 wrote:

Trick Of Light wrote:

helifax wrote:Right guys,
Here is the fix (wrapper + shader) that removes the blackbars in Surround.
Now I haven't tested it on AMD Eyefinity or 21:9. I only run 3D Surround.
But 99% chances are it will work for everyone;) If not, I am sorry
Like stated above, I am not sure it will work with any other type of wrapper! You are a bit on your own there!

Download link: http://3dsurroundgaming.com/3DVision/Ma ... d_Only.rar

Let me know if it works for you!
Cheers!

How do I install this?

Forgive me if I'm being a noob, but if I drag and drop the files into the Andromeda directory my game wont start.

Same for me. I hear "beepboop beepboop" and the game process takes up some processing power but the game never actually runs.

SpriggsyUK wrote:Got another instance of it not launching correctly and causing a beeping noise took a video as well for reference https://youtu.be/ZSXuBtoocGw

LuPoNe wrote:Being a simple user like you two, and making an educated guess here, I see two common factors:
1. Windows 10 Creators Update
2. AMD card

While I would assume that the latter would be very unlikely, given the wide range of issues that the former still holds, I could safely assume that it would be the Windows Creators Update changes that don't "talk" with the 3D Migoto libraries of the second "easy" fix from Helifax

I don't have an AMD card, but I don't have the Creators Update either, so they're the only two factors I can think of, and to rule them out, we would need more feedback from other users.

LuPoNe wrote:Patch 1.06 is out: no proper 21:9 fix.

3D Migoto fix from Helifax still works, I've noticed a little performance hit though (but it also may be windows 10 preparing the system update + my older CPU)

LuPoNe wrote:Patch 1.06 is out: no proper 21:9 fix.

3D Migoto fix from Helifax still works, I've noticed a little performance hit though (but it also may be windows 10 preparing the system update + my older CPU)

theblacklaser wrote:

LuPoNe wrote:Patch 1.06 is out: no proper 21:9 fix.

3D Migoto fix from Helifax still works, I've noticed a little performance hit though (but it also may be windows 10 preparing the system update + my older CPU)

It looks like the new patch actually broke 21:9 support. The game seems to think that 21:9 is the same as 4:3. All the GUI elements are pushed toward the center, where they weren't just yesterday. It is most noticeable in the Nomad with the mining interface open. I tried it with and without Hellifax, and it made no difference.

Pretty lame.

Helifax wrote:Right guys,
Here is the fix (wrapper + shader) that removes the blackbars in Surround.
Now I haven't tested it on AMD Eyefinity or 21:9. I only run 3D Surround.
But 99% chances are it will work for everyone;) If not, I am sorry
Like stated above, I am not sure it will work with any other type of wrapper! You are a bit on your own there!

Download link: http://3dsurroundgaming.com/3DVision/Ma ... d_Only.rar

Let me know if it works for you!
Cheers!

LuPoNe wrote:Apologies for the quick posting! I had it on and just loaded my final game save and in conversations was ok, didn't noticed that until now, I'm experiencing the same issue with the UI.

Although, removing the 3DMigoto files doesn't solve the issue, it seems like a game issue now.

theblacklaser wrote:

LuPoNe wrote:Apologies for the quick posting! I had it on and just loaded my final game save and in conversations was ok, didn't noticed that until now, I'm experiencing the same issue with the UI.

Although, removing the 3DMigoto files doesn't solve the issue, it seems like a game issue now.

Definitely a game issue. The UI scales sort of correctly (within a 16:9 box) up to 2560x1080. After that it gets weird, even at 2560x1440. They broke something in the 1.06 update.

PC – Improvements to display when running at different resolutions