10/13/2026 [22:45:18] GMT Home .:. Logout
Forums
Hardmaps.com :: Forums :: Map Making Forum :: Joint Operations
 
<< Previous thread | Next thread >>
Nile profiler guide
Moderators: Hardmaps Administrator, *HmS*Wedge, *HmS*grunt, *HmS*Trevor, *HmS*LongBow
Author Post
*HmS*Wedge
Wed Nov 17 2004
Captain Slow

Registered Member #3
Joined: Fri Dec 19 2003
Location: Scotland
Posts: 4651
NILE Profiler Quickstart Guide



The NILE profiler allows you to analyze the movements of all the players in a game. This is useful for map builders who want to see what real players do on their maps. This tool is not for seeing what players are doing on maps you did not make, such as NovaWorld maps. For this reason, the source .NPJ or .MIS file is needed to use the profiler.


To use the profiler youll need to have NILE, the source file of the map you are profiling, and an .SPH file. The .SPH file contains the profile information for a given game.


To generate a .SPH file, you will need to add a couple things to the shortcut you use to run Joint Ops. Right-click on the shortcut and choose Properties. Make sure you have the Shortcut tab selected. In the text field named Target you will see the path to your Joint Ops executable. You will need to add /profile to the end of the text already in the Target field. For example:

"C:\Program Files\NovaLogic\jointops\jointops.exe" /profile myprofile

Once you have done this click OK. When you run the game using this shortcut and host a game a .SPH file will be created with the filename you entered. In the example above it would be myprofile.sph. Each time the server cycles a new file will be created: myprofile2.sph, myprofile3.sph, and so on.




This is a link to Novas guide to using the profiler in Nile

ftp://ftp.novalogic.com/jotr/JOTR_NILEGUILDE_082604_xx.PDF




[ Edited ]
Back to top
Website
 

Jump:     Back to top

Syndicate this thread: rss 0.92 Syndicate this thread: rss 2.0 Syndicate this thread: RDF
Powered by e107 Forum System
All trademarks are copyright their respective owners.
This site is best viewed using 1280-1024 screen resolution.
{THEMEDISCLAIMER}
Render time: 0.0698 sec, 0.0100 of that for queries.