1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Discord Support team Facebook l2central.info

Trouble with Option.ini

Discussion in 'Technical Issues (Archive)' started by KrisNL, Dec 11, 2011.

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

    KrisNL User

    Joined:
    10.12.11
    Messages:
    4
    Likes Received:
    0
    hello,

    i got some problems starting up the game everything goes normally untill i select my char.. this is what shows up on the critical error:

    --------------------------------------------------------------------------------------------------------------------------------

    2011.12.11 02:15:52
    os : windows xp 5.1 (build: 2600)
    cpu : genuineintel intel(r) pentium(r) d cpu 3.00ghz @ 2995 mhz 1022mb ram
    video : ati radeon hd 2400 pro (6806)
    poscode : ls9(415) 0:0:0 2/0 [364]

    error setting display mode: createdevice failed (d3derr_invalidcall). please delete your option.ini file if this error prevents you from starting the game.

    history: ud3drenderdevice::unsetres <- createdevice <- ud3drenderdevice::setres <- uwindowsviewport::tryrenderdevice <- uwindowsviewport::togglefullscreen <- wm_syscommand <- uwindowsviewport::viewportwndproc <- wwindow::staticproc <- wm_unknown <- uwindowsviewport::viewportwndproc <- wwindow::staticproc <- dispatchmessage <- 00170330 161 <- messagepump <- mainloop

    ---------------------------------------------------------------------------------------------------------------------------------

    anyone can give some help cause i rly dnno what to do next.... thnx in advance...
     
  2. Famous

    Famous User

    Joined:
    03.12.11
    Messages:
    30
    Likes Received:
    2
    have you tried to delete the file then do fix all via the web launcher?
     
  3. Slasher

    Slasher User

    Joined:
    08.12.11
    Messages:
    158
    Likes Received:
    0
    you don't need to fix. lineage 2 when option.ini is deleted creates an new one, with lowest settings.

    try deleting the file, it's located in system of your installation directory.
     
  4. KrisNL

    KrisNL User

    Joined:
    10.12.11
    Messages:
    4
    Likes Received:
    0
    i deleted that option.ini file now 25 times already but still the same it still give the same critical error. i even adjusted that option.ini file according to another thread i found in here with some code's even that didn't help me at all.
     
  5. Eska

    Eska User

    Joined:
    24.11.11
    Messages:
    1,726
    Likes Received:
    11
    hello,

    please reinstall / update your directx.
     
  6. KrisNL

    KrisNL User

    Joined:
    10.12.11
    Messages:
    4
    Likes Received:
    0
    how can i do that cause i can't find any folder with directx in it in the lineage2 eu file ??
     
  7. KrisNL

    KrisNL User

    Joined:
    10.12.11
    Messages:
    4
    Likes Received:
    0
    i reinstalled directx 10 i could log 2 times for 30-40min each time but now its back to the beginning again that option.ini file i giving me a hard time. deleting it doesn't help cause if u start the game it is again in ur file's. change the code's in the file also doesn't help. only the new installed directx helped for 2 times. if anyone knowâ´s another option to fix this problem let me know.

    thnx in advance.
     
  8. Slasher

    Slasher User

    Joined:
    08.12.11
    Messages:
    158
    Likes Received:
    0
    have you tried to update your video card drivers?
     
  9. TGM_darken09

    TGM_darken09 User

    Joined:
    25.10.11
    Messages:
    186
    Likes Received:
    81
    what's your native resolution?
     
  10. Eska

    Eska User

    Joined:
    24.11.11
    Messages:
    1,726
    Likes Received:
    11
    good day,

    you can see actual solutions and issues' statuses here.
    additional instructions could be found here.
    if you can't find a solution for your issue you always can ask for moving the thread back into the main branch.

    best regards,
     
Thread Status:
Not open for further replies.