Not sure have I missed something, but in Single Player, if I toggle mandatory pit stop on/off and then restart the race with modded cars on the grid, all those modded cars will be removed from the grid. Standard cars do stay on the grid though. If I then try to add modded cars, I get notification that this server doesn't allow to use mods.
This also happens if I (dis)allow refueling and then restart the race. And if only modded cars are on server, the game will naturally throw me into lobby.
EDIT: It also happens, if I toggle allowing car reset on or off
This also happens if I (dis)allow refueling and then restart the race. And if only modded cars are on server, the game will naturally throw me into lobby.
EDIT: It also happens, if I toggle allowing car reset on or off
LFS freezes if I join (LFS.net-)server immediately after it has been (re)started
Hi!
So I found a bug which happens at least on hosts rented on this site. I tested this on 0.6V. Server which was tested is Sport Racing Team-Finland. Because I don't own that server, I can't see activity/log from that server.
My friend who is owner of that host decided to stop that server while I was connected there. When he did that, I was, as it should be, immediately timed out from that server. However, when he started that server again on that site, I immediately joined that server again. This time, LFS displayed "Connect timed out"-message. After that, I immediately tried to join that server again. This time it worked and I get to join on lobby, but after that, my LFS completely freezes.
When LFS freezes, it will increase that lag amount (or what do you call it?) to 32 in UDP. However, after that, it stays on that number. If I try to press any button on lobby screen, nothing happens. My connection also never seems to time out, so I'm basically just staying on lobby screen permanently. What do I also mean by freezing is that if I try to close LFS.exe, LFS then just displays black screen with lag bars on left bottom side of screen permanently. Therefore, LFS.exe doesn't close automatically.
The only way to close LFS.exe is by via task manager. I've attached couple screenshots (one displaying black screen and one from lobby) and deb.txt-file. Note that the lag bars are different in those screenshots because I took that Lobby-screenshot about 1 hour later, which means that it's possible to reproduce this bug.
I should mention that my friend pressed that Start-button immediately after restarting server is possible (there's that 1 minute period where restarting server is not possible). I also should mention, that I tried this several times and it happened every time if I were fast enough. I also noted that you don't need to be on the server during that moment when host owner shuts down that server.
Way to reproduce this:
So, here's a possible way to reproduce this bug. I'm not sure does this apply only to servers rented on LFS.net or on all servers. This is however, easier, to reproduce on hosts rented on this site.
1) Make sure you or someone else stops that server (on LFS.net/Hosting). That player doesn't need to connect to that server at that moment.
2) Immediately after restarting server is possible on LFS.net, restart that server.
3) Immediately after pressing start-button, make sure that you or another player joins to that server
4) That player will then receive message "Connect timed out". After that message is displayed, that player shuold immediately try joining that server again
5) This time, player will connect that server and sees lobby, but LFS freezes completely after that.
tl;dr: join server immediately after (re)starting it (on LFS.net). On first time, it doesn't let you join that server and when you immediately try to rejoin, it works, but LFS freezes completely after that
So I found a bug which happens at least on hosts rented on this site. I tested this on 0.6V. Server which was tested is Sport Racing Team-Finland. Because I don't own that server, I can't see activity/log from that server.
My friend who is owner of that host decided to stop that server while I was connected there. When he did that, I was, as it should be, immediately timed out from that server. However, when he started that server again on that site, I immediately joined that server again. This time, LFS displayed "Connect timed out"-message. After that, I immediately tried to join that server again. This time it worked and I get to join on lobby, but after that, my LFS completely freezes.
When LFS freezes, it will increase that lag amount (or what do you call it?) to 32 in UDP. However, after that, it stays on that number. If I try to press any button on lobby screen, nothing happens. My connection also never seems to time out, so I'm basically just staying on lobby screen permanently. What do I also mean by freezing is that if I try to close LFS.exe, LFS then just displays black screen with lag bars on left bottom side of screen permanently. Therefore, LFS.exe doesn't close automatically.
The only way to close LFS.exe is by via task manager. I've attached couple screenshots (one displaying black screen and one from lobby) and deb.txt-file. Note that the lag bars are different in those screenshots because I took that Lobby-screenshot about 1 hour later, which means that it's possible to reproduce this bug.
I should mention that my friend pressed that Start-button immediately after restarting server is possible (there's that 1 minute period where restarting server is not possible). I also should mention, that I tried this several times and it happened every time if I were fast enough. I also noted that you don't need to be on the server during that moment when host owner shuts down that server.
Way to reproduce this:
So, here's a possible way to reproduce this bug. I'm not sure does this apply only to servers rented on LFS.net or on all servers. This is however, easier, to reproduce on hosts rented on this site.
1) Make sure you or someone else stops that server (on LFS.net/Hosting). That player doesn't need to connect to that server at that moment.
2) Immediately after restarting server is possible on LFS.net, restart that server.
3) Immediately after pressing start-button, make sure that you or another player joins to that server
4) That player will then receive message "Connect timed out". After that message is displayed, that player shuold immediately try joining that server again
5) This time, player will connect that server and sees lobby, but LFS freezes completely after that.
tl;dr: join server immediately after (re)starting it (on LFS.net). On first time, it doesn't let you join that server and when you immediately try to rejoin, it works, but LFS freezes completely after that
Last edited by tankslacno, .
Hi! I've noticed several strange things and bugs in training lessons. At least one of them is related directly to this test patch and I found two others due to me trying to test that new Live Replay-feature in this test patch, meaning that they could be related to this test patch as well.
STRANGE THING #1:
While you can't use most commands in training lessons, for some reason /canrefuel works here even with parameter no when using that command via chat bind. This makes that "Pitstop - Formula BMW" training lesson significantly easier (and yes, I know you can already cheat in that lesson by just simply opening F12-box and making sure that you don't refuel at all, but this makes it even faster). I've attached a screenshot about this.
STRANGE THING #2:
You can cheat in "Chicane Course - Formula BMW"-lesson by simply shortcutting after second corner. You don't have to do those last two corners, you can simply drive between two cones and straight to the finish line. I've attached a screenshot about this.
STRANGE THING #3:
Due to that live replay-function introduced in this test patch, I had to test this in single player as well (I know it doesn't work here!). If I'm doing a training lesson and then decide to open another LFS instance to view that temp_spr-replay, something strange happens:
Viewing temp_spr-replay is not allowed at all and LFS will instead inform something about checkpoints/autoslalom tracks or failed header check. I've attached couple screenshots about this. However:
I found one way to view temp_spr-replay from training lesson when playing. It's really strange how I did it, but doing that will not only allow viewing that temp_spr-replay in another LFS instance, but it's actually a bug that causes training lesson to get stuck (I mean by that it's doesn't automatically end). I will tell more about this next:
Four actual bugs:
BUG #1:
So this is the way to view temp_spr-replays from training lessons: If you use command via chat bind that would normally result replay not getting recorded in single player (like command /wind), LFS itself will never end that training lesson. And you cannot end it by yourself either by pressing 1, 2 or Esc-button. The only way to end it (other than closing LFS entirely) is to press Shift+X or alternatively, use command /end via chat bind. What this means you can now watch that temp_spr-replay from that LFS instance or open another LFS instance to watch that.
What this does result as well is that even if you successfully complete training lesson and then use that command which normally would stop recording single player replay, LFS doesn't let you clear that training lesson.
Way to reproduce this:
1) Make a command that would normally end recording a replay in single player (like /wind 1) to a chat bind
2) Start training lesson. Doesn't matter if you finish it or not
3) Before that training lesson ends automatically, press that button where you assigned that command. That training lesson will never end then.
BUG #2:
If you don't have replay saving function enabled at all and you do that chat bind-bug I just mentioned, it still mentions "Replay not recorded" even though it wasn't recording in first place (or it actually was, check bug #3). This doesn't happen in single player. I've attached a screenshot about this.
BUG #3:
Even if saving single player replays is disabled, LFS still saves automatically replays of training lessons. Way to do this is to open another LFS instance and wait until your training lesson ends automatically in that original LFS instance. Now when in that training lesson you're viewing result of your training lesson, you can actually see in that other LFS instance that it saved that replay automatically. You can't rename it and if you exit that result screen in that training lesson, it will be deleted. To save it, you have to watch that replay at the same time in that other LFS instance when exiting that result screen.
Way to reproduce this:
1) Open LFS-instance. It doesn't matter if your SPR-saving is set to no save, manual or autosave
2) Open another LFS-instance after that.
3) Start training lesson and wait until it automatically finishes. Now, don't exit that screen where you view your result of that training lesson.
4) In that another LFS instance, go to Replays-page. That replay can be found here even if you don't have SPR-saving enabled at all. And if you're watching that replay at the same time you exit that "training lesson result"-screen in that another LFS instance, that replay will be saved. After that, you can rename it.
BUG #4:
If you use command /aiset or /aiset_all via chat binds, you can cheat in overtaking lessons. So what you can do, is for example to put command /aiset PRO 1 or /aiset_all 1 in F1 chat bind. If you then press that button during that overtaking lesson, it just changes that AI-driver's skill level to that skill level which makes these lessons easier (or harder) for you. I've attached a screenshot about this.
Also worth noting in overtaking lessons your skill level when completing those is based on how many AI-drivers you overtook. So if for some reason OK-wins and you beat both PRO- and QUICK-drivers, your skill level is QUICK, not PRO, even though that you won that PRO-skilled AI-driver.
Way to reproduce this:
1) Make a command /aiset PRO/QUICK/OK 1-5 or /aiset_all 1-5 to a chat bind
2) Start any training lesson about overtaking.
3) At any point during that training lesson before it finishes, press that button where you assigned that command. This way you can change that skill level for your AI-drivers to make that overtaking lesson easier or harder for you.
POSSIBLE BUG #5:
Is it on purpose that if I restart overtaking lesson, AI's will have that minimum fuel load at start instead of 50%? Check out that screenshot I attached about wrong skill levels, it also displays AI-drivers only having 2% fuel load at start instead of 50%.
STRANGE THING #1:
While you can't use most commands in training lessons, for some reason /canrefuel works here even with parameter no when using that command via chat bind. This makes that "Pitstop - Formula BMW" training lesson significantly easier (and yes, I know you can already cheat in that lesson by just simply opening F12-box and making sure that you don't refuel at all, but this makes it even faster). I've attached a screenshot about this.
STRANGE THING #2:
You can cheat in "Chicane Course - Formula BMW"-lesson by simply shortcutting after second corner. You don't have to do those last two corners, you can simply drive between two cones and straight to the finish line. I've attached a screenshot about this.
STRANGE THING #3:
Due to that live replay-function introduced in this test patch, I had to test this in single player as well (I know it doesn't work here!). If I'm doing a training lesson and then decide to open another LFS instance to view that temp_spr-replay, something strange happens:
Viewing temp_spr-replay is not allowed at all and LFS will instead inform something about checkpoints/autoslalom tracks or failed header check. I've attached couple screenshots about this. However:
I found one way to view temp_spr-replay from training lesson when playing. It's really strange how I did it, but doing that will not only allow viewing that temp_spr-replay in another LFS instance, but it's actually a bug that causes training lesson to get stuck (I mean by that it's doesn't automatically end). I will tell more about this next:
Four actual bugs:
BUG #1:
So this is the way to view temp_spr-replays from training lessons: If you use command via chat bind that would normally result replay not getting recorded in single player (like command /wind), LFS itself will never end that training lesson. And you cannot end it by yourself either by pressing 1, 2 or Esc-button. The only way to end it (other than closing LFS entirely) is to press Shift+X or alternatively, use command /end via chat bind. What this means you can now watch that temp_spr-replay from that LFS instance or open another LFS instance to watch that.
What this does result as well is that even if you successfully complete training lesson and then use that command which normally would stop recording single player replay, LFS doesn't let you clear that training lesson.
Way to reproduce this:
1) Make a command that would normally end recording a replay in single player (like /wind 1) to a chat bind
2) Start training lesson. Doesn't matter if you finish it or not
3) Before that training lesson ends automatically, press that button where you assigned that command. That training lesson will never end then.
BUG #2:
If you don't have replay saving function enabled at all and you do that chat bind-bug I just mentioned, it still mentions "Replay not recorded" even though it wasn't recording in first place (or it actually was, check bug #3). This doesn't happen in single player. I've attached a screenshot about this.
BUG #3:
Even if saving single player replays is disabled, LFS still saves automatically replays of training lessons. Way to do this is to open another LFS instance and wait until your training lesson ends automatically in that original LFS instance. Now when in that training lesson you're viewing result of your training lesson, you can actually see in that other LFS instance that it saved that replay automatically. You can't rename it and if you exit that result screen in that training lesson, it will be deleted. To save it, you have to watch that replay at the same time in that other LFS instance when exiting that result screen.
Way to reproduce this:
1) Open LFS-instance. It doesn't matter if your SPR-saving is set to no save, manual or autosave
2) Open another LFS-instance after that.
3) Start training lesson and wait until it automatically finishes. Now, don't exit that screen where you view your result of that training lesson.
4) In that another LFS instance, go to Replays-page. That replay can be found here even if you don't have SPR-saving enabled at all. And if you're watching that replay at the same time you exit that "training lesson result"-screen in that another LFS instance, that replay will be saved. After that, you can rename it.
BUG #4:
If you use command /aiset or /aiset_all via chat binds, you can cheat in overtaking lessons. So what you can do, is for example to put command /aiset PRO 1 or /aiset_all 1 in F1 chat bind. If you then press that button during that overtaking lesson, it just changes that AI-driver's skill level to that skill level which makes these lessons easier (or harder) for you. I've attached a screenshot about this.
Also worth noting in overtaking lessons your skill level when completing those is based on how many AI-drivers you overtook. So if for some reason OK-wins and you beat both PRO- and QUICK-drivers, your skill level is QUICK, not PRO, even though that you won that PRO-skilled AI-driver.
Way to reproduce this:
1) Make a command /aiset PRO/QUICK/OK 1-5 or /aiset_all 1-5 to a chat bind
2) Start any training lesson about overtaking.
3) At any point during that training lesson before it finishes, press that button where you assigned that command. This way you can change that skill level for your AI-drivers to make that overtaking lesson easier or harder for you.
POSSIBLE BUG #5:
Is it on purpose that if I restart overtaking lesson, AI's will have that minimum fuel load at start instead of 50%? Check out that screenshot I attached about wrong skill levels, it also displays AI-drivers only having 2% fuel load at start instead of 50%.
Last edited by tankslacno, .
I've attached an updated Commands.txt-file. Fixed some typos and changed that one line.
I've also updated those translations related to changes you did in those outdated In-Game Help-texts. I did that in that LFS Translations page. I just noticed that there is still one small outdated information in English on max_guests section:
While every other in-game help file does now mention S3 in English as well, this one still does not
I've also updated those translations related to changes you did in those outdated In-Game Help-texts. I did that in that LFS Translations page. I just noticed that there is still one small outdated information in English on max_guests section:
While every other in-game help file does now mention S3 in English as well, this one still does not
Hi!
I've attached an updated Commands.txt so that translation is relevant to your Commands.txt which you updated 5th February 2021.
However, I noticed two things when updating that and I think I should point them out:
1) I've already updated available number for smoothness of car updates per second from 3-6 to 3-12. if for some reason it's required to change that maximum number or revert it back to that original 3-6, I will update this file again.
2) This information in English Commands.txt-file catched my eye:
Is that part I bolded redundant? I don't find that "LFS Keys"-page anywhere here. I did find a page which displays similar info about those (LFSWorld) DB access commands here though: https://en.lfsmanual.net/wiki/Keys#LFS_World_commands_in-game
I was just wondering should that part I bolded get updated?
I've attached an updated Commands.txt so that translation is relevant to your Commands.txt which you updated 5th February 2021.
However, I noticed two things when updating that and I think I should point them out:
1) I've already updated available number for smoothness of car updates per second from 3-6 to 3-12. if for some reason it's required to change that maximum number or revert it back to that original 3-6, I will update this file again.
2) This information in English Commands.txt-file catched my eye:
Is that part I bolded redundant? I don't find that "LFS Keys"-page anywhere here. I did find a page which displays similar info about those (LFSWorld) DB access commands here though: https://en.lfsmanual.net/wiki/Keys#LFS_World_commands_in-game
I was just wondering should that part I bolded get updated?
Scawen, is it confirmed that in the official version, it'll be possible to add up to 32 AI's per player on multiplayer and that maximum number of packets sent per second by each car will be 12 instead of 6?
I'm asking this because I want to update in-game help translations related to those updated things before you will release new official patch, but I don't want to display false information in those
I'm asking this because I want to update in-game help translations related to those updated things before you will release new official patch, but I don't want to display false information in those
Scawen, not a bug but two questions:
1) Did you ask Victor that can we test this incompatible update on hosts rented on LFS.net or do we have to use Dedi Host/create own server on LFS Client?
2) I was wondering should we translators already translate those in-game help files for this incompatible update? I noticed that when starting a new host, in-game help files related to Max drivers (real + AI) and smoothness are still mentioned how they were in pre-0.6U13. What I mean is that in-game help files when starting a new host don't mention anything about allowing up to 32 AI's per guest PC or that maximum setting for smoothness is now 12. I noticed this on every language, English included.
What came to my mind however is that this is an incompatible update though. So should we translators wait a little bit before editing those in-game help files to see what changes are final in official patch?
By the way, I also noticed that English language doesn't mention anything about S3-mode in those in-game help files when starting a new host.
1) Did you ask Victor that can we test this incompatible update on hosts rented on LFS.net or do we have to use Dedi Host/create own server on LFS Client?
2) I was wondering should we translators already translate those in-game help files for this incompatible update? I noticed that when starting a new host, in-game help files related to Max drivers (real + AI) and smoothness are still mentioned how they were in pre-0.6U13. What I mean is that in-game help files when starting a new host don't mention anything about allowing up to 32 AI's per guest PC or that maximum setting for smoothness is now 12. I noticed this on every language, English included.
What came to my mind however is that this is an incompatible update though. So should we translators wait a little bit before editing those in-game help files to see what changes are final in official patch?
By the way, I also noticed that English language doesn't mention anything about S3-mode in those in-game help files when starting a new host.
I'm testing this with 32 AI's and I think I found a bug:
Testing with 32 AI's seem to be working fine when I'm alone at least but my bug is that AI's will not change tires even if i have tire change set to "always" in F12-box. I should also mention that I initially did disallow refueling in server settings but allowed it again via Admin-command during qualifying.
Tested this in Single Player as well, same thing happened
Before U17 (I tested this with 0.6U and 0.6U16), I didn't have any issue about this
Attached a Screenshot about this in multiplayer mode
EDIT: This happens also on player itself in both modes. I also tested other F12 settings (damage etc.) and they seem to work properly. It does change your tires if you change tire compounds.
Testing with 32 AI's seem to be working fine when I'm alone at least but my bug is that AI's will not change tires even if i have tire change set to "always" in F12-box. I should also mention that I initially did disallow refueling in server settings but allowed it again via Admin-command during qualifying.
Tested this in Single Player as well, same thing happened
Before U17 (I tested this with 0.6U and 0.6U16), I didn't have any issue about this
Attached a Screenshot about this in multiplayer mode
EDIT: This happens also on player itself in both modes. I also tested other F12 settings (damage etc.) and they seem to work properly. It does change your tires if you change tire compounds.
Last edited by tankslacno, .
I can answer that: AI driver goes to that pit box according to it's position when it started it's last sector before that AI driver decides to enter a pit lane. So if that AI is in 1st place when that AI starts last sector before it pits, it will go to the last pit box (aka the one closest to the pit exit).
About your thoughts about making conflicts with AI: since 0.6K they have become way too careful in the pit lane due to this:
I understand that they don't want to crash to each other, but what this has resulted is that if one AI is doing a pit stop and other AI is trying to enter the pit box directly in front of it (or vice versa, which means that one AI is trying to leave that pit box after finishing it and one AI is directly in front of it), that AI actually gets too scared and gets stuck at the pitlane. It results that AI is unable to properly enter it's assigned pit box before that AI who first made that pit stop actually completes it.
I attached a screenshot about this what I mean.
Scawen, I decided to test that pit stop bug:
I tested this ON SO1+FZR and UF1. Same thing happened: I also encountered that same thing if you adjust camber settings instead in those cars. It also happens if you adjust back tires.
However this is where it gets interesting: if you change tyre type, or wing in FZR's case, it works properly. But if you adjust camber and/or tyre pressure at the same time, that bug still happens.
And I also noticed one more confusing thing and one more actual bug:
1) If I decide to change my both front and rear tires type, it's still possible to have that F12-option Tyre change as never. I understand that option can be set to "never", if you don't decide to change all tires. It's just confusing that it says "never" even if you decide to change tyre type on all wheels. Of course, it does change your tires if you change tyre type regardless of tyre wear.
So in case you decide to change tyre type to all wheels, should that option then automatically be: Tyre change : "always"?
I attached a screenshot about this.
2) Actual bug, happened at least on FZR. How to reproduce this:
1) Adjust your rear tires tyre pressure to the lowest possible (for example, if you're using FZR, adjust it to 0.70)
2) Do a pit stop.
3) After that pit stop, you can see that on F12-window, tyre pressure is correct, but it still says that change is -0.10 bar at rear tires compared to current setups. I attached a screenshot about this.
I tested this ON SO1+FZR and UF1. Same thing happened: I also encountered that same thing if you adjust camber settings instead in those cars. It also happens if you adjust back tires.
However this is where it gets interesting: if you change tyre type, or wing in FZR's case, it works properly. But if you adjust camber and/or tyre pressure at the same time, that bug still happens.
And I also noticed one more confusing thing and one more actual bug:
1) If I decide to change my both front and rear tires type, it's still possible to have that F12-option Tyre change as never. I understand that option can be set to "never", if you don't decide to change all tires. It's just confusing that it says "never" even if you decide to change tyre type on all wheels. Of course, it does change your tires if you change tyre type regardless of tyre wear.
So in case you decide to change tyre type to all wheels, should that option then automatically be: Tyre change : "always"?
I attached a screenshot about this.
2) Actual bug, happened at least on FZR. How to reproduce this:
1) Adjust your rear tires tyre pressure to the lowest possible (for example, if you're using FZR, adjust it to 0.70)
2) Do a pit stop.
3) After that pit stop, you can see that on F12-window, tyre pressure is correct, but it still says that change is -0.10 bar at rear tires compared to current setups. I attached a screenshot about this.
I've also noticed few other situations where it could be useful to have that auto-repeat:
1) When holding (Shift+)TAB to view driver you want. I know I could just click left mouse button on standings to watch that driver, but I'm just used to hold that TAB button until I'm watching that driver I want. Of course, it's not too bad when there are just few drivers, but when there are many drivers racing, I need to press that TAB button several times now because I'm just so used to hold that TAB-button.
2) Probably auto-repeat could be allowed when changing camera views as well (aka when holding V-button).
3) Even though I'm not using wheel, I also noticed that if you want to have less or more force on your wheel, you need to press that ",/."-buttons several times now. I think in this case, auto-repeat could be allowed, so players could get that force amount they want more quickly.
Question:
Is it done on purpose that if I allow this, that remote car fuel load is only shown on clocks/meters? That fuel load is not shown on F12-menu. This came to mind when I saw that suggestion about allowing only Admins to see fuel load. At the moment, even they can't see that exact amount of fuel load if that fuel load can be seen via that command.
Also: should we translators get ready to translate those new U14 features soon? I already saw some lines in English (like those displayed in CPU usage display) which we can't translate yet.
Is it done on purpose that if I allow this, that remote car fuel load is only shown on clocks/meters? That fuel load is not shown on F12-menu. This came to mind when I saw that suggestion about allowing only Admins to see fuel load. At the moment, even they can't see that exact amount of fuel load if that fuel load can be seen via that command.
Also: should we translators get ready to translate those new U14 features soon? I already saw some lines in English (like those displayed in CPU usage display) which we can't translate yet.
Yes I was actually trying to do that and I know I should never use that as a replay name as I already said that it doesn't make sense.
Maybe it's not actually a message bug. Replay is actually named as "temp_mpr" and it works as long as you don't close LFS or start another session. I just thought it looked strange that in that attachment it first said "Could not rename temp_mpr - copied instead" and then said "Saved MP replay - temp_mpr". Sorry for that inconvenience.
However, I noticed something else related to that and it could be a bug: it's actually possible to save replay named temp_mpr in a rather strange way in 0.6U14.
So what I did was this: I started new LFS 0.6U14 host and started a race (I also tried this on 0.6U host, same results happened there).
I tried to save mpr-replay called "temp_mpr" in these four situations.
1) That LFS instance where I hosted that server was only LFS instance opened
2) I opened another LFS instance from same folder (so I could watch temp_mpr) but didn't watch any replays
3) I watched other replays in another LFS instance from same folder
4) I watched temp_mpr (aka now Live Replay) in another LFS instance from same folder
In first three cases, it correctly said that it could not rename or copy temp_mpr (similarly how it says you could not rename SPR in Single Player, if you try to save it as "temp_spr"). I've attached a screenshot about that message.
However, in fourth case, it actually saves that replay as "temp_mpr" in a same way I showed it in that previous attachment.
I tested this on 0.6U.exe as well, there, you can save it as temp_mpr (it actually says that), but it will be immediately removed from replays. The only way it won't be removed immediately if you're watching that specific replay in another LFS instance at the same time when you're saving it as "temp_mpr"
So, I just found it strange and it could be potential bug that 0.6U14 actually disallows to save replay as "temp_mpr" but if you're watching that specific (or now Live) replay on another LFS.exe from same folder, it actually allows and saves that replay in that name.
Like I said, it doesn't make sense to do that, so maybe it should be better to prohibit saving replays as "temp_mpr" or at very least, rename them automatically (probably in a same way how auto-save function names replays)
I think I found a small bug in messages. I tested this on both 0.6U and 0.6U14 hosts. It's possible to reproduce this bug, if you have one LFS instance in multiplayer race and then open another LFS instance to watch that temp_mpr.
Now this doesn't make sense, but if in that LFS instance, where you are in server, you save that replay as "temp_mpr", it says correctly that it could not rename temp_mpr - copied instead. However, immediately after that, it says "Saved MP replay - temp_mpr", even though that replay's name is clearly not temp_mpr.
In this case, should it say "Saved MP replay - [that replay's eventual name]" instead?
I attached one screenshot about this.
Hi!
I've watched couple events which have used this as a Livestream partner and I'm really impressed how well you handle these events
However, I have couple questions about this.
1) On your website (https://simbroadcasts.tv/about), you mention that there will be Live Timing coming soon. Is this going to be something similar to Wollet/Boothy/MoE-tracker (https://www.lfs.net/forum/thread/73414)?
2) Degats mentioned that this broadcast software will be released to public at some point in the future (https://www.lfs.net/forum/post/1958536#post1958536). If that's the case, could it be possible to use this software with AI's as well so it would be possible to use this both in Single Player and Multiplayer-modes (similarly how can you use TV Director in both of these modes)?
I assume that it could be possible, since the data which displays driver names (in standings etc.) looks to be taken from in-game racer names, not from usernames (again, in a similar way how TV Director displays that data in standings).
If yes, it's possible for me to be a beta tester especially for that thing, since it's really easy for me to organize AI-events in multiplayer as I have several S3-licensed accounts
I've watched couple events which have used this as a Livestream partner and I'm really impressed how well you handle these events
However, I have couple questions about this.
1) On your website (https://simbroadcasts.tv/about), you mention that there will be Live Timing coming soon. Is this going to be something similar to Wollet/Boothy/MoE-tracker (https://www.lfs.net/forum/thread/73414)?
2) Degats mentioned that this broadcast software will be released to public at some point in the future (https://www.lfs.net/forum/post/1958536#post1958536). If that's the case, could it be possible to use this software with AI's as well so it would be possible to use this both in Single Player and Multiplayer-modes (similarly how can you use TV Director in both of these modes)?
I assume that it could be possible, since the data which displays driver names (in standings etc.) looks to be taken from in-game racer names, not from usernames (again, in a similar way how TV Director displays that data in standings).
If yes, it's possible for me to be a beta tester especially for that thing, since it's really easy for me to organize AI-events in multiplayer as I have several S3-licensed accounts
Small question related to that AI-thing: since it requires us to connect to online to test it, could we test this patch on hosts rented on LFS.net or is the only way to test this is to download a Dedi host for that patch or start a new server from LFS itself?
About the AI-thing itself: I think up to 24 is great as I already have a lot of situations where 3 AI's is not enough for me. Those situations vary for having at least 5 AI's per player to having about 15 AI's per player.
However, if having 24 AI's per player is tough for connections, you could make a case for allowing up to 20 AI's per player. There are two reasons why I think that's a good number:
1) LFS has 20 cars, so players could test every car at the same time
2) At the moment, up to 40 (AI-)drivers can race on track at the same time, so you could have full grid while having only 2 users on server.
About the AI-thing itself: I think up to 24 is great as I already have a lot of situations where 3 AI's is not enough for me. Those situations vary for having at least 5 AI's per player to having about 15 AI's per player.
However, if having 24 AI's per player is tough for connections, you could make a case for allowing up to 20 AI's per player. There are two reasons why I think that's a good number:
1) LFS has 20 cars, so players could test every car at the same time
2) At the moment, up to 40 (AI-)drivers can race on track at the same time, so you could have full grid while having only 2 users on server.
It's not possible at the moment, sorry.
Unless you create another account (and buy another license) and have that user add 3 more AI's. Alternatively, you can just invite/ask another person to add his/her own AI-drivers (or if you have admin privileges, you can use command /uai [username] to add that user's AI-drivers by yourself)
Unless you create another account (and buy another license) and have that user add 3 more AI's. Alternatively, you can just invite/ask another person to add his/her own AI-drivers (or if you have admin privileges, you can use command /uai [username] to add that user's AI-drivers by yourself)
SRT is very likely ceasing organizing races
Hi guys and girls, Tankslacno here.
You might've been noticing that I've been missing from LFS and SRT for about 2 months. And that is because ultimately I've decided that I want to leave SRT-team and quit organizing these races. I left SRT yesterday.
Obviously this is not an easy decision for me, SRT has been part of my life for over 5 and ½ years, so just saying good bye after all of this ain't easy. There are a lot of reasons why I want to leave SRT, but it eventually just boils down to the reason of not having nearly that same amount of passion and motivation to organize these races I used to have few years ago.
I know that for some of you it may not be easy to understand, but for like a past year this Tournament Directing in SRT has been something I've been needing to do just because I have to do this. Not because I like this. So for past year organizing these races has just been something I don't want do anymore. I have had a feeling that if I would keep doing this, it would eventually affect negatively to my life and I certainly don't want that. I'm sure that quitting this is a big relief and absolutely right decision for me. My health is definitely more important than doing this.
For past year I had a plan that I want to quit organizing these races in SRT when year 2021 ends. Why? Because I calculated that I would've broken both these milestones:
- Organize over 1000 races
- Organize over 100 series
(For those who don't know, SRT started to organize races in April 27, 2014, it just expanded to here in 2017)
But that fire-incident which happened in May 2019 changed my plans. It was pretty much last straw for me, because that destroyed our servers and efficiently put this on hiatus. Server was supposed to open this month but it didn't. Very last nail in the coffin for me was the fact that opening that server from it's provider would've cost a lot more than it did this year/originally would have.
This means that unless someone else wants to continue organizing these races, SRT will cease organizing races from LFS.
But don't get me wrong, I have nothing against SRT and LFS. SRT has great members both as persons and drivers. And I'm not quitting LFS, as I'm still working at least as a translator for this game and testing those new patches. I just want to quit Tournament Directing via SRT.
In future, I may host Nick Arcade/Thrown Controllers-style game show for LFS(-drivers). That would be possible as I'm currently working as a freelance-Game Show Designer/Host. That job is kinda like successor for this. We'll see how that goes.
To everybody in SRT, to all racers and to anyone who even visited our server just for one second, thank you so much from the very bottom of my heart! I love you guys and girls so much!
Take care of yourselves!
-Tankslacno/Traceur
You might've been noticing that I've been missing from LFS and SRT for about 2 months. And that is because ultimately I've decided that I want to leave SRT-team and quit organizing these races. I left SRT yesterday.
Obviously this is not an easy decision for me, SRT has been part of my life for over 5 and ½ years, so just saying good bye after all of this ain't easy. There are a lot of reasons why I want to leave SRT, but it eventually just boils down to the reason of not having nearly that same amount of passion and motivation to organize these races I used to have few years ago.
I know that for some of you it may not be easy to understand, but for like a past year this Tournament Directing in SRT has been something I've been needing to do just because I have to do this. Not because I like this. So for past year organizing these races has just been something I don't want do anymore. I have had a feeling that if I would keep doing this, it would eventually affect negatively to my life and I certainly don't want that. I'm sure that quitting this is a big relief and absolutely right decision for me. My health is definitely more important than doing this.
For past year I had a plan that I want to quit organizing these races in SRT when year 2021 ends. Why? Because I calculated that I would've broken both these milestones:
- Organize over 1000 races
- Organize over 100 series
(For those who don't know, SRT started to organize races in April 27, 2014, it just expanded to here in 2017)
But that fire-incident which happened in May 2019 changed my plans. It was pretty much last straw for me, because that destroyed our servers and efficiently put this on hiatus. Server was supposed to open this month but it didn't. Very last nail in the coffin for me was the fact that opening that server from it's provider would've cost a lot more than it did this year/originally would have.
This means that unless someone else wants to continue organizing these races, SRT will cease organizing races from LFS.
But don't get me wrong, I have nothing against SRT and LFS. SRT has great members both as persons and drivers. And I'm not quitting LFS, as I'm still working at least as a translator for this game and testing those new patches. I just want to quit Tournament Directing via SRT.
In future, I may host Nick Arcade/Thrown Controllers-style game show for LFS(-drivers). That would be possible as I'm currently working as a freelance-Game Show Designer/Host. That job is kinda like successor for this. We'll see how that goes.
To everybody in SRT, to all racers and to anyone who even visited our server just for one second, thank you so much from the very bottom of my heart! I love you guys and girls so much!
Take care of yourselves!
-Tankslacno/Traceur
Last edited by tankslacno, .
Week 26 Events:
No races on this week either. But good news! Got a message that server should open in early July.
No races on this week either. But good news! Got a message that server should open in early July.
Week 25 Events:
No races on this week either. Still no idea when server will open again
No races on this week either. Still no idea when server will open again
Week 24 Events:
No races on this week either. Well at least SRT is having a meeting with it's members this weekend so at least that's something.
No races on this week either. Well at least SRT is having a meeting with it's members this weekend so at least that's something.
Week 23 Events:
No races on this week either. Still no idea when this server will open again. Sorry
No races on this week either. Still no idea when this server will open again. Sorry
Week 22 Events:
No races on this week either. Sorry
No races on this week either. Sorry
Week 21 Events:
No races, that fire incident is worse than we expected. Sorry
No races, that fire incident is worse than we expected. Sorry
Week 20 Events:
Unfortunately, due to very unfortunate force majeure-situation (fire) happened in same place where SRT's server is located, SRT's server is closed until further notice. So this week does not have races at all. And no idea when we can have races in that server again.
So sorry for this.
Unfortunately, due to very unfortunate force majeure-situation (fire) happened in same place where SRT's server is located, SRT's server is closed until further notice. So this week does not have races at all. And no idea when we can have races in that server again.
So sorry for this.
FGED GREDG RDFGDR GSFDG