The Elder Scrolls II: Daggerfall

The Elder Scrolls II: Daggerfall

Error code 519// Need help fixing
Every time i wait in the Crimson mug in dagger fall and walk outside my game crashes and gives me a Error code 519 other times i can get outside but as soon as i interact with somebody it crashes again. I patched with dag213 hoping that it would solve the problem and it hasn't so now im here. Any help would be appreciated. Thanks!!
< >
Showing 1-8 of 8 comments
Doesn't seem to be a common problem. I've seen one or two internet posts linking it with DOSBox cycles, but can't say if there is a real relationship. At any rate, I'd be surprised if it were a genuine Daggerfall bug.
Please confirm that you play Daggerfall (and not Daggerfall Unity) in Steam, and that you didn't edit df.conf (in the DOSBox subfolder of Daggerfall).
If yes, and before doing anything else, verify your Daggerfall installation in Steam. It fixes missing or corrupted files. Then try again.
If this doesn't help, open df.conf, and have a look at the "cycles=..." line. What does it say? If the value is not 50000, you could change the line to
cycles=50000 or
cycles=fixed 50000
Then save the file and try again. Does it help?

If not, please describe your PC. And are all crashes you mention accompanied by error 519? To install dag213 doesn't change anything - the Steam version has it already.
Did you modify your Steam installation of Daggerfall in any way, edit a configuration file, install a mod?
Lmaooo this is a lot im 21 and this is my first PC and i feel like an old timer when it comes to everything you just said. I have the OG free steam version and i have not modded it in anyway. The only thing i haven't done is mess with the DOSbox cycles. Ill try and figure it out, i managed to install DAG213 through console commands so im sure i can figure this out as well. My PC runs a RTX3050 more than capable of running daggerfall. Thanks for taking the time to comment and help me out
Originally posted by Doobiedoo813:
... i managed to install DAG213 through console commands ...
???
You can download dag213.exe from there: https://en.uesp.net/wiki/Daggerfall:Files, and then just run the exe, no console required. Which "console commands" did you use?
But, like I said, it's installed already, and it won't do anything.

Sorry that I can't be of more help. Verification should always be the first action (for any game on Steam) when you get crashes or technical error messages (just to make sure all files of the installation are there and not corrupt). And editing the cycles may or may not help. I just mentioned it, because I had read about it.

Have you tried going back to older savegames (or even starting a new game)? It is possible that the most recent one, or a few recent savegames, are damaged, and verification wouldn't fix damaged savegames.
I went to "browse files" on daggerfall through the steam library and i installed it through there. I think DF was the one i had to browse through but i gave up and uninstalled it lol and moved on to playing morrowind. I have a feeling that my files were corrupted and i probably would have needed to start a new game. Thanks again
lonetrav Feb 9 @ 12:41am 
Originally posted by Doobiedoo813:
I... I have a feeling that my files were corrupted and i probably would have needed to start a new game. ...
Most likely (and verification would have fixed it, unless a savegame was corrupted, and for corrupted savegames Daggerfall's FIXSAVE utility might help).
Have fun with Morrowind!
Originally posted by lonetrav:
Originally posted by Doobiedoo813:
I... I have a feeling that my files were corrupted and i probably would have needed to start a new game. ...
Most likely (and verification would have fixed it, unless a savegame was corrupted, and for corrupted savegames Daggerfall's FIXSAVE utility might help).
Have fun with Morrowind!

I agree it could be a corrupted save file, it was a lot more common with older games.
Klutch Feb 9 @ 10:26pm 
there was a lot of crashes, and broken quests in the last version of the game. i can remember always checking for a patch because you never knew when they would drop one, but that was 30 years ago
lonetrav Feb 10 @ 12:11am 
Originally posted by Klutch:
... i can remember always checking for a patch because you never knew when they would drop one, ...

You describe the situation before the final patch was released. After the final patch was released, at least my Daggerfall installation didn't crash anymore (for the "void bug" Bethesda made a workaround available).
And "broken" quests? Here my memory fails me. I know that uesp documents quest bugs, and I'm likely to have encountered one or the other - but I'm sure none of the quest bugs I encountered was game-breaking (worst case: a side-quest couldn't be completed). Well, it's possible that players stopped playing because they were annoyed that a few hours of sometimes tedious dungeon-crawling were lost :-).
Not much different from what you could say about today's games.
< >
Showing 1-8 of 8 comments
Per page: 1530 50