Quote:
|
Originally Posted by animepimp
This is most likely due to your server not having enough processor power to load two characters at once since you are probably running one of the clients on the same server. The client sometimes crashes or LDs when the server lags out while its zoning and having to much running at once can make it take longer than the client can handle.
|
Hmm interesting. im running on a hyperthreaded p4 3.02 gz machine. The server itself has a very small memory footprint while idle. While the other person is wandering around by himself cpu usage is under 3%. Of course ive been reading how eq is a major resource hog so it might be eating my cpu too much by itself
I'll test your theory when i have a chance. oh, one more thing is the zone server gives an unknown operator 032a i think when a zoneing is "aborted"
Quote:
|
It would be possible to add this in the server, but it would require editting a lot of the code and would slow the server down significantly because every message would have to check the time and convert it to a readable string which eats up processor time.
|
not as much as you might think. unless microsoft decided to make it complicated since studio 6. I believe the function in in the c header "time.h" (c++ header ctime i think). Here is a link to the c code. c++ not that much different as far as i can remember.
http://h30097.www3.hp.com/docs/base_...E/DOCU_024.HTM
the time it would take to retrieve the time and format it would be insignificant to the time it actually takes to display it in the window. when working with strings, when possible, use pointers when passing them around. performance is 10000x better that way.
plus.. there are not all that many messages even it if did take a long time.
as for editing lots of code. havn't you created an wrapper function for error reporting. It's always in a projects best interest to have a nice repetoire of utility wrapper functions. This allows you to make global changes to a commonly used feature without major revisions. a good rule of thumb is that if a proceedure, etc. is used more than ONCE, move it to its own function so if you decide to change it, you only change it once. not 30+ times.
Next time i think of it and im near my compiler. I'll throw you together some quick and dirty ones. if your interested. some functions im thinking of are like:
void info_report(int severity, char *buf);
severity 1=info 2=warning 3=error 4=fatal error ..etc.
buf .. the description
int ...
well i had others but it is midnight and techsupport is being slow and my brain went to bed an hour ago. laptop has power problems (which is where my compiler is ironicly)
how long does it take to create a trouble ticket .. longer than 45min so far.