[Bug 26292] Oblivion GOTY: OpenGL_Out_of_Memory (505)

wine-bugs at winehq.org wine-bugs at winehq.org
Sat Nov 26 11:23:41 CST 2011


http://bugs.winehq.org/show_bug.cgi?id=26292

Delporte <caffeine at calneva.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |caffeine at calneva.org

--- Comment #12 from Delporte <caffeine at calneva.org> 2011-11-26 11:23:41 CST ---
Not sure if this is helpful or not but thought I'd throw it out there. I also
get an immediate GL_OUT_OF_MEMORY (0x505) error when playing with all settings
on high--and can also confirm that setting shadows to anything other then 'low'
seems to be a main culprit. So while messing around on Google trying to find
out why the latest patch made the game significantly more unstable (another
issue entirely) I came across some posts mentioning that you can make the
TESV.exe LAA (Large Address Aware) so that It can address >2GB of memory.

If you don't have the latest patch you can use these instructions to make your
TESV.exe Large Address Aware -->
http://www.skyrimnexus.com/downloads/file.php?id=134&navtag=file/images.php?id=134&tab=3
.

If however you do have the latest patch and don't have a copy of the original
exe laying around you will need to go this route (I couldn't get it to work)-->
http://www.skyrimnexus.com/downloads/file.php?id=1013#content. This is because
the update made it so that steam can no longer be bypassed by running TESV.exe
directly and Steam also checks the integrity of TESV.exe. This method is
suppose to let Steam verify the EXE and THEN inject the LAA code. Again, I
couldn't get this method to work.

I ended up finding a copy of the original EXE and used the first method.

Anyway, my point? making the EXE Large Address Aware I was able to play for
more than 30 minutes with all settings at max and with no crashes, Out Of
Memory or otherwise (I quite because I had to go do some things so I'm not sure
how long it will last this way).

I'm not sure if this helps diagnose the problem in any way or if I'm just
masking the crash by throwing more memory at the game but just thought I'd
share.

BTW I'm running 64Bit Gentoo and I'm running the game from a 64Bit WINEPREFIX
and my rig has 16GB or ram.

If this is irrelevant info then let me know and if so, sorry for the wasted
space

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the wine-bugs mailing list