| Most Common Problem's with the game |
Cause: The client cannot properly load banned messages.
Solution: Delete obscene-e.dat in your Lineage II system folder and run L2Temida.exe again.
Error: General protection fault! History: UOrcMove-CalculateCRC32 <- UGameEngine-Init <- InitEngine
Cause: The client is missing one or more vital files that are required to load the game. You have not installed the patch or updater properly, you have accidently deleted files, or you are not using the right Chronicle.
Solution: Make sure none of your folders are empty; ie. systextures, staticmeshes, textures, animations.
Error: Negative delta time! History: UGameEngine-Tick <- UpdateWorld <- MainLoop
Cause: Your Lineage 2 client could not properly read your CPU clock speeds. This usually only happens with AMD processors.
Solution: Download the [AMD Dual Core Optimizer] program and install it.
Error: Failed to enter Entry: Can't find file 'Entry'. History: UGameEngine-Init <- InitEngine
Cause: Your client is missing one or more required files to launch the game. This may also occur if you install the L2 Server patch onto the wrong version of the game (Hellbound, Gracia, C5, etc).
Solution: Install the patch in the MAIN Lineage II folder, not the system folder or anywhere else. Installing it in the wrong place can cause this error.
Error: Application failed to initialize properly
Cause: This usually appears when you are using modded video card drivers, very outdated video card drivers, do not have the .NET Framework installed, or any combination of the three.
Solution: Update your video card drivers to the latest stable ones.
Error: General protection fault! History: UObject- DissociateImports <- UObject-EndLoad <- UObject:taticLoadObject <- (Engine.SkeletalMesh =anything can be here=) <- IsLoadedResource <- User:etPawnResource <- UNetworkHandler-Tick <- Function Name=NpcInfoPacket <- UGameEngine::Tick <- UpdateWorld <- MainLoop
Cause: This is 99% of the time caused by video card drivers being unable to load textures, or it can be very rarely caused by a missing texture.
Solution:
1. Update your video card drivers to the latest stable ones.
2. If step 1 does not work, do some searching to find out what driver versions work best for your video card. In my case and many others, the latest drivers have caused issues, and older drivers work much better.
Error: History: FArchiveFileReader:eek <- ULinkerLoad:eek <- TLazyArray<< <- FMipmap<< <- SerializeMips <- UTexture:erialize <- LoadObject <- (Texture LineageMonstersTex.death_knight.death_knight_t00 99684524==99684524/133323252 99683358 132383) <- ULinkerLoad:reload <- PreLoadObjects <- UObject-EndLoad <- UObject:taticLoadObject <- (Engine.Texture LineageMonstersTex.Death_Knight_T00 NULL) <- UOrcMove-CalculateCRC32 <- UGameEngine-Init <- InitEngine Cause: You have a corrupt texture, potentially from another private server that doesn't know how to create a proper patch or from an action you have done yourself.
Solution:
1. Download a fresh Lineage2 installer.
2. If step 1 does not work, reinstall DirectX and update your video card drivers to the latest stable ones.
Error: History: NConsoleWnd-RequestAuthLogin <- NCAuthWnd-OnLoginBtnClick <- NCAuthWnd-OnPasswordDone <- NControl:endEventMessage <- NCEditBox-OnKeyDown <- NCVirtualWndMain:assToFocusedWindow <- NCVirtualWndMain:assToFocusedWindow <- NCVirtualWndMain:assToFocusedWindow <- NCVirtualWndMain:ispatchWndMsg <- NConsoleWnd:ispatchWndMsgX <- NConsoleWnd:ispatchWndMsg <- UWindowsViewport-ViewportWndProc <- WWindow:taticProc <- DispatchMessage <- 006903B0 256 <- MessagePump <- MainLoop
Cause: Another program is intercepting your connection with the Auth server when you click 'Login'. This can be from almost anything.
Solution:
1. If you have an antivirus program such as AVG, disable all active protection while logging in and enable it again only once you are ingame.
2. If you have another Lineage 2 client open of a different chronicle (ex. logged into a Gracia Final Part 2 server while trying to login to Interlude one), close the other client and restart your client. Also close any other games that utilise an anti-cheat program, whether it be Gameguard, nProtect, etc. You should now be able to login.
Error: General protection fault! History: UUIScript-execGetPartyMemberCount <- UObject:rocessEvent <- (MinimapWnd Transient.MinimapWnd0, Function Interface.MinimapWnd.OnLoad) <- NCFrameWnd-OnXMLLoad <- XMLDataManager-CreateWindows <- XMLUIManager-CreateWindows <- NConsoleWnd-InitializeXMLUI <- NConsoleWnd-Initialize <- NConsoleWnd-Init <- UGameEngine-Init <- InitEngine
Cause: That usualy appears when you want to play some private server and you downloaded their Launcher that is not working propertly.
Solution: Delete your System Folder and then update L2Temida so you get a new one, and then try start game or setup server you want to play.
Error: General protection fault! History: FL2GameData-LoadL2DataBin <- FL2GameData-ObsceneDataLoad <- FL2GameData-Load <- UGameEngine-Init <- InitEngine
Solution: Delete your system folder and download Temida updater, once downloaded Run it and wait for the system to download.
Critical error when buy from shop:
Solution: Press: ctrl+alt+del -> task manager -> process -> find L2.exe - > right mouse -> set affinity -> and select only 1 core!
ERROR: (file "some file) is corrupt:
Solution: Delete folder System. Run the L2Temida.exe file in the main game folder and press Full Check. After this treatment, the game will start correctly.
ReadFile beyond EOF 750253+1/750253 History: ULinkerLoad:Serialize <- FString<< <- UTexture:Serialize <- LoadObject <- (Texture T_themepark.17_16BG 750225==750225/750225 132738 44082) <- ULinkerLoad-Preload <- ULevel-PreloadObjects <- ULevel:Load <- Load_Level <- UGameEngine:AdjustTerrain <- L2Seamless <- UGameEngine:Tick <- UpdateWorld <- MainLoop
Solution: Reinstall systextures folder or Reinstall Game.
SmartGuard has decided to close this game session (Event code: 39/1)
Cause: One of your files in the system folder does not match the server file.
Solution: Delete the system folder and do a Full Check or re-download the System folder from the Patch server.
Error setting display mode: CreateDevice failed (D3DERR_DEVICELOST). Please delete your Option.ini file if this error prevents you from starting the game.
Cause: The error will often appear in the case of GTX series graphics cards when we want to enable Full Screen
Solution: Delete the option.ini file and start the game. If the problem persists, you need to manually edit the file and enter your screen resolution there.
Insufficient Memory. Please check the Virtual Memory Option and avilable hard drive space.
You can check them by going to : Control Panel->System->Advanced->Performance->Settings->Advanced->Virtual memory.
Cause: Even a person who has a lot of RAM can see the error
Solution:
1. First, do what is written in the error description. Depending on the free disk space, you can set different values. I suggest Min. 10 240, Max 20 480.
2. If that doesn't help, reinstall the game and re-download the patch.
3. Right click on the L2.exe applications in the system folder, then click on then click on Compatibility, run the compatibility troubleshooter. Accept the compatibility that Windows suggests to you. Additionally, you can set the application to always run with Administrator privileges, check Run as administrator in the general tab.
History: FStaticTexture::GetTextureData <- l2ui_ch3.PlayerStatusWnd.ps_sizecontrol1 <- FD3DTexture::Cache <- FD3DRenderInterface::CacheTexture <- FD3DRenderInterface::HandleCombinedMaterial <- FD3DRenderInterface::SetSimpleMaterial <- FD3DRenderInterface::SetMaterial <- FCanvasUtil::Flush <- FCanvasUtil::BeginPrimitive <- FCanvasUtil::DrawTile <- UCanvas::DrawNormalText <- UCanvas::DrawTextToCanvas <- NCGDevice::DrawTextW <- NCNameCtrl::DrawName <- NCVirtualWndMain::DrawChildWindow <- NCVirtualWndMain::DrawChildWindow <- NCVirtualWndMain::DispatchWndMsg <- NConsoleWnd::ConsolePostRender <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- MainLoop
Solution:
Log in to another character on the same account. Then switch the character to the correct one. Sometimes the error pops up again. You have to try several times until you log in normally
Last modified: 2022/08/25 19:58