uMod & Mass Effect 3?

[GoogleCodeExporter]

- What steps will reproduce the problem?

uMod manages to hook only by using global hook, it cannot be injected with any 
other method (I do not have access to the window enabling me to add .tpf files).

When I load a .tpf file, both uMod and ME3 freeze and crash.

- What is the expected output? What do you see instead?

Though it is expected to load the file, both uMod and ME3 crash (stop 
responding).

- What version of the product are you using? On what operating system?

Mass Effect 3 v1.3 (all available DLCs installed - Origin digital version) on 
Windows 7 x64 HP SP1.

- Please provide any additional information below.

Texmod is working, limited, but working.

Can anyone provide any information whether this program can work like Texmod 
with ME3 or whether there is a chance it will be working with ME3 in the future?

Thanks for anyone who responds in advance!

Original issue reported on code.google.com by giorgosm...@hotmail.com on 28 Jun 2012 at 7:53

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok, deleted my previous comments. To sum it up, I got uMod working for ME3. 
Just follow the process like in TexMod to bypass Origin. 

Though it would seem like FPS hit is lesser compared to TexMod, it becomes more 
apparent when transitioning from one location to another, or if an 
event/cutscene is triggered, the game freezes for a while.

Original comment by mark26sa...@gmail.com on 22 Jul 2012 at 7:19

[GoogleCodeExporter]

Hi,

thank you for your comment. TexMod seems to calculate the hash each frame 
again, but uMod computes the hash only in moments, the hash might have changed. 
Thus uMod should in most cases do not slow down the game. It seem that ME3 uses 
the UpdateTexture function massively thus the hash is calculated very often and 
my hashing algorithm is very poor against them of TexMod.

I have taken now a faster one. It will come with the next upload.

Original comment by c...@koerner-de.net on 22 Jul 2012 at 8:01

[GoogleCodeExporter]

Wow, that was a quick reply. Thank you for the effort you are putting in this 
project. Looking forward to your next release.

Original comment by mark26sa...@gmail.com on 23 Jul 2012 at 10:42

[GoogleCodeExporter]

Mark, can you specify which method you got working? I tried to use the "Run 
from uMod" method for loading ME3 and that does seem to work, HOWEVER, it 
negates my ability to use FXAA d3d9.dll and/or ENB d3d by Boris. Both of which 
significantly improve the image quality. Something we texmodders believe go 
hand in hand with updated textures is improved shadows and lighting.

Which method would allow me to preserve the functionality of FXAA Tool and/or 
ENB?

Thanks!

Original comment by inbounds...@lugovsky.com on 11 Sep 2012 at 9:12

[GoogleCodeExporter]

To be more specific on my above comment. When I said, "negates" I mean my ENB 
is setup as normal, however, when ME3 loads it appears to have ignored the 
d3d9.dll in my Mass Effect 3 folder.

Texmod doesn't present the same issue and works (albeit slooooooowly and 
sometimes unstably) alongside ENB/FXAA.

Original comment by inbounds...@lugovsky.com on 11 Sep 2012 at 9:14

[GoogleCodeExporter]

Inbounds,

I realize that I am replying to a month old question and I'm sorry about that. 
I recently used uMod again, and for some reason, it just doesn't work anymore. 
I think it has something to do with the new Origin client. I had to reinstall 
the whole game. 

Unfortunately, I tried running it again only to get a "missing d3d9.dll". I'll 
try experimenting with it when I'm not busy.

Oh, and I used "Start game through uMod" before.

Anyway, if you frequent the Bioware Social Network and looked up the thread of 
smarteck, a kind user posted this:

"Navigate to Origin's Install location. Rename IGO32.dll to IGO32.dll.disable. 
Now restart Origin, and launch ME3. You shouldn't get an instant crash now.

Anyone that is using the FXAA tool, will get an instant crash after the latest 
Origin update. It's the IGO32.dll file that is causing this. Simply rename it, 
and problem is solved."

If that didn't work for you, I'm sorry I couldn't be of more help.

Original comment by mark26sa...@gmail.com on 5 Oct 2012 at 7:11