OldUnreal (Engine)

this

Critical: URender::AMD3DClipBspSurf
Critical: URender::OccludeBsp
Critical: URender::OccludeFrame
Critical: URender::DrawWorld
Critical: UGameEngine::Draw
Critical: UWindowsViewport::Repaint
Critical: UWindowsClient::Tick
Critical: ClientTick
Critical: UGameEngine::Tick
Critical: UpdateWorld
Critical: MainLoop

happens alot in large maps with alot of lighting or a ton of projectiles with lighting. a similar problem also happens with over 400+ meshes on the screen..
Typically it happens on maps that are UT style, large and open. I only know of this problem because of the mod my server runs, wich essentially.. pushes unreal to the limit, suprisingly, only running a 225server/client there's only this problem, and the bunch.bopen/assertion failed problem.

But this bug here is independant of renderer, or version. 225 d3d, ogl, software or glide, same with 226, including the OMP d3d and everything. I have exported > imported the map i can reproduce this on in seconds, it was a tomnjerry map, the original without texture/sound/music dependencies. so all of the walls have the default texture except one.
the download is here: http://www.klankaos.com/files/lighttest.zip The .U is code from myself and koopa's mod. the .unr has the original credits + whoever imported it from UT

When you load up, pick up the stinger and hold fire at the colored wall, pretty sure you'll just instantly crash with that error up there. Another question is has anyone actually seen this on smaller maps? i've only encountered this alot on this map, wich makes it unplayable with my mod.

I tried it and got the same results with UGold. I wonder if this is AMD cpu's only?

ScriptLog: Login: {KDS}pÍtßûll
Log: Possessed PlayerPawn: MaleThree dmlightmap.MaleThree1
Init: Initialized moving brush tracker for Level dmlightmap.MyLevel
Critical: URender::AMD3DClipBspSurf
Critical: URender::OccludeBsp
Critical: URender::OccludeFrame
Critical: URender::DrawWorld
Critical: UGameEngine::Draw
Critical: UWindowsViewport::Repaint
Critical: UWindowsClient::Tick
Critical: ClientTick
Critical: UGameEngine::Tick
Critical: UpdateWorld
Critical: MainLoop
Exit: Executing UObject::StaticShutdownAfterError
Exit: Executing UWindowsClient::ShutdownAfterError
Log: DirectDraw End Mode
Exit: UOpenGLRenderDevice::ShutdownAfterError
Exit: appExit
Uninitialized: Name subsystem shut down
Uninitialized: Log file closed, 10/01/07 15:47:00

It's not, if you use -nok6 it gives the error Critical: URender::ClipBspSurf insted of AMD3D clipbspsurf, unless it detects the hardware anyway.

whatever it is, 227 doesnt crash with the error you mentioned here...will make more tests tonight.

that'd be cool if it was already fixed haha

blah! we wanna test it our selves! give us a beta smirf!!!! wat more do u have to do anywayz? :-?

maybe trying to make sure the first test won't be a mess?

ok, actually it does crash. It only takes longer, you have to fire for a longer time, then 227 crashes as well. Guess its an overflow of some kind. Not sure yet, and not sure if this can be easily fixed yet.

lol

just thought i'd put my thoughts on this as a mapper but:

isn't this an obvious engine limit rather then a bug? i mean its very easy to replicate anywhere even in ued, just place several spheres, a light, extend its lightradius, move it around and watch ued crash

its even on the unreal technology/udn page that dynamic lights cause crashes on extensive usage because of the amounts of surfaces updated in real time, which sorta makes sense.

Yeah, but it doesn't mean it can't be fixed, by detecting WHEN there's too many dynamic lights and to stop rendering the newest ones..

I do have these client crashes from time to time with my UGold client. I can replicate a client crash with the Aura TraceStinger gun (Gun that fires many fast moving, glowing laser beams) on maps with fog. The dynamic lights of the laser projectiles make the fog light up, but usually after a few seconds of firing the client crashes. (The server does not crash)