Middle-earth: Shadow of Mordor

[JonnyO2]

Thanks gumbo! I guess that's a RTFM moment.

And yes, the latest patch to SOM broke the flawless plugin, so I am a sad ranger... I really missed the ultra wide view - I'm hooked!

[RealWild1]

This last build for SOM also states it enabled SLI support, so can anybody confirm whether that fix is no longer manually required?

HaYDeN, if you would be so kind as to re-fix the plugin? Thanks!

[Softscope]

Hey, I can't get my UI to work, probably because of the latest patch.

[TheRealDeal]

The Steam overlay doesn't work with the fix enabled, is it meant to be like this or is it just me?

EDIT: Turns out it was just a conflict with fraps.

[iAmTheTot]

I'm having the same Sauron's Army crap, Nvidia surround setup. It's gamebreaking enough for me to disable the fix, and that's a damn shame because it also means to play the game I have to disable surround so the game will render at 1920x1080. Which is super annoying because I have my desktop and windows all set up for a permanent Surround setup.
TL;DR it's annoying.

I would donate HAPPILY if this Sauron's Army crap could get fixed somehow. I have no idea what coding goes into this so I don't even know if it's possible, but I'd love you forever. And donate. Did I mention donate?

[LOWao]

iamthetot, you should consider donating now. Literally, this whole website and the support from it keeps multi-monitor gaming alive. As for the issue with Sauron's Army. What problems are you having? I can't find anything over here. I had a config edit and applied this fix and triple 1080p is working flawless over here. No pun intended.

[tricky]

Played for the first day (first couple of hours was frustrating, prepare to die a lot!, but it gets much better) without the Flawless fix, and it was pretty good expect for BSOD's every hour or two, and it only used the middle screen and a few inches of the left and right screen.

Then applied Flawless and WOW! it really does look great and run great fully triple wide. Also no more BSOD's! I did turn detail from Ultra to High to get better framerate, so looking at either another 780 for SLI, or a 980 so I go Ultra.

I also have the Sauron's army zoomed into too close so you cannot see the front rows, but I can figure it out my moving the gamepad around and once you select a captain, you can zoom on him, so not a dealbreaker for me.

[Tantrumus]

Any chance the Sauron's Army screen will get fixed so the first row can be seen?

Anyone have a workaround?

[Cinnabuns]

I just donated a hundred bucks and I'm also waiting for the Sauron's Army screen to get fixed.

As a workaround I've found that you can still mouse to them or use the arrow keys to switch between the 2 first rows of guys you can't see. That's what I do cause I don't care what they look like, I just want to get intel on the ones I don't have to see their strengths and weaknesses which you can still do. You just can't see them. Its sucks but its workable.

I guess Hayden has been busy.

[psychichigh]

Just saying; HaYDeN, thanks for the fix for SOM, it has made the game worth playing.

Found that since the last update to v1808.18 the need for the HUD Fix and the Menu FOV Fix are no longer needed in my circumstance (Unless disabling in FW does not actually disable them); and it may not be needed for others. Removal of the Letterbox is still necessary and the Game FOV fix is still necessary. I currently play at an FOV fine adjustment of 12.25, though I'm unable to change it in game. Researching this issue online points the issue to having a pirated copy, but paying for the game on Steam should not equate to a pirated copy... Unless I'm missing something with digital distributions...

I am running a full AMD system with 32 GB of memory and dual R9 290Xs, and I have found that the game is unstable with this much memory, with and without the hacks running, but a little less stable with the hack running. A workaround is to remove two sticks and bring it down to 16 GB, which will cause the game to crash a little less, though I'd prefer not to have to shut down my system and prep it to play the game. Just wondering if anyone else has run into this issue, or may it's just me smoking bad herbs again.

Recently switched over to manual display configuration instead of using detect, as I found that when I have the debug console open there was continually flooding due to video detection, which was coming up at random times.

This is currently what the debug console reads out to me while I'm playing SOM

Code: Select all

UpdateManager -> Hashing Dependencys...
PluginManager -> Instancing Module: Middle Earth: SOM
error running function: ...ShadowOfMordor\Dependencies\Scripts\MEShadowOfMordor.
lua:195: attempt to index local 'MenuFOV' (a nil value)
DisplayDetection -> Scanning process for signs of SoftTH injection
c_HackTool -> Successfully opened process, ID=5648
Suspending Thread
GameFOV - Addr=ShadowOfMordor.exe+54D5AA
LetterboxFix - Addr=ShadowOfMordor.exe+D64409
HUDFix - Addr=ShadowOfMordor.exe+E806DC
MenuFOV - Addr=ShadowOfMordor.exe+5DE475
MenuFOV - Addr=ShadowOfMordor.exe+14088C4 (float=1.78)
Un-Suspending Thread
Inject delay: 5ms, Configure() took: 340ms, Adjusted Inject delay: -335ms
Actual delay: 1ms
Suspending Thread
c_HackTool -> JMP candidate for GameFOV_cc, NOPS=1, Address=0x7ff7cfd0d5aa
c_HackTool -> JMP candidate for HUDFix_cc, NOPS=3, Address=0x7ff7d06406dc
c_HackTool -> Successfully allocated 4096 bytes at 0x7ff7d1480000 for ASM block
"FOVFix"
c_HackTool -> Assembly compile was successful
Un-Suspending Thread
c_HackTool -> Failed to write process memory at 0x7ff7d1470014, error code = 5
c_HackTool -> Failed to write process memory at 0x7ff7d1470014, error code = 5
c_HackTool -> Failed to write process memory at 0x7ff7d1470014, error code = 5
c_HackTool -> Failed to write process memory at 0x7ff7d1470014, error code = 5
c_HackTool -> Failed to write process memory at 0x7ff7d1470014, error code = 5

The debug console is showing that the HUD fix is still running? As well, there is an error with indexing of the MenuFOV being a null value (even though it's not??, as per the script). As well, it can be seen that the memory block 0x7ff7d1470014 can't be written to, my guess is either it's locked/secured memory, or there are issues with the memory does not contain the expected values to modify? I'm just taking a guess at that since I'm not sure if this is a windows kernel error code or one from Flawless Widescreen. Unfortunately I've only run the debug console a couple of times while playing this, and I don't remember or recall of this memory that the system can access is moving or not (I'd assume it's a dynamically assigned block and not static, but you can never tell with game developers)

Anyone have any clues on where to begin looking at the LUA script to resolve the issues with the MenuFOV coming up NIL during launch, and what the error code really means in regards to this memory block it can't write?

Thanks in advanced,

Just another triple monitor gamer


EDIT
I guess I'm just being a noob, ran a couple memory diagnostic applications and found that errors with either the memory, the north bus or the CPU, and will need to dig down further to figure out which is the cause of the game being unstable. Time to troubleshoot that once Christmas is done.

[dayglow]

Just downloaded as I bought it off of the steam sale. It seems that triple screen is broken again. If I run flawless with everything enabled the UI is off the screen and I can't see anything to select. If I turn off menu FOV fix and HUD fix like the other post in the thread, the menus appear fine, but the game is horribly stretched during play.

*edit* found out it's the AMD card detection that is not working as per Hayden's post in the thread. Changed it to manual and works as intended, thanks for the great support.

[Hey Friends]

Hey!

I'm very new to NV Surround and I'm having a little bit of an issue with this, I have a strong feeling it's something rather simplistic that I have messed up along the way... the message I'm receiving in the debug window is as follows -

Configure function call for the attached process failed, retrying in 14 seconds...

Last Error:
nil

Could someone point me in the right direction with the resolve for this?

*Edit* I read the above comment... all working as intended 10/10

[bkc6j]

I'm not sure what I am doing wrong, but I can't even get this one off the ground. I'm running 7680x1600 with NVIDIA Surround. When I first loaded the game, the were no widescreen options at all within the Video menu of the game. Just 2560x1600 or multiples of that (5120x3200).

So I loaded the right module for Flawless Widescreen and loaded the game again. Still 2560x1600. Normally, there would now be options within the game to change it. So next I tried to manually input 7680x1600 into Settings.cfg and that didn't work either (game sticks to one screen, but tries to run an insane resolution on the one screen).

So what step am I missing? How did everyone get the wider resolution even selected (I'm not having FOV issues, the other 2 screens aren't getting any signal at all).

PS: I am getting no errors from FW, and the detection seems to be working correctly from the message. I just can't figure out how to get the game to attempt to render the higher widescreen resolution.

[imusrt]

bkc6j if all else fails, you could spread the game manually (assuming FWS supports your game version).
Middle-earth: Shadow of Mordor screenshot. PLP manual full spread. Full-size & instructions here

[bkc6j]

bkc6j if all else fails, you could spread the game manually (assuming FWS supports your game version).
Middle-earth: Shadow of Mordor screenshot. PLP manual full spread. Full-size & instructions here

The manual method you recommended is the only way I've been able to get anything above 2560x1600 to display. But since I've never done that method before, I am not sure what all the offsets should be. It is working, but I still have the big window bar at the top of the screen. Which of these settings do I have wrong? Should ScreenHeight be smaller to take into account the bigger border? Or am I going in the opposite direction and should be making things bigger to push off the screen?

"ScreenHeight" "1572.000000"
"ScreenWidth" "7665.000000"
"ScreenX" "0.000000"
"ScreenY" "0.000000"
"WindowHeight" "1600.000000"
"WindowWidth" "7680.000000"

[imusrt]

Glad it works bkc6j. It is a more complex manual spread than many games, but you are nearly there. It may be that just your ScreenX & ScreenY numbers are missing.

Instructions have been updated to clarify.

[AVictorD]

Hi Guys,

Having a problem trying to get Widescreen (5760 x 1080) working with 3D Vision and vice versa. When using widescreen (No borders) the SLI record for SOM is ignored (no NVIDIA green text) and no 3D. If I change the Settings.cfg back to the original settings ( with 1920 x 1080) the SLI is recognized and the game can run in 3D but no widescreen.

Does anyone have a fix for this. Cheers,

Running NVIDIA 344.75 verion 1808.19 of SOM.

Settings.cfg
----------------
"DeviceAdapter" "0.000000"
"DeviceOutput" "0.000000"
"ScreenHeight" "1080.000000"
"ScreenWidth" "5760.000000"
"ScreenX" "872.000000"
"ScreenY" "125.000000"
"VSyncOnFlip" "0.000000"
"Windowed" "2.000000"
"WindowHeight" "480.000000"
"WindowWidth" "720.000000"

[jeff420]

Well it looks like the recent update broke the fix again. IT really sucks. I just want to play the game, but refuse to play on a single screen. It's feels so limiting after using 3 screens. Hopefully FWS gets updated soon. Thanks for the hard work Hayden

[AVictorD]

Well it looks like the recent update broke the fix again. IT really sucks. I just want to play the game, but refuse to play on a single screen. It's feels so limiting after using 3 screens. Hopefully FWS gets updated soon. Thanks for the hard work Hayden

It can run with "Borderless" or even "Windowed" where it can correctly determine the screen resolution for Surround (5760 x 1080), but no SLI and 3D Vision on these settings. Unfortunately FULLSCREEN fails to determine the screens actual resolution and sets predefined resolutions (eg. 1920 x 1080) or a single monitor. So SLI and 3D can ONLY run on a single monitor.

[helifax]

Well it looks like the recent update broke the fix again. IT really sucks. I just want to play the game, but refuse to play on a single screen. It's feels so limiting after using 3 screens. Hopefully FWS gets updated soon. Thanks for the hard work Hayden

It can run with "Borderless" or even "Windowed" where it can correctly determine the screen resolution for Surround (5760 x 1080), but no SLI and 3D Vision on these settings. Unfortunately FULLSCREEN fails to determine the screens actual resolution and sets predefined resolutions (eg. 1920 x 1080) or a single monitor. So SLI and 3D can ONLY run on a single monitor.

Maybe this post is what you are looking for in solving your issue:)
https://forums.geforce.com/default/topi ... 8/#4420798