Aller au contenu

Photo

Cursor selection occasionally freezes


  • Veuillez vous connecter pour répondre
5 réponses à ce sujet

#1
LeFibbo

LeFibbo
  • Members
  • 5 messages
Hi all,
I'm sorry if this has been posted before but Google and a quick glance through this forum didn't yield anything.

My problem is this:
Occasionally during the game, the cursor selection would freeze. What this means is: I can move the cursor around as expected but the highlighting that occurs when I move the cursor over a selectable object does not follow. It is instead frozen on one single object that I interacted with earlier (mostly one of the playable characters or an enemy). This prevents me from telling my characters e.g. to attack an enemy, cast a spell on an enemy or ally, or move to a particular spot (using the mouse only! it does work using the W-A-S-D keys however).

I haven't out yet what exactly causes the problem to happen, so I'll stick with: It happens occasionally. The problem usually solves itself after a bit of frantic
clicking around, selecting and aborting spells, opening menus, etc. But
as you can imagine, it is all rather annoying.
Has anyone else experienced this problem? Or does anyone know a solution?

An example:
The selection is frozen on Hawke. I select Bethany and cast an AOE spell like fireball. I see the AOE are centered on Hawke, no matter where I move the cursor. Casting the spell anywhere else is impossible. As is attacking any enemy or moving somewhere using the mouse. Also, outside of combat, no matter where I click, she will always initiate conversation with Hawke because he is still highlighted.

My system specs:
OS: Windows 7 Professional
CPU: Intel Core i7 930, 2.80GHz
RAM: 6 GB
Video: NVIDIA GeForce GTX 470
DirectX: 11
Game: standard retail version (PC), v1.00, no mods or anything

#2
mcrummer

mcrummer
  • Members
  • 1 messages
I have same issue. I find the quick solution to select another companion, and the cursor is unfrozen on that character. I will issue a command for that character, unfreeze the action for a split second, and then, go back to the original character. Usually, the cursor is unfrozen at that point. But I agree, it is frustrating.

#3
LeFibbo

LeFibbo
  • Members
  • 5 messages
Problem keeps occurring. It seems to accumulate at boss fights (which is extra frustrating because they usually involve long periods where you CAN'T SAVE).
The last few times, nothing seemed to help except restarting the program altogether. Not even exiting to the main menu did the trick.

#4
didymos1120

didymos1120
  • Members
  • 14 580 messages
The easiest way to fix it is to just point at the stuck-on-highlighted object for a moment. Or the character portrait. That works too.  It happening more during boss fights is almost certainly because you're doing more character-switching, which is the easiest way to trigger the bug.  In fact, it's the only way I've ever triggered it. 

Modifié par didymos1120, 31 mars 2011 - 12:19 .


#5
Taellosse

Taellosse
  • Members
  • 42 messages
I have had this happen periodically too, but only when I'm out of combat. Luckily, that means I've just needed to save and quit the program to get it sorted out. I can only imagine how much more frustrating it must be if it were to happen in the middle of a major fight.

#6
didymos1120

didymos1120
  • Members
  • 14 580 messages

Taellosse wrote...

I have had this happen periodically too, but only when I'm out of combat. Luckily, that means I've just needed to save and quit the program to get it sorted out. I can only imagine how much more frustrating it must be if it were to happen in the middle of a major fight.


I've had it outside fights too, and, again, it's always been fixable by just pointing at whatever's stuck in highlight-mode (also again, it's always been a character, and nearly always Hawke, so the portrait thing is still the quickest way) for a moment, which seems to clue the engine back in to where the mouse really is.  I think what's happening is that some engine event is either not always being sent or is being sent but isn't being handled. Re-pointing at the offending object then either finally sends it or re-sends it and by then the handler has caught up or whatever and receives it.  That's just a guess, but given how event-oriented DA:O is and the way DA2 behaves, it fits.