Why is the High Res Pack incompatible with 32-bit XP7 if onl : V - Skyrim

» Wed May 30, 2012 1:55 pm

On the point about DX11. Civ 5 uses DX11 MTR(Multi Threaded Rendering) and it really improved performance. NVIDIA implemented it first in their driver and why benchmarks were much better at the time.

» Wed May 30, 2012 9:05 am

Again, it's not a bug but how computer architecture works. It's as simple as that.

Well you clearly don't understand how memory works then. It's a known fact that 32bit OS has a limit on virtual address space and just because you read what the task manager say doesn't mean you understand the whole story of memory.

I just checked Rage on Win XP 32-bit and the 1.2 patch fixed the 32-bit only "large texture cache" issue. No doubt soon the Skyrim High Res Pack issue will be fixed for XP 32-bit and glorious awesomeness of 32-bit WinXP (over newfangled upstarts) will be proven yet again! Check back here for "told you so post".

PS: You guys must be video driver technical experts at ATI/NVidia or something. I guess my Ph.D. in Computer Science, Windows (Nt/2k..) project experience at Microsoft and software engineering experience are no match for your awesome knowledge and skills!

» Wed May 30, 2012 2:21 am

Nobody said you cannot run it on a 32bit system. The point is that on a 32bit system you will get near to the limits of a 32bit OS, which might well cause you problems, stability and performance issue. Again, nobody said it won't work. It's also the same with the Crysis 2 High resolution texture pack, 64bit is a requirement not because they want to push you on to 64bit but because of a the limits and issues a 32bit system can cause.

I couldn't care less about your PH. D, it's just paper saying you know something and doesn't hold any weight on forums.

» Wed May 30, 2012 9:07 am

Just want to point something out real quick: Don't look at the memory in use. Look at the commit size. Once a non-LAA 32-bit application even attempts to commit 2 GB+ of memory, it will crash. The amount of memory it's actively using means little.

» Wed May 30, 2012 5:27 am

Just want to point something out real quick: Don't look at the memory in use. Look at the commit size. Once a non-LAA 32-bit application even attempts to commit 2 GB+ of memory, it will crash. The amount of memory it's actively using means little.

Yup, all memory sizes I quoted above were for virtual memory (commit size).