Jump to content

BP_Lizard

Members
  • Content Count

    529
  • Joined

  • Last visited

Community Reputation

181 Excellent

About BP_Lizard

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you very much! I’ll tone it down and see how it goes. Funny thing was, I always run these settings (except maybe the 8X AA) and didn’t experience crashes until two or three updates ago. Thanks again.
  2. Thank you for your help and patience. Here are the screenshot of the graphics and dxdiag report. What did you crash into on takeoff? : Nothing. I just barely got off the ground after takeoff. Or in few occasions, still circling around the base, waiting for the AIs to take off. Seems like any mission that I play involving the Rhineland map crashes at one point of another. Sometimes a complete CTD, other times I have to perform hard reboot as the screen was frozen. MODs were uninstalled via JGSME and disabled ingame. DxDiag.txt
  3. Sorry for the late response. Haven't played in a long time. Mission (Single Player Mission) Rhineland Scenarios: BF109K4 - Protect The Ruhr I barely got off the ground from takeoff and it crashed. Location: Koln-Butzweilerhof base (Base pointed by the cursor) Pretty much any game mode played in the Rhineland map crashes.
  4. Hello @Han I hope you could help me with my CTD problem. The game just freezes for a moment, then CTD. No error message is displayed. Attached are the dxdiag text and the zipped dump file. Thank you very much. When you encountered the crash; Flying in a straight flight. Two allied planes behind me in formation. In what game mode (MP/QMB/campaign/scenario); Single player Mission flying the default Rhineland Tempest Mission In what mission; Default Rhineland Tempest Mission What did you do before the crash; The plane was just flying on a straight path with two allies behind me. What happened in the mission before the crash; The game momentarily froze, then CTD. No error message. Additional info you think is relevant to the crash. None. Windows Event log: Faulting application name: Il-2.exe, version: 1.0.0.1, time stamp: 0x5f623839 Faulting module name: landscape.dll, version: 0.0.0.0, time stamp: 0x5f6235d1 Exception code: 0xc0000005 Fault offset: 0x000000000003d747 Faulting process id: 0x47e0 Faulting application start time: 0x01d6914df6c20b34 Faulting application path: G:\Games\Steam\steamapps\common\IL-2 Sturmovik Battle of Stalingrad\bin\game\Il-2.exe Faulting module path: G:\Games\Steam\steamapps\common\IL-2 Sturmovik Battle of Stalingrad\bin\game\landscape.dll Report Id: 6f9438fc-a321-491a-bdd9-7a688234ba61 Faulting package full name: Faulting package-relative application ID: Il-2.exe.18400.zip DxDiag.txt
  5. Yeah. That's the first thing that I did when it started. Did it again after the last update.
  6. @RedKestrel : Thanks. I'll look into those. I forgot to mention that my games and Windows are on separate SSD drives.
  7. Thanks for the tips, guys. i’ll into those. @Thad : Wouldn’t hardware failure cause problem regardless of what you’re running? It’s only IL-2 that crashes.
  8. Been having frequent crash to desktop even before the latest update. Need a little help in diagnosing the problem, please. Thanks. MOBO: ASUS x99-A OS: Win 10 Home 64 bit Intel i7-5820K @ 3.30GHz (oc to 4.40GHz) 16Gig ram RTX 2070 Super (latest NVidia driver) Last time that it crashed, the application log showed this error: Faulting application name: Il-2.exe, version: 1.0.0.1, time stamp: 0x5f623839 Faulting module name: VCRUNTIME140.dll, version: 14.24.28127.4, time stamp: 0x5d8e68d2 Exception code: 0xc0000005 Fault offset: 0x00000000000012de Faulting process id: 0x2e34 Faulting application start time: 0x01d68e2f6ea7d0e9 Faulting application path: G:\Games\Steam\steamapps\common\IL-2 Sturmovik Battle of Stalingrad\bin\game\Il-2.exe Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll Report Id: f32701ec-46d0-410c-b1d5-9263a8417786 Faulting package full name: Faulting package-relative application ID:
  9. Awesome update. Thank you very much. So I tried directly assigning the gun control on the joystick's X and Y axes and it didn't move (hit T to unlock but still no difference). Any other button to hit to make it work? Thanks.
×
×
  • Create New...