My Vista 64 bit client stops working when I try to log into a server. (I know I have to upgrade it, but I don't have the $80 to do so).
My Win 8.1 64 bit laptop logs in no problem. My laptop heats up to fast so can't do anything serious on it..
Printable View
Windows 7 Home Extended, 64-bit.
I had exactly the same issue after the update: the client would just disappear without any error messages after selecting the server to enter; no related processes in the task manager.
Fiddling with the preferences file hasn't helped.
Thanks to the fix suggested by Dave46, I also renamed the d3d9.dll from the game directory, and after that I was able to run the game as normal.
I've tried running as an admin, removing the userINI file, renaming the document-lotro file, and removing the d3d9.dll (which I don't have one so I couldn't test this), I've also tried using the reset graphics setting in the launcher, nothing has worked yet.
Does anyone know how to change the DX version without getting in game?
Tried replacing the User Preferences file. Did not work. Guess I'll have to wait for the patch.
I tried everything what is mention in this thread. From Dev recommendation to delete Sweetfx or d3d9.dll..
Btw, tried sacrifice Hobbit to our lord and saviour Sauron - also dont work.
I renamed d3d9.dll, and now I'm in game.
Vista was a resource hog, Win7 fixed that, so any PC that could run Vista can run Win7 without any issues; and probably without having to update too many drivers, as many of the Win7 drivers were written for Vista.
Win8 thru 10, although I personally hate them, are also a lot easier on cpu use than Vista, so most Vista machines can run them - as long as there is driver support for your specific hardware.
I'm just trying to log in now......
And succeeded.
I suggest everyone having issues lists their hardware spec, av and firewall programs, to see if there are any commonalities. Previous issues have been caused by F-Secure, WinDefender, ZoneAlarm, and various gfx drivers from both AMD and Nvidea.
After the change over, the game now resides in
C:\Program Files (x86)\StandingStoneGames\The Lord of the Rings Online
It's worth doing a Copy of the
C:\Program Files\Turbine\The Lord of the Rings Online
To the new location and try running the game client from it, if you get Firewall msg, do Private only not Public.
Works fine for me. Quick suggestion that I ALWAYS do after an update, defrag your game directory with IObit Smart Defrag. Solves a lot of problems to keep your game directory as unfragmented as possible.
How does this have anything to do with the fact that I played ALL DAY yesterday, as I have for months, with NO ISSUES; yet today there was a "patch" and NOW am getting the error message "Lotroclient has stopped working"
Something got messed up in their patch today - I am not deleting, renaming, juggling, jiggling anything until I hear from the powers that are what to do about THEIR MISTAKE.
I decided to do a complete reinstall. Which had nothing to do with the problem that cropped up today.
Anyway, I say that to say this:
I got the game started by getting rid of the d3d9.dll file.
So, apparently, whatever changes they made today rendered SweetFX obsolete, at least for me.
Going to ReShade now.
+1 to Elle
In order to come up with a fix or workaround, finding the "common denominators" is helpful to isolate the root cause (or causes).
No one is suggesting a fundamental change. Let's just put our heads together and figure out a workaround. SSG will find the full answer, but it may take some time to code the fix, test it, push it out to customers, etc. Until then, if there's a "quick fix" uncovered by looking at the evidence, what's the harm for those willing to participate?
These files and hardware specs are not sacred pieces of information, they're just tools. If you don't want to give it a go, no problem, but it's not helpful to stand in the corner making demands.
The problem seems to be with the d3d9.dll file. I removed it from my Turbine/LoTRO folder in Programs(X86) and the game started. I put it back and the game didn't start.
I didn't have problems logging in, but this thread tipped me off that SSG might have converted some more components of the game to 64 bits, so I thought I'd try the usual running-out-of-memory experiment.
Immediately after doing a milestone travel to The Wastes, the client froze up. (It didn't CTD as expected; it actually froze up.) And it was long before it consumed the amount of memory that normally crashes it. (I think the commit charge was a little over 3 GB when it froze up.)
I realize this post isn't very valuable diagnostically. The only relevant information is that there seems to be a new way to freeze the game up that doesn't involve running out of memory.
Windows 7, 64-bit, Intel CPU, NVIDIA card, DX11.
Got home from morning work updated the game and logged in just fine running on Windows 10, 64 Bit.