Hello,
Could you test the follow change:
-Change "^s" to "/".
-Change "^v" to "|".
Because the encoding code, i took from insim.net fixed the japanese character bug. But i think it also read the "actual characters" instead of the previous (caret/circumflex (^)) methode of reading the "special characters".
Could you test the follow change:
-Change "^s" to "/".
-Change "^v" to "|".
Because the encoding code, i took from insim.net fixed the japanese character bug. But i think it also read the "actual characters" instead of the previous (caret/circumflex (^)) methode of reading the "special characters".
New Beta version: 7.0.7.3 Beta #6
NOTE: Requires LFS 0.6U22 to use/test LFS Lapper beta changes properly
Download the new beta version in the first post.
NOTE: Requires LFS 0.6U22 to use/test LFS Lapper beta changes properly
Download the new beta version in the first post.
=================================================
Changed:
=================================================
1: [Discord] Changed $DiscordUName to $UName.
2: [Discord] Added $UNameID into OnReceiveDiscordMessage(): Ah i see what you mean. Same thing as for channel ID for than for users.
Lemme check if that exists in the Discord API. I probably will make a new argument for that.
Lemme check if that exists in the Discord API. I probably will make a new argument for that.
what do you mean exacly with the "Discord ID of the user"
Is that the number behind the username like: Dan190NL#2141 ?
If yes, i can take a look to get that kind of info into $DiscordUname.
That means you have to split $DiscordUname into 2 separate values.
Is that the number behind the username like: Dan190NL#2141 ?
If yes, i can take a look to get that kind of info into $DiscordUname.
That means you have to split $DiscordUname into 2 separate values.
$IndexofID = indexOf( $DiscordUname, "#");
#Includes the Hashtag char
$DiscordUser = subStr( $DiscordUname,0,$idxOfFirtsSpace-1);
$UserID = trim( subStr( $DiscordUname,$idxOfFirtsSpace-1));
New Beta version :Beta #5
=================================================
Changed:
=================================================
1: [Discord] Event OnReceiveDiscordMessage()
-Number of arguments has been changed: OnReceiveDiscordMessage($ChannelID,$ChannelName,$DiscordUname,$Text)
2: [Discord] Set multiple channels for sending texts to LFSLapper:
-open MyInc.LPR in Includes folder 'Bin/Default/Includes' .
You are allowed to set 5 channels, seperate them with a comma ",". see example below.
-$DiscordChannelReceive = "0000000000,0000000000,0000000000";
Last edited by Bass-Driver, .
New Beta version: Beta #4
NOTE: Requires LFS 0.6U22 to use/test these changes properly
Download the new beta version in the first post.
NOTE: Requires LFS 0.6U22 to use/test these changes properly
Download the new beta version in the first post.
=================================================
Changed:
=================================================
1: [TEST] Record ID of Grip/Drift Database will now be shown in DumpVar();
$list = GetListTop( getConfigVar( DefaultTopCar ), 0, 0 );
IF ( getConfigVar( DefaultTopCar ) == "XFG" )
THEN
dumpVar ( $list );
ENDIF
2: PlayerVar: "Fuel" : remaining fuel percent "%", will set when acrossing a split or completing a lap.
Last edited by Bass-Driver, .
Hello Yisc[NL] ,
Give this a try.
Attachment contains only the .exe.
Grab the LFSLapper dir from the first post if you dont have it yet.
Note: New beta version in first post.
Give this a try.
Attachment contains only the .exe.
Grab the LFSLapper dir from the first post if you dont have it yet.
Note: New beta version in first post.
Last edited by Bass-Driver, .
New Betaversion released:
Requires LFS 0.6U21 to test it properly.
Grab the new version in the first post.
Changes:
Requires LFS 0.6U21 to test it properly.
Grab the new version in the first post.
Changes:
1: New PlayerVar: "Fuel" Display the fuel amount in percent "%" After player left the pit.
IF /showfuel=yes ELSE value = -1
2: New PlayerVar: "PitFuel" Display the fuel amount in percent "%" that is being add during a pitstop.
IF /showfuel=yes ELSE value = -1
Last edited by Bass-Driver, .
Beta: LFSLapper V7.0.7.3 #6
Hello Lapperusers,
Here is a small Beta update for the upcoming version.
NOTE #1, The events in LFSLapper.lpr has been changed.
NOTE #2, LFS 0.6U22 or higher required
See the summary of changes below.
Here is a small Beta update for the upcoming version.
NOTE #1, The events in LFSLapper.lpr has been changed.
NOTE #2, LFS 0.6U22 or higher required
See the summary of changes below.
+---------------------------------------------------------------+
|Changes from 7.0.7.2 to 7.0.7.3 Beta #6
+---------------------------------------------------------------+
=================================================
New:
=================================================
1: New PlayerVar: "CarConfig"
GetCurrentPlayerVar("CarConfig");
// Configuration (Config byte)
// UF1 / LX4 / LX6 : 0 = DEFAULT / 1 = OPEN ROOF
// XRR / FZR : 0 = DEFAULT / 1 = DRIFT / RX
// FXR : 0 = DEFAULT / 1 = RX
2: New event: OnBlueFlag();
OnBlueFlag($userName,$userNameBehind,$Time)
$userName = Player were the blueflag is ment for
$userNameBehind = faster Player behind $userName
$Time = Time of flag
3: New event: OnYellowFlag();
OnYellowFlag($userName,$State,$Time)
$userName = Player that is causing the yellowflag
$State = Yellowflag 1 or 0 (on/off)
$Time = Time of flag
4: New PlayerVar: "Fuel" Display the fuel amount in percent "%" After player left the pit.
IF /showfuel=yes ELSE value = -1
5: New PlayerVar: "PitFuel" Display the fuel amount in percent "%" that is being add during a pitstop.
IF /showfuel=yes ELSE value = -1
=================================================
Changed:
=================================================
1: Maxlaptime that will be stored to the database have been increased from 30 to 90 minutes, for really long layouts.
2: [TEST] Record ID of Grip/Drift Database will now be shown in DumpVar(); for certain Car/track requests.
$list = GetListTop( getConfigVar( DefaultTopCar ), 0, 0 );
IF ( getConfigVar( DefaultTopCar ) == "XFG" )
THEN
dumpVar ( $list );
ENDIF
3: PlayerVar: "Fuel" : remaining fuel percent "%", will set when acrossing a split or completing a lap.
4: [Discord] Set multiple channels for sending texts to LFSLapper:
-open MyInc.LPR
You are allowed to set 5 channels, seperate them with a comma ",". see example below.
-$DiscordChannelReceive = "0000000000,0000000000,0000000000";
5: [Discord] Changed $DiscordUName to $UName.
6: [Discord] Added $UNameID into OnReceiveDiscordMessage():
7: [Discord] Event OnReceiveDiscordMessage()
-Number of arguments has been changed: OnReceiveDiscordMessage($ChannelID,$ChannelName,$UNameID,$UName,$Text)
=================================================
Fix:
=================================================
# Nothing yet
=================================================
Removed:
=================================================
1: Event OnPlayerFlags();
Last edited by Bass-Driver, .
Ok i fixed it.
I had 'Streamlabs OBS' running. That App causes the crash.
Sorry for creating a topic.
I had 'Streamlabs OBS' running. That App causes the crash.
Sorry for creating a topic.
LFS Crash when switching from 3D(VR) to 2D [SOLVED]
LFS version: 0.6U (no testpatch)
Faulting application name: LFS.exe, version: 0.0.0.0, time stamp: 0x5c89394b
Faulting module name: graphics-hook32.dll, version: 1.2.2.0, time stamp: 0x5f7c21b8
Exception code: 0xc0000005
Fault offset: 0x0000502b
Faulting process id: 0x54d8
Faulting application start time: 0x01d6fcc4f4c75481
Faulting application path: C:\LFS\LFS.exe
Faulting module path: C:\ProgramData\obs-studio-hook\graphics-hook32.dll
Report Id: 649a9898-0bfb-4e3f-b6a1-5e7212c51ed1
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: LFS.exe, version: 0.0.0.0, time stamp: 0x5c89394b
Faulting module name: graphics-hook32.dll, version: 1.2.2.0, time stamp: 0x5f7c21b8
Exception code: 0xc0000005
Fault offset: 0x0000502b
Faulting process id: 0x54d8
Faulting application start time: 0x01d6fcc4f4c75481
Faulting application path: C:\LFS\LFS.exe
Faulting module path: C:\ProgramData\obs-studio-hook\graphics-hook32.dll
Report Id: 649a9898-0bfb-4e3f-b6a1-5e7212c51ed1
Faulting package full name:
Faulting package-relative application ID:
Hi Yisc,
It doesnt open the GUI for some reason.
Not even working on closed track configs.
I've set the number of splits with: !cfgsplits.
It does say 'Open configuation detected' with the amount of splits, but it doesnt open the GUI.
Also tried !pbstart. But that doesnt seem to work aswell except for the message.
Do i miss a step in this process?
Pitboard V2.13.
LFSLapper: 7.0.7.2
Thank you
It doesnt open the GUI for some reason.
Not even working on closed track configs.
I've set the number of splits with: !cfgsplits.
It does say 'Open configuation detected' with the amount of splits, but it doesnt open the GUI.
Also tried !pbstart. But that doesnt seem to work aswell except for the message.
Do i miss a step in this process?
Pitboard V2.13.
LFSLapper: 7.0.7.2
Thank you
Here is a small explaination about the laptimes.
The Maximum laptime that is recorded to the database was 5 minutes, before V7.0.4.6.
I changed that to 30 minutes due to a request of Sinanju, because he made layouts that took longer than 5 minutes. I cannot find that topic anymore.
For P V L, i changed that parameter to 90 minutes, which is he testing now.
But i believe with the current database code, it cannot go higher than 60 minutes. Due to some Time format limitations.
For laptimes above 60 minutes, it requires a time format(HH:MM:SS.mm) change inside the database, as i can see at the code. I'm not gonna do that. That takes a lot of time/work. And makes all previous lappers imcompatible.
Honestly, i never drove a lap that was longer than 30 minutes. So these are rare laptimes.
Other option i told PVL is custom timing. Just set a starttime and endtime/splittime with GetlapperVar("RaceTime"), and calculate the time between them. Those times can be stored in the userstored database or inside a textfile.
EDIT: i'm talking about laptimes on layouts.
EDIT #2: 90 min laptime with the current lapper code works like a sharm.
Bye,
The Maximum laptime that is recorded to the database was 5 minutes, before V7.0.4.6.
I changed that to 30 minutes due to a request of Sinanju, because he made layouts that took longer than 5 minutes. I cannot find that topic anymore.
For P V L, i changed that parameter to 90 minutes, which is he testing now.
But i believe with the current database code, it cannot go higher than 60 minutes. Due to some Time format limitations.
For laptimes above 60 minutes, it requires a time format(HH:MM:SS.mm) change inside the database, as i can see at the code. I'm not gonna do that. That takes a lot of time/work. And makes all previous lappers imcompatible.
Honestly, i never drove a lap that was longer than 30 minutes. So these are rare laptimes.
Other option i told PVL is custom timing. Just set a starttime and endtime/splittime with GetlapperVar("RaceTime"), and calculate the time between them. Those times can be stored in the userstored database or inside a textfile.
EDIT: i'm talking about laptimes on layouts.
EDIT #2: 90 min laptime with the current lapper code works like a sharm.
Bye,
Last edited by Bass-Driver, .
Thank you,
There is a current limit of 1 receiving channel: Discordchannel > LFSLapper. Not sure why you need more.
Not the less, it requires a rewrite and will make the current Lapper event (OnReceiveDiscordMessage) and some other variables not compatible with older Lapper versions. I do not want make changes that aren't compatible that fast between Lapperversions.
I will consider this change, if there are more requests.
Don't know how many players using this Discord function right now.
I whould like to see their Lapper projects.
There is a current limit of 1 receiving channel: Discordchannel > LFSLapper. Not sure why you need more.
Not the less, it requires a rewrite and will make the current Lapper event (OnReceiveDiscordMessage) and some other variables not compatible with older Lapper versions. I do not want make changes that aren't compatible that fast between Lapperversions.
I will consider this change, if there are more requests.
Don't know how many players using this Discord function right now.
I whould like to see their Lapper projects.
no, its hardcoded.
but its text is grey and displays the current Lapper version, so not very noticable.
but its text is grey and displays the current Lapper version, so not very noticable.
Release: LFSLapper V7.0.7.2
Hello LFSLapper users,
Few days ago i've got a report about a not properly working joinrequest() function.
The direction of the car and the height wasn't the same of the current car position.
See the summary of the fixes/changes below:
Few days ago i've got a report about a not properly working joinrequest() function.
The direction of the car and the height wasn't the same of the current car position.
See the summary of the fixes/changes below:
+---------------------------------------------------------------+
|Changes from 7.0.7.1 to 7.0.7.2 | fixes/changes
+---------------------------------------------------------------+
=================================================
New:
=================================================
Nothing
=================================================
Changed:
=================================================
1: PlayerVar($userName,"Z"): Z-axis has now 2 decimals xx.yy
2: PlayerVar($userName,"Heading"); Heading values changed ((0 - 180 degrees) & (0 - -179) degrees) instead of 0-359 degrees
3: Message ingame when LFSLapper has been connected after (re)loading.
Handy when your LFSlapper instance is running like a service instead of an app for hosting services.
=================================================
Fix:
=================================================
1: JoinRequest(): Did not retreive the correct height from the player.
2: JoinRequest(): Cars heading not proper calculated.
Last edited by Bass-Driver, .
Velocity Motorsports
Its time to introduce Velocity Motorsports after driving around in LFS for almost a couple of years.
Velocity Motorsports is a casual all-around simracing team founded 2/2/2019 by Dlocky (finland69) and Dan190NL (Bass-Driver).
The Team at first was supposed to be for a few friends who wanted to drive and enjoy the game together,
but during the last year it has been growing more than any of us expected.
It have led us into starting new different servers, frequently updating our LFSLapper scripts and in general, being more active in LFS.
Instead of being the most competitive team out there, our main goal is to deliver friendly and easily accessible servers
for everyone to enjoy. We are not expecting our members to be the fastest/best drivers out there, but having friendly and mature attitude in any situations. We are active in several disciplines like Race/Drift/Cruise and you may see VM tags in any kind of Live For Speed Servers.
All our servers are powered by LFSLapper.
Velocity Motorsports is a casual all-around simracing team founded 2/2/2019 by Dlocky (finland69) and Dan190NL (Bass-Driver).
The Team at first was supposed to be for a few friends who wanted to drive and enjoy the game together,
but during the last year it has been growing more than any of us expected.
It have led us into starting new different servers, frequently updating our LFSLapper scripts and in general, being more active in LFS.
Instead of being the most competitive team out there, our main goal is to deliver friendly and easily accessible servers
for everyone to enjoy. We are not expecting our members to be the fastest/best drivers out there, but having friendly and mature attitude in any situations. We are active in several disciplines like Race/Drift/Cruise and you may see VM tags in any kind of Live For Speed Servers.
All our servers are powered by LFSLapper.
Team Managers
VM.Dlocky (finland69)
VM.Dan190NL (Bass-Driver)
Trial Drivers
None
Drivers
VM.Demon (1Demon1)
VM.Spirts (spirtins1)
VM.Percii (Percii)
VM.Gytis (duokzaiba)
VM.Khaos (Khaos453)
VM.CarlzW ([CYP]Karlikcz)
VM.Ricky (RichRicky)
VM.Holm (rb26dettlove)
Our Servers:
VM.TimeAttack Join Host
VM.Racing S2 Join Host
VM.Racing GTI Join Host
VM.Drifting Join Host
Contact/Info:
Website: https://velocitymsports.com/
Discord: https://discord.gg/7QhkfBJ
Last edited by Bass-Driver, .
Thank you
Release: LFSLapper V7.0.7.1 (New Discord Feature)
Hello everyone.
Here a small LFSLapper update with a new Discord feature.
Here a small LFSLapper update with a new Discord feature.
+---------------------------------------------------------------+
|Changes from 7.0.7.0 to 7.0.7.1 | Discord feature Update/Fix
+---------------------------------------------------------------+
=================================================
New:
=================================================
1: New function: SendDiscordEmbed(); #Create and send Discord Embed
#DiscordChannel to receive this embed.
$Channel = "";
#Set Title/Description and color of the discord embed
$Title = "Embed Title";
$Desc = "Embed Description";
#Prefix must contain '0x' Followed by 6 chars 0-9 and A-F
$Color = "0xFF0000"; #RED
#Field Values
## Use %nf% to create a new field. (Add %nf% to $FieldValue and $FieldInline aswell) ##
$FieldTitle = "Field_01 Title"; #Title of the Field
$FieldValue = "Field_01 Value"; #Value of the Field
$FieldInline = "True"; #Use 'True' or 'False' to set Inline Fields.
#Use %nf% to add a footer image URL !! Not an local(pc) image.
$Footer = "LFSLapper Footer: ".GetLapperVar("ShortTime");
#Small Image URL on the right side of the Embed box.
$ThumbnailUrl = "";
#The Entire EmbedBox will fit to the same size as the ImageUrl.
$ImageUrl = "";
#Function to send Discord Embed
SendDiscordEmbed($Channel,$Title,$Desc,$Color,$FieldTitle,$FieldValue,$FieldInline,$Footer,$ThumbnailUrl,$ImageUrl);
=================================================
Fix:
=================================================
1: Couldn't use '\n' in discord messages
Last edited by Bass-Driver, .
Thanks for your request,
Its a nice addition to the current Lapper discord system.
I think it could use the same system as what Insim is using:
Ignore messages/command with a '!' prefix.
In Discord it should delete your message.
This could take a while to find out how it exacly works, and how code it properly, if possible. I might look into that in the future, but its not a must have for now.
Its a nice addition to the current Lapper discord system.
I think it could use the same system as what Insim is using:
Ignore messages/command with a '!' prefix.
In Discord it should delete your message.
This could take a while to find out how it exacly works, and how code it properly, if possible. I might look into that in the future, but its not a must have for now.
Thanks for testing.
its a mistake on my end.
I haven't explained it in the changelog.
its a mistake on my end.
I haven't explained it in the changelog.
Thanks for the report, will look into it.
I'm also not a programmer. Just doing this for fun. Google is your friend
Edit: Could you create a message within the sub
privmsg($DetectedPlayer);
I think with multiple players within the field of view it should look like this
i haven't tested this in a while (since Sun 3 Mar 2019), and i didn't get any feedback from it, so before changing any code i want to know what happends.
I'm also not a programmer. Just doing this for fun. Google is your friend
Edit: Could you create a message within the sub
PlayerDetection()privmsg($DetectedPlayer);
I think with multiple players within the field of view it should look like this
player1+player2i haven't tested this in a while (since Sun 3 Mar 2019), and i didn't get any feedback from it, so before changing any code i want to know what happends.
Last edited by Bass-Driver, .
New betaversion:
This contains some fixes when some variables are empty.
Download the LFSLapper directory from the first post and grab the .exe from this post.
This contains some fixes when some variables are empty.
Download the LFSLapper directory from the first post and grab the .exe from this post.
Thank you,
Please let me know if everything works, so i can build the official version of LFSLapper.
Please let me know if everything works, so i can build the official version of LFSLapper.
Beta: LFSLapper V7.0.7.1 (New Discord Feature)
Hello Lapper users.
I've been working on a new discord feature for LFSLapper.
Feature is been called Discord Embed. You can create multiple messages within a single messagebox.
EDIT: New betaversion: (Only.exe)
This contains some fixes when some variables are empty.
Download the LFSLapper directory from the first post and grab the .exe from this post.
Check for the variables and function below:
Code Example of the Attached Image.
I've been working on a new discord feature for LFSLapper.
Feature is been called Discord Embed. You can create multiple messages within a single messagebox.
EDIT: New betaversion: (Only.exe)
This contains some fixes when some variables are empty.
Download the LFSLapper directory from the first post and grab the .exe from this post.
+---------------------------------------------------------------+
|Changes from 7.0.7.0 to 7.0.7.1 Beta #1 |
+---------------------------------------------------------------+
- A Discordbot must be created to communicate between LFSLapper and Discord.
- In 'bin/default/includes/myInc.LPR' you can enter the 'DiscordToken' and the 'Discordchannel' to receive the messages from.
- Link to create a discordbot: https://github.com/reactiflux/discord-irc/wiki/Creating-a-discord-bot-&-getting-a-token
- Set DeveloperMode in your discordsettings to "ON' to copy the channel ID ( rightclick on the channel)
=================================================
New:
=================================================
1: New function: SendDiscordEmbed(); #Create and send Discord Embed
=================================================
Fix:
=================================================
1: Couldn't use '\n' in discord messages
Check for the variables and function below:
<?php
#DiscordChannel to receive this embed.
$Channel = "";
#Set Title/Description and color of the discord embed
$Title = "Embed Title";
$Desc = "Embed Description";
#Prefix must contain '0x' Followed by 6 chars 0-9 and A-F
$Color = "0xFF0000"; #RED
#Field Values
## Use %nf% to create a new field. (Add %nf% to $FieldValue and $FieldInline aswell) ##
$FieldTitle = "Field_01 Title"; #Title of the Field
$FieldValue = "Field_01 Value"; #Value of the Field
$FieldInline = "True"; #Use 'True' or 'False' to set Inline Fields.
#Use %nf% to add a footer image URL !! Not an local(pc) image.
$Footer = "LFSLapper Footer: ".GetLapperVar("ShortTime");
#Small Image URL on the right side of the Embed box.
$ThumbnailUrl = "";
#The Entire EmbedBox will fit to the same size as the ImageUrl.
$ImageUrl = "";
#Function to send Discord Embed
SendDiscordEmbed($Channel,$Title,$Desc,$Color,$FieldTitle,$FieldValue,$FieldInline,$Footer,$ThumbnailUrl,$ImageUrl);
?>
<?php
CASE "!embed":
#DiscordChannel to receive this embed.
$Channel = "";
#Set Title/Description and color of the discord embed
$Title = "LFSLapper Embed Title";
$Desc = "Embed Description";
#Prefix must contain '0x' Followed by 6 chars 0-9 and A-F
$Color = "0xFF0000"; #RED
#Field Values
## Use %nf% to create a new field. (Add %nf% to $FieldValue and $FieldInline aswell) ##
$FieldTitle =
"Field_01 Title"
."%nf%Field_02 Title"
."%nf%Field_03 Title"
."%nf%Field_04 Title";
$FieldValue =
"*Field_01 Value*\n*Field_01 Value*"
."%nf%Field_02 Value"
."%nf%```New BlockLine_01\nNew BlockLine_02\nNew BlockLine_03\nNew BlockLine_04\nNew BlockLine_05\nNew BlockLine_06\nNew BlockLine_07```"
."%nf%**Field_04 Value**\n**Field_04 Value**\n**Field_04 Value**\n**Field_04 Value**";
$FieldInline = "True%nf%True%nf%False%nf%False";
#Use %nf% to add a footer image URL !! Not an local(pc) image.
$Footer = "LFSLapper Footer: ".GetLapperVar("ShortTime")." %nf% https://velocitymsports.com/home/vmlogo.png ";
#Small Image URL on the right side of the Embed box.
$ThumbnailUrl = "https://velocitymsports.com/home/vmlogo.png";
#The Entire EmbedBox will fit to the same size as the ImageUrl.
$ImageUrl = "";
#Function to send Discord Embed
SendDiscordEmbed($Channel,$Title,$Desc,$Color,$FieldTitle,$FieldValue,$FieldInline,$Footer,$ThumbnailUrl,$ImageUrl);
BREAK;
?>
Last edited by Bass-Driver, .
FGED GREDG RDFGDR GSFDG