any way to reduce the font and size of the pitboard? Quite a lot of people have a reduced resolution and the pitboard takes up a little too much room. Just a thought

Quote from StableX :

any way to reduce the font and size of the pitboard? Quite a lot of people have a reduced resolution and the pitboard takes up a little too much room. Just a thought

Is that realy nessacery?
Even on my laptop the Pitboard isn't oversized.
If so, people will have to figure that one out themselfs.

Maybe think about getting the section bit (2,3,4) out of the config. It seems to me that setting is determined by the track. SO my suggestion is to get that automated.

Yisc, thats really awesome! Can't wait for a release.


Sil

Quote from fat-oil :

Hi,
Is there any new 64bits release of lapper available for LFS patch Z ?
Thanks

15 days i first asked, Houston can u read me ?

Quote from SpikeyMarcoD :

Maybe think about getting the section bit (2,3,4) out of the config. It seems to me that setting is determined by the track. SO my suggestion is to get that automated.

Yeah, I've thought about that too.
Maybe there's some willing to provide me a list with all trackcombo's and the number of splits on them (I realy haven't time to sort all that out myself) and then it wouldn't be that hard to automate that section.

Cant you get that from lapper. I mean it has that great split info. It needs to know the splits per track right?

Quote from SpikeyMarcoD :

Cant you get that from lapper. I mean it has that great split info. It needs to know the splits per track right?

Good thinking, it's all in the trackinfo.cfg
Okay, on my todo list

Quote from Easy_Mike :

a feature i like to see (i might missed it)
is that in handicap i can(with your help,thx) set the lowest intake restriction to lets say 20...but u can leave pit with 25?
thats a feature i would like to see..that the value u set.in this case 20% is the only accepted one.

it is possible i guess.

i turned of the ignoremode now

I think that's possible but requires manually made code. First you have to allow 20% and when that's value is met, you have to raise it with X percentage and then allow that. There will be a problem with that when the one that's asigned 20% goes back into pits and out on the track again. This driver will get a new value then and so it goes on and on. In order to escape that problem you have to store username and percentage so when that players leavers pits again, he doesn't get a new value. So yes, it's possible but requires some serious scripting.

I think what Easy Mike is referring to would be a small code change in the comparison line for the restriction. Instead of having something like CurrentRestriction==RequiredRestriction you'd just need CurrentRestriction>=RequiredRestriction. Of course I have no idea what variables are being used in the code but if it's a simple comparison like that in the code that small change would be all that's needed.

Quote from Cabby :

I think what Easy Mike is referring to would be a small code change in the comparison line for the restriction. Instead of having something like CurrentRestriction==RequiredRestriction you'd just need CurrentRestriction>=RequiredRestriction. Of course I have no idea what variables are being used in the code but if it's a simple comparison like that in the code that small change would be all that's needed.

It's not that easy (see: http://www.lfsforum.net/showthread.php?p=962254#post962254)
A couple of globalvars have to be declared and then some code to raise them when another value has been taken by someone. It's not impossible but isn't done in 5 minutes or so.

any idea on the new lapper release?

Quote from StableX :

any idea on the new lapper release?

No, Gai-Luron told me he's working on it and hoped to release it in the next couple of weeks.
So let's sit back and wait for the things to come
I've no doubt it will be good.

Quote from Yisc[NL] :

No, Gai-Luron told me he's working on it and hoped to release it in the next couple of weeks.
So let's sit back and wait for the things to come
I've no doubt it will be good.

agreed !

Quote from A.Fedorov :

Bug. VCom (grey color) display right.

p.s. on track AI

He used LX6, ban him. :P

It's time for the community to help me testing the latest release of my Pitboard.
Want to help me? Fine

Go to: Absolute-beginners.nl[test]
Track: AS2
Cars: FXR+XRR+FZR
Laps: 20
Pitwindow: Lap 7 upto and including Lap 14

Please test the new function of comparing split- laptime to the leader of the race
Also test this feature with the Pitboard switched off.
Number of splits are auto configured now so that option is removed from the config-screen.

Quote from Yisc[NL] :

It's time for the community to help me testing the latest release of my Pitboard.
Want to help me? Fine

Go to: Absolute-beginners.nl[test]
Track: AS2
Cars: FXR+XRR+FZR
Laps: 20
Pitwindow: Lap 7 upto and including Lap 14

Please test the new function of comparing split- laptime to the leader of the race
Also test this feature with the Pitboard switched off.
Number of splits are auto configured now so that option is removed from the config-screen.

Quote from A.Fedorov :

Bug. VCom (grey color) display right.

p.s. on track AI

HMM AI drivers with LX6
and you are a demo racer :bananadea:bananadea:bananadea:bananadea

Quote from Yisc[NL] :

It's not that easy (see: http://www.lfsforum.net/showthread.php?p=962254#post962254)
A couple of globalvars have to be declared and then some code to raise them when another value has been taken by someone. It's not impossible but isn't done in 5 minutes or so.

I had seen that post and realize there's a bunch of different variables to take into account when the comparisons are being done. I don't really know the code on this as I've never looked at it but would imagine that a subroutine would have been put in place to just send data to for doing a quick check and passing back pass or fail type return. In that one subroutine would be the only spot to make the change in how it checks, if the subroutine exists. That's what I had been thinking about when I posted about the quick change and like I stated already, I haven't even looked at this code to really know how it's been implemented.

Yes, I'm primarily a VB person and not well versed on C or Net so not sure how/if subroutines would be handled in those as I'm sure this is programed in one of them. Feel free to ignore everything I say if you like since it's been a very long time since I coded stuff, was just throwing out an idea.

Quote from Cabby :

I had seen that post and realize there's a bunch of different variables to take into account when the comparisons are being done. I don't really know the code on this as I've never looked at it but would imagine that a subroutine would have been put in place to just send data to for doing a quick check and passing back pass or fail type return. In that one subroutine would be the only spot to make the change in how it checks, if the subroutine exists. That's what I had been thinking about when I posted about the quick change and like I stated already, I haven't even looked at this code to really know how it's been implemented.

Yes, I'm primarily a VB person and not well versed on C or Net so not sure how/if subroutines would be handled in those as I'm sure this is programed in one of them. Feel free to ignore everything I say if you like since it's been a very long time since I coded stuff, was just throwing out an idea.

No problem giving ideas or you opinion
We "can't change" the code of Lapper itself so we have to do it with the code in the config-file.

Quote from Yisc[NL] :

It's not that easy (see: http://www.lfsforum.net/showthread.php?p=962254#post962254)
A couple of globalvars have to be declared and then some code to raise them when another value has been taken by someone. It's not impossible but isn't done in 5 minutes or so.

thx for reply. im have no clue about programing but im good at demanding stuff
take your time with it. if u even bother.
anyway. i like the program sofar and will use it when needed.

Quote from Easy_Mike :

thx for reply. im have no clue about programing but im good at demanding stuff
take your time with it. if u even bother.
anyway. i like the program sofar and will use it when needed.

Lol, I've got a life too
But I'm not the worst person in the world so I made some code for you. There's only one problem, the handicap-section of the current version of Lapper doesn't accept IF-statements so at the moment this code can't be used. I'll notify the developer of Lapper and hope he can/will fix this problem for the next release. A file with the needed code is included with this post. It's made for 3 players now but can easily be expanded.

Yisc, I like the script but I think you forgot some checks. Granted as you said the IF statements can't currently be used but you never do a check with the $nextweight variable. You declare it and set a value to it but that's all you do with it.

Quote from Cabby :

Yisc, I like the script but I think you forgot some checks. Granted as you said the IF statements can't currently be used but you never do a check with the $nextweight variable. You declare it and set a value to it but that's all you do with it.

What kind of check should I do with it.
I declare the variable and give it no value.
In the OnConnect event I have the following code:


$player_1 gets the start_weight and then $next_weight is set to $start_weight+5
After that the value of $next_weight is raised by 5 with every player connecting.