PART 3: WHY SHOULD I USE AUTOSAVE REPLAY SETTING, IF POSSIBLE?
Other parts:
1) Introduction
2) Different replay saving options
3) Why you should use autosave replay setting (You are here)
I will say this immediately: it makes any experience in LFS far less stressful!
I honestly don't care how familiar you are with your setup and how you will always remember to manually save your replays. Have you ever thought about this:
- You accidentally shut down your game, or go to entry screen or leave the server
- Your computer downloads automatic updates and drivers all the time without telling you. It may decide all of sudden to restart your computer by on its own to install them, leaving you no choice!
- You touch a very loose power cord of your computer and it turns your power off
- You lose elecrticity in your house or in your area
- You lose internet connection all of sudden
- You get suddenly kicked or banned, due to any (or lack of) reason!
- Your hard drive suddenly doesn't function in a way it should be
- Your antivirus software gets overzealous of LFS and shuts it down, thinking it's dangerous software. For this, you should also read my another LPT of LFS which is: Avoid posting issues obviously caused by antivirus software
I could go on and on of hundreds of realistic scenarios that can screw your gameplay in LFS experience. There is no other feeling more defeating, than you finally getting a WR, and you're so excited to share it. Only to see you forgot to save it.
Being open about is I can, when Rockingham was introduced, I managed to get few WRs on obscure track/car combinations (because there really weren't many hotlaps). Those WRs only lasted for few days before I lost them. Just before that, I've had a time where I did WR of a track/car combination after doing so many laps on that, only to not have the replay being saved when I did that (I only had manual save). That did make me not wanting to do any hotlaps for a significant period of time. And when I finally tried again, I did notice the WR was significantly improved, which would have resulted me doing at least several more days of having an attempt that was even close to that.
Making a replays to autosave, takes literally 10 seconds of your time, when you go the correct setting in the game options. It is one time 10 second minor inconvience to save you hours of headaches later, especially if you are doing a league or event that is only held once and will not be done again!
When I started organizing races in 2014, I didn't have full access to my server until late 2017. Very first thing I did, when I got access, was to enable autosave there. Why? Because I personally did have issues myself, where I couldn't get recording of the whole session. That's why I missed some of the important qualifying/race replays and I had to ask from other users, could they have them. I almost got all of them, but man it was a pain to obtain them.
Heck, does anyone remember the good old SpdoRacing Event Database? JoshDiFabio did create that and allowed users to have their own leagues there. But Josh did get quite annoyed by the fact that few of these users didn't save all their replays which could result that league getting removed there. Josh had to add this information for users (you have to log in to view it as it is in Inactive Leagues section which is not visible unless you've logged in): https://www.lfs.net/forum/post/1378597#post1378597
And finally, you may sometimes want to watch take return to trip to the memory lane and watch some old replays. You may find something very interesting (or controversial) later on!
Finally: for those wondering, both Belarussian and Estonian translations don't have the "- not recommended" part of that text. In those languages, it will just say autosave. Now it is possible assigned translators couldn't get that "- not recommended" part in their langugae there, if there isn't enough room, as every translation string has a maximum length. But it is also possible that they decided not to include that on purpose.
I've been thinking Scawen, when the new version gets released, would you consider removing the "- not recommended" part of the autosave setting from translations? People nowadays have much better computers than 20 years ago
Other parts:
1) Introduction
2) Different replay saving options
3) Why you should use autosave replay setting (You are here)
I will say this immediately: it makes any experience in LFS far less stressful!
I honestly don't care how familiar you are with your setup and how you will always remember to manually save your replays. Have you ever thought about this:
- You accidentally shut down your game, or go to entry screen or leave the server
- Your computer downloads automatic updates and drivers all the time without telling you. It may decide all of sudden to restart your computer by on its own to install them, leaving you no choice!
- You touch a very loose power cord of your computer and it turns your power off
- You lose elecrticity in your house or in your area
- You lose internet connection all of sudden
- You get suddenly kicked or banned, due to any (or lack of) reason!
- Your hard drive suddenly doesn't function in a way it should be
- Your antivirus software gets overzealous of LFS and shuts it down, thinking it's dangerous software. For this, you should also read my another LPT of LFS which is: Avoid posting issues obviously caused by antivirus software
I could go on and on of hundreds of realistic scenarios that can screw your gameplay in LFS experience. There is no other feeling more defeating, than you finally getting a WR, and you're so excited to share it. Only to see you forgot to save it.
Being open about is I can, when Rockingham was introduced, I managed to get few WRs on obscure track/car combinations (because there really weren't many hotlaps). Those WRs only lasted for few days before I lost them. Just before that, I've had a time where I did WR of a track/car combination after doing so many laps on that, only to not have the replay being saved when I did that (I only had manual save). That did make me not wanting to do any hotlaps for a significant period of time. And when I finally tried again, I did notice the WR was significantly improved, which would have resulted me doing at least several more days of having an attempt that was even close to that.
Making a replays to autosave, takes literally 10 seconds of your time, when you go the correct setting in the game options. It is one time 10 second minor inconvience to save you hours of headaches later, especially if you are doing a league or event that is only held once and will not be done again!
When I started organizing races in 2014, I didn't have full access to my server until late 2017. Very first thing I did, when I got access, was to enable autosave there. Why? Because I personally did have issues myself, where I couldn't get recording of the whole session. That's why I missed some of the important qualifying/race replays and I had to ask from other users, could they have them. I almost got all of them, but man it was a pain to obtain them.
Heck, does anyone remember the good old SpdoRacing Event Database? JoshDiFabio did create that and allowed users to have their own leagues there. But Josh did get quite annoyed by the fact that few of these users didn't save all their replays which could result that league getting removed there. Josh had to add this information for users (you have to log in to view it as it is in Inactive Leagues section which is not visible unless you've logged in): https://www.lfs.net/forum/post/1378597#post1378597
And finally, you may sometimes want to watch take return to trip to the memory lane and watch some old replays. You may find something very interesting (or controversial) later on!
Finally: for those wondering, both Belarussian and Estonian translations don't have the "- not recommended" part of that text. In those languages, it will just say autosave. Now it is possible assigned translators couldn't get that "- not recommended" part in their langugae there, if there isn't enough room, as every translation string has a maximum length. But it is also possible that they decided not to include that on purpose.
I've been thinking Scawen, when the new version gets released, would you consider removing the "- not recommended" part of the autosave setting from translations? People nowadays have much better computers than 20 years ago
Last edited by tankslacno, .
PART 2: DIFFERENT REPLAY SAVING OPTIONS
Other parts:
1) Introduction
2) Different replay saving options (You are here)
3) Why you should use autosave replay setting
[not enabled - not stored]
What does this do? This option makes sure that you cannot save a replay at all. You will be only greeted with a message that replay is not recorded if you try to save it. Only way you can get that replay is asking the host or another user who were on that host at the time and ask can they give you a replay. If they can't, tough luck.
There are only three possible situations where you should ever choose this option:
1) You are constantly facing this issue: "MP Replay: stash full replay" and it kicks you out of server, freezes your LFS etc.
2) Your 2 (or 1 in case of Single Player) button is broken and gets pressed by even the lightest touch
3) You are owner of a LFS.net host and you exclusively race there. In that case, you should make sure that replay saving is enabled for the host.
You can do that from here: Hosting --> Your hosts --> Click host name --> Replays --> Enable replay saving for this host? --> Pick option Yes and click Submit. Doing that will make sure the replays are saved in LFS.net hosting area. Keep in mind that those replays are only stored for 4 months. After that, they're deleted automatically, so make sure to download the necessary ones before that.
Other than these three instances, you should never pick this option, because there really is never a reason why you should pick this over the other two.
[enabled - manual save]
This option does allow you to save a replay once. You can only save the replay on a moment that is beginning of a session (or the moment you joined the server) and beginning of the following session. To save it, you have to do the following:
- Press Esc and click the Replay button (only works in Single Player)
- Press 1 (only works in Single Player)
- Press 2 and provide a name for the replay (works in both Single Player and Multiplayer)
In the first two options, it will save the replay using automatically generated name. Remember, that in case of Single Player, choosing any of the options ends that session instantly. So don't do it too early! In multiplayer, session does continue normally, but you won't be able to save the remainder of the session. You have to wait until next session starts or leave the server and rejoin.
There is also alternative way: in case you leave the server before you saved that replay, all is not lost. You can still find that replay by going to this folder: [LFS-instace]/data. From there:
- If you want to save your SPR-replay, go to spr-folder and you find a file named as temp_spr.
- If you want to save your MPR-replay, go to mpr-folder and you find a file named as temp_mpr.
In both cases, to prevent it not being lost, rename that file to something else. If you join a new server, or start a new session without doing that, this temporary file will be overwritten by a new temp_spr/mpr file. To prevent any risks, you should probably not even close LFS before you've renamed that file.
[auto save - not recommended]
This option saves every time automatically. Replays are saved when a new session starts (or ends) or when you leave the server. Replays are named this: TrackAbbreviation_SessionName_SessionLength_NumberOfRacers_NumberOfFinishers[_x]
The _x means that if there is already a replay on that track, on that session, with that session length and number of races and finishers, it will be added to end of it so it will not overwrite the existing replay. Please note that Practice sessions don't follow this format entirely, because there are no laps.
However, you can still use manual save by typing 2 and naming it. Keep in mind that the same rule applies here, you can only save once, so the rest of the session is not recorded.
And one thing to keep in mind, that autosaving does NOT save every replay. Yes, it does save every multiplayer replay, but in case of single player, it doesn't save it if the replay saving is being interrupted. If you change a wind, race length, specatate, join, add autocross objects etc., you will get a red message that Replay is not being recorded.
Now, the way this setting is typed is probably a big reason why those aforementioned issues happened. Because that setting says "- not recommended", people will think it's a bad option and should not be used and therefore prefer the manual saving instead. There are two reasons (primary and secondary), why I think devs did want to add that not recommended part there.
1) Because almost every replay is saved, you can and will have replays in your LFS-instance that you don't need. This will naturally fill up your system storage over time. Now, if you have very little storage left, then fine, you should keep the manual setting. But other than that, you should always stick to the autosave.
2) And, because every replay is saved with that automatically generated name (unless you manually save it), it can become hard for user to find the replay they need. Of course you can rename it either in-game, or inside the [LFS-instance]/data/spr (or mpr) folder.
In case you're wondering, at the time I'm posting this on my little over 2 year old laptop, I have over 800 mpr files, and they take 13,2 GB of storage. Good example is that I have 5 hour Endurance race, which took almost 200 MB. One replay, yes.
Now, if you are worried that your computer gets filled over time by with these replays, remember you can always do a backup of your mpr (and spr) folders (or heck, your LFS instance) on an external hard drive, USB stick, online cloud etc. and then remove the files inside those folders from your LFS instance. Just make sure to put the backup to somewhere else other than in your computer, because if you put them into same hard drive in your computer, well, if you lose all your data of that hard drive, you will also lose your backup!
I highly recommend you to use the autosave setting, unless you have a really valid reason not to.
Valid reasons include:
- You are only racing on a server you host, you have enabled replay saving on that LFS.net host and you have access to those replays
- You have very little space left on your computer
- You somehow face constant issues when replay saving (manual or automatic) is enabled. At this point, you should probably reinstall LFS or create a thread at the Technical Assistance section.
Why autosaving should be enabled? Read part 3 (next post) to see why.
Other parts:
1) Introduction
2) Different replay saving options (You are here)
3) Why you should use autosave replay setting
[not enabled - not stored]
What does this do? This option makes sure that you cannot save a replay at all. You will be only greeted with a message that replay is not recorded if you try to save it. Only way you can get that replay is asking the host or another user who were on that host at the time and ask can they give you a replay. If they can't, tough luck.
There are only three possible situations where you should ever choose this option:
1) You are constantly facing this issue: "MP Replay: stash full replay" and it kicks you out of server, freezes your LFS etc.
2) Your 2 (or 1 in case of Single Player) button is broken and gets pressed by even the lightest touch
3) You are owner of a LFS.net host and you exclusively race there. In that case, you should make sure that replay saving is enabled for the host.
You can do that from here: Hosting --> Your hosts --> Click host name --> Replays --> Enable replay saving for this host? --> Pick option Yes and click Submit. Doing that will make sure the replays are saved in LFS.net hosting area. Keep in mind that those replays are only stored for 4 months. After that, they're deleted automatically, so make sure to download the necessary ones before that.
Other than these three instances, you should never pick this option, because there really is never a reason why you should pick this over the other two.
[enabled - manual save]
This option does allow you to save a replay once. You can only save the replay on a moment that is beginning of a session (or the moment you joined the server) and beginning of the following session. To save it, you have to do the following:
- Press Esc and click the Replay button (only works in Single Player)
- Press 1 (only works in Single Player)
- Press 2 and provide a name for the replay (works in both Single Player and Multiplayer)
In the first two options, it will save the replay using automatically generated name. Remember, that in case of Single Player, choosing any of the options ends that session instantly. So don't do it too early! In multiplayer, session does continue normally, but you won't be able to save the remainder of the session. You have to wait until next session starts or leave the server and rejoin.
There is also alternative way: in case you leave the server before you saved that replay, all is not lost. You can still find that replay by going to this folder: [LFS-instace]/data. From there:
- If you want to save your SPR-replay, go to spr-folder and you find a file named as temp_spr.
- If you want to save your MPR-replay, go to mpr-folder and you find a file named as temp_mpr.
In both cases, to prevent it not being lost, rename that file to something else. If you join a new server, or start a new session without doing that, this temporary file will be overwritten by a new temp_spr/mpr file. To prevent any risks, you should probably not even close LFS before you've renamed that file.
[auto save - not recommended]
This option saves every time automatically. Replays are saved when a new session starts (or ends) or when you leave the server. Replays are named this: TrackAbbreviation_SessionName_SessionLength_NumberOfRacers_NumberOfFinishers[_x]
The _x means that if there is already a replay on that track, on that session, with that session length and number of races and finishers, it will be added to end of it so it will not overwrite the existing replay. Please note that Practice sessions don't follow this format entirely, because there are no laps.
However, you can still use manual save by typing 2 and naming it. Keep in mind that the same rule applies here, you can only save once, so the rest of the session is not recorded.
And one thing to keep in mind, that autosaving does NOT save every replay. Yes, it does save every multiplayer replay, but in case of single player, it doesn't save it if the replay saving is being interrupted. If you change a wind, race length, specatate, join, add autocross objects etc., you will get a red message that Replay is not being recorded.
Now, the way this setting is typed is probably a big reason why those aforementioned issues happened. Because that setting says "- not recommended", people will think it's a bad option and should not be used and therefore prefer the manual saving instead. There are two reasons (primary and secondary), why I think devs did want to add that not recommended part there.
1) Because almost every replay is saved, you can and will have replays in your LFS-instance that you don't need. This will naturally fill up your system storage over time. Now, if you have very little storage left, then fine, you should keep the manual setting. But other than that, you should always stick to the autosave.
2) And, because every replay is saved with that automatically generated name (unless you manually save it), it can become hard for user to find the replay they need. Of course you can rename it either in-game, or inside the [LFS-instance]/data/spr (or mpr) folder.
In case you're wondering, at the time I'm posting this on my little over 2 year old laptop, I have over 800 mpr files, and they take 13,2 GB of storage. Good example is that I have 5 hour Endurance race, which took almost 200 MB. One replay, yes.
Now, if you are worried that your computer gets filled over time by with these replays, remember you can always do a backup of your mpr (and spr) folders (or heck, your LFS instance) on an external hard drive, USB stick, online cloud etc. and then remove the files inside those folders from your LFS instance. Just make sure to put the backup to somewhere else other than in your computer, because if you put them into same hard drive in your computer, well, if you lose all your data of that hard drive, you will also lose your backup!
I highly recommend you to use the autosave setting, unless you have a really valid reason not to.
Valid reasons include:
- You are only racing on a server you host, you have enabled replay saving on that LFS.net host and you have access to those replays
- You have very little space left on your computer
- You somehow face constant issues when replay saving (manual or automatic) is enabled. At this point, you should probably reinstall LFS or create a thread at the Technical Assistance section.
Why autosaving should be enabled? Read part 3 (next post) to see why.
Last edited by tankslacno, .
Please use autosave replay setting, if possible
TL;DR: Enabling autosave replays takes 10 seconds of your time and it makes your life so much easier and less stressful in LFS!
PART 1: INTRODUCTION
In this thread, I'm explaining why you should definitely enable replay autosaving, if it's possible for you. To improve readability, I've divided this text into three parts. You can jump to the next part by clicking the link in it.
Other parts:
1) Introduction (you are here)
2) Different replay saving options
3) Why you should use autosave replay setting
Hi! This is more like a LPT (Life Pro Tip) for you LFS users.
I've noticed recently there have been couple threads here, where a user is accusing another user for bad behavior. But they have a problem, they have nothing to backup their accusations, and that is because they forgot to save their replay.
Here are couple threads as examples, both were created just a few days ago:
- https://www.lfs.net/forum/thread/112911
- https://www.lfs.net/forum/thread/112923
So, how do I make sure I get that replay?
When you go to the Options --> Game, you see there are two settings:
- Single player replay save. This applies to SPR folder/files
- Multiplayer replay save. This applies to MPR folder/files
Both of them have 3 different options to choose from. Read part 2 to see what these different options mean.
PART 1: INTRODUCTION
In this thread, I'm explaining why you should definitely enable replay autosaving, if it's possible for you. To improve readability, I've divided this text into three parts. You can jump to the next part by clicking the link in it.
Other parts:
1) Introduction (you are here)
2) Different replay saving options
3) Why you should use autosave replay setting
Hi! This is more like a LPT (Life Pro Tip) for you LFS users.
I've noticed recently there have been couple threads here, where a user is accusing another user for bad behavior. But they have a problem, they have nothing to backup their accusations, and that is because they forgot to save their replay.
Here are couple threads as examples, both were created just a few days ago:
- https://www.lfs.net/forum/thread/112911
- https://www.lfs.net/forum/thread/112923
So, how do I make sure I get that replay?
When you go to the Options --> Game, you see there are two settings:
- Single player replay save. This applies to SPR folder/files
- Multiplayer replay save. This applies to MPR folder/files
Both of them have 3 different options to choose from. Read part 2 to see what these different options mean.
Last edited by tankslacno, .
Outdated information and four typos in Vehicle Mod Submission Guidelines
Hi!
You may notice the guidelines of vehicle mod submissions here: https://www.lfs.net/files/vehmods/regulations
There is a bit of outdated information:
Firstly, there is a typo: "access leves" when it should be "access levels". And secondly, the custom and private have been merged. Private option doesn't exist anymore
There are also three other typos, which I've underscored in the quotes:
- Second paragraph of point 5.
withold = should be withhold
- Point 5.1.
permision = should be permission
- Paragraph after point 6.3.
submissons = should be submissions
You may notice the guidelines of vehicle mod submissions here: https://www.lfs.net/files/vehmods/regulations
There is a bit of outdated information:
Firstly, there is a typo: "access leves" when it should be "access levels". And secondly, the custom and private have been merged. Private option doesn't exist anymore
There are also three other typos, which I've underscored in the quotes:
- Second paragraph of point 5.
withold = should be withhold
- Point 5.1.
permision = should be permission
- Paragraph after point 6.3.
submissons = should be submissions
Here's MPR, yeah it's definitely that user.
EDIT: And yes, I do confirm it's indeed the "CGames Drift" host. Just remember they will log your IP address if you join there
EDIT: And yes, I do confirm it's indeed the "CGames Drift" host. Just remember they will log your IP address if you join there
Last edited by tankslacno, .
Do you know the admin of that server which you can contact? They may have those replays stored and they can also ban that user.
Or, if it's not possible, you can ask another user who were online on the server at that time, and ask, did they save a replay of it and could they send it to you?
For the future:
I recommend that in-game, you go to the Options --> Game --> Multiplayer replay save. Set it to [auto save - not recommended]. That way, it does save every session for you, so you don't accidentally forget to save replays.
Of course, it can and most likely will save some replays you don't need, but if you are worried about does it take too much space in your computer, you can always remove them from the [LFS-instance]/data/mpr folder
Or, if it's not possible, you can ask another user who were online on the server at that time, and ask, did they save a replay of it and could they send it to you?
For the future:
I recommend that in-game, you go to the Options --> Game --> Multiplayer replay save. Set it to [auto save - not recommended]. That way, it does save every session for you, so you don't accidentally forget to save replays.
Of course, it can and most likely will save some replays you don't need, but if you are worried about does it take too much space in your computer, you can always remove them from the [LFS-instance]/data/mpr folder
Last edited by tankslacno, .
1) That is not a screenshot. You can watch a replay and when they see a message that they have connected/disconnected you can take a screenshot of the in-game moment that shows message history with that message included. If you can't find it, but you are sure it is in that replay, you can just attach that mpr to your mesasge.
2) You can edit your messages, you don't need to post several messages in a row
Could it be possible for you to attach the .mpr replays instead of posting three links? It is safer to just post them as attachment here (at least I had no idea what site is "ibb.co" before). Or alternatively, post a screenshot where we can see a message of that user connecting or disconnecting, or getting kicked out or banned. With that message, we can see their username.
I don't want to sound mean, but your message "His user is pxldaddy" doesn't actually prove that it is indeed that "asd" user.
I don't want to sound mean, but your message "His user is pxldaddy" doesn't actually prove that it is indeed that "asd" user.
Last edited by tankslacno, .
The one thing I'm curious: does the 7G2 make any difference at all when using VPN (or immediately after disconnecting from VPN)? I'm just thinking is it necessary for Scawen to have that user agent option in-game anymore, or should that be removed, if it doesn't make any difference?
About my question:
I just noticed that Scawen actually did already have an answer to it that one can find from the another thread (the Norwegian translation). Here's that answer from Scawen:
So, no big changes regarding of translation lines in the new version
I just noticed that Scawen actually did already have an answer to it that one can find from the another thread (the Norwegian translation). Here's that answer from Scawen:
So, no big changes regarding of translation lines in the new version
Worth noting, if you want to play LFS again in the future: I recommend that in-game, you go to the Options --> Game --> Multiplayer replay save. Set it to [auto save - not recommended]. That way, it does save every session for you, so you don't need to ask here.
Of course, it can and most likely will save some replays you don't need, but if you are worried about does it take too much space in your computer, you can always remove them from the [LFS-instance]/data/mpr folder. In case you're wondering how much space do they take, my laptop which is little over 2 years old has 817 mpr-files at the moment I'n writing this post. Size of that folder is 13,2 Gb
Of course, it can and most likely will save some replays you don't need, but if you are worried about does it take too much space in your computer, you can always remove them from the [LFS-instance]/data/mpr folder. In case you're wondering how much space do they take, my laptop which is little over 2 years old has 817 mpr-files at the moment I'n writing this post. Size of that folder is 13,2 Gb
Scawen or Geraldine can correct me if I'm wrong, but I've understood they can only change your email if all these three conditions are met:
1) You have forgotten your password,
2) You don't have access to an email that is currently linked and
3) You are able to provide proof of purchase for the license you bought. Something like a scan of a credit card statement with an entry for "WWW.LIVEFORSPEED.NET" or a PayPal transaction ID will do.
Source: https://www.lfs.net/faq/54
1) You have forgotten your password,
2) You don't have access to an email that is currently linked and
3) You are able to provide proof of purchase for the license you bought. Something like a scan of a credit card statement with an entry for "WWW.LIVEFORSPEED.NET" or a PayPal transaction ID will do.
Source: https://www.lfs.net/faq/54
Scawen will not revert back to the previous model. Doing so would not only be waste of time Scawen could spend on developing LFS, but would also result every account, including yours, having much higher risk of getting stolen.
And I will ask you a question. Honestly, would you rather:
1) Wait one week (or soon just 6 days) and after that, get to play S3 for your life or
2) Take that big risk that could occur anyday of rest of your life. Risk where your account and your license (which, according to yourself, spend your last money on it) would get stolen, meaning in worst case scenario, that would absolutely be possible here, you would need to start from scratch, create another account and buy another license?
And, it's just one week, it will go faster than you think. And I also have an answer for your question "What's worse than a whole week?". Answer is: two weeks.
From the link Flame posted, you can find the reason for all of these security measures. Here's the quote from Scawen:
Go to this address: https://www.lfs.net/account/details
You can set your new email by there. Now, because you cannot access your old email, you have to wait for 7 days before you can set your new email. After that, you can set a unlock code also from that page, which will be sent to your new email
Why you have to wait 7 days? It's for security reasons, without that, it would be much easier to change emails and passwords instantly, which would allow another person to steal your account, and your license.
You can set your new email by there. Now, because you cannot access your old email, you have to wait for 7 days before you can set your new email. After that, you can set a unlock code also from that page, which will be sent to your new email
Why you have to wait 7 days? It's for security reasons, without that, it would be much easier to change emails and passwords instantly, which would allow another person to steal your account, and your license.
Unfortunately you can't access the layout editor in demo.
That's also got into my mind: demo users could have access to that drag strip, but options regarding that would be significantly limited compared to licensed users (it would be limited to only up to 2 players as well as always fixed start positions and fixed length)
If demo users would like variety, they would need to have multiple track configutations, which would have different length, like 1/8 mile, 1/4 mile and 1/2 mile configurations
That's also got into my mind: demo users could have access to that drag strip, but options regarding that would be significantly limited compared to licensed users (it would be limited to only up to 2 players as well as always fixed start positions and fixed length)
If demo users would like variety, they would need to have multiple track configutations, which would have different length, like 1/8 mile, 1/4 mile and 1/2 mile configurations
Yeah, that is one added plus. The 1km is the absolute maximum length for this track. While 1/4 mile (402m) is the most commonly used length on drag strips, it's not the only length available. Drag races are also on held 1/2 mile (804m) tracks (Airship Attack does these for example), as well as 1000-foot (304.8m) and 1/8 mile (201m) long tracks.
So with this Blackwood: devs could add a different drag track compared to AU3 and AU4, as they don't have to use a 1/4 mile length.
Remember that devs are updating all the tracks at the moment, so now it would be good time for devs to add more track configurations. It would be more waste of time to do this when Scawen is making an update containing those new tire physics, because adding new track configurations is not really related to updating tire physics.
For Blackwood, you have to wonder, can you add any more track configurations? Well, drag strip would be one candinate for that and it makes more sense because consider this:
1) The track already exists
2) Devs can pretty much just use AU3 as a preset when adding it
3) It is significantly different type of track compared to the other track configurations in Blackwood
It would be much less waste of time for devs than people may think. Devs don't need to start from scratch, because they already know how the game works with dragstrips.
When Blackwood got updated in 2017, even demo users got a new track configuration, but licensed racers got much more (Historic Reverse and that surrounding area). Did the fact that even demo users got a new track configuration cause any harm? No.
Because of the fact that licensed users will get so much content in the updated versions (remember that South City and Kyoto Ring will be massively revamped), I'm perfectly fine if demo users get one new track configuration for the updated Blackwood at the same time. This is exactly what happened in 2017 and no one got angry back then. And this time, it would be a track configuration, that not only is much different to other track configurations, but already exists in the game.
One important point about this suggestion to consider is that this would likely be simple for devs to add, but would bring something new for users as well and allow even more possibilites (like top speed testing)
It is still possible to use LAN. If you use version 0.6V3 or earlier, you can use that to host and play LAN games, because you can use your LFS account on two different computers. Unfortunately, that version doesn't have mods.
Otherwise, you need to get another account and another license as versions 0.6W and newer don't support that anymore.
Otherwise, you need to get another account and another license as versions 0.6W and newer don't support that anymore.
I highly recommend ProtonVPN. However, I'm not exactly sure, is the Netherlands available only in the Plus version (thankfully if you buy it during Black Friday, it should cost less than 3 euros per month), or is it also available in the Free version. I know that the available servers/countries are significantly limited in the Free
And for anyone wondering, is it safe? Yes it absolutely is! Consider this:
1) It has a strict no-log policy and has obeyed it for several years
2) It's not owned by any huge mega corporation
3) It's located in Switzerland, and it has to obey even stricter regulations than EU-countries, who are under GDPR
4) It's open source software!
Translated the quote by DeepL:
I haven't done really much about it, because I want to know first, is it even possible to do it in the first place.
About the amount of users LFS has:
- 145214 users that have set their country as Finland
- 17882 users that have set their country as Sweden
- 12397 users that have set their country as Norway
And I would say almost all of these users are indeed from they country they told they're from. There are about 17000-18000 speakers in Norway, 5000-6000 in Sweden and 2000 in Finland. So, one could assume as since there are more Northern Sámi speakers in Norway than registered LFS users from that country, there is a good chance of a Northern Sámi speaking people playing LFS.
About that does it make sense: Scawen himself has said that he is always open for LFS being as accessible as possible. https://www.lfs.net/forum/post/1936125#post1936125 - so it is something that would be nice to have, but is not essential for the game.
One reason why some of those popular languages with millions of speakers, like Hindi and Arabic don't have translation in LFS is simply because:
- With Hindi, it does have special characters that are not currently supported in LFS
- With Arabic, it does have special characters and the text is right-to-left - those are not supported in LFS
Scawen has told that he would be interested to see how he can add the support to those languages, after the graphical updates and tire physics have been finished.
With Northern Sámi, it does have special characters, but it should be possible with ASCII to use alternative versions of those characters. For example, with letter "Đ", we can use Dh (or just D if there is no other choice) instead when you know you can't use D with stroke. I know that UTF+8, which LFS doesn't use or support at least yet, fully supports all Northern Sámi characters.
I haven't done really much about it, because I want to know first, is it even possible to do it in the first place.
About the amount of users LFS has:
- 145214 users that have set their country as Finland
- 17882 users that have set their country as Sweden
- 12397 users that have set their country as Norway
And I would say almost all of these users are indeed from they country they told they're from. There are about 17000-18000 speakers in Norway, 5000-6000 in Sweden and 2000 in Finland. So, one could assume as since there are more Northern Sámi speakers in Norway than registered LFS users from that country, there is a good chance of a Northern Sámi speaking people playing LFS.
About that does it make sense: Scawen himself has said that he is always open for LFS being as accessible as possible. https://www.lfs.net/forum/post/1936125#post1936125 - so it is something that would be nice to have, but is not essential for the game.
One reason why some of those popular languages with millions of speakers, like Hindi and Arabic don't have translation in LFS is simply because:
- With Hindi, it does have special characters that are not currently supported in LFS
- With Arabic, it does have special characters and the text is right-to-left - those are not supported in LFS
Scawen has told that he would be interested to see how he can add the support to those languages, after the graphical updates and tire physics have been finished.
With Northern Sámi, it does have special characters, but it should be possible with ASCII to use alternative versions of those characters. For example, with letter "Đ", we can use Dh (or just D if there is no other choice) instead when you know you can't use D with stroke. I know that UTF+8, which LFS doesn't use or support at least yet, fully supports all Northern Sámi characters.
Blackwood Drag Strip as a selectable track configuration
Hi!
We know that LFS will have massive graphical update and all tracks, except Fern Bay, will be revamped. This got me thinking, it would probably be simple enough to add a selectable track configuration into the updated Blackwood: Drag Strip.
Using the begin of Historic backstraight, more precisely the first part of the straight, where drivers don't need to turn/correct their steering, and ending just before drivers need to do that slight right-turn at the backstraight, you could have a drag strip there.
I actually measured that, and very conveniently, the track distance would be exactly 1km in length! Not only it would be possible to have head-to-head races, drivers could also test their top speed and see how well they can change gears on straight there.
Because drivers only need to drive straight with no need to turn, adjust steering or brake, it would be much simpler than normally to add this track configuration. And it would be even simpler to add this considering this track alraedy exists, so there would be pretty much no need to do any changes into the updated Blackwood. Heck, we already have the Long Acceleration - Formula BMW FB02 training lesson available, you could probably use that track, but start from little earlier than usual to make sure it would last exactly 1km.
About this track, there would need to be following conditions for it to actually work in the game.
Conditions would be pretty much identical to AU3:
- Only up to 2 players can drive there at the same time (due to track width)
- It wouldn't be possible to set practice or qualifying.
- Race length is always 1 lap
- Hotlapping is not allowed
- Pit stops are not possible by default
- These stats would count towards LFSWorld's drags / wins stat. Wins there would not count towards Races won stat
- Entering to the track would probably done from the pitlane, if someone joins late or after race has finished. After all, that's how it's done for all other Blackwood tracks.
You could probably just copy the style how game behaves at Autocross Drag Strip and paste it there, with of course doing slight modifications to make sure it works properly. Basically, AI would behave exactly the same as it does in AU3/AU4, where when they see a green light, they start driving just straight line for that track length and immediately after finish line, they brake until they've stopped and then turn off their engines
One another reason about this suggestion is that because this graphical update is massive, it would make sense to have something new even for demo users. Demo users would also get to feel like they will get something extra, when these tracks get revamped and graphics get released. Therefore, this update would remind me of 2017 Blackwood update, where even the demo drivers got a new track configuration (Historic), but less content than licensed users, who got that whole surrounding area as well
And for those wondering, doesn't Autocross type of tracks always belong to licensed users? Well, not always: demo users have already gotten taste of Autocross, because Autocross Skid Pad was released on 0.2A, and unlockable S1-content was released when 0.3A was released. Between that time, Skid Pad was a demo track! It wouldn't be first time a test track would be released for demo users
Finally, remember what LFS.net and LFSManual both mention:
It would therefore be even more fitting to add a head-to-head drag strip there
EDIT: And just to clarify, it doesn't need to be 1km in length. It could also be 1/2 mile, or 1000 meters, 1/8 mile, 1/4 mile etc. 1km is pretty much the longest possible length with this dragstrip.
We know that LFS will have massive graphical update and all tracks, except Fern Bay, will be revamped. This got me thinking, it would probably be simple enough to add a selectable track configuration into the updated Blackwood: Drag Strip.
Using the begin of Historic backstraight, more precisely the first part of the straight, where drivers don't need to turn/correct their steering, and ending just before drivers need to do that slight right-turn at the backstraight, you could have a drag strip there.
I actually measured that, and very conveniently, the track distance would be exactly 1km in length! Not only it would be possible to have head-to-head races, drivers could also test their top speed and see how well they can change gears on straight there.
Because drivers only need to drive straight with no need to turn, adjust steering or brake, it would be much simpler than normally to add this track configuration. And it would be even simpler to add this considering this track alraedy exists, so there would be pretty much no need to do any changes into the updated Blackwood. Heck, we already have the Long Acceleration - Formula BMW FB02 training lesson available, you could probably use that track, but start from little earlier than usual to make sure it would last exactly 1km.
About this track, there would need to be following conditions for it to actually work in the game.
Conditions would be pretty much identical to AU3:
- Only up to 2 players can drive there at the same time (due to track width)
- It wouldn't be possible to set practice or qualifying.
- Race length is always 1 lap
- Hotlapping is not allowed
- Pit stops are not possible by default
- These stats would count towards LFSWorld's drags / wins stat. Wins there would not count towards Races won stat
- Entering to the track would probably done from the pitlane, if someone joins late or after race has finished. After all, that's how it's done for all other Blackwood tracks.
You could probably just copy the style how game behaves at Autocross Drag Strip and paste it there, with of course doing slight modifications to make sure it works properly. Basically, AI would behave exactly the same as it does in AU3/AU4, where when they see a green light, they start driving just straight line for that track length and immediately after finish line, they brake until they've stopped and then turn off their engines
One another reason about this suggestion is that because this graphical update is massive, it would make sense to have something new even for demo users. Demo users would also get to feel like they will get something extra, when these tracks get revamped and graphics get released. Therefore, this update would remind me of 2017 Blackwood update, where even the demo drivers got a new track configuration (Historic), but less content than licensed users, who got that whole surrounding area as well
And for those wondering, doesn't Autocross type of tracks always belong to licensed users? Well, not always: demo users have already gotten taste of Autocross, because Autocross Skid Pad was released on 0.2A, and unlockable S1-content was released when 0.3A was released. Between that time, Skid Pad was a demo track! It wouldn't be first time a test track would be released for demo users
Finally, remember what LFS.net and LFSManual both mention:
It would therefore be even more fitting to add a head-to-head drag strip there
EDIT: And just to clarify, it doesn't need to be 1km in length. It could also be 1/2 mile, or 1000 meters, 1/8 mile, 1/4 mile etc. 1km is pretty much the longest possible length with this dragstrip.
Last edited by tankslacno, .
Possible to add Northern Sámi language?
Hi!
I was wondering Scawen, I've been learning Northern Sami (in Finnish it means Pohjoissaame) for some time now, which is by far the most popular of the Sami Languages. The official name is Davvisámegiella (or just Sámegiella when speaking about Sámi languages itself). I could have a possibility to start translating LFS from English to Northern Sami language. However, I know it will definitely take some time from me to do that.
You can find more information about it here: https://en.wikipedia.org/wiki/Northern_S%C3%A1mi
However, I've found some possible issues about this:
EDIT: I already have one answer for this particular question. 1) Can you tell, will the new version have so many new or updated translation strings, that does it make sense for me to actually start translating it? Or should I wait for the new version that would have those updated translation strings?
2) There are only 25000 speakers of that language in the whole world, so it may be quite difficult to find any testers. There are speakers in Finland, Norway and Sweden, but I don't know if any of them play LFS
3) There are some special characters used in Sámi keyboard. I'm wondering does LFS support all of those characters. You can find it here: https://divvun.no/en/keyboards/layout-sme.html - and also from the Wikipedia page here: https://en.wikipedia.org/wiki/S%C3%A1mi_languages
- These are the special characters: Áá, Čč, Đđ, Ŋŋ, Šš, Ŧŧ, Žž
Of course loanwords can still use those replaced characters, for example cars and tracks name would still use those characters that are normally replaced in Northern Sami.
4) Is there anyway I can add a new language into LFS for testing? Or do I have to replace one of the existing languages with that?
5) If it's necessary, how much of the game would I need to translate before this language could be accepted into LFS? I know I would need to translate at least the help-file but do I need to translate every single translation string?
DISCLAIMERS:
1) I will not guarantee this translation project will actually be completed due to those aforementioned issues. It will definitely take some time from me to actually do it. I would first want to know, does it make sense for me to even start translating it into that language
2) Only the Northern Sámi would be added, no other Sámi languages. Sorry for those 2 people who speak Ter Sámi (https://en.wikipedia.org/wiki/Ter_S%C3%A1mi)
3) There are small differences between countries that use Northern Sámi. For example, some words may be typed differently in Norway than in Finland. I would use the Finnish version of course
I was wondering Scawen, I've been learning Northern Sami (in Finnish it means Pohjoissaame) for some time now, which is by far the most popular of the Sami Languages. The official name is Davvisámegiella (or just Sámegiella when speaking about Sámi languages itself). I could have a possibility to start translating LFS from English to Northern Sami language. However, I know it will definitely take some time from me to do that.
You can find more information about it here: https://en.wikipedia.org/wiki/Northern_S%C3%A1mi
However, I've found some possible issues about this:
EDIT: I already have one answer for this particular question. 1) Can you tell, will the new version have so many new or updated translation strings, that does it make sense for me to actually start translating it? Or should I wait for the new version that would have those updated translation strings?
2) There are only 25000 speakers of that language in the whole world, so it may be quite difficult to find any testers. There are speakers in Finland, Norway and Sweden, but I don't know if any of them play LFS
3) There are some special characters used in Sámi keyboard. I'm wondering does LFS support all of those characters. You can find it here: https://divvun.no/en/keyboards/layout-sme.html - and also from the Wikipedia page here: https://en.wikipedia.org/wiki/S%C3%A1mi_languages
- These are the special characters: Áá, Čč, Đđ, Ŋŋ, Šš, Ŧŧ, Žž
Of course loanwords can still use those replaced characters, for example cars and tracks name would still use those characters that are normally replaced in Northern Sami.
4) Is there anyway I can add a new language into LFS for testing? Or do I have to replace one of the existing languages with that?
5) If it's necessary, how much of the game would I need to translate before this language could be accepted into LFS? I know I would need to translate at least the help-file but do I need to translate every single translation string?
DISCLAIMERS:
1) I will not guarantee this translation project will actually be completed due to those aforementioned issues. It will definitely take some time from me to actually do it. I would first want to know, does it make sense for me to even start translating it into that language
2) Only the Northern Sámi would be added, no other Sámi languages. Sorry for those 2 people who speak Ter Sámi
(https://en.wikipedia.org/wiki/Ter_S%C3%A1mi)3) There are small differences between countries that use Northern Sámi. For example, some words may be typed differently in Norway than in Finland. I would use the Finnish version of course
Last edited by tankslacno, .
Having multiple accounts itself won't be an issue as long as you understand the Terms and Conditions (https://www.lfs.net/agreement) and have bought (or received via voucher) the possible licenses legally from LFS Shop.
For example, there is a rule 3.1:
It just says that you may install LFS on 2 computers, but nothing prevents you for having multiple LFS instances in that one computer, for example having one instance for each account for example. In fact, some of the streamers have to use multiple accounts to make their broadcast work (like Simbroadcasts and multiBC)
Please avoid posting issues obviously caused by antivirus software
Hi!
I tried to post this to the Patch TEST Forum section (https://www.lfs.net/forum/66-Patch-TEST-Forum), but since it looks like only devs and moderators can create new threads there, I decided to post this into technical assistance. For now, I didn't post this into Bugs - Program section (https://www.lfs.net/forum/10-Bugs---Program), because this is not a LFS bug. Scawen or one of the mods, feel free to move or copy this thread to the more appropriate place if necessary
Every time a new test patch or, to a lesser extent, official patch of LFS gets released, various different antivirus softwares get overzealous about this exe. Most likely (but not certain) reason is because the new patch exe is very new, so it doesn't have any reports telling that this file is safe. What this can cause is one or more of the following, but not limited to, issues:
- Game not getting downloaded at all, or only partially
- Game not starting at all
- Game only barely starting, after many tries. You may encounter some error messages, like this one I did receive in 2019: https://www.lfs.net/attachment/193681
- Game starting, but then suddenly shutting down
And then, in almost all of these cases, you will almost immediately get a notification from your antivirus software, that the LFS.exe is potentially dangerous. Even if you choose to allow it, some antivirus softwares (like Avast), will still think it's potentially dangerous and prevent you from going forward. One thing you can do is wait after allowing it. Usually after a while though (it is possible enough users reporting it safe causes it to be safe), the issue goes away. This issue with antivirus softwares may apply to both LFS.exe and LFS_Editor.exe.
Scawen has stated this: https://www.lfs.net/forum/post/2094495#post2094495
How to report LFS.exe as false positive:
False positive means that antivirus software mistakenly thinks the file you're trying to open is malware etc. when it's actually not. Usually in the antivirus software itself, you can report it safe. But alternatively, I've posted some links for several different antivirus software sites, where you can report LFS.exe being false positive. Feel free to tell me more links about these
- Avast: https://www.avast.com/report-false-positive#pc
- AVG: https://www.avg.com/en-ww/report-false-positive#pc
- Avira: https://www.avira.com/en/analysis/submit
- BitDefender: https://www.bitdefender.com/en-us/business/submit
- Eset: https://support.eset.com/en/kb141-submit-a-virus-website-or-potential-false-positive-sample-to-the-eset-lab
- F-Secure: https://www.f-secure.com/us-en/support/submit-a-sample
- KasperSky: https://opentip.kaspersky.com/
- MalwareBytes: https://forums.malwarebytes.com/forum/122-false-positives/
- McAfee: https://www.mcafee.com/en-us/consumer-support/dispute-detection-allowlisting.html (only allows ZIP, RAR and pre-extracted files)
- Microsoft/Windows Defender: https://www.microsoft.com/en-us/wdsi/filesubmission
- Norton: https://submit.norton.com/
- Sophos: https://intelix.sophos.com/
- Trend Micro: https://helpcenter.trendmicro.com/en-us/article/tmka-14388
What you should NOT do?
Well, obviously you should NOT tell the LFS.exe is false negative (stating that antivirus softwares are incorrect thinking LFS exe is safe)
But on more serious note: if it's obvious that your issue is caused by antivirus software's behavior and not by LFS itself, please do not report about it in LFS Patch Test Forum, Bugs - Program etc. Do not tell Scawen to fix this issue clearly caused by antivirus software. You may wonder why? Because:
Scawen cannot do anything against any overzealous antivirus software
Your message is essentially useless for him, and if you already know the issue is obviously caused by overzealous antivirus software, it is also complete waste of time for you as well. It doesn't matter how many times you report it, Scawen simply can't do anything at all to fix it! Remember: Scawen is responsible for developing Live for Speed, Scawen is not a developer of any antivirus software!
The only thing what Scawen can do here in LFS, is to add a disclaimer to the downloads page, or to the F.A.Q page, stating that various antivirus softwares may detect LFS as false positive. (Or to move this thread to Patch TEST Forum and/or Bugs - Program section). But of course that disclaimer itself doesn't prevent antivirus softwares falsely reporting LFS (test) patches potentailly being malware.
Also, remember LFS Terms and conditions, rule 1.3: https://www.lfs.net/agreement
How can I detect is the issue obviously caused by antivirus software and not by LFS?
Like I stated in the title, and in this post already: this statement only applies to situations, where it is obvious that your issue is caused by antivirus software and not by LFS.
Easiest way to notice the issue is obviously caused by antivirus software is that if you almost immediately get a notification/report from your antivirus software about LFS, then it is clear that your issue with LFS was caused, not by LFS, but by that antivirus software.
Alternatively, what you can do is to try to disable the antivirus software for time being and then try to see if the issue comes again. One method, what Flame CZE told me in Discord is that he has excluded his LFS instance folder from antivirus realtime checks. If the issue does come out, without any antivirus softwares then it is very likely that the issue is indeed in LFS.
Finally: if you're unsure, is the issue caused by LFS or antivirus software, then of course, you can report about it in LFS Forum. It's always better to report it in that case than not
I tried to post this to the Patch TEST Forum section (https://www.lfs.net/forum/66-Patch-TEST-Forum), but since it looks like only devs and moderators can create new threads there, I decided to post this into technical assistance. For now, I didn't post this into Bugs - Program section (https://www.lfs.net/forum/10-Bugs---Program), because this is not a LFS bug. Scawen or one of the mods, feel free to move or copy this thread to the more appropriate place if necessary
Every time a new test patch or, to a lesser extent, official patch of LFS gets released, various different antivirus softwares get overzealous about this exe. Most likely (but not certain) reason is because the new patch exe is very new, so it doesn't have any reports telling that this file is safe. What this can cause is one or more of the following, but not limited to, issues:
- Game not getting downloaded at all, or only partially
- Game not starting at all
- Game only barely starting, after many tries. You may encounter some error messages, like this one I did receive in 2019: https://www.lfs.net/attachment/193681
- Game starting, but then suddenly shutting down
And then, in almost all of these cases, you will almost immediately get a notification from your antivirus software, that the LFS.exe is potentially dangerous. Even if you choose to allow it, some antivirus softwares (like Avast), will still think it's potentially dangerous and prevent you from going forward. One thing you can do is wait after allowing it. Usually after a while though (it is possible enough users reporting it safe causes it to be safe), the issue goes away. This issue with antivirus softwares may apply to both LFS.exe and LFS_Editor.exe.
Scawen has stated this: https://www.lfs.net/forum/post/2094495#post2094495
How to report LFS.exe as false positive:
False positive means that antivirus software mistakenly thinks the file you're trying to open is malware etc. when it's actually not. Usually in the antivirus software itself, you can report it safe. But alternatively, I've posted some links for several different antivirus software sites, where you can report LFS.exe being false positive. Feel free to tell me more links about these
- Avast: https://www.avast.com/report-false-positive#pc
- AVG: https://www.avg.com/en-ww/report-false-positive#pc
- Avira: https://www.avira.com/en/analysis/submit
- BitDefender: https://www.bitdefender.com/en-us/business/submit
- Eset: https://support.eset.com/en/kb141-submit-a-virus-website-or-potential-false-positive-sample-to-the-eset-lab
- F-Secure: https://www.f-secure.com/us-en/support/submit-a-sample
- KasperSky: https://opentip.kaspersky.com/
- MalwareBytes: https://forums.malwarebytes.com/forum/122-false-positives/
- McAfee: https://www.mcafee.com/en-us/consumer-support/dispute-detection-allowlisting.html (only allows ZIP, RAR and pre-extracted files)
- Microsoft/Windows Defender: https://www.microsoft.com/en-us/wdsi/filesubmission
- Norton: https://submit.norton.com/
- Sophos: https://intelix.sophos.com/
- Trend Micro: https://helpcenter.trendmicro.com/en-us/article/tmka-14388
What you should NOT do?
Well, obviously you should NOT tell the LFS.exe is false negative (stating that antivirus softwares are incorrect thinking LFS exe is safe)
But on more serious note: if it's obvious that your issue is caused by antivirus software's behavior and not by LFS itself, please do not report about it in LFS Patch Test Forum, Bugs - Program etc. Do not tell Scawen to fix this issue clearly caused by antivirus software. You may wonder why? Because:
Scawen cannot do anything against any overzealous antivirus software
Your message is essentially useless for him, and if you already know the issue is obviously caused by overzealous antivirus software, it is also complete waste of time for you as well. It doesn't matter how many times you report it, Scawen simply can't do anything at all to fix it! Remember: Scawen is responsible for developing Live for Speed, Scawen is not a developer of any antivirus software!
The only thing what Scawen can do here in LFS, is to add a disclaimer to the downloads page, or to the F.A.Q page, stating that various antivirus softwares may detect LFS as false positive. (Or to move this thread to Patch TEST Forum and/or Bugs - Program section). But of course that disclaimer itself doesn't prevent antivirus softwares falsely reporting LFS (test) patches potentailly being malware.
Also, remember LFS Terms and conditions, rule 1.3: https://www.lfs.net/agreement
How can I detect is the issue obviously caused by antivirus software and not by LFS?
Like I stated in the title, and in this post already: this statement only applies to situations, where it is obvious that your issue is caused by antivirus software and not by LFS.
Easiest way to notice the issue is obviously caused by antivirus software is that if you almost immediately get a notification/report from your antivirus software about LFS, then it is clear that your issue with LFS was caused, not by LFS, but by that antivirus software.
Alternatively, what you can do is to try to disable the antivirus software for time being and then try to see if the issue comes again. One method, what Flame CZE told me in Discord is that he has excluded his LFS instance folder from antivirus realtime checks. If the issue does come out, without any antivirus softwares then it is very likely that the issue is indeed in LFS.
Finally: if you're unsure, is the issue caused by LFS or antivirus software, then of course, you can report about it in LFS Forum. It's always better to report it in that case than not
Last edited by tankslacno, .
Technically it is possible:
On normal tracks, you can use Autocross objects to modify the already existing tracks (so like using ramps on the track or having checkpoints in a different location). However, remember that AI drivers will use their normal racing line, so you can't use this method on any tracks where AIs can't have a racing line (i.e. car parks, open configurations) and you can't block the normal racing line much - otherwise they can't finish their lap!
And, as of 0.7G, you can also control AI in pretty basic level using InSim: https://www.lfs.net/forum/thread/110309 - however, according to Scawen, that is not intended to racing, only for cruising and training. But technically, you can create a custom layout on Layout Square, Autocross etc. and then use InSim to control that AI to drive on that custom track/layout.
On normal tracks, you can use Autocross objects to modify the already existing tracks (so like using ramps on the track or having checkpoints in a different location). However, remember that AI drivers will use their normal racing line, so you can't use this method on any tracks where AIs can't have a racing line (i.e. car parks, open configurations) and you can't block the normal racing line much - otherwise they can't finish their lap!
And, as of 0.7G, you can also control AI in pretty basic level using InSim: https://www.lfs.net/forum/thread/110309 - however, according to Scawen, that is not intended to racing, only for cruising and training. But technically, you can create a custom layout on Layout Square, Autocross etc. and then use InSim to control that AI to drive on that custom track/layout.
Last edited by tankslacno, .
FGED GREDG RDFGDR GSFDG