forums | blogs | polls | tutorials | downloads | rules | help

Error message

Deprecated function: The each() function is deprecated. This message will be suppressed on further calls in remember_me_form_alter() (line 78 of /var/www/siegetheday.org/sites/all/modules/contrib/remember_me/remember_me.module).

Lost mouse control with Win 10

My nephew is playing DS2 under Windows 10, and it just started giving a strange problem. When he starts the game, it puts up the blank screen with the progressing dots, then minimises itself. Clicking on the button to restore the window leaves him with no control over the mouse. The cursor location goes to a corner, and won't move.

I can't reproduce these symptoms, having tried messing with bad ini settings and other possible causes. Anyone have any ideas?

On my Win 10 laptop, it just works, even in wide-screen mode that the game was never intended to support.

Hi ghastley,
I recall several people having this issue with Windows 8, but could not find anything when using Windows 10. Might be useful to have more information on system configuration and the revision of the game.
Elf

I think most of what we want to know shows only when you get past this.

It may have to wait until I go visit next month. He's in UK, I'm in US, so I can't easily look over hos shoulder. My copy works, and his did until it suddenly changed its mind.

What was the cause on Win 8?

ghastley wrote:
I think most of what we want to know shows only when you get past this.

It may have to wait until I go visit next month. He's in UK, I'm in US, so I can't easily look over hos shoulder. My copy works, and his did until it suddenly changed its mind.

What was the cause on Win 8?

Can not remember what the cause was in Windows 8, however I do believe that iryan reported the problem, I will have to look in his old posts. Just wondering if he might have updated a driver or did an update of Windows prior to the game quiting. I am kind of shooting in the dark as I still use Windows 7.
Elf

For anything serious, I do too, but I have a laptop that came with Win 8 that I changed to 10, as the lesser of the two evils. My nephew's laptop came with 10, as it's more recent. Win 10 does seem to run things better than 8 did.

He's not the type to go look for driver updates or anything that technical. If one was pushed from MS, he'd just agree to it, though.

A couple of things he could try first, before any further tinkering around is required.

1- What type of mouse has he got?, if its a wireless one he might try updating to the latest drivers or even going back to the older drivers that were working.
2- If he's got a usb mouse he can plug that in instead, if that works its probably the wireless mouse drivers which are at fault, if the usb mouse doesn't work either at least he's eliminated the other mouse driver problem.

It's wired, and he's tried unplugging and using the laptop's touchpad, with no change.

Wireless on a laptop is usually no benefit, as the dongle is as much of an issue as the wire. I still prefer wired with a desktop, as there's less to go wrong, or slow down.

Since it was working before, we're trying to figure out what could have changed. Windows Update could have done something, but an in-game typo could also be at fault.

Is it really the control over the mouse (alone) that is lost? :o

As far as I remember, many 'white dots' related matters had to do something about internet access - resp. DS2 requests it but doesn't get an answer from the target called. Hence a look into the Windows Firewall settings may be worth trying, if the firewall has clear instructions what to do when DS2 is looking for internet access.

So perhaps this is the/a reason why you never get as far to achieve mouse control!?

The minimising thing is the start of the issue (that shouldn't be happening) and the mouse part may be a side-effect of that. If the game thinks it has no window extent, then the cursor has nowhere to go.

I'll have him check the shortcut for "start minimised", in case that did it.

I seems there is a large number of problems that could be causing the problem with your nephew's computer running DS2. Registry Errors, problem with the DS2 Executive, Problem with the ini file, The Hosts File tripping over a non existent multi player site can happen even in single player, and the list goes on.

I therefore have a few questions.
1. Is it a retail box version of the game or the steam version?
2. Is he using All-Saves or the Standard start?
3. Is he running the game in full screen or windowed mode?
4. What screen resolution is he using?
This list also goes on - but enough questions for now.

Elf

It will be the retail version, not Steam, and not using All-saves. Both of those add complexity he'd avoid.

I'd suspect the answers to the other two are "whatever the game chose", as editing the shortcut would be too much effort.

ghastley wrote:
It will be the retail version, not Steam, and not using All-saves. Both of those add complexity he'd avoid.

I'd suspect the answers to the other two are "whatever the game chose", as editing the shortcut would be too much effort.

Well since he is using the retail version, it could be that something is wrong with CD 1, or the DVD that the game requires to start. Never had this issue with DS2 or Broken World, but it did occur when my DS1 CD 1 had a scratch in it. Sometimes the game would start and sometimes a few dots in lower left and then nothing, not even an error message. Therefore I would suggest that you take the following when you visit him. A copy of DS2 All-Saves because once installed the game start is just a different icon, Make a copy of your DS2 Disk 1 just in case his is damaged or Download the No CD start from here. http://m0001.gamecopyworld.com/games/pc_dungeon_siege_2.shtml again after installed the game starts the same way. There is also a version for broken world. I use both so that I do not have to carry the disks between computers. My DS1/LoA DVD after installing does not need to be in system.

Elf

Mine is known to be bad. I have to sneaker-net a copy of terrain.ds2res over from another machine after ignoring the read error during install. However that doesn't stop it validating when I play.

The no-CD start is worth using just to avoid the disk wear, so I'll probably grab that (and use it myself).