Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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?
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.
Have fun with Morrowind!
I agree it could be a corrupted save file, it was a lot more common with older games.
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.