2010.7.16 01:42:19
OS : Windows XP 5.1 (Build: 2600)
CPU : AuthenticAMD AMD Sempron(tm) Processor 2800+ @ 1610 MHz 1023MB RAM
Video : Radeon X1300 Series (6641)
PosCode : LS8(83) -11968:123693:-3088 1/0 [480]

CreatePixelShader failed(D3DERR_INVALIDCALL).

History: UD3DRenderDevice::CreatePixelShader <- FD3DPixelShader::Init <- InitShader <- FD3DShaderManager::GetShader <- FD3DRenderInterface::DrawPrimitive <- DrawSection <- StaticMesh=GL_CV_LOD_S.GL_C_H02_LOD SectionIndex=0 <- RenderStaticMeshLod <- StaticMesh=GL_CV_LOD_S.GL_C_H02_LOD Owner=19_21.StaticMeshActor1126 Instance=19_21.StaticMeshInstance1553 <- FDynamicActor::Render <- SolidRendering <- RenderLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- SceneNodeRender <- Draw <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- MainLoop


clean gracia final client

all ze taim

i don't know how it is in ati, but look for an option that modifies pixel shader while running l2
or just update the driver
i had pixel shader problems with bioshock too

Yep it's something with the pixel shader. Check drivers.

imo its pixelshader

Didn't see that. It sais failed to create pixel shader (duh), but paranthesis sais invalid direct3d call. Direct3d is the normal mode through which video is displayed, directly through the video card. this means that either your video card's shader pipelines are fried (but I guess other games are working fine so it's prolly not the case), or your driver is failing, which is normal since ati has noobish driver devs compared to nvidia.

dl new driverz?

prolly ati failure
if "fried card" would be the problem, imo it'd end up in a blue screen of death while attemting to create one or the pc wouldn't even boot[which is the case for most video cards nowadays]
l2 could actually run though, if u force it, but u would end up seeing blank black stuff all around instead of texture here and there

y, download new drivers, or there are certain programs that allows you to handle pixel shader manually, nvidia has this kind of setting

Not necessarily blue screen. My old video card had a broken pipeline and what happened was that everything 2d and shaderless 3d was fine. When a shader was applied to 3d, it either gave an unhandled error that the shader could not be created, or it would build the shaders in forms of artifacts, like this:

or this


Or sometimes artifacts correlated to movement. Those are most likely shader artifacts. Like a line sticking out of the character's leg or head or smth. And if the character isn't moving, those artifacts simply freeze aswell.

i had the second stuff
y, you got a point, that one happened to me with mah 5yo video card sometimes and after a lil while i got freeze
but i assume this has to be a software not a hardware-side problem, since gs has only problems with l2, same as i got blank textures at a few games

fixd after game reinstallation

/fail

then y, it was one of the same problem as i had:D