PyLotRO Forum

Since Turbine's "problem" with the Update 5 distribution, PyLotRO has not been exiting for me when I exit LOTRO.

I don't know if this is wide spread or not, see:
http://www.codeweavers.com/compatibility/browse/name/?app_id=2869;forum=1;msg=114834

Basically, when I first patched LOTRO with Update 5 at around 3pm the patch sequence finished apparently with no problems. However, once PyLotRO completed the account verification, it put up a black screen waiting for the Turbine Client to load. I could find no obvious problem. The Turbine Tech forum had a number of posting implying that an issue with the Turbine Client. About 4 hours after my first patch attempt, I tried again, and several items patched "again."
Naturally I didn't save the first patch run. However, attached is the second, so you can see what was apparently "messed up" in the first patch run.
<patch run output>==
Connecting to patch.lotro.com:80

Checking files...
files to patch: 8 bytes to download: 6103080
Patching files:

Downloading ProjectVersion.
Decrypting.
Downloading browser/greprefs/all.js.
....
Decrypting.

Downloading TWebBrowser.dll.
Decrypting.
Downloading OpenGLGraphicsCore.dll.
..........

Decrypting.
Downloading D3D11GraphicsCore.dll.......
.........

Decrypting.

Downloading D3D10GraphicsCore.dll.
Decrypting.

Downloading TTEPatchClient.dll...........
................ lots of dots

Decrypting.

Downloading lotroclient.exe...........
................. lots of dots

Decrypting.
.... lots of dots
File patching complete

Connecting to patch.lotro.com:80

Checking files...
files to patch: 0 bytes to download: 0
Patching files:
File patching complete

Connecting to patch.lotro.com:80

checking data...
data patches: 0 bytes to download: 0
unlock: 0 empty: 0
result code: 0x00000000
Patching data:

Data patching complete.
All patching complete.

Finished
===<end>
At any rate, the issue is that when you quit the game. It appears to end normally, going back to the black screen.
However, PyLotRO does not terminate. I've let it sit for several hours but nothing happens. If I quit it via the OSX "quit" option for the application, PyLotRO terminates as you would expect and the black screen goes away. You can also cause PyLotRO to quit and the black screen to go away if you quit CXG out from under it.

Magill

It sounds like the client terminating isn't killing the process that PyLotRO launches it in, so PyLotRO is sitting happily waiting to catch out put from what is in effect a dead process. It is more a question of what the client is doing when exiting to stop it truly terminating.

I'll update my client and give it a go, see if I can spot anything odd but it probably is a support ticket for lotro itself aka Turbine strike again 😊 .

This might be an osx only problem as I've tried with cxg and vanilla wine and it always quits fine. It does show pylotro, then go entirely black for a second then go normal again.

Alan Jackson wrote:

This might be an osx only problem as I've tried with cxg and vanilla
wine and it always quits fine. It does show pylotro, then go
entirely black for a second then go normal again.

Sadly, I have no problem believing that. Lion does have some strange "eating" habits... :)

It is clearly a case where using the "Dock" to quit PyLotRO does cleanly quit PyLotRO and then the black screen goes away.
Alternatively, if you Quit CXG, PyLotRO is "aborted?" by CXG, which continues to run, PyLotRO, however has quit and the black screen has gone away and you can immediately re-launch PyLotRO without re-launching CXG. So far I have not found any clue in OSX logs as to what is "not" happening. (Not much of a surprise there.) I've looked through the "default" logs from CXG and PyLotRO in the bottle, but don't find anything.

Alas, proving a negative is always such fun. Clearly PyLotRO is not getting the HUP (or whatever), but "Why?" No idea. Other than that issue, everything continues to work fine.

BTW, there is one additional post on the CXG LOTRO forum reporting the same problem. I suspect that SWTOR is impacting the number of folks playing LOTRO at the moment. My kin on Gladden is averaging 10-20 folks on line since the 20th while previously 50-75 (2-3 screens) was "normal" in the evenings.

The problem happens to me consistently, so if you come up with any ideas on debug steps to try, I can easily check them out

I'm wondering if Linux has the same problem but copes better.

Lotro ends, you see your desktop then you get a black screen for a second and then go back to the desktop. Perhaps under osx that black screen part isn't ending correctly. The only other thing I can think of is in the options file there is a couple of fake full screen options, maybe playing with them will help.

Trouble is we don't know if it the process not ending right or another problem with apples x11 implementation.

observations...

• I just noticed tonight, the UserPreferences.ini file is NOT updating.

What I don't know is WHEN it should be updating -- It is clearly not updating if I go to the character screen, change the audio settings, accept them and then quit.

Easy to see the settings did not change nor did the file update time.

Same for launching a character ... putzing around in-game a few mobs, and then quitting.
Again no update.

In both cases, it appears that the client is in fact, NOT terminating -- i.e. that "old black magic" ... er screen, on quit.

I've tried all the different "tricks" to terminate PyLotRO/LOTRO (hard to tell which is running at that point) but nothing changes in the .ini file.

So the question I have is ... When should that update occur... I assume it only is written when the Turbine Client exits.
Can you tell from the Linux side?

Alternatively (or in addition) is this actually a WINE/CO bug? i.e. the write is not working, and therefore should be bugged to Codeweavers.

edit: some text removed/changed - "please do not mention beta results in general forums" , thanks .

UserPrefs is written during the game client shutdown, so if it isn't terminating correctly the UserPrefs will not get written. I'll fire it up sometime this weekend to see if the UserPrefs get written when I exit, as under linux the client does appear to close.

It is probably worth raising the issue with Codies as the client exit problem is certainly a contributing factor if not the actual cause but as I said I'll see what results I get my end and post back.

Just tested, exits ok (you do get the flicker of a black screen) and UserPrefs written to.

Looks like it is an OS X problem, be interesting to see if it is Lion specific if someone still has the previous version (Snow Leopard?)

I upgraded to OS X Mountain Lion (10.8) over the weekend ...

PyloRO/LOTRO now quit "cleanly" and the UserPreferences.ini file updates again!