1. Discord Support team Facebook l2central.info

Game Crashes,after event update s.o.s

Discussion in 'Technical Issues (Archive)' started by WeNeedBetherSupport, May 21, 2014.

Thread Status:
Not open for further replies.
  1. WeNeedBetherSupport

    WeNeedBetherSupport User

    Joined:
    21.05.14
    Messages:
    2
    Likes Received:
    0
    i did check and diagnostic util. but its same doesnt help s.o.s... s.o.s :confused:

    2014.5.21 21:20:53 [gtick=192 lgticks=1]
    build date : tue may 13 11:39:45 2014

    os : windows 7(32) 6.1 (build: 7601), service pack 1.0
    cpu : genuineintel intel(r) core(tm)2 duo cpu e7300 @ 2.66ghz @ 2669 mhz
    ram : 3071mb ram
    logicalcore : 2
    physicalcore : 2
    video : nvidia geforce 8600 gt (2049)
    poscode : ls9(581) 0:0:0 2/0 [423]
    video resources : 26 mb
    ime :

    readfile failed(precache): return=0 count=0 buffercount=525 error=data error (cyclic redundancy check).

    history: ulinkerload::serialize <- ustaticmesh::serialize <- loadobject <- (staticmesh rune_agit_s.rune_agit_3-02 12435927==12435927/16538162 11916467 681301) <- ulinkerload::preload <- preloadobjects <- uobject::endload <- uobject::staticloadobject <- (engine.level none.mylevel 21_16.unr) <- loadlevel <- ugameengine::loadmap <- mapname=21_16.unr <- localmapurl <- ugameengine::browse <- clienttravel <- ugameengine::tick <- updateworld <- cmainloop::updatetheworld <- mainloop
     
  2. BeerWarrior

    BeerWarrior User

    Joined:
    28.02.13
    Messages:
    156
    Likes Received:
    21
    recently a similar thread was created and if i recall right the character had to be moved elsewhere by a gm.
    i suggested to check for potentially damaged file, your report mentions a mesh file rune_agit_s.usx, its standard location is lineage ii eu\staticmeshes\rune_agit_s.usx

    you may want to check its properties, here's what mine looks like, see if yours is the same or different, if it's different then repair your game.

    rune_agit_s.usx
    size: 16,538,190 bytes
    md5: 6a00772e15cfe474c7d3617dfe8622c4
     
Thread Status:
Not open for further replies.