[bug]Demo - Jet Artifact and Wierd 2nd Bug

Hey Everyone got a couple of bugs to report, the 1st is very straight forward on isle in the imperial base a jet artifact was permenently left there and stayed there till the map ended,

Heres the Screenie

http://www.187.org.uk/wtf.jpg

2nd is a bit hard to describe, I was just playing Emerald on Turret Syndrome with about 9 other people, I was with the flag behind the my own base (Blood Eagle) Trying to fend off a couple of chasers. I fired a couple of discs and nothing appeared out the end of the spinfusor so I assumed I had lagged out. I looked around and saw everyone else still moving and I typed "Lag?" to test reaction time, there was no lag my ping was fine but for some reason noone could fire there weapons.

You couldnt respawn either, B had no effect and when I killed myself with nades and the respawn map came up pressing 1/2 or clicking on them had no effect. Everyone else on the server had the same problem and the only way to remedy it was to recconect to the server.

It seemed like a pretty big bug that you guys might want to look into.

My Specs are (However Irrelivent they may be)

2.5GHZ Athlon XP (OC @ 2.6)
512MB DDR400
Sapphire Radeon 9600 XT 256
WD Caviar SE 80GB

Sorry I didnt do a search for previous reports cause im tired and about to go to bed. Hope this helps

:bump:

I've seen stuff like that JP artifact before; the same with glowing green repair lights. Although the second bug may have just been a server side issue. Probably a critical bug in that ded.server beta?

It was before the dedicated server was released

Then it was probably just someone's bad cable connection acting up.

Last time I checked Turret Syndrome wasnt on cable, while I am not exactly sure what connection it has, it has run 18 players flawlessly every time ive been on it (which is a lot, its the main server I play on)

Any chance of some Dev input? :)

ya its like the whole battlefield gets quite.

you can see others, but no chat, no firing (hear but dont see)

Chat worked People could read what I was typing and I could see what they were typing. It seems a pretty serious bug which is why I would love some dev input.

that artifact might have baan me. i got hit with a huge lagspike while i was playing as i tried to jet, after it stopped my jets looked like they were stuck on, though it didnt take energy or move me. i died and the artifact stayed there.

In addition to this I just had a lovely crash on Emerald I was in heavy armor and was just landing (badly) near the BE base and as soon as I hit ground It quit to windows and gave me this

No Label

Crash Time: 10/09/04 22:56:45

OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 1899 MHz with 511MB RAM
Video: RADEON 9600 SERIES (6476)

TV Build Number: 62740

Assertion failed: a->Location == a->Location [File:.\Havok\HkLevel.cpp] [Line: 683]

History: SyncActiveRB [Org Pos: -1345376640.00,-607793280.00,227327232.00 DeltaPos: 1.#R,1.#R,1.#R FinalPos: 1.#R, 1.#R, 1.#R] <- HavokSyncRigidBody [(VehicleBuggy48, base: None)] <- HkLevelData::syncWorldToH avok <- HavokStepDelta <- TickLevelSubsystems <- TickAllActors <- ULevel::Tick [(NetMode=3)] <- TickLevel <- UGameEngine::Tick <- UpdateWorld <- MainLoop

Powersurge, the second thing you described is what happens when a server completely lags out or dies. Due to the way the engine is coded, it kind of guesses what people would do next to compensate for lag, but if the server lags out it just gives them stupid AI movements.

For example if a guy is runnng in a certain direction and the server dies, he'll carry on running in that direction until the server either returns to normal or.. never.

This happened to me on Turret Syndrome last week whilst Winterlake was up. I got to the enemy base and realised that I couldn't fire, and then I noticed that people were moving around rather.. stupidly. I followed and watched some "guy" run all the way up to the boundary box and then just continue running into it. :p

I eventually decided the server'd had it and disconnected, only to find the server on my server list again with 16 people on it. Somehow it'd rebooted without letting my client know, and I assume I could have stayed in that "limbo" state forever had I not disconnected.

I remember the same thing happening way back on Planetside, incidentally. I'd be driving across the landscape for bloody ages, then get to a base and find the doors wouldn't open. I knew that I'd lagged out at that point, and cried.

They werent moving on a set course. For Instance I saw 1 teammate jet up onto the top of our base fire 20 shots of his chaingun.....realise its not working and return to the inventory.

I was still able to talk to everyone, hence how I knew everyone else had the same problem. The server was still very much alive we just had non functioning weapons, respawns and the inventory stations didnt work.

There has been a patch after that, so you should probably see if it happens on that patch too, or if they fixed it already...

There has been a patch after that, so you should probably see if it happens on that patch too, or if they fixed it already...

I'd love to but unfortunately us Brits are having to wait for retail....nevermind the patch

Just to comfirm that it isnt "someone's bad cable connection" I conectact DeeVee who informs me that Turret Syndrome runs off a 100MB pipe.