| Pages: 1 2 3 4 [5] 6 7 8 9 :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 1 post(s) |
DigitalCommunist
   |
Posted - 2004.09.25 18:31:00 -
[121]
 Originally by: juduzz
Originally by: Faramir
I've had this since the start of the game.
I seem to be able to reproduce it by changing my windowsclock.
This seems to trigger the same effect. Try it and see if i'm right?
I'm gonna try the AGP 8X thing.
Its funny you should say this,
I used to get the identical bug about2 months ago which co isided when my BIOS wouldnt retain setting like time ect because i was using to many high power USB devices.
My bios (on my ASUS mobo) has problems keeping track of time too.. always resets itself 3 hours back.. 
I'm pretty much convinced its hardware related.. either something to do with the bios clock, asus mobo, or nvidia chipset
_____________________________________
Perpetually driven, your end is our beginning.
"Can I be a consultant for EVE II?" - WhiteDwarf |
DigitalCommunist
|
Posted - 2004.09.25 18:31:00 -
[122]
Originally by: juduzz
Originally by: Faramir
I've had this since the start of the game.
I seem to be able to reproduce it by changing my windowsclock.
This seems to trigger the same effect. Try it and see if i'm right?
I'm gonna try the AGP 8X thing.
Its funny you should say this,
I used to get the identical bug about2 months ago which co isided when my BIOS wouldnt retain setting like time ect because i was using to many high power USB devices.
My bios (on my ASUS mobo) has problems keeping track of time too.. always resets itself 3 hours back..
I'm pretty much convinced its hardware related.. either something to do with the bios clock, asus mobo, or nvidia chipset
_____________________________________
Perpetually driven, your end is our beginning.
"Can I be a consultant for EVE II?" - WhiteDwarf |
Dopefish
|
Posted - 2004.09.25 20:32:00 -
[123]
Its probably the chipset. The early versions of nforce2 were crap, soundstorm *****ling noises, southbridge overheating etc. And since onboard audio and both NIC's run through the southbridge i wouldnt be too suprised if that was the reason 
I got a tip that i should disable the 3com NIC in bios and use nvidias as that would lower temperatures...havent tested it tho as i normally get this lag after quite some time of playing and im currently very bored and i dont wanna play, plz dont make me.
Swedish chef does not like cake |
Dopefish
|
Posted - 2004.09.25 20:32:00 -
[124]
Its probably the chipset. The early versions of nforce2 were crap, soundstorm *****ling noises, southbridge overheating etc. And since onboard audio and both NIC's run through the southbridge i wouldnt be too suprised if that was the reason
I got a tip that i should disable the 3com NIC in bios and use nvidias as that would lower temperatures...havent tested it tho as i normally get this lag after quite some time of playing and im currently very bored and i dont wanna play, plz dont make me.
Swedish chef does not like cake |
Etienne
|
Posted - 2004.09.25 21:47:00 -
[125]
This bug appears since months for me. It regularly happened even during mining. The screen stutters for a moment and no action you invoke will be executed for a while, but you can write one sentence into a chat window which will appear with correct timestamp and AFAIR also reaches other people. Afterwards you will get a Beep when you try to finish/send a sentence with RETURN during this hangup time.
It happened regularly even during mining ops some months ago. If you target something like a rock when it appears, the targetting time will rise to the time of the hangup. The hangup time always was the same for me, some weeks ago the timer jumped to something like 70 seconds and when it reached zero - the "fast forward" effect was executed and the game reacted again. Other internet software which occasionally ran in the background, didnt show any network problem during this time.
Then some time ago (maybe those ~5-6 patches you mentioned), this hangup problem slightly changed - now the hangup time is something like 20 minutes for me.
If i have drones out when it happens, they will visually jump away from their current position and during the hangup time will slowly proceed back to their real position/distance. During the same time when they are visually some KM away from my ship, the distance display will still show their real distance.
Due to the targetting timer and the drones behaviour, it is clear that my client knows in advance when this "hangup" is finished. Obviously i cant sit out 20 minutes anymore, so i do a relog now with all the annoying problems reulting from it 
It happened during entering warp, during beeing docked and during mining (with and without npc) to me and has lead to 2 of the worst losses in eve for me. Once when i lost a very costly item (and several hours work) due to it, i had heaps of logs including some logged server exceptions which appeared right to that time, but it didnt even help my petition
MSI Nforce2 Board
1gig ram
Radeon9700 128mb
win XP pro
The gfx card runs at 8x AGP speed, i have installed win xp pro twice in between without any effect to this. |
Etienne
|
Posted - 2004.09.25 21:47:00 -
[126]
This bug appears since months for me. It regularly happened even during mining. The screen stutters for a moment and no action you invoke will be executed for a while, but you can write one sentence into a chat window which will appear with correct timestamp and AFAIR also reaches other people. Afterwards you will get a Beep when you try to finish/send a sentence with RETURN during this hangup time.
It happened regularly even during mining ops some months ago. If you target something like a rock when it appears, the targetting time will rise to the time of the hangup. The hangup time always was the same for me, some weeks ago the timer jumped to something like 70 seconds and when it reached zero - the "fast forward" effect was executed and the game reacted again. Other internet software which occasionally ran in the background, didnt show any network problem during this time.
Then some time ago (maybe those ~5-6 patches you mentioned), this hangup problem slightly changed - now the hangup time is something like 20 minutes for me.
If i have drones out when it happens, they will visually jump away from their current position and during the hangup time will slowly proceed back to their real position/distance. During the same time when they are visually some KM away from my ship, the distance display will still show their real distance.
Due to the targetting timer and the drones behaviour, it is clear that my client knows in advance when this "hangup" is finished. Obviously i cant sit out 20 minutes anymore, so i do a relog now with all the annoying problems reulting from it
It happened during entering warp, during beeing docked and during mining (with and without npc) to me and has lead to 2 of the worst losses in eve for me. Once when i lost a very costly item (and several hours work) due to it, i had heaps of logs including some logged server exceptions which appeared right to that time, but it didnt even help my petition
MSI Nforce2 Board
1gig ram
Radeon9700 128mb
win XP pro
The gfx card runs at 8x AGP speed, i have installed win xp pro twice in between without any effect to this. |
pardux
|
Posted - 2004.09.25 23:20:00 -
[127]
 this is always happening to me.
i lost a rifter+skills(cargo) in my first month because of this i was hunting with a friend(he was in a moa) in a 0.4 system we both just stopped with couple of rats around. couple of minutes later we are in a pod. he petitioned and we didnt get anything back.
now when this happens it is very annoying but i just run my tank and push autopilot(first set destination) then the game(after about 5minutes) starts to respond and everything happens about 1-2minutes slower
seems like i dont get any data but they still get it from me
Fluffy carebear
(\_/)
(O.o)
(> <) This is Bunny. Copy Bunny into your signature to help him on his way to world domination. |
pardux
|
Posted - 2004.09.25 23:20:00 -
[128]
this is always happening to me.
i lost a rifter+skills(cargo) in my first month because of this i was hunting with a friend(he was in a moa) in a 0.4 system we both just stopped with couple of rats around. couple of minutes later we are in a pod. he petitioned and we didnt get anything back.
now when this happens it is very annoying but i just run my tank and push autopilot(first set destination) then the game(after about 5minutes) starts to respond and everything happens about 1-2minutes slower
seems like i dont get any data but they still get it from me
Fluffy carebear
(\_/)
(O.o)
(> <) This is Bunny. Copy Bunny into your signature to help him on his way to world domination. |
Ronyo Dae'Loki
|
Posted - 2004.09.25 23:47:00 -
[129]
If I'm counting right, almost every single person having this problem is running on an nForce2 board.
-------------
My salsa makes all the pretty girls want to dance and take off their underpants.
I <3 ( . Y . ) |
Ronyo Dae'Loki
|
Posted - 2004.09.25 23:47:00 -
[130]
If I'm counting right, almost every single person having this problem is running on an nForce2 board.
-------------
My salsa makes all the pretty girls want to dance and take off their underpants.
I <3 ( . Y . ) |
|
|
Dr Snarl
|
Posted - 2004.09.26 00:02:00 -
[131]
I get this problem frequently. Particularly when I have two clients going at the same time. The outcome I really hate from this is the classic cap bug afterwards as well, in that u need to dock/relog to get the graphic/percentage to reflect the actual cap position.
Anyway, the outcome on both clients is typically screen shudder, with eventually after 2 mins the clients catching up with the action - although you tend to get lots of log messages ahead of the graphics.
System
AMD 2800XP
ABIT NF7-S
1Gb RAM
Radeon 9700 PRO
________________________________________________
"One may smile, and smile, and be a villain" -- William Shakespeare
"Forgot it, just Snarl" -- Dr Snarl |
Dr Snarl
|
Posted - 2004.09.26 00:02:00 -
[132]
I get this problem frequently. Particularly when I have two clients going at the same time. The outcome I really hate from this is the classic cap bug afterwards as well, in that u need to dock/relog to get the graphic/percentage to reflect the actual cap position.
Anyway, the outcome on both clients is typically screen shudder, with eventually after 2 mins the clients catching up with the action - although you tend to get lots of log messages ahead of the graphics.
System
AMD 2800XP
ABIT NF7-S
1Gb RAM
Radeon 9700 PRO
________________________________________________
"One may smile, and smile, and be a villain" -- William Shakespeare
"Forgot it, just Snarl" -- Dr Snarl |
DigitalCommunist
|
Posted - 2004.09.26 00:27:00 -
[133]
Originally by: Ronyo Dae'Loki
If I'm counting right, almost every single person having this problem is running on an nForce2 board.
yep, looks like an nForce2 issue..
I'll check if theres some new firmware for the motherboard, but I highly doubt that it will fix this. Oveur take note please.
_____________________________________
Perpetually driven, your end is our beginning.
"Can I be a consultant for EVE II?" - WhiteDwarf |
DigitalCommunist
|
Posted - 2004.09.26 00:27:00 -
[134]
Originally by: Ronyo Dae'Loki
If I'm counting right, almost every single person having this problem is running on an nForce2 board.
yep, looks like an nForce2 issue..
I'll check if theres some new firmware for the motherboard, but I highly doubt that it will fix this. Oveur take note please.
_____________________________________
Perpetually driven, your end is our beginning.
"Can I be a consultant for EVE II?" - WhiteDwarf |
Cyleth
|
Posted - 2004.09.26 08:55:00 -
[135]
Edited by: Cyleth on 26/09/2004 08:57:40
It's not all nforces, at least I dont have it anymore. And I used to have it with VIA-chipset few times also. However, what I find very interesting is that the asus mobo you lot got problems with seems to have some problems with certain memory modules.
This sounds really stupid, but... have you all got the latest bios version?
Also, there is various models of A7N8X(-e, deluxe, -wm, -x)
I dont think the whole A7N8X is retarded, but the certain version(s)/model(s) of it.
Also, you could try to install beta nforce drivers.
And btw, I got the bug with my current mobo once. I had agp 4x mode on. I changed it to 8x when I noticed it and never got it again. Could be coincidense once again. 
--
|
Cyleth
|
Posted - 2004.09.26 08:55:00 -
[136]
Edited by: Cyleth on 26/09/2004 08:57:40
It's not all nforces, at least I dont have it anymore. And I used to have it with VIA-chipset few times also. However, what I find very interesting is that the asus mobo you lot got problems with seems to have some problems with certain memory modules.
This sounds really stupid, but... have you all got the latest bios version?
Also, there is various models of A7N8X(-e, deluxe, -wm, -x)
I dont think the whole A7N8X is retarded, but the certain version(s)/model(s) of it.
Also, you could try to install beta nforce drivers.
And btw, I got the bug with my current mobo once. I had agp 4x mode on. I changed it to 8x when I noticed it and never got it again. Could be coincidense once again.
--
|
Squelch
|
Posted - 2004.09.26 11:43:00 -
[137]
I get the same problem and I have an A7N8X-Deluxe rev 1.04 and a brand new A7N8X-X for my other account. This has been happening for 8 to 10 months, usually at least once every 2 hours or so. Both computers & accounts are affected in the same way.
|
Squelch
|
Posted - 2004.09.26 11:43:00 -
[138]
I get the same problem and I have an A7N8X-Deluxe rev 1.04 and a brand new A7N8X-X for my other account. This has been happening for 8 to 10 months, usually at least once every 2 hours or so. Both computers & accounts are affected in the same way.
|
Seto Mazzarotto
|
Posted - 2004.09.26 11:54:00 -
[139]
Edited by: Seto Mazzarotto on 26/09/2004 11:55:50
Let's see... I've got:
GeForce FX 5200, 8x agp.
NForce MCP2 IDE.
I also get the *****ling sound from time to time, but that's apparent in other programs as well.
Also, I've got a screenshot here.
With lame joke included. 
-----------
Fighting for the ideals of freespace, posthuman ethics, and rock & roll. |
Seto Mazzarotto
|
Posted - 2004.09.26 11:54:00 -
[140]
Edited by: Seto Mazzarotto on 26/09/2004 11:55:50
Let's see... I've got:
GeForce FX 5200, 8x agp.
NForce MCP2 IDE.
I also get the *****ling sound from time to time, but that's apparent in other programs as well.
Also, I've got a screenshot here.
With lame joke included.
-----------
Fighting for the ideals of freespace, posthuman ethics, and rock & roll. |
|
|
PredatorBE
|
Posted - 2004.09.26 11:55:00 -
[141]
I also have this problem.
The game looks like its frozen, but it still accepts your commands. The screen wont update so you dont see what your are doing. As stated here bofore, your corpmates dont see anything abnormal about you, your ship just sits there until the period of "lag" is over. I usualy relog because thats the fastest way to get back in the game.
I know when this is happening not only by the screen shake you get, but also by my harddrive making some noise for like 1 - 2 seconds, then it goes silent and I know im "lagged".
The problem doesnt only occur in space, ive had it inside stations a couple of times too.
Yes, I am also using a Asus A7N8X - deluxe.
A solution to this problem would be welcome, as this occurs several times a day.
Greetz |
PredatorBE
|
Posted - 2004.09.26 11:55:00 -
[142]
I also have this problem.
The game looks like its frozen, but it still accepts your commands. The screen wont update so you dont see what your are doing. As stated here bofore, your corpmates dont see anything abnormal about you, your ship just sits there until the period of "lag" is over. I usualy relog because thats the fastest way to get back in the game.
I know when this is happening not only by the screen shake you get, but also by my harddrive making some noise for like 1 - 2 seconds, then it goes silent and I know im "lagged".
The problem doesnt only occur in space, ive had it inside stations a couple of times too.
Yes, I am also using a Asus A7N8X - deluxe.
A solution to this problem would be welcome, as this occurs several times a day.
Greetz |
TWD
|
Posted - 2004.09.26 12:11:00 -
[143]
Same problem, also nforce2 chipset.
|
TWD
|
Posted - 2004.09.26 12:11:00 -
[144]
Same problem, also nforce2 chipset.
|
Hue Jorgon
|
Posted - 2004.09.26 12:40:00 -
[145]
Edited by: Hue Jorgon on 26/09/2004 13:02:31
I started getting this when I change motherboard. All other hardware remains unchanged.
Old Mobo: ASUS A7V333 (VIA which is what I should have stuck too)
New Mobo: ASUS A7N8XE-DELUX (NForce2)
Tried many different chipset drivers and bios version.
Linkage |
Hue Jorgon
|
Posted - 2004.09.26 12:40:00 -
[146]
Edited by: Hue Jorgon on 26/09/2004 13:02:31
I started getting this when I change motherboard. All other hardware remains unchanged.
Old Mobo: ASUS A7V333 (VIA which is what I should have stuck too)
New Mobo: ASUS A7N8XE-DELUX (NForce2)
Tried many different chipset drivers and bios version.
Linkage |
Arrik
|
Posted - 2004.09.26 13:55:00 -
[147]
I just came here after GM Rendo posted in a separate thread on the same issue. In his post, he said the common factors seem to be users with Asus boards, or a combination of Asus mobo and GeForce graphics card.
My motherboard is an Epox nForce 2 (8RDA+), and I'm using an ATI Radeon 9700 Pro. For me, the issue first appeared after I applied the first of the Castor patches in January 2004, and dogged me up until a few patches ago. I don't recally exactly when I stopped seeing this problem, but it does *seem* to have stopped for me.
The only factors that I think I can attribute the problem being solved to are:
(*) v4.24 of the nVidia unified drivers for my motherboard.
(*) Catalyst v4.7
(*) A recent patch, sometime with the last 3 months
(*) The fixes applied to the nodes/the new nodes
When I was suffering it, the problem did look like the servers simply stopped sending my packets of new informaiton - either recycling the last one or sending none at all. Information flow from you to the server doesn't stop, otherwise you'd be disconnected pretty quickly, and I think that anything you send is acted on by the server at the time (hence the fast forward warping if you've chosen to warp).
Test with a tool like Ping Plotter have shown no change in packet loss when it occurs, and no sudden rise in ping...so the problem doesn't look to be connection related - to me it seems clear that it's server side, somewhere.
|
Arrik
|
Posted - 2004.09.26 13:55:00 -
[148]
I just came here after GM Rendo posted in a separate thread on the same issue. In his post, he said the common factors seem to be users with Asus boards, or a combination of Asus mobo and GeForce graphics card.
My motherboard is an Epox nForce 2 (8RDA+), and I'm using an ATI Radeon 9700 Pro. For me, the issue first appeared after I applied the first of the Castor patches in January 2004, and dogged me up until a few patches ago. I don't recally exactly when I stopped seeing this problem, but it does *seem* to have stopped for me.
The only factors that I think I can attribute the problem being solved to are:
(*) v4.24 of the nVidia unified drivers for my motherboard.
(*) Catalyst v4.7
(*) A recent patch, sometime with the last 3 months
(*) The fixes applied to the nodes/the new nodes
When I was suffering it, the problem did look like the servers simply stopped sending my packets of new informaiton - either recycling the last one or sending none at all. Information flow from you to the server doesn't stop, otherwise you'd be disconnected pretty quickly, and I think that anything you send is acted on by the server at the time (hence the fast forward warping if you've chosen to warp).
Test with a tool like Ping Plotter have shown no change in packet loss when it occurs, and no sudden rise in ping...so the problem doesn't look to be connection related - to me it seems clear that it's server side, somewhere.
|
Gungankllr
|
Posted - 2004.09.26 15:32:00 -
[149]
Same problem,
Nvidia GE Force MX 400
www.hadean.org
|
Gungankllr
|
Posted - 2004.09.26 15:32:00 -
[150]
Same problem,
Nvidia GE Force MX 400
www.hadean.org
|
|
|
|
|
| |
|
| Pages: 1 2 3 4 [5] 6 7 8 9 :: one page |
| First page | Previous page | Next page | Last page |