Regarding controller type, I don't necessarily have that information. Only if a setup is extracted from a hotlap can I know what controller was used with it. So for full usability that would have to become one more option people have to fill in themselves.
Setup names can now be edited. You can use pretty much any UTF8 character you like, and LFS colour codes are allowed as well. Note that setup names can only be 15 (normal) characters long.
I've also done some track and class auto detection on the existing setups. The same check will also be applied to newly added setups.
That setup was set to private, but was also a forum post attachment. And in that case it automatically becomes public again. I'm now displaying public in that case.
The filtering issue should be solved now, too.
EDIT - one thing i wonder about though .. if you set a setup to Team, and then set the browsing filter to private, you won't see that setup at the moment.
The logic now is that you only want setups set to Private. But my mind tells me that when I set the filter to Private, I want my setups. But then I'd have to change the wording of the filter, as its meaning slightly changes.
I wonder how you see it?
EDIT 2 - the filter would then have these options :
my team's setups
I've added an extra filter for private / team (+private) / any.
I've removed the submit button as that's just an annoying extra click.
Your settings now also persist for the duration of your browsing session, for consistency.
Hm there's no such list atm. It's just that any team member's setups will now be visible in the existing lists, where previously they would not (as well as setup details page and setup download), provided they have set the setup access level to Team.
I suppose you would like a way to only see team setups?
Team access to setups is now functional as well.
The team editor on lfsworld still needs to be used to compose the members of a team, which is an editor that can do with improvement .. but the access bit on the setup side here works at least.
hmm, on setup extraction? I definitely check for file length and do a whole bunch of header checks. I can do some more sanity checks on the body though (and have now).
How do you mean a short description? The ability to add one? Or are you missing seeing notes anywhere? I do still have to add the ability for anyone to add a note to any setup, in general.
I considered wr vs benchmark and thought benchmark was a bit more interesting because it gives you a bit better idea of how relatively good your hotlaps are. If you only see green, then you are doing very well! It's not possible to show that with the WR time only. Ideally I'd show both like on lfsworld, but there's no room in the table left.
An api would be nice to have yep. Probably will have to make one anyway if LFS itself wants to download them at some point.
Oh about distance to benchamark not being readable .. it reads fine here. Not sure what you're seeing. Maybe can do a screenie?
I am however known for being very bad with colours though
Here is the url for the public pages : https://www.lfs.net/files
This will get its own link in the menu bar, but for now i'm keeping the link in this thread only, so you guys can give it a test.
The main setup listing is a bit empty atm, but that's because pretty much all of the current setups were imported from forum attachments, for which I had no classification or track usage data.
Hopefully people will fill in this information and that reminds me I need to make those values editable more easily, directly before or after upload.
Could you try once again? I will then get some more debug information and can have a closer look.
You can simply and safely select all your hotlaps and import them again. It will skip those that are already imported.
Ok the next part is now available : hotlap setup import.
If you have hotlaps uploaded at LFS World, you will see an "Import your hotlap setups" button on your setups page.
Clicking that will give you an overview of your hotlaps allowing you to select from which you want to extract the setups. You can also indicate the access level you want to give them (private, team, public).
The importer will automatically fill in all car setup details like the track it was driven on and it will keep a record of the hotlap it was extracted from, so that this information can be printed on other pages. That reminds me I still have to do that.
The public setup browser is coming along nicely and is nearing completion. Could be out later tonight, or otherwise tomorrow.
Actually I have two templates - one for plain text and one for html. So it's not that weird.
Yes, I suppose I could create a mechanism that converts the html version to plain text but just can't be bothered in this case.