Opis: Difference between revisions

738 bytes added ,  10 months ago
→‎Summary Tab: Ping time, forced chunks
(Tracking Tab)
(→‎Summary Tab: Ping time, forced chunks)
Line 7:
 
== Summary Tab ==
This is the default tab. On this tab you can see various information, such as the tick time overall, network data between the client and server (upload rate, download rate, ping, ...) as well as the amount of forced chunks and loaded chunks. To trigger a profiling session, click on the button named "runRun Opis". A progress bar will display under the button which changes to "Running..." while a profile is generating.
 
Generating a profile willis slowsvery downtaxing seriouslyon the server and [[lag]] should be expected during the process. Once it'sprofiling is finished, the game window will freeze, thetaking some time for the game to process all the data. Once it's done, everythingdata goeswill backpopulate to normal,the andother youtabs. can visitUse the Tracking tab or Server timing tab to learn more about lag on the server.
 
Ping time as used by Opis includes not only packet travel time between the client and server but also the processing time of that packet at the server. For example, a high ping time might correlate with a delay between breaking a block client-side, and having that block actually be removed from the game world and drop as an item. Ping is also graphed at the bottom of the Summary tab in real time.
 
Forced Chunks are [[Chunkloading|chunkloaded]] chunks, usually by an item such as a Railcraft [[Anchor]] or mod like [[FTB Utilities]]. Loaded Chunks are all chunks currently active in memory.
 
== Tracking Tab ==
4,389

edits