Dead Space Crash about umod HOT 12 OPEN

Can you please use the version with loging mode enabled and provide me the 
uMod_log.txt, which should be in the game directory after you have run the game.

Best
ROTA

I Still can't seem to pull textures from the game, I created an output folder 
on my desktop and when I attempt to load the textures, none are put into the 
output folder, I have the "Save all textures" box ticked and have-reloaded the 
save. Didn't work, anyway I'll attach this log for you, I'd appreciate some 
help with getting this all working 

In the log text I can't see any notice about an action from the GUI, therefore 
the "save all texture" mode was not enabled in the game. This means you did not 
used the update function. If you change something you must press the update 
button in uMod1 and over the context menu (right click in the bottom window, 
where also the mod-packages are listed) in uMod2 (what you are using).

I'm still not getting any input from the GUI, Set keys, Updated. Set text and 
texture highlight colour, updated. Select single textures, Updated. Select a 
save file, still got nothing. If i'm not mistaken, i'm launching the game 
through Steam. The readme said something about not launching it through Umod?

I am sorry, I could not answer yesterday. The system was read only for network 
maintenance.

Well I get the feeling you make all your settings in the "default page" which 
does not belong to any game! I should in future disable the update menu entries 
for the first page to make this more clearly.

If you start a game through uMod or
1) you enabled the global hook
2) added the game to the list
3) start the game by your own
then in uMod a separate tab window will open labelled with the name of the game 
exe (without the .exe file extension). In uMod V2 also the injection method 
should be printed and in the same window the number of created DirectX9 devices.

If no such extra tab-window is opened, then uMod has not injected the game.

If the extra tab is opened and the injection method (you have chosen) is 
displayed but no (DX9), (DX9:a number), (DX9EX), or (DX9EX:a number) is 
written, then uMod could inject the game but somehow was to late to detour some 
DirectX functions (e.g. global hook and GW1 under WinXP). Therefore you are 
also not able to use uMod with this game.

(DX9: a number) is a counter for IDirect3DDevice9 objects created by the game 
and detoured by uMod (one object is displayed as (DX9) instead of (DX9:1)). 
Only such detoured IDirect3DDevice9 objects uMod can be manipulated by uMod.

But due to a bug this counter is not decreased, so it is the sum of once 
created devices and not the actual number.

Okay, the second tab opened like normal. I updated everything, loaded the Map 
again. "(DX9)" is in the Injection area, so i'm thinking Dead Space is 
Incompatible with Umod, or it might just be the steam version.

There is also a still open problem with certain kind of textures. uMod is not 
able to compute the hash of all textures "types". It might be the worse case 
that Dead Space might only use these textures and uMod is therefore not working.

It would be great if you can upload the uMod_log.txt. If you're using the 
logging version of uMod, then this file is created in the game directory. It 
contain information about created device, textures and their formats, ... 

Alright, Here is the log, I hope it helps you in the development of Umod. Let 
me know what you find

I guess uMod has problems with spaces in the directories names and in the game 
name. I think I only must put quotes around the file name. But the executable 
of Dead Space is labelled as "dead space.exe" therefore at least one space is 
in the texture file names.

And there are also some (5-10) textures, which could not be locked by uMod, but 
these you are not able to select.

This would apply for all copies of dead space then, Correct?

If you can rename the game executable to deadspace.exe (without space) and also 
select a save directory without spaces in the path, then you could test if my 
theory is correct. But unless the binary has a space in the name, you still 
have the problem for all copies.

I must admit, that I cannot reproduce the error with spaces in the path or the 
binary name any more. Therefore this should also not be the bug!

I am sorry, but I don't have any clue what is going wrong with DeadSpace and 
uMod