General Category > Unofficial F/A-18 Acceleration Pack board

FA/18 CTD with SEQ button

<< < (2/6) > >>

seaviper:
No CTD's here ! I have loaded plans via the default planner and used only the cockpit avionics while flying.

Vista 32, FSX, Acceleration, Xload, UTX USA & Canada
AMD 64 X2 6000+
Asus M2N32-SLI Deluxe
4GB 800mhz DDR2
XFX Geforce 7950GX2
SoundBlaster Xfi-Platinum
SATA 300 GB/s HD
Saitek X52

Wolf_Rider:
Hi,
Yep... same problem

Create plan/ send plane to airfield, in cockpit select WPT... select SEQ and it all falls over   ???

Seriously, great work on the model  :o

virtuali:
Sorry, still doesn't happen here. When I wrote the tutorial, I obviously had to take the same steps, load a flightplan, send the airplane to the departing airfield, pressing WPT and then SEQ to take screenshots, but I never had any crash.


Have you tried updating your Visual C++ runtimes to last version ?

You can do it by installing our Zurich scenery trial OR, if you are not interested, you can download the runtimes from here:

http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en

Wolf_Rider:
Nope... still no go

 Problem Event Name:   BEX
  Application Name:   fsx.exe
  Application Version:   10.0.61637.0
  Application Timestamp:   46fadb14
  Fault Module Name:   MSVCR80.dll
  Fault Module Version:   8.0.50727.762
  Fault Module Timestamp:   45712238
  Exception Offset:   00008a8c
  Exception Code:   c000000d
  Exception Data:   00000000
  OS Version:   6.0.6000.2.0.0.768.3
  Locale ID:   3081
  Additional Information 1:   8988
  Additional Information 2:   37aebcfc1ce546039b15a08dfa1a99be
  Additional Information 3:   0be6
  Additional Information 4:   38f4e2f248c4a825876a4e843322cbcd

virtuali:
This is strange.

Searching in Google for msvcr80.dll and the 00008a8c offset, gives several result, coming from all applications.

I used the name of the dll and the offset, because it gives an idea during in which function the crash happened. Msvcr80.dll is part of the VC++ runtimes, and the 00008a8c is an offset to one of the many library function. It looks like several other programs that do not have anything to do with Flight sim, also suffer from a crash in the same library function.

There's seems to be a pattern, some of the users fixed the problem by returning the memory management strategy to the default setting. Have you changed the swap file setting, from handled by Windows (default) to a specific minimum/maximum size ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page