Two bugs?

[Murderlove]

Hello there,

I have encountered two bugs in Killing Floor I think, so here goes:

1)Build KillingFloor_Build_[2009-02-09_10.82]

OS: Windows XP 5.1 (Build: 2600)
CPU: GenuineIntel PentiumPro-class processor @ 2675 MHz with 2047MB RAM
Video: NVIDIA GeForce GTX 285 (8520)

General protection fault!

History: SkeletalMeshGet <- USpriteEmitter::UpdateParticles <- AEmitter::Tick <- TickAllActors <- ULevel::Tick <- (NetMode=3) <- TickLevel <- UGameEngine::Tick <- Level KF-BioticsLab <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 4C576C61 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free

2)In the achievement section one can see for example how many sirens or bloats one has killed. I know that I have I have killed more than 10 sirens, but see no such thing in the achievement section. Even if I only have killed 5 I do not see how many I have killed e.g. 6 out of 100 and so on.

[Lekwid]

Originally Posted by Murderlove

Hello there,

I have encountered two bugs in Killing Floor I think, so here goes:

1)Build KillingFloor_Build_[2009-02-09_10.82]

OS: Windows XP 5.1 (Build: 2600)
CPU: GenuineIntel PentiumPro-class processor @ 2675 MHz with 2047MB RAM
Video: NVIDIA GeForce GTX 285 (8520)

General protection fault!

History: SkeletalMeshGet <- USpriteEmitter::UpdateParticles <- AEmitter::Tick <- TickAllActors <- ULevel::Tick <- (NetMode=3) <- TickLevel <- UGameEngine::Tick <- Level KF-BioticsLab <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 4C576C61 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free

2)In the achievement section one can see for example how many sirens or bloats one has killed. I know that I have I have killed more than 10 sirens, but see no such thing in the achievement section. Even if I only have killed 5 I do not see how many I have killed e.g. 6 out of 100 and so on.

Yes, I'm also getting error #1 fairly frequently. I have no clue what the cause of it is and I haven't noticed anything particular that I was doing at the time that could have resulted in that error.
This error does not occur with any other games I currently own on steam.