Has anybody been able to use CFF Explorer from Explorer Suite III to allow the DAOrigins.exe file to use more than 2gb ram? I have 6 on my system and would like it to take full advantage of it because I'm running the game with the JBTextures mod and am experiencing issues where there are black or missing textures in certain areas. I heard that using the 4gb patch will fix this but when I try to use it and then load the game I get an error from steam (I believe its error 51). I can use this patch on other games like Fallout 3, New Vegas, Oblivion and Morrowind just fine - and I own the Steam versions of all of those games, but I can't use it with Dragon Age Origins.
Interestingly, I seem to recall having the same missing texture errors a while ago when playing the original Dragon Age: Origins and the 4gb patch worked fine then, but with the Ultimate Edition it doesn't (again, I own the Steam version of both Origins and Origins: Ultimate Edition).
Dragon Age Origins - Ultimate Edition Steam version and the 4gb patch (CFF Explorer)
Débuté par
Browncoat1984
, janv. 11 2011 06:40
Retour en haut
#2
Posté 11 janvier 2011 - 06:47
Browncoat1984
-
- Members
- 20 messages
Okay, I figured out what to do! I own both Dragon Age: Origins and Dragon Age: Origins Ultimate Edition. I remember being able to use the patch on DA:O so I re-downloaded DA:O. I enabled the patch and then copied my addins folder from DA:OUE so I would have the DLC and everything worked perfectly!
#3
Posté 11 janvier 2011 - 08:40
Nemesis047
-
- Members
- 3 messages
So.... Any way for this to work for people who don't have DA:O? I only have the ultimate edition from steam.
#4
Posté 11 janvier 2011 - 08:51
Browncoat1984
-
- Members
- 20 messages
Unfortunately I don't think it will, I think the only way for that to happen is for people to contact Valve and/or Bioware about the issue.
#5
Posté 11 janvier 2011 - 09:28
Nemesis047
-
- Members
- 3 messages
So I paid money for a game that crashes every other time i cast certain spells? great.
#6
Posté 11 janvier 2011 - 11:31
DekklinOfDeath
-
- Members
- 3 messages
Ugh, i'm having the same problem i'm afraid. I've got a system that can more than handle this game, but crashes abound, especially when playing an Arcane Warrior (with all those modal abilities activated). I love this game so much, but these crashes are infuriating. I've tried everything under the sun, setting cpu affinity, setting cpu priority, vid card drivers, run in xp compatability... Nothing's working. This is the only thing that has a hope of fixing this issue. People all over are having these crashes yet I havent heard any word about a new patch.
#7
Posté 24 janvier 2011 - 01:41
Trixor
-
- Members
- 13 messages
I love how people forget that Bioware is part of the EA conglamorate. Don't expect any fixes anytime soon. DA2 is close to release, so there is little to no money to be made with DA:O anymore. Deal with it.
I'm having the same crap as well (also with ME2, so i'm getting used to it)
I'm having the same crap as well (also with ME2, so i'm getting used to it)
#8
Posté 24 janvier 2011 - 05:31
RaenImrahl
-
- Members
- 5 386 messages
A list of the top things that can cause game glitches/crashes when casting visually "demanding" spells (my opinion, and in no particular order):
1) You're playing at a higher resolution than the program is capable reliably using on your system.
2) You have the in-game graphics settings (AA, Texture detail, etc) set higher than DA can reliably run on your system.
3) The control software for your video card (i.e, Catalyst or Nvidia Control Panel) is overriding or "enchancing" the 3D settings of the application to an extent that your CPU or GPU can't handly it reliably.
4) You have a really fast graphics card (with fast running RAM) but a CPU that's closer to the games minimums. The disparity can cause some headaches, as DA is klunky game that is CPU heavy. See: http://social.biowar...8/index/5562579 and other posts.
5) You have a CPU that is being overclocked. DA doesn't seem to react well, at least not reliably, to this. EDIT: It does not necessary relate to an overheating issue, BTW.
6) You have a graphics card that is overclocked-- this can be tricky, because some cards come "factory overclocked", so it may be overclocking and you've never touched it. Driver updates can help here. So can manually adjusting the ram timings on your GPU (see link in #4).
7) Your system is overheating-- I know how frustrating this answer can be. It does happen, though, and if it does, it doesn't mean you're a bad person!
8) You're computer is loading an astounding amount of crap into memory when Windows boots. See: http://social.biowar...8/index/5816873 as an example.
9) You've modded the game or done some other sorts of unconventional things to it.
10) You're playing too damn long in one sitting-- unless you have a bladder made of cast iron, you're going to need to take a bathroom break once in a while. Save and restart the game, or better yet, reboot the PC while you tinkle. Clear out your systems memory and give it a chance to catch its digital breath.
11) You're multi-tasking too many other applications while also playing the game.
12) EDIT: Any combination of the above-- this happens a lot and makes troubleshoot all the more... well... troublesome.
There are, of course, many other factors. Hardware combinations, some iterations of Crossfire or SLI, an old, abused installation of Windows... all of these things probably play a part. Some people also believe the latest (and we can assume final) patches for the game are bugged-- I have never encountered a problem with them, but since they change how the game uses system resources, I don't doubt that some people experience issues.
Finally, remember that software, especially OS's, are a living thing. They change, grow, and get sick. Keeping an OS in good operational state is essential when playing a demanding game like DA. Also, not all 3D games put the same demands on a system-- DA seems to be unique in how it is coded, at least to the extent that it relies on the main CPU for certain effects-- at least if other posts on this site can be believed.
Just some proverbial food for thought.
1) You're playing at a higher resolution than the program is capable reliably using on your system.
2) You have the in-game graphics settings (AA, Texture detail, etc) set higher than DA can reliably run on your system.
3) The control software for your video card (i.e, Catalyst or Nvidia Control Panel) is overriding or "enchancing" the 3D settings of the application to an extent that your CPU or GPU can't handly it reliably.
4) You have a really fast graphics card (with fast running RAM) but a CPU that's closer to the games minimums. The disparity can cause some headaches, as DA is klunky game that is CPU heavy. See: http://social.biowar...8/index/5562579 and other posts.
5) You have a CPU that is being overclocked. DA doesn't seem to react well, at least not reliably, to this. EDIT: It does not necessary relate to an overheating issue, BTW.
6) You have a graphics card that is overclocked-- this can be tricky, because some cards come "factory overclocked", so it may be overclocking and you've never touched it. Driver updates can help here. So can manually adjusting the ram timings on your GPU (see link in #4).
7) Your system is overheating-- I know how frustrating this answer can be. It does happen, though, and if it does, it doesn't mean you're a bad person!
8) You're computer is loading an astounding amount of crap into memory when Windows boots. See: http://social.biowar...8/index/5816873 as an example.
9) You've modded the game or done some other sorts of unconventional things to it.
10) You're playing too damn long in one sitting-- unless you have a bladder made of cast iron, you're going to need to take a bathroom break once in a while. Save and restart the game, or better yet, reboot the PC while you tinkle. Clear out your systems memory and give it a chance to catch its digital breath.
11) You're multi-tasking too many other applications while also playing the game.
12) EDIT: Any combination of the above-- this happens a lot and makes troubleshoot all the more... well... troublesome.
There are, of course, many other factors. Hardware combinations, some iterations of Crossfire or SLI, an old, abused installation of Windows... all of these things probably play a part. Some people also believe the latest (and we can assume final) patches for the game are bugged-- I have never encountered a problem with them, but since they change how the game uses system resources, I don't doubt that some people experience issues.
Finally, remember that software, especially OS's, are a living thing. They change, grow, and get sick. Keeping an OS in good operational state is essential when playing a demanding game like DA. Also, not all 3D games put the same demands on a system-- DA seems to be unique in how it is coded, at least to the extent that it relies on the main CPU for certain effects-- at least if other posts on this site can be believed.
Just some proverbial food for thought.
Modifié par RaenImrahl, 24 janvier 2011 - 05:34 .
#9
Posté 25 janvier 2011 - 02:00
Trixor
-
- Members
- 13 messages
Tbh, the coding is utter crap. Crashes like these should be fixed asap (unless you're a part of the EA conglamorate, ofc). Even though you'll think it trivial, these crashes are going to put a dark shadow over DA2. With the release of DA2 so close, people will be interested in DA:O, and they'll start to look for information, and most of the information that is to be found on DA:O is "it is a great game, but prepare to cope with unexplained crashes, random memory leaks and Maker's Breath, warped characters".
The game has a solid story line, but the crashes really, REALLY put me off for DA2.
The game has a solid story line, but the crashes really, REALLY put me off for DA2.
#10
Posté 25 janvier 2011 - 03:57
RaenImrahl
-
- Members
- 5 386 messages
Trixor wrote...
Tbh, the coding is utter crap. Crashes like these should be fixed asap (unless you're a part of the EA conglamorate, ofc). Even though you'll think it trivial, these crashes are going to put a dark shadow over DA2. With the release of DA2 so close, people will be interested in DA:O, and they'll start to look for information, and most of the information that is to be found on DA:O is "it is a great game, but prepare to cope with unexplained crashes, random memory leaks and Maker's Breath, warped characters".
The game has a solid story line, but the crashes really, REALLY put me off for DA2.
You bring us an EXCELLENT point. I suspect, simply based on the concept that some folks at EA/Bioware do read these posts, and more importantly, the tech support logs, that they're aware that the coding is clunky. I've mentioned in other posts that, when discussing the remarkably smaller hard drive space requirement for DA2, the developers have said that the game's been made more efficient.
That said, they are in a pickle, aren't they? They can advertise the fact that DA2 is more efficient, because then they're admitting defects in DA:O.
#11
Posté 30 juillet 2011 - 01:01
mouser9169
-
- Members
- 27 messages
My necro of the day:
The coding of DA:O isn't exactly klunky, but it is inefficient - and that is by design. All the "freedom" we have to change things in the game that are handled by the scripting system take up a lot more CPU cycles than if they were simply hardcoded into the engine.
After reading the post above, I suspect this is why there's no toolset for DA2. My bet would be they've moved all (or at least many) of the scripts back into engine code.
The coding of DA:O isn't exactly klunky, but it is inefficient - and that is by design. All the "freedom" we have to change things in the game that are handled by the scripting system take up a lot more CPU cycles than if they were simply hardcoded into the engine.
After reading the post above, I suspect this is why there's no toolset for DA2. My bet would be they've moved all (or at least many) of the scripts back into engine code.
