| Pages: 1 [2] 3 :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Darmed Khan
   |
Posted - 2005.08.09 15:06:00 -
[31]
The biggest problem I suffer from is when war targets refuse to show on the overview. Hopefully they can get all these bugs fixed in the next patch, the overview used to work great 
|
Aktar
|
Posted - 2005.08.09 16:10:00 -
[32]
Agreed the overview seems a little laggy especially during Empire battles with many people in the overview.
Suggestion: Create a setting that does not allow u to target a non-threat. Basically if object = Yellow or Red, Allow target, else = DO NOT TARGET!!!
But honestly this is definitely a bug because who in their right mind would target Concord or a non threat in Empire?
The rules clearly state that any agression in 0.5+ will result in ship destruction.
With that being said, clearly this is a bug to be dealt with.
|
sidthesexist
|
Posted - 2005.08.09 16:58:00 -
[33]
i believe the whole overview is gimped at the min a mate lost a harpy the other day due to a ship not showing in the overview all he saw was a crow so went in to attack then found there was a tempest in a sniping position that wasnt showing hence goodbye harpy 
|
JP Beauregard
|
Posted - 2005.08.09 17:01:00 -
[34]
I for one have given up on the overview. Apparently, it was deliberately designed not to give accurate information.
There simply is no other reason that I can think of why that thing should still be such a source of confusion nine months into Exodus after all the bug reports filed during Exodus testing - and after Exodus launch.
JP Beauregard
=======================
Thinking will ruin your EVEperience.
|
Snyper Kitten
|
Posted - 2005.08.09 17:03:00 -
[35]
Ive had this problem a few times with enemies showing up as gang members or alliance members. As for planets, stargates and billboards ...i wouldnt know cause i dont have all that junk cluttering up my overveiw
--------------------
You thought you saw a putty tat? |
Kraven Kor
|
Posted - 2005.08.09 17:10:00 -
[36]
 Originally by: Sherkaner
May I direct your attention to the bug reporting page? 
Bug reports about transient issues like this are especially useful if they include a logserver log.
And to stall any groaning replies of "Why should I bug report it? There have been a bazillion forum threads about it, CCP must be aware of it!"
Bugs like this are very hard to track down, isolate, and reproduce. Because of this, the BHs want as many bug reports about it as possible. Don't assume that someone else will report it, as long as the bug is not fixed (or there's a sticky in the Game Development forum saying that this bug is known and doesn't need to be reported) you should treat it as unknown, and submit a bug report of your own, as detailed as possible.
If you think that this one is a nasty bug that should be squashed ASAP, run logserver, make screenshots, take notes of what you were doing at the time when it happened, and submit everything to bugs.eve-online.com. And ask your friends and corp members to submit bug reports, too
If you have questions about how to use logserver or how to submit bug reports, please read the stickies in the Game Development forum, and feel free to ask questions there.
I have a better idea: Why don't you make an easy to use bug report feature in game, which automatically does the logserver thing. Expecting the players to log out or minimize the game to report a bug is, well, expecting a lot. We are lazy and want to play a game. We are not being paid in any way to test your software.
Also, you should get better at reimbursing ships due to in-game, known bugs. Many players have given up on petitioning for ship losses due to game bugs, and I think that is a pretty sad statement.
|
theRaptor
|
Posted - 2005.08.09 17:32:00 -
[37]
Originally by: Kalixa Hihro
I guess the fact that the interface is written in python might have something to do with the slow updates. I have the same issues in inventory windows, in the station, everywhere.
Lets see a show of hands of people that drag something from a container 10 times before it finally goes pop or moves where it is supposed to go?
C++ would probably do a much better job for this purpose, as well as cause a big PIA to reprogram it all in C++.
No the Python is not the problem, the game has been written in Python for two years. CCP did some coner cutting in order to reduce lag in the Cold War patch, and that corner cutting has majorly ****** up the overview. I would prefer the lag back if it mean't my damn overview actually worked.
And I have no problem transferring items between cans, and I am in Australia on dialup, so I would have a chat to your ISP.
And a lot of this game is written in C++, the graphics and other low level stuff would be, with hooks for Python to call. And for this sort of client side stuff you do *not* need the speed (CPU maxes out at 20% on EVE normally). The problem is bad optimizations that CCP have done.
That is not dead which can eternal lie,
And with strange aeons even death may die.
-- Ancient "Dirt" Religious figure. |
theRaptor
|
Posted - 2005.08.09 17:35:00 -
[38]
Originally by: JP Beauregard
I for one have given up on the overview. Apparently, it was deliberately designed not to give accurate information.
There simply is no other reason that I can think of why that thing should still be such a source of confusion nine months into Exodus after all the bug reports filed during Exodus testing - and after Exodus launch.
No they did a lot of optimizations in the Cold War patch to reduce lag, and they have made all the UI update a lot less. If you hovered your mouse over the speed bar it used to show current speed, now it only updates that when the mouse is moving.
Really this is the number one problem they should be working on. At least the colours on ships in space seems to be accurate.
That is not dead which can eternal lie,
And with strange aeons even death may die.
-- Ancient "Dirt" Religious figure. |
danneh
|
Posted - 2005.08.09 17:36:00 -
[39]
same problem FIX IT
|
Sherkaner
|
Posted - 2005.08.09 17:45:00 -
[40]
Originally by: Kraven Kor
I have a better idea: Why don't you make an easy to use bug report feature in game, which automatically does the logserver thing. Expecting the players to log out or minimize the game to report a bug is, well, expecting a lot. We are lazy and want to play a game. We are not being paid in any way to test your software.
You are of course right insofar that you aren't being paid to test the game. Quite the opposite, you are paying for the game, and you can expect it to be as bug-free as humanly possible; the responsibility for finding and fixing bugs lies solely with the CCP QA department.
However, you are obviously bothered by this issue (else you wouldn't post here), and submitting a detailed bug report would help creating a bug fix faster.
I know that creating such a detailed bug report takes a lot of effort, and you aren't required to do it. Submitting on is entirely voluntary on your part, but if you want to see the bug fixed soon, it's in your own best interest to take some time to write the bug report, and would be greatly appreciated by the EVE QA dept
Originally by: Kraven Kor
Also, you should get better at reimbursing ships due to in-game, known bugs. Many players have given up on petitioning for ship losses due to game bugs, and I think that is a pretty sad statement.
It's not really my place as a forum moderator to comment GM actions, but I hope I'm allowed a few words:
The main problem with reimbursement is that losses caused by client bugs often do not show up in the server logs, and GMs can only use those server logs to verify and reimburse losses. All data generated by the client (including screenshots and game logs) could in theory be manipulated, and malicious people could exploit it to create fraudulent petitions and unrightfully gain items.
Losing items because of bugs or lag is very unfortunate, and I sympathize with everyone who had such a loss, but please understand that GMs must obey a strict reimbursement policy and cannot reimburse every loss.
|
TheMoog
|
Posted - 2005.08.09 18:02:00 -
[41]
Edited by: TheMoog on 09/08/2005 18:04:47
Originally by: theRaptor
Originally by: Kalixa Hihro
I guess the fact that the interface is written in python might have something to do with the slow updates. I have the same issues in inventory windows, in the station, everywhere.
Lets see a show of hands of people that drag something from a container 10 times before it finally goes pop or moves where it is supposed to go?
C++ would probably do a much better job for this purpose, as well as cause a big PIA to reprogram it all in C++.
No the Python is not the problem, the game has been written in Python for two years. CCP did some coner cutting in order to reduce lag in the Cold War patch, and that corner cutting has majorly ****** up the overview. I would prefer the lag back if it mean't my damn overview actually worked.
And I have no problem transferring items between cans, and I am in Australia on dialup, so I would have a chat to your ISP.
And a lot of this game is written in C++, the graphics and other low level stuff would be, with hooks for Python to call. And for this sort of client side stuff you do *not* need the speed (CPU maxes out at 20% on EVE normally). The problem is bad optimizations that CCP have done.
I'm not sure if you're totally right about this. For Cold War, it seems very likely that they recoded the entire UI in another language, probably to support others charsets.
What make me say that is the multitude of small bugs that wasn't there before the patch, and are now appearing out of nowhere:
- Overview bugs (all of they above happened to me and corp mates).
- Speed and cap don't refresh anymore.
- Trouble transfering from cans to cargo/items.
- Blinking buttons when there's no reason to blink. (wallet, evemail)
- Time to load items/cargo/corp hangars content increased.
- Pinned down windows that are still draggable.
- Camera facing the station when undocking.
- Ctrl + click to lock now often need to be done twice. (never an issue before)
I am inclined to think those are the result of an overall recoding of the UI, with some unfilled holes that can be due to many things:
- Haste.
- The dev who recoded it wasn't the same that originally did it.
- Forgotten feature.
- Something more mystical ... |
Kraven Kor
|
Posted - 2005.08.09 18:03:00 -
[42]
Originally by: Sherkaner
Originally by: Kraven Kor
I have a better idea: Why don't you make an easy to use bug report feature in game, which automatically does the logserver thing. Expecting the players to log out or minimize the game to report a bug is, well, expecting a lot. We are lazy and want to play a game. We are not being paid in any way to test your software.
You are of course right insofar that you aren't being paid to test the game. Quite the opposite, you are paying for the game, and you can expect it to be as bug-free as humanly possible; the responsibility for finding and fixing bugs lies solely with the CCP QA department.
However, you are obviously bothered by this issue (else you wouldn't post here), and submitting a detailed bug report would help creating a bug fix faster.
I know that creating such a detailed bug report takes a lot of effort, and you aren't required to do it. Submitting on is entirely voluntary on your part, but if you want to see the bug fixed soon, it's in your own best interest to take some time to write the bug report, and would be greatly appreciated by the EVE QA dept
Originally by: Kraven Kor
Also, you should get better at reimbursing ships due to in-game, known bugs. Many players have given up on petitioning for ship losses due to game bugs, and I think that is a pretty sad statement.
It's not really my place as a forum moderator to comment GM actions, but I hope I'm allowed a few words:
The main problem with reimbursement is that losses caused by client bugs often do not show up in the server logs, and GMs can only use those server logs to verify and reimburse losses. All data generated by the client (including screenshots and game logs) could in theory be manipulated, and malicious people could exploit it to create fraudulent petitions and unrightfully gain items.
Losing items because of bugs or lag is very unfortunate, and I sympathize with everyone who had such a loss, but please understand that GMs must obey a strict reimbursement policy and cannot reimburse every loss.
Wouldn't it be much better to have an in-game bug report I can just hit F12 or whatever to bring up petition menu, fill in the bug report, and have it automatically run logserver? Do you realize how much better data you would be getting with an in-game, fast, easy to use bug report feature? How much more often we would be willing to take the time and bug report?
I know that community assistance in fixing bugs is a good thing. But enabling your community to more easily do so would be a GREAT thing. For all involved parties.
|
Kraven Kor
|
Posted - 2005.08.09 18:10:00 -
[43]
In addition, it would help to sort the valid bug-related ship losses from those losses which had nothing to do with a bug. If ship reimbursement required a bug report, that is, and then ONLY if that bug report was a useful in-game tool. Which it isn't. Though it darn well should be.
|
Daolin
|
Posted - 2005.08.09 18:13:00 -
[44]
Originally by: Kraven Kor
Wouldn't it be much better to have an in-game bug report I can just hit F12 or whatever
There used to be an ingame bug report feature in Castor. It was discontinued because it was buggy 
|
Necrologic
|
Posted - 2005.08.09 18:13:00 -
[45]
What's even worse than this is the chat bugs, especially the one where people can't see what you are saying in a private convo.
|
Bobby Wilson
|
Posted - 2005.08.09 18:22:00 -
[46]
Had this problem too. Lucky no ships were totally destroyed at the time, but it did allow somebody who should have died to get away...
BW
Originally by: Nervar
We allready play EvE wich by definition allready makes us the most patient people on the planet.
|
Jacob Majestic
|
Posted - 2005.08.09 18:22:00 -
[47]
Verone, I had this problem as well. I resolved the issue by deleting my /cache folder after the CW patch and let the game rebuild it.
|
Letouk Mernel
|
Posted - 2005.08.09 19:18:00 -
[48]
Sounds like we're just about ready to start deriding CCP for their bug-ridden code, again, which is something they are trying to avoid with their new QA department (not very impressive thus far).
We've had a bunch of new features recently, and it makes no sense to advertise your game as having even more new features in the future, if the community turns around and starts poking fun at it and telling all the newbies how buggy it is.
|
Revan Kahn
|
Posted - 2005.08.09 19:25:00 -
[49]
Just chiming in to say i get this a lot as well and its a royal pain in the arse.
|
HUGO DRAX
|
Posted - 2005.08.09 20:11:00 -
[50]
I never had this problem but I deleted the machonet folder after upgrade.
|
Reiisha
|
Posted - 2005.08.09 20:21:00 -
[51]
Originally by: Istvaan Shogaatsu
I lost a small number of ships to this. Naturally, the GMs helpfully declined to reimburse all of these :\
Youve got enough stuff reimbursed :P
|
Ilyana
|
Posted - 2005.08.09 20:27:00 -
[52]
Reading some of these threads is like watching sine waves. One moment CCP is the best, the next they suck hard coz of bugs.
|
Jonkai
|
Posted - 2005.08.09 21:02:00 -
[53]
Yep suffer from this too, was a pain in the backside when we have empire wars.
Didn't know about 'tab' closing and opening the overview, thanks for that :)
|
Auraurious
|
Posted - 2005.08.09 21:06:00 -
[54]
I have not had this problem before, however it should be noted that i both deleted my machonet folder after the patch, and didn't have color settings in the overview until recently. one thing i have had a problem with is that when i change a neutrals standing to positive it doesn't always show up right away. this could be atributed to the fact that the overview doesn't refresh as much anymore. however it stayed the same even after both warping away and back, and jumping through a gate. my other theory is that it has something to do with corp settings as well as personal ones.
__________________________
There are 3,259,687 bunnies left in signatures from all over the world... The rest scored a 9.489 on taste test charts. |
Del Narveux
|
Posted - 2005.08.09 21:17:00 -
[55]
Ya I have this crap too. I dunno what they did to the UI for the coldwar patch, but it was not good.
_________________
[SAK] And Proud Of It! -- aka Cpt Bogus
Is that my torped sig cloaking your base?
Originally by: Wrangler
Well, at least we have forum PvP..
|
DjDangle
|
Posted - 2005.08.09 21:40:00 -
[56]
All my corp are having serious overview bug problems! Sort it out as it's annoying as hell!!
------------
"I'm gonna eat you little fishy...." |
Hllaxiu
|
Posted - 2005.08.09 21:56:00 -
[57]
Originally by: Ilyana
Reading some of these threads is like watching sine waves. One moment CCP is the best, the next they suck hard coz of bugs.
Cosine - the threads never start at 0.
Proud member of Elite Academy. |
Plekto
|
Posted - 2005.08.10 03:30:00 -
[58]
The way to fix this once and for all is to have the 2-d graphics and info in a seperate smaller window. That way, you'd have, say a 800*600 smaller window for purely 3d graphics and flying(with all the overlays, it's actually quite cluttered right now, so this would actually *improve things*) - with not ONE OVERLAY - and a row of smaller windows outside of the main flight screen coverig the other functions.
See - mixing 2d and 3d in Direct-X is just asking for trouble.
|
Istvaan Shogaatsu
|
Posted - 2005.08.10 03:34:00 -
[59]
Hey. Now that this is being recognized as a real problem, you figure I'd have any luck re-petitioning the ships I lost to this bug? Last time around I got zilch back.
|
Plekto
|
Posted - 2005.08.10 04:01:00 -
[60]
Note - this "tiled" approach is popular with a couple of games. Angband, though devoid of 3d graphics, is a good example(I've seen a few games like Spaceward Ho! that slao use this approach quite well). One main window and a cluster of user-configurable text and information windows that can be slid around and docked and messed with. Your main screen stays clean and sane. Your graphics card doesn't blow itself up. And, since it's purely ascii text and information, the data is fast and bulletproof in those windows. Btw, ascii text has 16 colors - more than enough to cover any status/flagging issues.
Optimally, the next version of this game would have a ton of windows like this. It also would solve the problem for dual screen users. One does 1200*1000 main, and the other is a simple 15 inch/whatever monitor hooked up to a second budget 3d card.
|
| |
|
| Pages: 1 [2] 3 :: one page |
| First page | Previous page | Next page | Last page |