Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - mgr.inz.player

Pages: [1] 2 3 ... 9
Cry of Fear Mod Discussion / Re: Most annoying part of Cry Of Fear?
« on: 26 April, 2014, 10:16:38 PM »
Maze. I found a solution, always turn to the right on any junction:

Thank you.

All I can say: this bug has to do something with light which comes from flare or The Book.
I'm not sure if that information will help.

Above fix needs more tests.

"Warning: this topic has not been posted in for at least 120 days."
Yes I know. Don't hurt me.  :wheelchair:

I've been away from this forum for a long time. Why I replied in this old topic?
I just wanted to try "steam version" of this game/mod and I noticed this problem still occurs. Game crash or freeze when I die with the flare out. The same with Simon's Book.

suiciders + nightmare mode + Simon's Book flames = crash festival.

I attached debugger... Looks like it is "access violation" error - this is what debugger shows:
Code: [Select]
"client.dll"+756EF: 85 C0                 -  test eax,eax
"client.dll"+756F1: 0F 85 44 01 00 00     -  jne client.dll+7583B
"client.dll"+756F7: E8 F4 C1 FB FF        -  call client.dll+318F0
"client.dll"+756FC: 84 C0                 -  test al,al
"client.dll"+756FE: 0F 85 37 01 00 00     -  jne client.dll+7583B
"client.dll"+75704: 8B 44 24 54           -  mov eax,[esp+54]
"client.dll"+75708: 85 C0                 -  test eax,eax
"client.dll"+7570A: 0F 84 2B 01 00 00     -  je client.dll+7583B
"client.dll"+75710: F6 05 8C CF C9 09 10  -  test byte ptr [client.dll+10CF8C],10
"client.dll"+75717: 0F 84 1E 01 00 00     -  je client.dll+7583B
"client.dll"+7571D: 8B 83 9C 00 00 00     -  mov eax,[ebx+0000009C]        <===== access violation
"client.dll"+75723: 83 F8 0D              -  cmp eax,0D
"client.dll"+75726: 74 12                 -  je client.dll+7573A
"client.dll"+75728: 83 F8 19              -  cmp eax,19
"client.dll"+7572B: 74 0D                 -  je client.dll+7573A
"client.dll"+7572D: 83 3D EC 6F 03 0A 0D  -  cmp dword ptr [client.dll+4A6FEC],0D
"client.dll"+75734: 0F 85 01 01 00 00     -  jne client.dll+7583B
"client.dll"+7573A: 8B 54 24 38           -  mov edx,[esp+38]

I analyzed above. Crash happens when EBX is 00000000. I forced skipping that part of code. Result? Flares or Book no longer creates additional source of light.

So I added extra check (I patched process memory) like this:
"If EBX is 00000000, then immediately turn off light from flare or Book or whatever"

And it worked!

So, I hardcoded that patch in client.dll file (from "Cry of Fear\cryoffear\cl_dlls" ) and I no longer have game crash or freeze when dying with flare or Simon's Book. Side effect is: Steam will overwrite client.dll with original file, if you have "Always keep this game up to date". Anyone interested?

Nothing changes if you used the patch in a 32-bit Windows.
Not entirely true...

If he has over 2GB (like 3GB or 4GB) he can still use it (read second half):

Few 32bit applications that have LAA (large address aware) flag set:
- Firefox
- Opera
- Camtasia 8
- Borderlands 2
- ...

So, devs can upload/update that cof.exe without worries.

To benefit from this LAA you have to have:
- for 64bit OS - over 2GB, like 3GB or more RAM
- for 32bit OS - over 2GB, like 3GB or more RAM and added extra parameter to startup entry. (see my previous post)

If you have just 2GB or less (and  it doesn't matter 32bit or 64bit OS), Cry of Fear will still work normally (as well as original exe).

Cry of Fear Questions and Answers / Re: Question about time counting
« on: 18 June, 2013, 10:29:32 PM »
will the time between the last save and death be counted into the total time?

It's the same fix used for Skyrim long time ago. You know, "Skyrim 4GB fix".
Fix just enables one bit, "Large Address Aware" bit.

Patcher posted in this topic and patcher for "Skyrim" just sets that one bit/flag and calculate new checksum. (EXEs have checksum field. It's not necessary)


So, only 5-6 bytes are changed.

It means that 32bit application can access up to 4 GiB on x64 operating systems and up to 3 GiB on x86 (more or less).
Details here:

64bit OSes - no changes needed.

32bit OSes with >2 GiB RAM:
Quote from: CODE sucks
32bit   Windows XP, Server 2003:
(basically: /3GB switch added to boot.ini)

32bit   Windows Vista, Windows 7, Server 2008:
just run this command (Programs, Accessories, right-click on Command Prompt and select "Run as Administrator):
Code: [Select]
bcdedit /set IncreaseUserVA 3072

Good finding anyway.

I have an idea to implement this into the next steam update.
How about you have two cof.exe files one that has the 64bit patch, and one that dosen't. then you have the launcher detect if the system is 32 or 64 bit then have it check how many ram it has so it can launch the appropriate exe file.
No need. Many 32bit applications (before Win7 and Win8 even exits) have LAA bit enabled. Firefox.exe, for example, has this bit set. One EXE should be fine.

Cry of Fear Suggestions / Re: Chainsaw as an unlockable weapon
« on: 28 May, 2013, 11:59:43 AM »
The Flashing Gold Chainsaw with Attached Speargun of Death to the Max!

Cry of Fear Suggestions / Re: Death before killing wheelchair simon
« on: 28 May, 2013, 07:10:31 AM »
If you load that map with console command, not all "scripts" will be loaded.

Games with many scripts (Tomb Raider 2013 and DeadSpace3 for example) can break if you use trainers or cheats. Plus, if there is auto-save  system, you are screwed.

@ladderglitch, could you upload your save file
Look which slot it is, then send SAV file from STEAM\steamapps\common\Cry of Fear\SAVE
For example, slot 3, send me "cofsave3.sav" file.

Plus information where you dropped it.  The same room you get it? Another room? Can you back track to that room?

Note: If that room has changed, like, now it has bloody wall, different lit, I can not help.
(some rooms have two versions. Second version on second map. If you dropped it in first version...)

I will check if I can do "ladder bringer".  Tool will be something like trainer, but with only one option (if I succeed).

@jacksepticeye, PM'ed you.

Yes. "CoF1.6 standalone" has more FPS drops than "CoF mod". I have to use "prop fade distance: ON".

Previously, with "CoF mod", I didn't have this problem, I played whole game with "prop fade distance: OFF" without drastic FPS drops. (I only had issues with  No Free Edicts, solved with this: -num_edicts 2048 -heapsize 1024000 )

nVidia Control Panel -> 3D Settings -> Manage 3D Settings -> Global Settings tab -> Restore

Or make new profile:
3D Settings -> Manage 3D Settings -> Program Settings tab -> Click Add
In another window you will see list. Ignore it. Click browse, choose cof.exe (STEAM\steamapps\common\Cry of Fear\cof.exe).

For almost each entry choose: "application controlled" or "Off". Triple buffering: ON. Threaded optimization: OFF, texture filtering quality - high performance. Just an example. Try other settings.

Btw. If you have "preferred graphics processor" option there (you have more than one graphic), choose the one which is more powerful.

I'm using this options:

Create userconfig.cfg file (create new txt file and change file name extension to cfg) here:
STEAM\steamapps\common\Cry of Fear\userconfig.cfg

and paste this:
Code: [Select]
alias +jumpduck "+jump; wait 5; +duck"
alias -jumpduck "-duck; wait 5; -jump"
bind "SPACE" "+jumpduck"
Yes, I know that there are other, 'better & faster', versions. I don't care.

At the end of train scene - "chapter 6 - it's not over yet" - it will be easy.

Pages: [1] 2 3 ... 9