| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Greeble
   |
Posted - 2003.06.25 09:36:00 -
[1]
In your eve directory there are two files - logserver.exe and template.lbw.
Make a backup of template.lbw.
Each time you want to make a useful log, do the following:
1) Make sure an Eve client IS NOT running.
2) Double click the logserver.exe application.
3) In logserver, do File -> Open Workspace
The logserver is now listening for an Eve client to get its logs.
4) Run your version of Eve (whether the latest testing build or the Live build for Tranquility).
5) Get in a position to reproduce the bug that you want a log for. This might involve going to a certain place, or training a skill, or doing something first; whatever.
6) When you are ready to reproduce the bug, first focus (or alt-tab to) the logserver window, and press ctrl+del. This clears the logs generated UP UNTIL that point, so that the only logs in the file you will shortly save are relevant to the bug you're reproducing - it makes a smaller file to upload.
7) Focus (or alt-tab) back to the Eve client, and reproduce the bug.
8) When you've finished reproducing the bug you want to log, focus (or alt-tab) back to the logserver window.
9) Do File -> Save Workspace As
10) Pick a descriptive name for the log file, and hit save.
11) Use winzip or whatever you like to make a .zip file of the log file (please just zip files, not ace or rar or whatever).
12) Put your dxdiag.txt (generated from dxdiag) in the zip file too, as well as any screenshots you made of the bug being reproduced (PLEASE convert those to .jpg).
13) Make a bug report for the bug, following the guide posted elsewhere in this forum, and attach your zip file. In the bug report, please list the filenames of the files in the zip file.
- Greeble
Polaris BugHunter |
Levi
|
Posted - 2003.06.25 14:20:00 -
[2]
thx - greeble, never got mine to work right yet. maybe this will help if i need to do a bug report.
you should make this a sticky - along with the other reply i saw in another post about BRs. (it was long, simple, & descriptive) ;)
lol, beat me to it! (a sticky by the time i posted) :P
Edited by: Levi on 25/06/2003 14:21:39
|
Crypton
|
Posted - 2003.06.29 11:30:00 -
[3]
Aye what if the bug we are trying to reproduce simply locks ur system so you cannot alt+tab back and forth? I have a few that do this and have reported them but still no luck on a solution. 1 being that when 2 people are using the Unstable Power Fluxuator I on each other when having it set to autorepeat, both players systems get locked to a halt. I have been able to reproduce this bug at least 6 times in a row with a fellow corp member.
** hijacked Stav excuse #101 **
 Quote:
dude read my lips, the entirety of m0o (all like 2 of us) was playing homeworld 2 all weekend
|
Greeble
|
Posted - 2003.06.29 17:08:00 -
[4]
In that case, run the game windowed and try to reproduce it.
Failing that, put precise reproduction steps in your report. Come to #eve-chaos on irc.coldfront.net and ask if anyone else has the bug, or knows about it.
- Greeble
Polaris BugHunter |
Crypton
|
Posted - 2003.06.30 12:03:00 -
[5]
I will try that, thnx :P
** hijacked Stav excuse #101 **
Quote:
dude read my lips, the entirety of m0o (all like 2 of us) was playing homeworld 2 all weekend
|
Drutort
|
Posted - 2003.08.03 01:01:00 -
[6]
Edited by: Drutort on 03/08/2003 01:15:42
how is this for a bug???
run game full screen... go to window then try to go full screen again... then pc reboots LOL
ya so much for saving that log...
any other ideas? never used to happen before
this is what i get in logs:
Quote:
File created 2003.08.03 01:07:38
An exception has occurred. It has been logged in the log server as exception #3
An exception has occurred. It has been logged in the log server as exception #4
blue.List: Key 0 out of range, size is 0
blue.List: Key 0 out of range, size is 0
blue.List: Key 0 out of range, size is 0
hmm i cleared all others and backed them all up though of course...
seems that i have been getting lots of the above
what am i supposed to do if i cant save the work space? if it reboots my system?
support Idea: QuickInfo an alternative to ShowInfo
my MoBlog |
Greeble
|
Posted - 2003.08.03 16:08:00 -
[7]
Read (in the other sticky) about how to use the crash handler. Or at any rate, which files it generates.
- Greeble
Polaris BugHunter |
Hellmar
|
Posted - 2003.08.13 23:43:00 -
[8]
Click this link -> How do I run the log server and what for?
|
soltys
|
Posted - 2003.09.10 12:30:00 -
[9]
Quote:
7) When you are ready to reproduce the bug, first focus (or alt-tab to) the logserver window, and press ctrl+del. This clears the logs generated UP UNTIL that point, so that the only logs in the file you will shortly save are relevant to the bug you're reproducing - it makes a smaller file to upload.
Actually, it's a little bit more complicated. If you alt-tab to logserver, whose storages under log subtree are not opened, ctrl-del won't have any positive effect. You must open them (in case of template - 15 mdi windows) if you want to achieve anything with ctrl-del.
----------------------------------------------------------
Damage stats: click version v1.1.02 retail. |
Derran
|
Posted - 2003.09.12 03:31:00 -
[10]
I created a file with information about a particular crash I have been experiencing so where do I submit it? The ingame bug reporter doesn't allow you to include file submissions.
|
Helison
|
Posted - 2003.09.12 10:04:00 -
[11]
http://myeve.eve-online.com/bugreporting.asp
|
Silver Striker
|
Posted - 2003.09.19 18:16:00 -
[12]
Everything from about step 3 on is just not geared towards your typical user imo.
Ideally the program will start and open up a workspace of it's own, and then player starts eve and gets to the point of the bug. Player presses big start button, replicates the bug, and clicks stop. Message window pops up and asks for brief description of the problem, player types in comments, clicks send. (Send should attach any files it needs, zip them, and send them)
Any chance of making a dummy logserver program for lazy ppl like me?
That's fantastic, really, but we need more COW BELL!!!! |
Greeble
|
Posted - 2003.09.20 12:24:00 -
[13]
We work with what we've got.
People willing to help out on the chaos server are not the typical sort of player in the first place, though, so the fact that there's more to the process isn't as terrible a thing as it might otherwise be.
- Greeble
Polaris BugHunter |
Majin Buu
|
Posted - 2003.11.24 15:09:00 -
[14]
it keeps people like me who havent got a clue about anything to do with programing from finding bugs and being able to reprot them, but with Greeble's help i was able to make the log server work and submit a bug (after spamming tomb with 85 lines of text in irc )
BoB KillBoard |
Braxtun
|
Posted - 2004.03.19 07:45:00 -
[15]
As far as I can tell there is no template.lbw file now. Can the process be completed skipping that step?
x
|
Daniel Jackson
|
Posted - 2004.04.24 17:25:00 -
[16]
Edited by: Daniel Jackson on 24/04/2004 17:27:54
Originally by: Greeble
In your eve directory there are two files - logserver.exe and template.lbw.
Make a backup of template.lbw.
Each time you want to make a useful log, do the following:
1) Make sure an Eve client IS NOT running.
2) Double click the logserver.exe application.
3) In logserver, do File -> Open Workspace
4) Select template.lbw in the Open Workspace dialog box.
what if you don't got the template.lbw cause I dont have one.
Caldari will once again rise above the gallente and take back Caldari prime!
Image done by Denrace |
CCP Hammerhead
|
Posted - 2004.04.24 23:21:00 -
[17]
Originally by: Daniel Jackson
Edited by: Daniel Jackson on 24/04/2004 17:27:54
Originally by: Greeble
In your eve directory there are two files - logserver.exe and template.lbw.
Make a backup of template.lbw.
Each time you want to make a useful log, do the following:
1) Make sure an Eve client IS NOT running.
2) Double click the logserver.exe application.
3) In logserver, do File -> Open Workspace
4) Select template.lbw in the Open Workspace dialog box.
what if you don't got the template.lbw cause I dont have one.
Yes you can still create a log. Just create a new document in the log server before you launch eve. The file won't be as organized as one created from the template but the devs should still be able to find the information they need.
|
Dotar Sojat
|
Posted - 2004.12.18 14:23:00 -
[18]
I have a better idea, since we are basically paying your salaries how about you guys doing the work and providing us with a quality product. It is not my job to spend my time logging the errors of this game.
This would be like an auto mechanic asking me to crawl under my truck and see what is leaking and from where and taking photographs of it and then delivering them back to his shop after I have already paid in advance for a new part he just installed...reality check.
It matters little if 12,000 players are online if they are all having errors and losing ships for inexplicable reasons, that is like saying that an event was a success since it drew a large crowd even though what they came to see never happened.
You guys need to put the rest of the stuff in the market we are supposed to have and just stick to debugging the code we have right now, then just stick to keeping the servers running. The isk has already been sent so to speak.
I think we deserve a non-beta product for once. |
Dotar Sojat
|
Posted - 2004.12.18 14:23:00 -
[19]
I have a better idea, since we are basically paying your salaries how about you guys doing the work and providing us with a quality product. It is not my job to spend my time logging the errors of this game.
This would be like an auto mechanic asking me to crawl under my truck and see what is leaking and from where and taking photographs of it and then delivering them back to his shop after I have already paid in advance for a new part he just installed...reality check.
It matters little if 12,000 players are online if they are all having errors and losing ships for inexplicable reasons, that is like saying that an event was a success since it drew a large crowd even though what they came to see never happened.
You guys need to put the rest of the stuff in the market we are supposed to have and just stick to debugging the code we have right now, then just stick to keeping the servers running. The isk has already been sent so to speak.
I think we deserve a non-beta product for once. |
Tarliah
|
Posted - 2004.12.18 15:05:00 -
[20]
I agree, why should we be doing your work for you and paying for your mistakes with stress and frustration on an incorrectly implemented patch or update??
I wish you would spend more time getting people who can test / program and VARIFY that your code works prior and post implementation.
You have a downtime every day..what do you do with it?? I donĘt know of any other internet game that has a daily downtime.
This latest patch is evidence enough that you lack the system life cycle maturity to carry out simple patches...In a nut shell it's total crap!! the interface doesn't work, the so called colours are a joke, auto pilot doesnĘt function properly, you cant even make sub-folders for book marks now. I spend more time restarting the game..hell my PC for that matter than I do playing your game.
Bottom line is why should the public test your work for you? If you cant code, test, implement and UAT properly, then donĘt attempt it 
 Here is an idea for the dev team : Either fix this dam patch or roll it back!!!! and stop friggen around with coping, moving and sending log files which you probably donĘt read/action anyway (just takes up more usless space on our equipment)
|
Tarliah
|
Posted - 2004.12.18 15:05:00 -
[21]
I agree, why should we be doing your work for you and paying for your mistakes with stress and frustration on an incorrectly implemented patch or update??
I wish you would spend more time getting people who can test / program and VARIFY that your code works prior and post implementation.
You have a downtime every day..what do you do with it?? I donĘt know of any other internet game that has a daily downtime.
This latest patch is evidence enough that you lack the system life cycle maturity to carry out simple patches...In a nut shell it's total crap!! the interface doesn't work, the so called colours are a joke, auto pilot doesnĘt function properly, you cant even make sub-folders for book marks now. I spend more time restarting the game..hell my PC for that matter than I do playing your game.
Bottom line is why should the public test your work for you? If you cant code, test, implement and UAT properly, then donĘt attempt it
Here is an idea for the dev team : Either fix this dam patch or roll it back!!!! and stop friggen around with coping, moving and sending log files which you probably donĘt read/action anyway (just takes up more usless space on our equipment)
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |