is there a 64 bit executabe for P.O.E.?

I'd love to see an option in a theoretical 64-bit version to simply load up all game assets to RAM. It'd take forever to start up, but that would be the only loading screen I would see from then on out.

Quite a bit "I have heard..." and "I think..." in this thread. This article is a bit older, but the basics are the same: http://www.tomshardware.com/reviews/64-bit-vista-gaming,2250.html

The 'problem' or rather 'limitation' is that any 32 bit OS (Mac OS and Linux included), can only physically address a total of 4GB of ram. This includes ALL ram (system ram, cache ram, vram etc etc).
In general, any 32 bit OS can usually only access about 2GB of RAM for apps etc since the rest is generally used by the system.
A 64bit OS overcomes this limitation by being able to address 8TB of ram.

"

Raztax escreveu:

The 'problem' or rather 'limitation' is that any 32 bit OS (Mac OS and Linux included), can only physically address a total of 4GB of ram. This includes ALL ram (system ram, cache ram, vram etc etc).
In general, any 32 bit OS can usually only access about 2GB of RAM for apps etc since the rest is generally used by the system.
A 64bit OS overcomes this limitation by being able to address 8TB of ram.

This doesn't always mean better performance.

Quick comment about 64bit OS vs 32Bit;

I upgraded from Xp32 to 7-64 a while ago, added ram
(which PoE did not even need frankly) and everything
ran significantly better.

Windows 7, or I suspect windows vista, or even Xp64
can handle a 64 bit core better. Because windows is handling
its own personal business far better, PoE will have the
benefit of leftover clock cycles.

I think the fact that I'm on 7-64 matters a lot over
Xp64, as windows 7 is constantly using 2 cores,
and is capable of spiking all 4 cores at the drop
of a hat. So the OS architecture matters a whole hell
of a lot.

Not sure if PoE benefits from 64bit execution but the
OS sure as hell does... PoE doesn't need 8 gigs of ram
But since windows7 can use that to work on its backend
then PoE gets the leftover attention and runs better.

paging is the worst thing ever.

TL:DR Windows 7 64, on its own... is a gigantic performance
upgrade over winxp32 (with multicore). Winvista and windows 8
are probably also excellent upgrades. I suspect xp64 is less
dramatic or even not noticable over xp32, as the performance
boost i'm talking about is OS internal, multicore support.
with 64 bit drivers and extensions doing more work faster.

"

Mortezzah escreveu:

Lol. It would see significant performance gains if optimized for 64 bit, not merely recompiled. They don't merely because the core audience isn't there yet. Eventually everyone will be, and they will.

What? who the hell doesn't have more then 4gb of ram in 2013, people are paying them 500-9000 dollars for support packs but they cant buy 60$ worth of ram?

POE is a memory hog, im pretty sure its already 64bit as well. Thats why it crashes constantly on 32bit systems, keeps hitting the ram limit. It uses more than 4gb in wine anyways, that may not hold true for windows though.

"

Mortezzah escreveu:

Lol. It would see significant performance gains if optimized for 64 bit, not merely recompiled. They don't merely because the core audience isn't there yet. Eventually everyone will be, and they will.

I would like to point out that making it 64bit is just a simple recompile. You dont know how code works, or compilers either it seems.

Worst case scenario, you have to change some variable types, or ignore some gcc warnings.

I switched to win 7 64 from winxp 32 a couple days ago. Performance is significantly improved. I don't know anything about what you guys are talking about, I'm just offering what I found in practice.

"

tramshed escreveu:

"

Mortezzah escreveu:

Lol. It would see significant performance gains if optimized for 64 bit, not merely recompiled. They don't merely because the core audience isn't there yet. Eventually everyone will be, and they will.

I would like to point out that making it 64bit is just a simple recompile. You dont know how code works, or compilers either it seems.

Worst case scenario, you have to change some variable types, or ignore some gcc warnings.

It unfortunately is almost never as easy as a simple recompile for complex gaming code, for a variety of reasons: bitshifting is different in 32 bit vs 64 bit thus a recompile won't work; or if the programmer used 4 instead of sizeof(void*) you run into things a recompile can't fix; or if a lib being included doesn't have a native 64 bit equivalent then a recompile won't work; or problems with pointer arithmetic can come up; memsize types in unions in 32 vs 64 bit yields potential issues; array types issues can exist; virtual funcs with args of memsize type has potential problems; how arrays are indexed can be a prob; etc etc etc. There are a plethora of other reasons why it's not that simple. The biggest reason is that game programmers are invariably under the gun on deadlines, and while they could spend extra time to make sure everything was scalable and portable, they rarely have that requirement or luxury of time thus they don't bother.