I encountered an extreme problem attempting to take my character across from the forest realm (includes Oja Road) into the Ojaveda realm. The two regions meet in the green cavern.
No matter what I did, when I hit the region border, the following region would load, but as soon as I attempted to move, the previous region would reload... and so it continued, back and forth. I tried walking across. I tried running across. I tried jumping, strafing and you name it. I tried it straight on, I tried it at an angle, in the middle and along the sides. I must have tried twenty time. Nothing worked. The only thing I could do was to hit UNSTICK which placed me back in the forest realm a ways, but this did not help me to attain my goal fo traveling to Ojaveda.
One of the GM\'s was kind enough to find a work-around for me (thank you, Neeve !). That work-around is to edit the psclient.cfg file (in PS main directory) and change the setting for the loading of maps. The setting below is what you want.
Planeshift.Client.Loading.KeepMaps = true
This did work and I was able to successfully continue my journey. However, this also gave me a sort of visual clue as to what might be happening at a code level.
When I had just logged back in, following the change in the psclient.cfg file, I was still in the forest realm. I then stepped across the line... and the Ojaveda realm loaded (as expected). I then touched the up arrow key to move forward... and ... the very first thing that occured was that my character slid BACKWARDS a ways (an action that would certainly trigger the loading of the previous realm). Whether this is a trick of the animation or whether the arrow key is mis-interpretted momentarily when one crosses into other realms I cannot say, but it might indicate a place to start to look for this glitch.
I must also say that I have run into similar behaviour instabilities between the realms in other parts of the game, but not to the same extreme extent so that I couldn\'t get across.
This problem cannot be classed as merely annoying. I regard this as a serious issue.
PS In response to Seytra\'s post which follows. I agree with what Seytra says about autorun, that has happened to me, too (and that may also be regarded as a bug). But please note that in this case the bug happened to me WITHOUT autorun.
