Hi,
Here mine gui. lol (works almost fine , only a small bug with the reverse tracks ).
I have a small question to. Is it posible to set a time race lesser then 1 hour? I can do /hours 1 for a 1 hour race but is it posible to set up a race for 30 or 15 min.?
Hi,
Its posible to use a var for the numbers of lap's and set that var with a kind of a gui. see the one from yisc or me above. Need some changes to set track rotation ( i think i make that in future )
Edit: yisc was faster (and that is a beter option to) lol
Okay, it's finished, tested as good as possible (a big thanks to [R-R] SumbeamNL)
The section for Number of stops / Pitwindow is only shown when you're using my code for the Pitboard, otherwise it will be hidden since it is of no use to you.
Some lines are marked with # and a comment about the Pitboard software.
This GUI isn't protected so you have to add some $allow="" code to restrict it to certain users, otherwise everyone can control your server!
If you find a bug or think something can be made in a better way, please contact me.
I've been working on setting up buttons for showing the !top table for each of the vehicle types (see Top Blank image), to save typing it in.
However, just now, if you want to look at one vehicle, you have to click Ok at bottom of table to then look at another vehicle type, otherwise the table is overwritten by next car table.
For instance, I opened the BF1 table (Top BF1 image), then opened the FXR table without first closing the BF1 table. This has meant that the smaller FXR table has overwritten the top part of the BF1 table (Top FXR image).
The "Ok" button for closing the !top table must exist in Lapper somewhere, probably in the main program, but it doesn't appear in the LFSLapper.cfg file.
Does this Ok button have an existing (hidden) subroutine that I can use to close the 1st table before opening the 2nd table, or is there some other way?
Yes you're doing that correctly. The 'problem' is with Lapper, since !top is a builtin command so you can't close a table which is generated by such command. I hope this will change in a future version so we can make our own tables.
My lapper seems to have stopped collecting drift scores. New high drift scores aren't appearing in the !drf command, and checking DriftPB.txt file, there hasn't been additions for a while.
I haven't turned off the drift database function in my lapper, so don't know where I'm going wrong.
Had a look at all the files that are part of the server where lapper kept, and there's one called cfguser.txt with few names in it.
Looking back at my DriftPB, these are the last people to get drift points.
Can anyone advise what the letters and True/False mean?
EDIT:
Silly me! Found I had 1 and a half drift sections in my lapper config file. Because I was working on my drift scoreboard for a while, I'd cut out a large part and put it at the top of my config to make it quicker to work on. Sorry if I've caused anyone any work trying to find my problem.
However, still like to know what the cfguser.txt file is for.
When I join on server as an administrator (with admin pass), I can vote to kick and ban over the list of drivers, and if I join as a guest (without admin pass) options for vote are not available.
I also noticed some kind of odd voting behaviour with LFSLapper. I configured Lapper to allow voting for restart and quali for all non-admins. Sometimes it works correctly (opening the vote/need button at the top of the screen) but sometimes, even in the very same session, e.g. after the next race, every try to vote - even by admins - is immediately cancelled.
Furthermore when this happens and I restart the race as admin with /restart command this action can then be cancelled through anybody by voting restart.
I can't reproduce this. Any clues, what causes it?
EDIT: Just noticed $InRaceVoteLapsMinMax was set to "1-0". Don't know what made me set it like this. Interesting though that the /restart command could be cancelled through anybody's vote.
When I set number of stops through !stops command to anything greater than 0 and no pit window is set, the pit lane doesn't open at all and I get a sto&go penalty after first lap.
That's correct behaviour of the software. The pitlane is opened when the value set with pitwindowstart is reached. If this value is blanc, the pitlane won't open. If you want to set x number of stops but not a specific window, set the window to the whole race. Like this:
Race length: 20 laps
!stops 2
!pitwindowstart 1
!pitwindowstop 20
Pitlane will open immediatly for the duration of the whole race.
I wanted to set the pit window to 1 - "last lap" automatically when using !stops command, but couldn't find a variable which gives me the actual number of laps set for the race. So for now I set it 1 -100 through
at the end of Sub Stops. Would be nice if $argv=100 could be replaced by $argv=$laps_race or something. I prefer to not have a pit window when none is set instead of not being allowed to pit at all.
Btw: Isn't
$pitwindow_1=$pitwindow_1-1; # Verminderen met 1 omdat de ronden waar je in zit ook goed is om te pitten
supposed to be part of Sub Pitwindowstart() instead of Sub Pitwindowstop()?
Could cause some trouble imho if you decided to set a new pitwindowstart but leaving pitwindowstop as it was.
My dutch isn't good enough either to understand what it is supposed to do, but I guess it is required to make IF (laps_done >= pitwindow_1) true in the right lap. Hope, I got that right...
PS: Is the pit lane supposed to be closed in lap 1 whichever setting for pitwindowstart you use? I added a corresponding IF (pitwindow_1 > 0) THEN Pit CLOSED, ELSE Pit OPEN in Event OnSpbSplit1() to display Pit OPEN also in first lap when pitwindowstart is set to 1 (or 0). That should also correspond with pit stop actions (Stop in first lap will cause a player_x_pitstops drop when pitwindowstart is set to 1, won't it?).
If you don't want a pitwindow you have to clear it with: !pitwindowclear
That will set the number of stops and the pitwindow to blanc.
If you still want a mandatory pitstop, you can set in LFS.
At the moment it isn't possible to set !stops without using a pitwindow.
I'm building a new version of the Pitboard to go with the whole new version of Lapper which is currently developed by Gai-Luron and things are coming down nicely. I will try to implement your wish in this new version.
Yeah I've implemented that a litte weird and have it rewritten (complete with a nice GUI) in the new version.
The pitlane is always open when $number_of_stops is blanc, otherwise it's closed until $LapsDone >= $pitwindow_1 && $LapsDone < $pitwindow_2
The new version of the Pitboard can have up to 3 pitwindows with every window containing X stops.
This is for use with LFSLapper V5.714 latest.
(Can probably be updated for later versions - I think the 'PBDrift.txt' part now changed).
If you do use this, then please make and keep back up copy of your original LFSLapper.lpr file.
Please read through my script, as it gives instructions and information on certain parts that you will have to look out for and to change some settings (believe it or not, but I'm not a drifter, so don't know if settings [speed/angles] are suitable.
Special thanks to GaiLuron for his lapper program, and Yisc[NL] and Tim[NL] for advice.
Very special thanks to my son who reminded me that to get a positive number, all you have to do is multiply 2 negative numbers together. And if one of these is your original negative number and you multiply by -1, then you change your original negative number to a positive. Doesn't sound much, but it had me stumped! I learned this at school over 35 years ago, but have never had to use it before! Without this piece of information, if you drifted car one way you would have got a proper number for the angle, but a negative number if drifted the other way.
Anyway, hope you enjoy.
REMEMBER: You use this at your own risk. I take no responsibility for anything!
(works almost fine , only a small bug with the reverse tracks ).
)
