I an pretty sure Bethesda is done with Skyrim as it is...
They will be no native 64 bit version for sure. But you could play skyrim on a 64 bit operating system without any special problems.
And actually, i thing skyrim will be a timeless game not because it's not written in a 64 bit version, but because it's the only action role-playing video game that's that huge and fun to play.
Except that it sold over 20 million copies worldwide, and also received awards from various gaming sites and publications.
Actually, It was voted No.1 in Good Game's top 100 video games of all time. !!!
---------
> Cause the 32-bit having the max capacity hit at 2-3gb of space and then crashing numerous times. <
You are talking about mods most likely. !!!
However, Skyrim It's a 32-bit .exe, mostly because it's more or less a port from the consoles with minimal re-programming done to make it work on your PC. !!!
Making the step to a 64 bit client, needs some workarounds. You should read that below:
Spoiler And correct me if i'm wrong but I'm pretty sure 64 bit both benefits the graphics card and CPU capabilities of your computer in gaming.
There are a few extra instructions available on x64 CPUs, but [most of] those instructions can be used in x86 processes in any case. So, so far as performance benefits goes - there aren't really any implicit advantages.
How hard would it really be for zenimax to create a 64 bit client? any programmers out there feel free to input.
Depends entirely on how portable the code was written in the first place. Memory addresses in x64 are 64 bits wide, while x86 addresses are 32 bits wide
When you use memory addresses (which you do a lot) you use something called a pointer (it points at a location in memory). A pointer is a number that has to be the same size as the address size on your CPU. If any 32 bit pointers are present in the program and you compile it and run it on x64 it will crash unpredictably and intermittently. Basically, Zenimax can't just go and "compile for x64" and expect things to go well - a lot of QA will be involved.
Additionally, they are using some 3rd party libraries (you know these as .dlls). The thing about DLLs is that they are also compiled against a certain platform (x86 vs. x64). It is a CPU and operating system limitation that you cannot load a x86 library (DLL) into a x64 process (EXE) - this means they would also need to make sure that x64 version of all the libraries they use are available.
At the end of the day it comes down to a lot of combing through code to make sure pointers were used correctly, and a lot of time in QA making sure that nothing breaks.