adosorken wrote:I found a copy of list_waypoints.sql and just made my own new_drops.sql from the existing table (worldserver loads it just fine, so the structure is probably correct).
The client crashes after logging in and selecting a channel.
Looks like it's trying to read a file that isn't present. The file path is truncated, so I did a directory search with wildcards. The source of the crash is Rose_Engine/Client/Util/CFileSystemNormal.cpp on line 87:
- assert( m_pFile && "Read failed from FileStream, file description is null" );
This assert() is causing the client to crash. The whole function is as follows:
- int CFileSystemNormal::Read( void *lpBuf, unsigned int nCount )
- {
- assert( lpBuf && "Read failed from FileStream, output buffer is null" );
- assert( m_pFile && "Read failed from FileStream, file description is null" );
- if( m_pFile == NULL || lpBuf == NULL )
- {
- return 0;
- }
-
- memset( lpBuf, 0, sizeof( char ) * nCount );
- return fread( lpBuf, 1, nCount, m_pFile );
- }
Why the assertion is failing is beyond me. The code looks solid. Also, I am not sure what file it is attempting to load.
That whole CFileSystemNormal class is one that I added to load stuff in from file rather than VFS.
I kind of cobbled some of it together as a copy of CFileSytsemVFS which is the way it would have loaded from VFS originally. hence the reason that the "asserts" are still there. I hate those bloody things. They create a break point if the assertion fails for any reason. One of my projects is to remove every last one of them from the entire source by the end.
It's kind of difficult to figure out which file it's reading from.
That's one of the reasons I added a Client_Log class.
The whole client loading process is being logged each time you run it. At least it is as long as you have a folder named "log" in the root directory of your client. If you don't, just add an empty folder named "log" then run up the client again
Inside the "log" folder you will find two logs. "InOutPackets.log" which logs all packet traffic to and from the client and "ClientLog.log" which logs the startup sequence of the client
It might not tell you precisely which file it's trying to load but it will clearly show teh last one that worked correctly so we can track it back easier. It might even show the actual file..... maybe.
Need to lookup information on NARose items, skills, quests?
Now featuring a newly completed skill tree for all classesFormatting fixed for different resolutions"A Gazelle is nothing but a giraffe plotted logarithmicaly"