Maintenance for the week of December 22:
• NA megaservers for maintenance – December 22, 4:00AM EST (9:00 UTC) - 8:00AM EST (13:00 UTC)
• EU megaservers for maintenance – December 22, 4:00AM EST (9:00 UTC) - 8:00AM EST (13:00 UTC)

Please make a 64x Bit client...

mollyirma2000b16_ESO
I have no idea why you would make the client 32x bit seeing as it is a 2014 game. Perhaps it is because of how long the game has been in development.


But please make a 64x bit client.

Sincerely, Everyone playing ESO.
  • SK1TZ0FR3N1K
    SK1TZ0FR3N1K
    ✭✭✭
    I completely agree with this. We are way past 32 bit clients on the PC. Even that other MMO, which I have refused to play for the last 4 years, has a 64 bit client. I like this game, even with all the flaws that are still present from Beta. Even with the really "iffy" 5 day early access. Even with the "wacky" layout of the forums. I like this game...but I, and many other's, would love this game with a 64 bit client.
    Edited by SK1TZ0FR3N1K on April 8, 2014 8:51PM
    “There are three kinds of men. The ones that learn by readin’. The few who learn by observation. The rest of them have to pee on the electric fence for themselves.” -Will Rogers
  • wrlifeboil
    wrlifeboil
    ✭✭✭✭✭
    In general, a 64-bit client makes sense but specifically would it help ESO's performance that much? It's more than just recompiling the code for 64-bit. I remember when WoW released their 64-bit client not too long ago and the real world performance gains were minimal.
  • SirAndy
    SirAndy
    ✭✭✭✭✭
    ✭✭✭✭✭
    The biggest gain would be system memory.
    Right now, if you're lucky, you can get a max. ~3.5GB of memory for a 32bit app.

    I have 16GB in my rig, most of which could be used by ESO to cache textures and scenery to speed up zone loading and reduce stutter when running outside.

    Heck, they could even throw in a high-res texture pack and keep most of them in memory at the same time.
    ;-)
    Edited by SirAndy on April 9, 2014 12:13AM
  • RastSekyd
    RastSekyd
    ✭✭
    It'd be nice, but I think I'd like a true full-screen mode first. It'd be a nice performance boost over this clumsy borderless maximized window we have right now.
  • wrlifeboil
    wrlifeboil
    ✭✭✭✭✭
    SirAndy wrote: »
    The biggest gain would be system memory.
    Right now, if you're lucky, you can get a max. ~3.5GB of memory for a 32bit app.

    I have 16GB in my rig, most of which could be used by ESO to cache textures and scenery to speed up zone loading and reduce stutter when running outside.

    Heck, they could even throw in a high-res texture pack and keep most of them in memory at the same time.
    ;-)

    With Microsoft dropping support for WinXP, most running 32-bit version, and users being forced to transition at a turtle's pace to Win 7/8, it'll be interesting to see how soon game devs start releasing PC games designed for 64-bit systems only. 12-18 months?
  • mollyirma2000b16_ESO
    I will agree that ''true fullsceen'' is also important if not more. But since i have 12GB RAM it's annoying to see how ESO only uses up to 2GB. This is a 32x bit resctriction.
  • gimmetheloot
    I will agree that ''true fullsceen'' is also important if not more. But since i have 12GB RAM it's annoying to see how ESO only uses up to 2GB. This is a 32x bit resctriction.

    Definately needs exclusive fullscreen but the bolded part is wrong, the games using up to 2GB because that's all it wants at that time. LAA x32 applications can use up to ~ 3.5GB.

    Creating a 64 bit client only makes sense if you were hitting the LAA limit and causing oom crashes. If it was a more open world without zones and/or as suggested a higher res texture pack, then it might make sense.

    However, this is coming out on consoles remember? It needs to be "lite".
    Not forgetting that many people run 32bit OS (for whatever reason Idk) so there goes some potential customers.
  • Saerydoth
    Saerydoth
    ✭✭✭✭
    ESO is LAA so it does not have a 2GB restriction. On a 64-bit OS it can actually use 4GB.
  • Moonraker
    Moonraker
    ✭✭✭✭
    I will agree that ''true fullsceen'' is also important if not more. But since i have 12GB RAM it's annoying to see how ESO only uses up to 2GB. This is a 32x bit resctriction.

    Definately needs exclusive fullscreen but the bolded part is wrong, the games using up to 2GB because that's all it wants at that time. LAA x32 applications can use up to ~ 3.5GB.

    Creating a 64 bit client only makes sense if you were hitting the LAA limit and causing oom crashes. If it was a more open world without zones and/or as suggested a higher res texture pack, then it might make sense.

    However, this is coming out on consoles remember? It needs to be "lite".
    Not forgetting that many people run 32bit OS (for whatever reason Idk) so there goes some potential customers.
    Consoles will be 64-bit at least PS4.
  • GrimMauKin
    GrimMauKin
    ✭✭✭✭
    Surely it wouldn't be hard to produce a 64bit client? It seems odd that there isn't one when you consider that a 32 bit OS is listed in the minimum specs. for PCs but the recommended specs. only contain 64 bit OSes (7 & 8).
    I am one of The Great Mediocracy, those whose role in life is to provide the baseline by which The Few deem themselves Great.
  • wrlifeboil
    wrlifeboil
    ✭✭✭✭✭
    GrimMauKin wrote: »
    Surely it wouldn't be hard to produce a 64bit client? It seems odd that there isn't one when you consider that a 32 bit OS is listed in the minimum specs. for PCs but the recommended specs. only contain 64 bit OSes (7 & 8).
    It appears that 12% of people who used Steam last month played on computers running 32-bit Win 7.

    That's three times more than Steam users running Macs.

    ESO runs fine as a 32-bit client. Unless the devs can get measurable performance gains, they should work on the higher priority items on their plate. WoW users had this 32-bit vs. 64-bit debate a while ago. It would apply to ESO as well. Read this thread from 2011:
    http://us.battle.net/wow/en/forum/topic/2593046791
  • zipper76_ESO
    wrlifeboil wrote: »
    SirAndy wrote: »
    The biggest gain would be system memory.
    Right now, if you're lucky, you can get a max. ~3.5GB of memory for a 32bit app.

    I have 16GB in my rig, most of which could be used by ESO to cache textures and scenery to speed up zone loading and reduce stutter when running outside.

    Heck, they could even throw in a high-res texture pack and keep most of them in memory at the same time.
    ;-)

    With Microsoft dropping support for WinXP, most running 32-bit version, and users being forced to transition at a turtle's pace to Win 7/8, it'll be interesting to see how soon game devs start releasing PC games designed for 64-bit systems only. 12-18 months?

    Watch Dogs is coming May 27th and there is no 32 bit version whatsoever. So it is happening already.

    SOURCE:http://www.pcgamer.com/2014/04/07/watch-dogs-system-requirements-confirmed-wants-a-64-bit-system-with-significant-oomph/
  • mollyirma2000b16_ESO
    Why are they concerning themselves so hard on Consoles...? The majority of the income is going to come from the PC version... And i'm sorry but the console version sounds/looks pretty bad... You need quite a few buttons to play ESO and it's going to be a mess on consoles. I don't even know what they're going to do in PvP and if they can even freely zoom like we can with our scroll button or if they're stuck on a fixed camera position.
  • uktitanb16_ESO
    EQ Next and EQ Next LandMark are 64bit only and they are Still in Beta.
  • wrlifeboil
    wrlifeboil
    ✭✭✭✭✭
    EQ Next and EQ Next LandMark are 64bit only and they are Still in Beta.

    Are they going to be released this year?
  • wrlifeboil
    wrlifeboil
    ✭✭✭✭✭
    Why are they concerning themselves so hard on Consoles...? The majority of the income is going to come from the PC version... And i'm sorry but the console version sounds/looks pretty bad... You need quite a few buttons to play ESO and it's going to be a mess on consoles. I don't even know what they're going to do in PvP and if they can even freely zoom like we can with our scroll button or if they're stuck on a fixed camera position.

    Who knows? It might be a good port.
  • Nazaan
    Nazaan
    RastSekyd wrote: »
    It'd be nice, but I think I'd like a true full-screen mode first. It'd be a nice performance boost over this clumsy borderless maximized window we have right now.

    Clumsy is not a word I'd use for it. To be honest it works seamlessly. As a dual monitor user I love it. I do agree that the option for full screen would yield some benefits though. Main one for me is Shadowplay recording (desktop mode seems to be limited in functionality).

    The 64 bit client would also yield very little performance improvements, the whole memory restrictions thing is a myth and something that was worked out a long time ago. Question is why do you want it to use memory it doesn't need?
  • uktitanb16_ESO
    To be Honest I really don't know, I haven't logged in to Eq next Landmark in a few weeks (been kinda busy playing this =) hehe)
  • SamWale
    SamWale
    ✭✭
    Is there any news on this 64 bit client update?
  • SlaaMM
    SlaaMM
    ✭✭
    I have no idea why you would make the client 32x bit seeing as it is a 2014 game.


    But please make a 64x bit client.

    Sincerely, Everyone playing ESO.


    Signed ,
    agreeed ,
    he's right you know he's right,
    do this like last year,
    at least make an option,
    don't and all the bullys will make fun of you,
    the game really begs for more memory,
    playing this game on a haswell pc without 64 bit is like driving a Ferrari with only first and second gears,
  • Elf_Boy
    Elf_Boy
    ✭✭✭
    A 64 bit engine would be nice for those of use with x64 systems.

    Access to more application memory is just one of many different abilities x64 code has available to it.

    Wiki has a good read if you can get though the jargon and the dense information. Close to the end is a section called "Pros and Cons."

    The first line of which says:

    "A common misconception is that 64-bit architectures are no better than 32-bit architectures unless the computer has more than 4 GB of random access memory.[27] This is not entirely true:"

    Another key quote:

    "Some 64-bit architectures, such as x86-64, support more general-purpose registers than their 32-bit counterparts (although this is not due specifically to the word length). This leads to a significant speed increase for tight loops since the processor does not have to fetch data from the cache or main memory if the data can fit in the available registers."

    There are other issues, programming to use the additional registers that are individually larger is not just a recompile, someone who knows and is experianced with x64 coding needs to do this work. This would take time that could be spent on bug fixes. New features and other issues.

    Another big issue is that x64 code take more hard disk and RAM space, all those extra 32 bits everywhere chew up space like a bunch of hungry little kids. People with only 2-3-4 gb will start to be left out in the cold.

    So yes I want x64 code and think it would be awesome, not as easy or simple as many people think.

    The wiki article I referenced can be found @ : http://en.wikipedia.org/wiki/64-bit_computing

    I was one of many many many beta testers for the WOW x64 code. It was in development for a very long time. It had unique bugs and issues, I ran into more then one quest I could not finish in x64. I would have to quit, load the x32 engine do my turn in or whatever and then log off and back to x64 (after filing a bug report of course).

    I'd be happy to help beta test an x64 ESO engine too (hint-hint) if such a thing did currently exist.

    **EB**
    ** Asus Crosshair VI Hero, Ryzen 1800x, 64GB DDR4 @ 3000, GTX 1080 ti, 4K Samsung 3d Display m.2 Sata 3 Boot Drive, m.2 x4 nvme Game Drive **
  • Daethz
    Daethz
    ✭✭✭
    Agreed. Why was this game even made for 32bit?
    Xbox One - 64bit
    Ps4 - 64bit
    PC's that can max ESO's settings out - Likely all 64bit
    Windows 9 - Likely 64bit exclusive, or atleast it should be at this point.

    32bit is, pardon my french, old trash that needs to be buried because its stinking up the place.
    Waiting, and watching, for the return of Melee Weapons.
    -Subsidiary of The Fighters Guild
  • Mitharus
    Mitharus
    ✭✭✭
    Daethz wrote: »
    32bit is, pardon my french, old trash that needs to be buried because its stinking up the place.

    The x86 instruction set is trash that needs to be thrown out. Unfortunately, that isn't going to happen. I mean, look at Itanium. That instruction set was so much cleaner, but there just was no way for it to get traction.

    The only place a cleaner instruction set has gotten traction is on ARM. The MIPS/SPARC instruction sets were pretty nice from what I can recall as well. (1)

    I know the x86 instruction set hasn't cleaned up it's act any yet. Hell, x86_64 is a horrible hack onto x86. :/

    -M

    (1): This is from ... a year or two *looks around* back. Could have easily changed...
  • The_Nephilim
    If you want a quick Fix get CFF Explorer found here:

    http://www.ntcore.com/exsuite.php

    You can get the exe to address more then 2gb of ram.. there is a guide somewhere how to change and set ther address of more then 2gb for the exe.. I just did it and got a major FPS increase..

    here are the directions. IMPORTANT MAKE A BACKUP OF THE ORIGINAL EXE BEFORE CHANGING IT..

    Click the folder icon or go to File -> Open and browse your PC for TESV.exe.

    Click on File Header at the left, find Characteristics at the right, and click the Click here blue button.

    Tick App can handle >2GB address space.

    Click OK. Save by clicking the disk icon or going to 'File -> Save.

    Overwrite the file when it asks you to.

    NOTE: If you use this method, you need to keep the backup of the exe file you changed with CFF Explorer.
    When you update your game, you will need to copy the backup exe back to folder and replace the edited exe file.

    Go to the folder which has the executable file you changed.
    Delete the current *.exe file.
    Rename the backup executable back to the original name, now you can safely

    Edited by The_Nephilim on August 3, 2014 3:31PM
  • Elf_Boy
    Elf_Boy
    ✭✭✭
    CFF Explorer, and others that do the same thing, are useful tools.

    The use with ESO is extremely limited as the game is already LAA (or so I have read here in the forums, I have not verified that information however)

    With LAA enabled by default or by mod the game would be able to access 4bg MAX providing the system is able to provide it.

    There is a whole lot more to x64 code then just being able to access more ram with a specific application.
    ** Asus Crosshair VI Hero, Ryzen 1800x, 64GB DDR4 @ 3000, GTX 1080 ti, 4K Samsung 3d Display m.2 Sata 3 Boot Drive, m.2 x4 nvme Game Drive **
  • Saerydoth
    Saerydoth
    ✭✭✭✭
    Daethz wrote: »
    Agreed. Why was this game even made for 32bit?
    Xbox One - 64bit
    Ps4 - 64bit
    PC's that can max ESO's settings out - Likely all 64bit
    Windows 9 - Likely 64bit exclusive, or atleast it should be at this point.

    32bit is, pardon my french, old trash that needs to be buried because its stinking up the place.

    It wouldn't surprise me. Some new games don't even support 32-bit anymore (Watch Dogs is an example) - meaning if you don't have a 64-bit CPU/OS you can't even launch the game.
  • Cry_Wolfe
    Cry_Wolfe
    ✭✭✭
    Wildstar has both 32 and 64 clients .... no one has to be left out in the cold ../justsaying
  • yv3tt3
    yv3tt3
    can a dev please tell us if there are plans to give us a 64x client ?
  • yv3tt3
    yv3tt3
    i would really appriciate an answer !
  • stefan.gustavsonb16_ESO
    stefan.gustavsonb16_ESO
    ✭✭✭✭✭
    They gave an answer in an ESO Live session a while back, and it's not being planned for the near future. There is 32-bit middleware in the game, and they can't just recompile that. Besides, the current problems with this game are not on the client side. The lag is a server side problem, and the bugs and the lack of new content are developer problems. A 64-bit client would not solve anything at this point, and spending any significant developer resources on it would be stupid.
Sign In or Register to comment.