A Land Far Away

Okay usually the scroll wheel on my mouse controls the zoom function, but sometimes after playing a bit it changes to control the cycling of my quick slots. I have also noticed that when this happens I cannot run at all even if i disable detect mode or click on a hostile to attack them. If i quit the game and log back on it seems to fix things, but the problem always returns later. Not being able to access the spells I have on my 1st row of quick slots and not being able to run in combat is a horrible combination. Any ideas what might be causing this to happen? Does this ever happen to anyone else?

Id be interested to learn why this is also, had similar problems in the past

Your shift button is stuck.

shift-scroll scrolls quickbars
shift-click makes you walk regardless of modes.

it happens to me all the time, tap shift once or twice and all will be well

Audark wrote:Your shift button is stuck.

shift-scroll scrolls quickbars
shift-click makes you walk regardless of modes.

it happens to me all the time, tap shift once or twice and all will be well

+1

thanks!

indeed! No idea why I hadn't thought of that! thankyou

I have a different issue.

Occasionally, a key such as "I" or "W" becomes my middle-mouse click -- you know, where you can move around the camera without moving the character? If I hold down W to move forward, I won't move; however, if I move my mouse while holding down W, suddenly my camera goes all funky. To top this issue off, going into the key bindings shows nothing changed, and it doesn't fix unless I reassign the key causing the issue to itself again (even though it STILL STATES IT DOES ITS ORIGINAL FUNCTION, NOT ANYTHING ELSE).

A bit of a pita, no?

Thats certainly odd. Made sure there is no external programs that might be messing with your keybinds?

It sounds like your W key seems to be getting re-assigned to 'Mouse Look'.

Magile wrote:A bit of a pita, no?

Welcome to NWN2.

As an aside, I think but am not sure, that using WASD to walk around causes lag so i would avoid it if possible.

It does.

Basically when you just click somewhere it sends the location update once to the server and once to all the other players. When you use WASD it's sending a constant stream of updates from you to the server and out to everyone on the same map as you.

This causes a lot of server and bandwidth strain and many admins think it's the number 1 cause of lag on NWN2 PWs. When several people are in one area all using WASD the amount of extra packets flying back and forth from them to the server is more than most servers can handle, creating lag for everyone on the server. This can even cause people to crash or disconnect. In extreme cases (10+ people all using WASD in one area without stopping) you can crash the server.

Enforcing a no WASD rule is pretty tough though.

Munmun wrote:It does.

Basically when you just click somewhere it sends the location update once to the server and once to all the other players. When you use WASD it's sending a constant stream of updates from you to the server and out to everyone on the same map as you.

This causes a lot of server and bandwidth strain and many admins think it's the number 1 cause of lag on NWN2 PWs. When several people are in one area all using WASD the amount of extra packets flying back and forth from them to the server is more than most servers can handle, creating lag for everyone on the server. This can even cause people to crash or disconnect. In extreme cases (10+ people all using WASD in one area without stopping) you can crash the server.

Enforcing a no WASD rule is pretty tough though.

I only use WSADD to reposition myself; however, I had remembered that some patches ago the WSAD latency issue was fixed to some extent. The client extension also claimed to fix pathing and latency issues with movement, if I recall correctly. I'm fairly sure that WSAD is safe(r) to use these days than it was when ALFA 1.0 first went live.

Now if only they'd fix the 2D portraits.

It has improved quite a lot since when nwn2 first came out. It used to be that 3 people all using WASD in the same area would slowly make a server become unresponsive.

Still best to avoid using WASD as much as possible sadly. Unless they refine how it sends packets that deal with elevation changes there will always be some issues.

I agree with 2D portraits completely. There's no reason for that bug.

I think it's odd how that portrait thing is only for ALFA. Gremlins in the server box?

HATEFACE wrote:I think it's odd how that portrait thing is only for ALFA. Gremlins in the server box?

i totally use a portrait and no one complains