EA was in charge for programming all the data they use. I contacted Steam and in the end they revealed to me they were not authorized to create/change the program files they've been sent. My first thought was that Steam was responsible for setting up the game loader that actually puts out Steam Error 51 when altering the. I thought to myself: What the hell, why not just try it!? So I used CFF Explorer, set the LAA flag within the file header of my DAOrigins.exe and had to learn that the steam version of the game well differs from the retail-DVD-version that people who got this flag set and working must have had installed.
Most of these people stated they had significantly reduced slowdown as well as loading times and crashing behavior compared to the former case with unmodified. The community uses the phrase Memory Lags for it and that got me stuck on testing the possibility that the exact fix that didn't work for me in Fallout 3, might do something good here.Īfter some research I discovered several people's notes about the effects of Large Address Awareness on the DAOrigins.exe and the actual game experience. With Dragon Age a different common problem caught my attention, as I experienced it. My issues were caused by graphic driver intricacies. Fallout 3 however didn't benefit from setting this LAA Flag in my case. I first stumbled across the possibility of setting a Large Address Aware Flag when searching for solutions for steady crashes in Fallout 3, some years ago. This question is more of a plea or advice or a reminiscence about QA or user-friendliness endeavors in a wider sense. Hallo dear community and hopefully also dear development staff,
0 kommentar(er)
