Author Topic: Access Violation at address 0056DF6F in module 'SOLDAT.EXE' Read address FFFFFFF  (Read 1187 times)

0 Members and 2 Guests are viewing this topic.

Offline Coolio

  • Camper
  • ***
  • Posts: 320
  • Well cya all.
Ok i tired clicking on video captability and that wont even work? what should i do? PLEASE HELP ME. :( ;D
BANNED

Offline edak

  • Flagrunner
  • ****
  • Posts: 505
  • AussiEdak
Please read other similar posts, but here is the fix

The only way I could get around this issue was to:

1. Check 16 bit
2. Select 640x480
3. Turn OFF antialiasing AND dithering
4. Turn ON video compatibility
5. Turn OFF force software
6. Turn OFF ATI fix.
7. Run in full screen

let us know how this goes.

UPDATED 12-Aug-2010 FIXED LINKS!!!!! - 18 Apr 2007 - NOW WITH FULLLY MODDABLE MAP TEXTURES! Modders, further customise your soldat!

Offline Arato

  • Major(1)
  • Posts: 35
  • Arato pwnage
    • Elite Newbs
you don't have to run full screen it works small screen for me

Offline TimespliTT

  • Major(1)
  • Posts: 6
  • Time To SpliTT
ill just post this here
im getting

Access Violation at address 0056DF6F in module 'SOLDAT.EXE' Read address 00000000

maybe fixed it i clicked make compatible
« Last Edit: May 01, 2007, 06:44:49 pm by TimespliTT »

Offline ChiefBlackFoot

  • Major(1)
  • Posts: 13
sounds like what happens when you as a programmer try to read from a string or structure that no longer exists...  delphi should take care of this so maybe it's a problem with battleye or video hardware

Offline GordonFreeman

  • Major(1)
  • Posts: 7
Quote
sounds like what happens when you as a programmer try to read from a string or structure that no longer exists...  delphi should take care of this so maybe it's a problem with battleye or video hardware


In string or structure types it does take care, but it doesn't in types and classes that needs to be created and destroyed... In fact, the Access Violation exception is the most common when u work with objects of any kind. I think that all Delphi developers suffer when an exception of this kind appears (because sometimes they're really difficult to debug  >:().

And the most strange thing is that Direct3D libraries are interfaced, so... they shouldn't raise Access Violation exceptions. But, f.e., if the IDirect3DDevice9 doesnt start due to a hostil environment, it has a nil reference and may raise that.

Sorry about my english (Im from Argentina)!
Ill see you on the Dark Side of the Moon