MySEQ Client/Server 2.0.0 Beta is Out!!!

[MQSEQ2]

The new MySEQ Client/Server 2.0.0 is out and ready ready for Beta testing.

http://www.dvolve.net/EQ/MySEQ

You will need to Download the Client 2.0.0, Support Files and Server 2.0.0, even if you have downloaded them before.

Please test it out against the 1.x stuff and let me know which options are not the same.

Currently I know the Sorting of the SpawnList and Spawn Timers are not working as expected. They will be done ASAP as well as all the Player's Stats, GroundItems in a List.

I would install these in there own directory so you can have both versions running. Make sure you copy the support files into the Client 2.0.0 directory. If you want to rename the MySEQServer. Exe you must also rename the Ini file match the name (ie. MyServer.Exe = MyServer.Ini)

Good Luck and let me know ASAP any issues.

[AriB]

WOOOT GREAT JOB TRYING OUT NOW!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[Tbird038]

Server is refusing the connection....any ideas???

[MQSEQ2]

Make sure you use the real IP Address and not the 127.0.0.1. I will look in to that.

Turn on logging in the Client and the Server (Manually create the logs directory for the server).

[maj021]

Also make sure you switch the ports around - its 5555 by default on the client, 6969 by default on the server.

Just downloaded it, going to fire it up soon ;) Can't wait

[maj021]

Is there a problem with the offsets provided in the zip file? Getting a partial spawn list with some corrupted data (some coordinates in the equipment, ect) - but the offsets look about the same as 1.17's.

Turned on logging, no errors occuring on either the client or server side.

[maj021]

Tried installing it on the same machine as I'm running the server on - I get the server actively refusing the connection error also. Doesn't do that on my networked laptop.

And yes, I changed the IP :)

I saw you have offsets listed for primary and secondary weapons, but they're not on the list. Thats what I was really looking forward to with 2.0! :)

Still can't get the partial spawn list on the laptop figured out though, I'm assuming its a bad offset somewhere but I can't track it down.

[Knave]

This isnt working for me either.

When I first run it i get a pop up that tells me that Docking.bmp(it is there in the main directory) cannot be found and to check the path. After that I set up the ports, changed the IP from the default and hit go. The connection seems to be working as the server shows that there has been a connection established. For whatever reason it just sits there and no map or spawn list shows up.

I checked the logs and there is a line that shows me being disconnected and then Error in Requestpacket: Object reference not set ot an instance of an object.

I also get the "unable to connect to server" message but it is sporatic. sometimes it works, sometimes it doesnt.

[Just Some Guy]

Hmm, it works for me but its really slow in updating.

[Mixy!]

It fires up and operates for me. The spawn list is really, really slow in updating. The map is slightly offcenter.
My processor useage is up signifigantly (20% with 1.15.17; 87% - 95% with 2.0B)
Other things:
The value in the AA colum is either 3, or 255
The guild thing, and officer / member seem to be working properly

In it's current state it is unuseable for me. The updated are slow, and it's killing my athlon 650.

Network useage seems to be up as well. (0% with 1.15.17; 0% - 4% with 2.0B)

Dont get me wrong at all, im very happy that it's out in beta!! I just figured i'd post a few of my observations.

-Mixy!

[maj021]

Maybe thats the laptop's problem, its only a 400mhz and those hard drives have terrible access rates back then. The thing is so slow :)

[MQSEQ2]

I will work on the Server doing some filtering on mobs.

This is why I've ask folks in the past to do some testing with the Tester program to make sure we were going down the right path.

The weapons will be added soon enough. The issue is there are 4 different files to try and pull the weapons information from and I need some time to figure out which is the best way to get that info.

The SpawnList should not be updating alot of information at this time. I will do some testing via a Ini setting to turn on/off the SpawnList updating of stuff like the XYZ, distance etc.

The more input from gfolks the quicker I can narrow down the areas that need to be worked on.

[Iwannasee]

I had problems getting 2.x server client working earlier this evening. It would show a connection, but I couldn't get any response with either the 2.x client or the 2.x tester... I gave up and loaded the 1.x programs. I tried again later with the 2.x stuff and it worked this time. The 1.x stuff was still running, nothing was changed in the 2.x .ini files.

A few things I noticed with the tester...
SvF and SvC (I think those were the two) were still swapped. :)
The number labeled Base HP was neither my HP without spells or my current HP...
(player) Server wasn't showing anything.
Everything else seemed correct...

Data transfer from server to client on another computer was really slow and running 1.x and 2.x at the same time was next to impossible. We can blame that on the 850 Athalon on the client computer though. :)

I was hoping to see some of the info from the tester incorporated into the new client. I'm still wondering how/if you're gonna do that. :)

[maj021]

Never had any problems with the 2.0 testers, they've just suddenly popped up :(

[Iwannasee]

What I noted above was with the new 2.x server... If I recall correctly, the tester worked fine with the prior 2.x server...

And I just noticed, both the 2.x server and client remained in memory after closing the programs. The client was running at almost 100% processor time, I think that's the only reason I noticed it. Checked server to find it still in memory too. :)

[AriB]

Mine wont connect eather........ =/

Internet <-> Server(Win xp) <-Hub-> Myseq(win 98)

Its strange it wont connect I have tryed just about evthing I can thing of Even tryed connecting on the same computer ............

[MQSEQ2]

I will check it out. It sounds like the Client is not releasing the Server all the time so it should be fairly easy to resolve. I will start running the code on a 400 MHz laptop.

I will need to make some changes to the Tester to make sure it still works properly with the Server. There was some changes made to accomodate some of the new stuff.

I will also set the default port in the client to 6969 instead of 5555 so that the 1.x and 2.x can run at the same time.

I need folks to start logging stuff to see if there are errors being generated. Without that info I will never be able to track anything down.

[JohnW]

Downloaded the MySEQ Sever Beta 2.0.0, MySEQ Client 2.0.0 and the support files. The test server loads up and listens for connection on port 6969. I can telnet to that port. I changed my ip address and port in the test clieent and get the error that the server is actively refusing the connection. I turned on logging and the log file shows this:

01/27/2004 10:14:25:56 - Error in Settings.Load(): Could not find file "C:\wseqtestclient\prefs.xml".

I checked and that file is in that directory.

If I use the old MySEQ tester, it will connect to the new server however.

[Tbird038]

Great job man....looks wonderful...

Couple of things to start...and sure there will be more questions...

;1. Circle does not move with me....(stays on a square that seems to represent my position as I Zoned in)

2. Had some issues with zoning....made it work by stopping then restarting...

3. Had some issues as I mentioned before with the Server refusing the connection...made it work (all i think i did was change logging in either the client or the server...and have NO idea why that worked...)

Last...Consider the prod powered down AND outta here...Really excellent effort man!!!

*T*

Can the server support both v1 and v2 clients at the same time?

[MQSEQ2]

I'm reworking some of the TCP/IP routines to get a better results. I have not figured out what has caused the CPU to double at this time.

The Server 2.x will only work with the 2.x products.

[JohnW]

For whatever reason, I rebooted and was able to connect. However in the spawn list, I only get a couple mobs listed.

[Dark]

I couldnt get the map to auto load. I had to do it manually.
After i zoned it stopped working.
When i quit the myseq.exe client process kept running.

I didnt have alot of time to test it and will give it a longer test tonight.

[madman13]

Looking good here too!

I had the same difficulity getting the client to connect to the server as stated above... I had the port set correct, as well as my IP.. I'd hit connect and the server would respond with connected.. and it even would show my Char name if I right clicked on the server icon in the tray... but the client would show nothing.

After I shut down the client and server several times and resterted them... it started working!

I noticed a LARGE increas in Network traffic and Proccessor lag with v2.0 which I never saw with the tester proggy.

A few small things I noticed:
When clicking on Options>options>folders> (The ... next to "Spawn Timers") does not open a box for the user to select the path... no biggie I entered it manually.

After I managed to get v2.0 up and running the "directional lines" were shown.. but not facing the correct direction in which the person was actually moving.

Gonna toy with it more tonight.. and I'll turn on logging to see if I can capture anything!

Lets keep testing this and get as much info out there so we can move forward, this requires EVERYONES help!

[MQSEQ2]

Here is a new .Exe

http://www.dvolve.net/EQ/MySEQ/MySEQBeta.zip

This fixes a few items.

I don't know what broke the Client to cause the CPU jump.

Try this Exe and let me know what else is flakey while I track down the Hawg. (VB get ready!)

[MQSEQ2]

Make sure you also test 1.x and 2.x at the same time to verify the 2 are the same.

I've noticed the direction line being off in the 1.x on ocassions too.

[maj021]

This fixed the problem with trying to connect to the server using the same machine that EQ is on. Comparing it to 1.17 on the laptop and it looks the same spawnwise.

Still getting the same problem on the laptop when I try to load it up - loading 10 spawns into the spawn window and map then stopping, seems pretty random on which spawns it decides to load. Usually it'll update these 10, and sometimes a new spawn will come and replace one on the list. Seems kind of random as to when it'll happen.

Still no errors on the error log though..

Thanks for working so hard to get this up and running :)

[MQSEQ2]

I get a complete list of spawns (or atleast what looks like a full list). I will add some counters to compare the SpawnList to what actually comes to the Client.

[maj021]

Well I turned on the movement vectors (I don't normally play with them on, it gets pretty messy in a raid environment) and had the same thing happen that a previous poster described. Once someone starts moving, their vector gets stuck in the direction that it first moved in, even when they turn a different direction. It looks pretty funny honestly :)

I don't think my last post was very descriptive. I was trying to say that I get the 2.0 client to work fine and show a full spawn list on this computer (the one I play EQ on), although it is really processor intensive. When I try to run the 2.0 client on my laptop (networked over, runs 1.17 fine) it only gives a partial spawn list.

Going to try fully reinstalling 2.0 on the laptop and see how it goes..

[maj021]

Well, the client is at least logging some errors laptop side now:

01/27/2004 03:26:34:87 - Connected to Server: 192.168.1.103
01/27/2004 03:26:34:92 - Server Version: 2.0.0
01/27/2004 03:26:34:98 - ProcessPacket - Requested PacketType: 6 Received PacketType: 0
01/27/2004 03:26:35:31 - Short Zone Name: (PoTranquility)
01/27/2004 03:26:35:31 - Using Short Zone Name: (PoTranquility)
01/27/2004 03:26:35:42 - Zone Map Loaded: .\maps\PoTranquility.map
01/27/2004 03:26:41:68 - ProcessPacket - Requested PacketType: 3 Received PacketType: 128
01/27/2004 03:26:41:79 - ProcessPacket - Requested PacketType: 2 Received PacketType: 0
01/27/2004 03:26:44:37 - ProcessPacket - Requested PacketType: 3 Received PacketType: 128
01/27/2004 03:26:44:48 - ProcessPacket - Requested PacketType: 2 Received PacketType: 1
01/27/2004 03:26:44:48 - ProcessPacket - Requested PacketType: 5 Received PacketType: 2
01/27/2004 03:26:56:01 - ProcessPacket - Requested PacketType: 3 Received PacketType: 128
01/27/2004 03:27:08:54 - ProcessPacket - Requested PacketType: 3 Received PacketType: 128
01/27/2004 03:27:08:65 - ProcessPacket - Requested PacketType: 2 Received PacketType: 1
01/27/2004 03:27:08:70 - ProcessPacket - Requested PacketType: 5 Received PacketType: 2
01/27/2004 03:27:18:70 - ProcessPacket - Requested PacketType: 1 Received PacketType: 128
01/27/2004 03:27:25:18 - ProcessPacket - Requested PacketType: 3 Received PacketType: 128
01/27/2004 03:27:25:23 - ProcessPacket - Requested PacketType: 2 Received PacketType: 0
01/27/2004 03:27:25:29 - ProcessPacket - Requested PacketType: 5 Received PacketType: 2
01/27/2004 03:27:27:43 - ProcessPacket - Requested PacketType: 3 Received PacketType: 128
01/27/2004 03:27:27:54 - ProcessPacket - Requested PacketType: 2 Received PacketType: 0
01/27/2004 03:27:28:69 - Disconnected from Server: 192.168.1.103

Not sure if this is any help or not..

At least I'm buffing up my post count!

[MQSEQ2]

Ok folks the High CPU % has been knocked down.

In Client 1.x I have seen the CPU run at 30% +- 5%
In Client 2.x I have seen the CPU run at 35% +- 10%

Try this out and let me know some input.

http://www.dvolve.net/EQ/MySEQ/MySEQBeta.zip

I will start updating the version numbers in a couple of days.

I'm also going to add options to toggle the SpawnList updates for all the different options we currently update. This has been the source of the CPU Hawg becuase it updates the SpawnList everytime the spawns moves (XYZ vs XY only) and the HP's for spawns. I know in the releases prior to the 1.15.x they never updated the list as often but over time we added what folks have wanted to see but we will now give you the option to turn off the updates to any of the options (ie. don't update when the Spawns XY changes). This will only effect the SpawnList not the map.

[maj021]

Much better :) Running about 15% utilitzation compared to 60ish before.

[JohnW]

The first update of MySEQ did let me see the spawn list, however the map wouldn't autoload. It also didn't target the spawn when I targeted something in EQ.

I just downloaded the second update, will try it in a bit to see whether the map loads or not.

(I could manually load the map, however targeting didn't work and sometimes the mobs would populate on the map and sometimes they wouldn't.)

[MQSEQ2]

Sounds like your map directory wasn't setup. I've had folks say they have had no issues with the maps.

You can use the same map directory, cfg, filters, etc as the 1.x, just point both versions to the same directories and you won't need multiple copies of them.

[MQSEQ2]

Btw the Direction Lines are now working properly as well. Make sure you download the latest Beta.Zip file.

[MQSEQ2]

Currently working on the Range Circle issue on slow updating.

[MQSEQ2]

I got the Range Circle working.

I will be releasing a new Client/Server 2.0.1 tomorrow that will fix most of the issues. The 2.0.1 will be the current Beta with source and .Exe. I will create a new thread once I post the new Beta code.