When choosing to use the 64-bit client, it allows me to log in and choose a game world; however once the launcher closes the game client does not launch.
Windows 10 Home
Build 1909
When choosing to use the 64-bit client, it allows me to log in and choose a game world; however once the launcher closes the game client does not launch.
Windows 10 Home
Build 1909
Ditto.. select world then client shuts down.
Rexshoo Gland
When I launched, I got a firewall message and had to open it for the new client then it worked. Not sure if it'll be your problem or some other issue, but just tossing that out in case your firewall is blocking the 64-bit client.
Same as above. After selecting the world, nothing happens. 33 bit still works fine.
Edit: Manually added *game directory*/x64/dndclient64.exe to the firewall. No change.
My python launcher script launches the game while it is set to 64 bit. However, i don't know how to tell once i'm in the game if i'm running 64 or 32 bit.
Last edited by Shein; 02-12-2020 at 11:16 AM.
Furian of Khyber
It does not work for me either. I turns my screen blue doesn't crash my computer but I have to restart it to get things back to normal. Maybe I'll wait a few updates before I try again it is clearly not ready yet.
Selected the 64bit option and tried to start game - I could enter username and password and select world, the launcher then closes and that is as far as I get.
The game still works in 32bit.
I am using Windows 10 home.
Didn't work for me at first, either. But I logged in using the 32 bit and mucked about a bit and then logged out. When I tried the 64 bit again it worked for me. So it might need the initial 32 login to clean up the upgrade.
Oh, you guys are boring. Look what it does to my laptop
https://www.ddo.com/forums/showthrea...=1#post6294946
"People are stupid; given proper motivation, almost anyone will believe almost anything. ... People's heads are full of knowledge, facts, and beliefs, and most of it is false, yet they think it all true." Terry Goodkind
I'm running on windows 10 professional, working fine. I confirmed via the task manager that I am running the 64 bit client.
Obviously more reports are needed with more details to figure out what is wrong for those who can't run it.
Working fine here after allowing it to work with the Firewall. Also Windows 10 Pro.
Swapped through my entire roster of characters of my main account and no slow downs so far. Liking what I'm seeing so far. 3.5GB used max so far.
:: edit :: Up to 3.75GB, but it's come back down again. Trying to see if I can get it to load more in.
J1NG
Last edited by J1NG; 02-12-2020 at 12:14 PM.
Thelanis: Yijing (*Completionist* TR 20 Aasimar Scourge Monk Level 20 / Epic Level 10)
Thelanis: Pocket-Monks: Sightblur, Peashoote, Jigglypath, Jedinja.
Invisible Fences, unkillable Target Practice Dummy's, Shared Bank's, Pale Lavender Ioun Stones, the dimensional barrier between Eberron and Shavarath, I've broken them all...
Works fine here ...
Windows 10 Pro
2004 Version
Build 19555
Defender & Windows Firewall
Epitaph for Europe : Valete Keeper Devourerque -- honos et laus insint memoriam et honorem vestram. Gaudium et praedas, quos dedisti generose ad gimpes nostris, in cordibus atque nostris sempiternum. Valete atque semper et gloriose in aeternitatem fideles et robustes CCC !!! - I Was a Mournlander ... - Keeper/Mournlands/Lamannia/Ghallanda
I get to the server selection screen. When I choose "Play," the client closes and never opens back up. In order for me to play, I have to restart the client, go back to the 32-bit client, and then hit "Play."
I'm running the 64-bit version of Windows 10 Professional, Version 1909 (OS Build 18363.657) with the newest Windows Updates from yesterday.
BTW...my Windows firewall is NEVER on.
EDIT: Using AMD Radeon GPUs on a laptop (integrated) and PC (actual card).
I'm seeing about half that, but i only cycled through 6 bank toons. Watching task manager I have the feeling that GPU usage is lower. I can't think of a reason why the switch would matter unless you have to thunk to talk to NVIDIA, but I would expect that to be a CPU cost, not GPU. Maybe the 64-bit graphics libraries are smarter?
i had to specifically configure the dnd64bit client in the x64 folder to use my nvidia card in the nvidia panel to get around that messy all blue and green screen after hitting the play button.
the client will NOT start if the notebook is set to choose the graphics card on its own, and only lotro and ddo with the new 64bit client have this strange issue.
acer helios 300 on windows 10, all the newest drivers. (but does not matter, since i my wife has the same issue with lotros 64bit on her asus rog notebook) and we both had some different drivers over time with lotro.
it does look like the 64bit client has problems when theres an integrated video card and the panel is configure to let the system choose on its own, but is prefering the nvidia card.
its the same on ddo now as it was with lotros 64bit client for us.