7 respuestas en este tema

[WiredWraith]

When in Character Mode (my preferred mode for enjoying the scenery) while moving and stopping my character will sometimes suddenly turn around facing a random direction OR will snap back to an area a few feet before.  I'm sure this is yet another engine issue but is there a fix (he asks hopefully)? Kind of annoying to be moving across an area only to "teleport" back to a position you were in earlier.  I feel like a mouse on a gerbil wheel and the gerbil is angry..

[Tchos]

The turning around bug and some instances of the rubber band bug, as well as many others, are fixed by using the Client Extension.

[WiredWraith]

The turning around bug and some instances of the rubber band bug, as well as many others, are fixed by using the Client Extension.

 

Thanks, Tchos, for the reply.  I use your NWN2 UI mods, btw.  Really nice Wish there was something like that for NWN1 besides the high resolution font option.  About the turning around bug, perhaps I should have mentioned that I did install the Client Extension, and, yes, it did serve as a partial fix for the issue.  It still would turn around as often as before but I noticed that the client extension would detect this and immediately correct it.  As long as you have Camera Drive in character mode turned off it's not too jarring.  The rubber banding problem is a little more serious, but if you're telling me it won't happen as often with the Client Extension, well, that's at least something.  Wish there was a full solution for this though.  NWN1 has something slightly similar with the turning around bug where your character will sometimes "skid" when you stop.  Maybe someday if Atari releases the source code for these games these bugs will finally be squashed.  One can only hope.

[Tchos]

Yes, there is no way in NWN1 to create a UI mod like mine without rewriting the game executable, whereas in NWN2 it's just a matter of changing the XML.  I wish there were, since NWN1's "high resolution font" is still far too small for my eyesight, and I hate the dialogue box being a tiny box in the corner, when dialogue is so important in games like this.

 

As for the rubber banding, are you using the keyboard to move, by any chance, or perhaps using the method of holding down the mouse button to move forward?  I used to use those, but I found the rubber banding was still too much as you mention, and I switched to the click-to-move method.  It still happens occasionally, but not so much.  I haven't seen the turning around bug at all since I started using the client extension, but I personally use the Exploration camera, not the Character camera.  I don't know if that has anything to do with it.

 

It would indeed be a happy day if the source code were released.

[WiredWraith]

As for the rubber banding, are you using the keyboard to move, b

 

 

By any chance, or perhaps using the method of holding down the mouse button to move forward?

 

 

 

Yes, I like to simulate a 3rd person perspective like in so many other action & role-playing PC games, so I tend to like Character Mode, and moving the character either with keyboard or holding down left-mouse button for forward movement.  AFAIK, this problem always occurs to some degree and only occurs in Character Mode.  Mouse-click movement works fine.

[kevL]

"they" don't release source code.

"we" write it. Someyear i'm going to start banging away at Xoreos -- it's the only way to get 3.5e (or a cross w/ 3.0e as i'd prefer), and the hope of a bug-free NwN2.

[DrMcCoy]

Maybe someday if Atari releases the source code for these games

Highly unlikey. The rights situation for NWN1 alone is probably quite complicated: Atari (a subsidiary of Infogrames Entertainment), as its publisher probably has some stake, so does BioWare (not owned by EA) since they kept using the engine base for their later titles. Wizards of the Coast, a subsidiary of Hasbro, might have a say as well, because of D&D.

Then they need to scrub the codebase of the Bink and Miles middleware they're using; those belong to RAD Game Tools. And probably many of the API usage bits too, because those are probably derived from example code provided by their SDK (as you do). Likewise, all Gamespy-interfacing pieces probably need to be removed as well.

(And that's just NWN1. The middleware "problem" has gotten worse in later games.)

That's a lot of work, and legal detective-work and wrangling, to be done. And for what gain? Prestige? They don't care. There's no monetary gain to be had, that's for sure. And a tiny sliver of a chance for potential future monetary reward by keeping the code closed and maybe licensing its use again some day. (They already did so in the past with CD Projekt RED for The Witcher, so those sub-licensing options are probably engraved into all the other contracts and ready-to-go.)
 

snap back to an area a few feet before

My best educated guess is still that this rubber-banding is a mis- or belated communication between the server and the client instance of the game (which still both run in singleplayer mode, too). It's there in NWN1, NWN2 and the KotORs as well. Not 100% sure about the Dragon Ages.

There's probably no real fix to be done from the "outside", with datafiles and mods alone. That's an issue with the game code proper.

[Tchos]

My best educated guess is still that this rubber-banding is a mis- or belated communication between the server and the client instance of the game (which still both run in singleplayer mode, too). It's there in NWN1, NWN2 and the KotORs as well. Not 100% sure about the Dragon Ages.

There's probably no real fix to be done from the "outside", with datafiles and mods alone. That's an issue with the game code proper.

 

That's why I always recommend the client extension, since as a program that hooks into the processes and modifies the game code as it's running, it's the only way we currently have to fix some of these problems.  Of course I would welcome a game engine replacement like your Xoreos.

 

I did notice just now in the more detailed changelog that the 90-degree spin bug is only fixed here when it happens during strafing.