Freelancer Community Network
Reminder: Internet Explorer 6 or below are NOT supported.
HomeHome
ForumForum
WikiWiki
DownloadsDownloads
ForgeForge
Multiplayer Connection Tutorial
Collapse/Expand Random Image
Collapse/Expand Login
Username:

Password:

Remember me



Lost Password?

Register now!
Collapse/Expand Chat
Collapse/Expand Who's Online
128 user(s) are online (104 user(s) are browsing Forum)

Members: 0
Guests: 128

more...
Collapse/Expand Donations
Monthly costs: -30€
Income (ads): +5€
Donations (last month): +0€

Current balance: 55€
(last updated 04/2021)

Please make a donation if you want to help keeping The-Starport online:

Thanks!
Collapse/Expand Links
Collapse/Expand Advertisement
There are currently 36 users playing Freelancer on 42 servers.
September. 21, 2023

Browsing this Thread:   1 Anonymous Users



 Bottom   Previous Topic   Next Topic  Register To Post



FL Client Error Log Reader?
Starport Admin
Joined:
2008/6/24 16:40
From http://www.freeworlds-tow.net/dev
Group:
Registered Users
Starport Admin
$$$ Supporters $$$
Posts: 1123
Offline
This has been a pet peeve of mine for a long time now. When I go to test for bugs, I see no errors come up on the flserver command screen. But when I go look into the flspew or FL client error log there are a number of errors. The issue is, for the most part, all the numbers and names absolutely mean nothing to me and I can't correct the error the game is getting pissy about.

Hence, I'm asking is there someone out there that knows how to decipher this? Or, better yet, can make a program, similar to the CRC tool, that allows us to figure out what the engine is complaining about?


Posted on: 2011/2/21 20:27
Open in new window
Top
Re: FL Client Error Log Reader?
Just can't stay away
Joined:
2008/6/16 20:41
Group:
Registered Users
FLServer Admins
Trusted Speciality Developers
Posts: 312
Offline
Means someone has to have the knowledge of what is written there. Is there somewhere the knowledge documented, e. g. in the wiki?

Tools are always nice if they take off load. I comply and such a tool would be handy. Good idea tho!

Posted on: 2011/2/21 21:13
Open in new window
Top
Re: FL Client Error Log Reader?
Just can't stay away
Joined:
2010/8/25 22:40
From Romania
Group:
Registered Users
Posts: 196
Offline
Search for adoxa`s createid and whatis tools .

Posted on: 2011/2/21 22:00
Top
Re: FL Client Error Log Reader?
Home away from home
Joined:
2009/8/16 2:58
From Qld, Aus.
Group:
Registered Users
FLServer Admins
Trusted Speciality Developers
Senior Members
Posts: 2042
Offline
Code:
rem initial step to create the database
createid -sh
rem use the database to translate hashes to nicknames (or descriptions)
flunhash flspew.txt | more

You should use the command line for CreateID, but after that you should be able to just drop flspew.txt on Flunhash, then view the resulting flspew.txt.txt.

Posted on: 2011/2/22 5:37
Top
Re: FL Client Error Log Reader?
Starport Admin
Joined:
2008/6/24 16:40
From http://www.freeworlds-tow.net/dev
Group:
Registered Users
Starport Admin
$$$ Supporters $$$
Posts: 1123
Offline
Awesome. I was able to find some new bugs and now can fix them. That being said, how would I go about finding the fixes for these types of errors?

Code:
C:\work\builds\dalibs\dalibs-build\build\Src\RendComp\VMesh\VMPartArch.cpp(697) : NOTICE:General: VMESH: couldnt find material 3859000974
C:\work\builds\dalibs\dalibs-build\build\Src\RendComp\VMesh\VMPartArch.cpp(697) : NOTICE:General: VMESH: couldnt find material 4085157495

Posted on: 2011/2/22 12:50
Open in new window
Top
Re: FL Client Error Log Reader?
Home away from home
Joined:
2009/8/16 2:58
From Qld, Aus.
Group:
Registered Users
FLServer Admins
Trusted Speciality Developers
Senior Members
Posts: 2042
Offline
CreateID only works on the ini files; you'll still have to run materials through CRCTool. Of course, if they really don't exist, that won't help either (the first doesn't in vanilla; the second is shield_1). Hm, one way might be to run everything through XML Project, then search the files for 0x, to find which meshes weren't decoded. That should at least tell you the which model is using the material.

Posted on: 2011/2/23 5:01
Top