Runtime error and crash

I;m having the same problem, any help. Hate paying $20 to have a game that doesn't work

Had crashes under multiplayer, when looking at the servers list. And then I remembered I had ffdshow installed.

So, I added launcher.exe & simulator.exe (./LockOn Flaming Cliffs 2\bin\x86\stable) into both video and audio ffdshow decoder exclusion lists and the problems went away.

Hope it helps

Thanks for the tip but I have no idea what "ffdshow" is and I do not use it.

For me (and others) this bug/issue is related to the memory management in both FC2 and DCS:BS while running under 32-bit OS (Windows XP Pro here). The CTD happens when simulator.exe RAM-usage gets beyond a specific point (in my case roughly ~1.35 GB).

This bug/issue is known by ED and planned to be fixed in upcoming patch.

See http://forums.eagle.ru/showthread.php?t=54162&page=6 for more information by a ED rep.

/KC

A bit low on motivation but still trying to find cause/solution/workaround to this issue and have been setting up Performance Counters in XP to see more exact what RAM-usage is when the CTD happens.

Attached are eight screenshots showing simulator.exe memory usage (working set) for FC 2 1.2.1 when CTD happens in both SP and MP, see first for diagram legend.

Only thing I can conclude from this so far is that it doesn't happen on exact same memory usage but always when simulator.exe memory usage is high, just guessing here but maybe it's some other Win32 resource that runs out!?

Anyone have any advice/thoughts? Also, are there any other counters to track that would be helpfull for the developers?

PS: If anyone want's the Performance Counter profile for XP Pro to do same tests just let me know...

/KC

I'm trying to better understand what the memory usage (Working Set) actually is since the difference is quite big between different tests and also why it's a huge difference from the Peak Mem Usage value showed in Taskmanager (see attached pics, all taken after the CTD happend).

The information I found from MS regarding the Working Set is...

Process : Working Set.

 

This is the current size of the memory area that the process is utilizing for code, threads, and data. The size of the working set will grow and shrink as the VMM can permit. When memory is becoming scarce the working sets of the applications will be trimmed. When memory is plentiful the working sets are allowed to grow. Larger working sets mean more code and data in memory making the overall performance of the applications increase. However, a large working set that does not shrink appropriately is usually an indication of a memory leak.

Is the Working Set showing the "simulator.exe" process virtual memory usage and Peak Mem Usage (in Task Manager) showing "simulator.exe" process actual RAM usage, anyone knows?

/KC

Maybe a dumb question:

You guys have FC 2 installed on same drive were you have installed your OS?

Try install on different drive.

I have 2 hdd's in my system:

1. OS

2. LockOn

Here's how i installed it:

1. Install Lockon 1.0
   
2. Install Flaming Cliffs
   
3. Install Patch 1.12b for "LockOn 1.1: Flaming Cliffs" simulator
   
4. Start Lockon and reboot if asked
   
5. Install the Starforce Update
   
6. Reboot
   

Then FC 2 and the FC 2 patch.

Hope this helps.

Never ever i had problems with APPCRASH (knocking on wood)

Anyways, maybe you should try it.Cant do any harm i guess.

Good luck!

Maybe a dumb question:

 

You guys have FC 2 installed on same drive were you have installed your OS?

 

Try install on different drive.

 

I have 2 hdd's in my system:

1. OS

2. LockOn

 

 

 

Here's how i installed it:

1. Install Lockon 1.0
   
2. Install Flaming Cliffs
   
3. Install Patch 1.12b for "LockOn 1.1: Flaming Cliffs" simulator
   
4. Start Lockon and reboot if asked
   
5. Install the Starforce Update
   
6. Reboot
   

Then FC 2 and the FC 2 patch.

Hope this helps.

Never ever i had problems with APPCRASH (knocking on wood)

 

Anyways, maybe you should try it.Cant do any harm i guess.

 

Good luck!

No need of #2, #3, #4 and #5.

Just install lockon, then FC2 in a different folder (as an administrator and outside /program files)

Its just the way i did this install.

And worked for me so far.......:thumbup:

Hi Emmer,

You guys have FC 2 installed on same drive were you have installed your OS?

Same as you...

C-drive is OS and FC2 (& BS) is installed on D-drive.

OT: See you have F10's "Johan Red" marking in your profile, fond memories of that since I live ~3 km from the old F10 airbase.

/KC

No need of #2, #3, #4 and #5.

Just install lockon, then FC2 in a different folder (as an administrator and outside /program files)

Ok, will give that one a try.....thx!

Saves a lot of work.

Attached are the Performance Counter profiles if anyone want's to do their own tests. Just dubbel click on the profile before you start the sim...

Works with FC2 and DCS:BS in XP/Vista/Win 7 32-bit. I also included one specific profile for DCS:WH I did for a friend.

/KC

DCS_Memory_usage.zip