VGOEmulator.net

I'd like to see if a few of you will log into the official test server "New Telon" and run like hell across a number of chunks. Test going back and forth across chunks, and the same ones, to test that the bug we had last week is fixed.

We just tested connectivity to my services, so if you get client timeout errors, be sure you run the latest VGClientLauncher.exe and your loginserver.txt file should get updated automatically at startup (in case the VG live launcher deleted it). Right now, that file being incorrect or missing is 90% of the connection issues.

Report back here if you have any issues, or just want to tell the guys "Great Job". Soon as I hear from anyone, I will push the current development branch to Public SVN for you to play with.

Ok I finally got it to work. Had to go into the vglauncher options and save it again, even though I had not changed any settings.

I am now crossing chunks.

1st: got kicked back to login when I tried to enter 3rivers, toon was unavailable, had to restart launcher. going to try again.
2nd: kick back to login after trying to chunk to shrine of flames. Toon was available.
3rd: Kick to login at 3 rivers again, toon not available had to relog.
4th: north to Shrine of Flames, West to Southwatch, South to Spires Keep, West to Ruin Falls, North to Beranid Hills, Side trip into Graystone for giggles. North to Fields of Despair, West to Bordinairs Cleft where it was SNOWING, and going South to Southwatch I got black screen, and never got kicked out. Had to exit manually.

Hmm, okay. I'll need Xen or Foof to tell me what I need to look for in the logs to provide them the information to resolve these issues.

We're still looking for x,y,z data from the chunk files, so I wonder if some of the chunks you were heading into just had bad data? The DB Editor's Chunk List would show if they are fully ready for tourists.

Thanks for testing. Btw, the latest VGClientLauncher posted should automatically re-write loginserver.txt on launch of the laucher. If it does not, you probably have an older version - or my code is bugged 1.0.6 I think is the current version.

That is probably what it did, even though I went to options after downloading the latest version.