ParaEngine Log files

log.txt file

General log file is the first place to examine for errors when programming with NPL. You can discover compiling errors, runtime errors, mini-dump, script log result, database operations, warnings and other errors. 99% of chances are that the answer is already in the log file.

Location	Log file (log.txt) is located at the root path of your ParaEngineSDK installation
example	Plug-in loaded: NPLWebServiceClient.dll Begin transaction: ResourceStore:PutItem End transaction: ResourceStore:PutItem warning: texture file not found:url(Texture/3DMapSystem/IntroPage/16number.png

• NOTE1: It is a good practice to quite a quick launch icon on the desktop for this file.
• NOTE2: You should use a LUA compiler in your NPL source editor to discover compiling errors prior to execution.

Out to log file

One of the most important way to debug NPL script file is to insert temporary log statement in code and examine the log file at runtime. Simple write log("Any sentences\n")

There is also an AdvancedLog helper class in NPLModules for logging.

perf.txt file

Performance log file (Perf.txt) contains statistics for the performances of core modules in ParaEngine.

Location	Performance log file (Perf.txt) is located at the root path of your ParaEngineSDK installation.
example	<Audio Engine Framemove> Avg: 0.000004 Dev: 0.000000 Max: 0.000020 Min: 0.000004 Total Frames: 422 <Main Render> Avg: 0.003500 Dev: 0.001908 Max: 0.151791 Min: 0.002011 Total Frames: 422 <GUI Render> Avg: 0.001820 Dev: 0.000418 Max: 0.030882 Min: 0.001204 Total Frames: 422 <present> Avg: 0.000309 Dev: 0.000045 Max: 0.002871 Min: 0.000082 Total Frames: 422

Net.txt file

If you use the built-in TCP|UDP networking engine, it will output log to this file.

Location	Network log file (Net.txt) is located at the root path of your ParaEngineSDK installation.