Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DDO Update 36 Patch 2 #5

Open
puddinhead opened this issue Sep 29, 2017 · 1 comment
Open

DDO Update 36 Patch 2 #5

puddinhead opened this issue Sep 29, 2017 · 1 comment

Comments

@puddinhead
Copy link

With the recent update of 36.2 for DDO Pylotro the DDO client may produce a blank screen when trying to log in thru using the pylotro client. Renaming the dndclient.exe to something else and then changing the dndclient_awesomium.exe to dndclient.exe is a work around at this time. Could an option be added to the pylotro client to tick a box so that it chooses the awesomium executable in the future should subsequent patches cause these types of issues?

@nwestfal
Copy link

@puddinhead, I added code awhile back in my fork to check for local game client override in TurbineLauncher.exe.config in the game directory, in order to deal with a similar issue with a LOTRO update. I didn't test it with DDO since I don't play it, but if it uses the same mechanism (TurbineLauncher.exe.config) to override the default client it might work for DDO too. If you want to try it: https://github.com/nwestfal/pylotro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants