LCKB
Сompilation errors - Printable Version

+- LCKB (https://lckb.dev/forum)
+-- Forum: ** OLD LCKB DATABASE ** (https://lckb.dev/forum/forumdisplay.php?fid=109)
+--- Forum: Guides & Help Section (https://lckb.dev/forum/forumdisplay.php?fid=193)
+---- Forum: Help & Support (https://lckb.dev/forum/forumdisplay.php?fid=157)
+----- Forum: Ep4 Support (https://lckb.dev/forum/forumdisplay.php?fid=128)
+----- Thread: Сompilation errors (/showthread.php?tid=5000)

Pages: 1 2


- MLIKE - 12-25-2022



12 minutes ago, Veni said:




yup, remove it. just return true/false cant check which one it is im ingame rn llol




okay now I'll try and tell you about the result




- MLIKE - 12-25-2022



17 minutes ago, Veni said:




yup, remove it. just return true/false cant check which one it is im ingame rn llol





I did so, but most likely I misunderstood you, the error remained the launch does not occur



 



 



// [2013/01/16] sykim70



ENGINE_API bool SE_CheckEngine()



{



#if !defined(_DEBUG) && !defined(KALYDO) && !defined(G_KOR) && !defined(VER_TEST) && !defined(G_CHINA)



    AnalyzeApplicationPath();

 


#endif



    return false;



}





- MLIKE - 12-25-2022



23 minutes ago, MLIKE said:





 



Just cutting it out ?



 



// [2013/01/16] sykim70



ENGINE_API bool SE_CheckEngine()



{



#if !defined(_DEBUG) && !defined(KALYDO) && !defined(G_KOR) && !defined(VER_TEST) && !defined(G_CHINA)



    AnalyzeApplicationPath();

 


    // check binary.lod



    CTString strFullPath = strDirPath;



    CTString fnTemp = strFullPath + "data\\etc\\binary.lod";



    CTString data = OpenPersistentSymbolFile2(fnTemp);

 


    CTString oneline;



    if (!GetOneLine(data, oneline))



        return false;



    int nCount = atoi(oneline.str_String);

 


    if (!GetOneLine(data, oneline)) // stamp



        return false;

 


    UINT srcLen, targetLen, targetTime;



    UINT minTime = -1;



    UINT maxTime = 0;



    for (int i = 0; i < nCount; i++)



    {



        if (!GetOneLine(data, oneline))



            return false;



        fnTemp = strFullPath + oneline;

 


        if (!GetOneLine(data, oneline))



            return false;



        srcLen = (UINT)atoi(oneline.str_String);

 


        if (!GetFileInfo(fnTemp.str_String, targetLen, targetTime))



            return false;

 


        if (srcLen != targetLen)



            return false;

 


        minTime = min(minTime, targetTime);



        maxTime = max(maxTime, targetTime);



    }



    if (maxTime-minTime > 60*3) // 3 min



        return false;

 


#endif



    return true;



}




I tried to delete it all and without adding anything, now let's look at the result




- Veni - 12-25-2022


im out of the game now, just change it to this: 

// [2013/01/16] sykim70
ENGINE_API bool SE_CheckEngine()
{
return true;
}

 

or remove the check from Nksp.cpp




- MLIKE - 12-25-2022



10 minutes ago, Veni said:




im out of the game now, just change it to this: 


// [2013/01/16] sykim70
ENGINE_API bool SE_CheckEngine()
{
return true;
}


 



or remove the check from Nksp.cpp




in Nksp.cpp deleted everything


    // [2013/01/16] sykim70



    //if (!SE_CheckEngine())



    //  return FALSE;





- Stormax - 12-25-2022


/index.php?/profile/22113-mlike/&do=hovercard" data-mentionid="22113" href="/index.php?/profile/22113-mlike/" rel="">@MLIKE 

/index.php?/topic/15375-the-client-does-not-start/&do=embed" style="height:215px;max-width:502px;">

 Try my solution.

And for your error isn't a problem for start LC, source you use is bugged.




- Scura - 12-25-2022


lunch the client trough the local microsoft debuger (on visual studio), once the client crash, it should tell you more details. Remember to compile with symbols 




- claycodes - 07-11-2023


The initial warnings occurred because the debug information created by visual studio is was not in the expected place, which can be fixed by compiling the packages in 3rdparty and setting the correct output path for the .pdb files. However the files missing does not cause the crash you experienced. You just won't be able to debug it with those symbols.