Jump to content
Welcome to the virtual battlefield, Guest!

World War II Online is a Massively Multiplayer Online First Person Shooter based in Western Europe between 1939 and 1943. Through land, sea, and air combat using a ultra-realistic game engine, combined with a strategic layer, in the largest game world ever created - We offer the best WWII simulation experience around.

F9 = ctd ??


bronco69
 Share

Recommended Posts

i drive my TIGER from CHARLEROI to BINCHE ... got a nice spot ... i want to make a screenie ... press F9 ... BANG!!! CTD

and it isnt the first time it happened the same way

Link to comment
Share on other sites

Can you post the wwiollog.txt?

Did it print the screenshot?

dont know if the screenshot was created ... some time ago now

i dont have the .txt file .... searched my whole computer for it... even tried: wwiiollog.txt

Link to comment
Share on other sites

I've had a ticket for this before but that was closed as works for me. If ti happens again please let me know.

Link to comment
Share on other sites

this happened a lot to me in 1.30/1.31 eventually I just stopped taking screenies

just tried it at map screen. instant ctd.

and no, it did not print the screenshot

ww2_log had this to say:

Date and time: 10/26/2010 23:29:29

Program compile time: Oct 14 2010 16:38:24

File version: 1, 32, 4, 255

GL Vendor: NVIDIA Corporation

Renderer: GeForce GTX 285/PCI/SSE2

C++ Exception: class std::runtime_error 'Out of memory' at address 7630B727

OS-Version: 6.1.7600 () 0x100-0x1

[7630B727] (KERNELBASE): : RaiseException

[00CB1B7F] (ww2): :

[00793759] (ww2): :

[00957F04] (ww2): :

[0095A7AB] (ww2): :

[0095AC7F] (ww2): :

[00792AF8] (ww2): :

Edited by Rubbish
Link to comment
Share on other sites

  • 4 months later...

ctd's occured on my system when the corresponding HDD was in power save mode. after disabling power saving on the /$USER$/ drive, they did not happen anymore when taking screenshots.

so long slpr

Link to comment
Share on other sites

In 1.32 this means you ran out of memory. In 1.33 this should not happen. Make sure you report which version you got this error on.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...