You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
@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
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?
The text was updated successfully, but these errors were encountered: