History
v1.3 - 16/05/2007: Added GPL69Rank definitions.
v1.2 - 30/11/2006: Provided compatibility with .ini files generated via the GPLRank site. Silverstone benchmark time of GPL65Rank and GPL65v2Rank fixed.
v1.1 - 22/10/2006: Wrong scanning of a GPLRA-generated .ini file fixed.
v1.0 - 16/05/2006: Initial release.


Legal Notice
This software is provided as is without any kind of warranty: use it at your own risk. JRankViewer is made for free and for public usage only: no commercial use is allowed. Please, do not distribute any part of this software without permission.
This is neither a GPLRank official software neither a Sierra/Papyrus product.


What is JRankViewer?
JRankViewer is a program for calculating handicaps of the GPLRank ranks. It provides a simple way to show your best laptimes and your handicaps for the tracks of a specific GPLRank rank.
It supports the following GPLRank ranks: GPLRank, ChallengeRank, HistoricRank, MunchausenRank, GPL65Rank, GPL65v2Rank, GPL69Rank. For each of the previous the Monster rank handicap is also computed.


Getting Started
Since JRankViewer is a Java application, you need a Java Virtual Machine installed on your system to run it. Most of the home computers come with a Java Runtime Environment (JRE) already installed. You can check if your computer is equipped with the JRE by typing "java -version" in the command console. If you don't have the Java Runtime Environment installed, you can freely download the Standard Edition from https://www.java.com.


Installation & Startup
JRankViewer can be used with any operative system capable of running a Java Virtual Machine such as Windows, MacOS, Unix, GNU/Linux.
To install, copy the JRankViewer folder in any desired location of your hard disk.
To run, execute the JRankViewer.bat file contained in the above folder.


Usage
To use JRankViewer you need a GPL-generated-like .ini file which contains your best laptimes.
If you want to use JRankViewer to see your GPLRank handicaps only, you have to select the player.ini file contained in the Players\<driver name> subfolder of your GPL installation.
Otherwise, it is recommended to first use GPL Replay Analyser to extract times and create such .ini file (GPL Replay Analyser is a free tool for Grand Prix Legends, created by Jonas Matton and Martin Granberg, that can be found at https://gplra.pike.nu/).


Troubleshooting
If the configuration file created by JRankViewer get damaged, the program will not run at all. In this case manually remove the Config.ini file located in the program folder and run JRankViewer again: a new, default configuration file will then be created.


Please, read the readme file included for further informations and credits.
Comments and feedback are welcomed.



Download JRankViewer v1.3





This post has been edited by yDNA: May 16 2007, 08:54 AM

Hi yDNA

Sounds very interesting
I´ll try it tonight.

Thanks
tommi

Looks like a very nifty tool. Thanks.

Many thanks for updating this
Cool!!

Looks cool yNDA Thanks.

Is it very difficult to let it work with the TotalRank aswel ???

Hi Pedro.
No, it's not difficoult at all to let JRV works with TotalRanks.

To achieve that JRV should be updated each time a new track come out and is added to the TotalRank (monthly? ). More precisely: its track list only should be updated.

A solution could be to let JRV dynamically update its track entries, each time you run it, by downloading the last track list available from the GPLRank site (or from the Alternative Track DB).

Unfortunately this is impossible for two main reasons. First: actually JRV is not an official GPLRank tool so I do not have any kind of contact within the GPLRank staff. Second: JRV is designed to work offline without the need of an internet connection, this is its main purpose. It's independent from the GPLRank site at all and this let it fully usable even if the GPLRank site is down (as it happened times ago).

The dynamic updating feature could be implemented as an extra however. Let see if this tool will became so popular among gplers to justify this new feature.

Lets hope so, Thanks yNDA

A little bug has been discovered: the Silverstone time of the GPL65Rank (GPL65v2Rank also) is compared to a wrong benchmark.
To fix the problem:

1) Go to the folder where JRankViewer is installed and locate the JRankViewer.jar file.

2) Open it using a packaging utility such as WinRAR.

3) Go under the Core folder.

4) Drag into this folder the file contained in the archive attached below overwriting the old one (WinRAR will show a dialog, simply click on Ok).

5) Close the archive.

The above is only a temporary fix before the next release. I need some day to look for other wrong benchmarks (if any), code other minor updates I've already planned, recompile all the sources and organize the package.

The help of a TotalRanker would be welcomed to check other time related discrepancies.

Many thanks for your new release today!!

You have rubbed the lamp for three times, master yDNA

The readings from the Challange, Historic and Munschausen are (in my case) correct.
However the reading from de GPL rank are different

Because of the two places where de data are coming from (player.ini and Replays on HD) this can be explaind.
To check it out I created / generated a Player.ini from https://gplrank.schuerkamp.de/php-pub/user.php?generateFile
but, locating this file in the JRankViewer displays no time's (yet?)
So I can not compare the GPL times for you (master yDNA)

I hope this is of any help to you.
Ather wise you have one wish to go

Greeting Pedro.

Have you tried with the new 1.2 version (see post #1)?

Now I have..........................

Houston I have a problem.
The readings I get from https://gplrank.schuerkamp.de/php-pub/user.php?generateFile are not compleet!
Your JRanksVieuwer displays this (mishap) perfectly.

This is what I have done:
1 put all my replays in the GPL\Replay folder and made a PB.ini file with RA7.7
2 upload this file to the Ranking site.
3 Generated a Laptime from https://gplrank.schuerkamp.de/php-pub/user.php?generateFile
4 compared the two file's by loading them in JRankViewer and compare the time's with the Ranking DB

By example:
In the Ranking DB I have a race time for Crystal Palace
I have a replay on HD
When I select The ReplayAnalyser.file in JRankVieuwer, this time is displayd!
When I select The ScheurkampDB.file in JRankVieuwer, this time is not displayd!
I Checked the file in notepad, and there is no Race time for CP in de SchuerkampDB.file

So in short
I can not check wether your JRankVieuwer is working correct or not, compard with the SchuerkampDB.site,
becuase my replay collection is not complete, and the https://gplrank.schuerkamp.de/php-pub/user.php?generateFile is ...............not working well???
On the other hand, JRankVieuwer display perfectly and simple wich replay's I am missing (when I use RA7.7)


A other thing:
When I select Rank:GPL65 and GPLv2Rank, JRankVieuwer is displaying time,s (I do not drive 65!) when my 67time.ini is selected.
Is this normal?

Hope this is to any use to you Andrea

Thank you very much Pedro, your feedback is the most complete I've ever recieved so far.

Ok, let me comment your results.

I don't know if the 'Generate ini file' feature of the GPLRank site currently works well or if it is bugged somehow. I think you should ask the GPLRank staff about this problem.
Anyway, you reported that the .ini generated by the site misses a time for Crystal Palace even if you lapped there. Obviously the missing entry in the .ini lead JRV to the same lack: this is absolutely normal.



Yes.
This happens for every track that is shared in more than one rank: same track entry in the .ini results in a positive match while scanning for different ranks. Remember that it is you that force JRV to show times as part of the '67 season rather than the '65. So, when you select GPL65Rank form the rollout menu you're saying that the .ini considered contains times of the '65 Season.
'67 times of the original GPL tracks result in VERY negative times in the '65 ranks but those datas are obviously meaningless.

Apart for this I read from your feedback that JRV is working as it should do.
Thank you.

Thanks for your new version