Lag Issues

[*cryptc]

Agreed. When it works, it works great. When it lags, it is unplayable. Even chatting takes 2 - 3 minutes to react after hitting enter.

Basicly what happens is that once there's pathing issues happening enough that it pushes the cpu to 100% usage; everything starts to lag...

[*Aslya]

If pathfinding is such a problem for the pressure it put on CPU, why not deactivate it ? We use it by habit, but moving with the keyboard and such wouldn't be that problematic, especially if that mean no more lag. Probably not a popular suggestion, but...

[*cryptc]

Monsters also use pathfinding

[*lorgin_2003]

Unless it was fixed, a second time, the WASD movement causes a ton of lag itself. From what I can remember, the way it works is that it's constantly trying to find new paths as long as you have the button held down. Instead of just finding the path and moving along it, as per the mouse movement. Obsidian did a fix for it when they were still paying attention to the game, but it didn't even really help all that much. In general, keyboard movement should be avoided as much as possible, aside from minor adjustments, in NWN2. Even though it worked perfectly fine in NWN1.

[*Plaxy100]

Did you upgrade from a duel Core to a Quad Core/Octacore and when setting the server did you set Affinity? I mention this cause the exact same thing happen when we upgraded Comps over at Haven to what they use now. it was awesome but deadly intermittant lagspikes would accure it seems the game is only capable of using up to 2 cores and when trying to Hyperthread causes the CPU to over comp.

[*Brindas]

Heh.. lag time is now nearly five minutes for messages to send.

[*Jambi]

Unless it was fixed, a second time, the WASD movement causes a ton of lag itself.  From what I can remember, the way it works is that it's constantly trying to find new paths as long as you have the button held down.  Instead of just finding the path and moving along it, as per the mouse movement.  Obsidian did a fix for it when they were still paying attention to the game, but it didn't even really help all that much.  In general, keyboard movement should be avoided as much as possible, aside from minor adjustments, in NWN2.  Even though it worked perfectly fine in NWN1.

Yeah WASD for me doesnt work very good either, even on the older system. I had too get used too clicked movement, WASD caused alot of "rubberbanding"


From the sort of lag were getting, to me it feels like the server keeps overflowing its memory banks, and has too flush them. Not sure if it might be a hardware issue. Perhaps min/max buffer settings? Dunno.. just talking about some experience i had with a rig :)

[*Nerull]

Huh. Strange. I've been using WASD since nwn1. Never found an issue with it.

Where's my 'The more you know' Rainbow image...

[*Drachshyish]

I've noticed some definitive rubberbanding when using WASD, which is my default when it comes to controlling movement.

[*Jambi]

From the sort of lag were getting, to me it feels like the server keeps overflowing its memory banks, and has too flush them. Not sure if it might be a hardware issue. Perhaps min/max buffer settings? Dunno.. just talking about some experience i had with a rig  :)

I take back what i said, if it was a memory dump then the server would have "freezes" .
But it seems after the lag resolves, the game catches up. aka super fast combat. Seems to be connection related.

Its still strange how smooth the server runs, after jsut sitting thru huge lag spikes. Something is being cleared / dumped when the server goes ham