The online racing simulator
Searching in All forums
(932 results)
felplacerad
S3 licensed
Quote from Sobis :Is this down or just didn't refresh yet?

I'm not aware of any issues. The update interval is 10 minutes (edit: but your client may update less often, of course).
Last edited by felplacerad, .
felplacerad
S3 licensed
Maybe you can ask this guy where he got his logo from. Looks almost identical - Just a different palette and orientation.

... Or this fellow LFSer.

Edit: By the way, initially I misread your question and thought you were asking for the original image rather than the original creator. I did spend a little time trying to find the original source but only came up with not very legitimate looking "free" clipart sites that did not appear to give proper credit in any of their images (like this one, for example).
Last edited by felplacerad, .
felplacerad
S3 licensed
Made another small little adjustment so that line breaks (<br>) are not stripped from the feed. I took me 5 years to realize that I had made a mistake. But now long posts are easier to read. I use Flym but it should work equally well in Feedly and other RSS readers.

Edit: Hmm, perhaps I should keep images too .... Uhmm
Last edited by felplacerad, .
felplacerad
S3 licensed
Quote from felplacerad :
Anyway. When I find the time (probably tomorrow) I'll make a little adjustment to the feed to correct a small issue I noticed with Feedly. The item title (as well as the "Visit Website" button that appears when you expand an item) leads nowhere rather than to the post. This happens because Feedly (to me, incorrectly) uses the Feed's <guid> element rather than the <link> element as the reference for the links.

I suspect that this change will cause a large number of duplicate items.

It's been done. And as I suspected it did trigger a bunch of "new" items to appear. But not to be worried, it was just a one-off thing to fix the broken links.
felplacerad
S3 licensed
Yup. I got that.

It's an active thread with up to 50 posts a day. Sometimes someone will post at the same time Feedly decides to refresh my feed. There's nothing I can do about that.

Thanks for the interest, though. I'm glad people find the feed useful. Smile
felplacerad
S3 licensed
Quote from LakynVonLegendaus :Again the times match.

But don't bother with it lol

Yeah, no. I won't. I stand by my previous conclusion. Smile

Also, I just noticed another Feedly "quirk" It doesn't display post times correctly. Rather than displaying when a post was published (as described in the <pubDate> element), it displays the time the was received (eg: when Feedly refreshed my feed).

Perhaps you've noticed that both entries in your notification appears to have been posted "8 minutes ago" when, in fact, they were posted an hour apart. Perhaps that may add to the confusion.

Edit: For my own piece of mind I'll post each visit by Feedly's "fetcher" bot throughout the day:

8.29.198.25 - - [12/Nov/2019:08:38:37 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 35698 "
8.29.198.26 - - [12/Nov/2019:08:49:18 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 35698 "
8.29.198.25 - - [12/Nov/2019:11:39:25 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36249 "
8.29.198.27 - - [12/Nov/2019:11:50:14 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36249 "
8.29.198.27 - - [12/Nov/2019:14:40:25 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36518 "
8.29.198.26 - - [12/Nov/2019:14:51:00 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36975 "
8.29.198.27 - - [12/Nov/2019:17:41:20 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36975 "
8.29.198.26 - - [12/Nov/2019:17:52:13 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36975 "
8.29.198.27 - - [12/Nov/2019:20:42:17 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 37229 "
8.29.198.25 - - [12/Nov/2019:20:52:58 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 37229 "
8.29.198.35 - - [12/Nov/2019:21:48:02 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 37382 "
8.29.198.36 - - [12/Nov/2019:21:48:12 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 37382 "
8.29.198.33 - - [12/Nov/2019:21:48:13 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 37382 "
8.29.198.25 - - [12/Nov/2019:23:43:20 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 37759 "
8.29.198.27 - - [12/Nov/2019:23:53:48 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 37759 "

Last edited by felplacerad, .
felplacerad
S3 licensed
Aaand there we go:

8.29.198.27 - - [12/Nov/2019:20:42:17 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 37229 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 3 subscribers; like FeedFetcher-Google)"

Feedly just refreshed (after being idle for about 3 hours), and like clockwork the notification(s) appeared in Feedly Notifier. The posts that eclipsed and gu3st created meanwhile did not trigger any notifications.

Also, now that Feedly has refreshed it might have read the ttl setting that I had added since the last visit. if Feedly does in fact adhere to that setting the somewhat arbitrary reresh intervals should be fixed too. We'll see.

Edit: Nope. Looks like Feedly will update whenever it feels like it:

Quote from Feedly :How often will Fetcher retrieve my feeds?

Fetcher shouldn't retrieve feeds from most sites more than once every hour on average. Some frequently updated sites may be refreshed more often. Note, however, that due to network delays, it's possible that Fetcher may briefly appear to retrieve your feeds more frequently.

Last edited by felplacerad, .
felplacerad
S3 licensed
Heh,

Right now we have a "pending" post by Scawen posted at 18:47. Oops, actually two (another one at 18:51). They have already been added to my feed, but they're not showing up in Feedly yet (the time is 19:01). It'll be interesting to see when they're added to Feedly (I'll see it in the access logs) and when the notification appears.

Note that pressing the refresh button in Feedly won't actually make it refresh the feed. It's just a GUI thing.

Edit: I went ahead and added the <ttl> element. Hopefully it'll make Feedly refresh more regularly.
Last edited by felplacerad, .
felplacerad
S3 licensed
Quote from LakynVonLegendaus :Yes, that is a post by Scawen and that post was created at 14:47. And the notification was triggered by a post by driftchris at 17:42.

Again, that's just a coincidence. Neither my feed or Feedly knows when someone posts, so notifications can not be triggered by such an event - The information simply isn't there (unless Feedly has created their own scraper for lfsforum.net and - for some reason - concatenates it with my feed. But that would be some next-level insanity Ya right)

That said, once I get around making the fix I mentioned earlier, I'll add an <ttl> element indicating that aggregators such as Feedly should update more regularly.
Last edited by felplacerad, .
felplacerad
S3 licensed
Quote from LakynVonLegendaus :For the third time - the feed is fine. My problem is that sometimes the notifications are being triggered by wrong posts.

This time it wasn't Flotch though. So at least a change Big grin

But that is in fact a notification about a post that Scawen made earlier - in which he quotes someone. That's the intended behavior.

https://www.lfs.net/forum/post/1951725#post1951725

The timing of driftchris posting at the same time Feedly / Feedly Notifier updated is just a coincidence (I can't really make sense of Feedly's update interval).

8.29.198.25 - - [12/Nov/2019:08:38:37 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 35698 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 3 subscribers; like FeedFetcher-Google)"
8.29.198.26 - - [12/Nov/2019:08:49:17 +0100] "GET /lfsdev-rss HTTP/1.1" 301 3785 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 2 subscribers; like FeedFetcher-Google)"
8.29.198.26 - - [12/Nov/2019:08:49:18 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 35698 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 2 subscribers; like FeedFetcher-Google)"
8.29.198.25 - - [12/Nov/2019:11:39:25 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36249 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 3 subscribers; like FeedFetcher-Google)"
8.29.198.27 - - [12/Nov/2019:11:50:14 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36249 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 2 subscribers; like FeedFetcher-Google)"
8.29.198.27 - - [12/Nov/2019:14:40:25 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36518 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 3 subscribers; like FeedFetcher-Google)"
8.29.198.26 - - [12/Nov/2019:14:51:00 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36975 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 2 subscribers; like FeedFetcher-Google)"
8.29.198.27 - - [12/Nov/2019:17:41:20 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36975 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 3 subscribers; like FeedFetcher-Google)"
8.29.198.26 - - [12/Nov/2019:17:52:13 +0100] "GET /lfsdev-rss/ HTTP/1.1" 200 36975 "-" "Feedly/1.0 (+http://www.feedly.com/fetcher.html; 2 subscribers; like FeedFetcher-Google)"

Last edited by felplacerad, .
felplacerad
S3 licensed
So, did the following post show up in your feed? Seems fine to me. Uhmm

https://www.lfs.net/forum/post/1951727#post1951727

It appears to fit all of the discussed criteria.

Anyway. When I find the time (probably tomorrow) I'll make a little adjustment to the feed to correct a small issue I noticed with Feedly. The item title (as well as the "Visit Website" button that appears when you expand an item) leads nowhere rather than to the post. This happens because Feedly (to me, incorrectly) uses the Feed's <guid> element rather than the <link> element as the reference for the links.

I suspect that this change will cause a large number of duplicate items.
Last edited by felplacerad, .
felplacerad
S3 licensed
I don't know! For me, everything appears to be working fine.
Last edited by felplacerad, .
felplacerad
S3 licensed
Basically, my "scraper" visits the forum, searches for posts by Scawen (as well as Victor and Eric) and adds the content of the posts to a RSS feed.

I wasn't familiar with with Feedly or the Feedly Notifier extension, but after looking at them quickly I gather that it'd work something like this:
  1. The scraper visits the forum and searches for developer posts.
  2. New posts are added to the "original" RSS feed.
  3. In Feedly, you've added the RSS feed as a source, effectively creating a "copy" of the feed.
  4. In Firefox, you've installed Feedly Notifier and logged in with your Feedly account, allowing the extension to monitor Feedly's copy.
So, when a new post is added to the original RSS feed, Feedly adds it to it's own copy, and finally Feedly Notifier displays a notification in Firefox / your desktop.

Since I can't find any posts by Flotch in the original RSS feed (view-source:https://www.liveforspeed.se/lfsdev-rss) or in Feedly (see screenshot) the problem must be with the Feedly Notifier extension -- Though I did not get any notifications from Flotch when setting it up in Firefox.

Since the posts sometimes contain HTML (for example when people are quoting or including links or images) I would not be surprised that certain parsers may interpret the feed incorrectly, but since the feed does in fact validate I can't really think of something I could do differently.

That said, I'll keep the Feedly Notifier extension in Firefox for a while and keep an eye on it.

Edit: Would you too please log in to Feedly and check if any posts by Flotch are showing up there? If not, the problem is most definitely with Feedly Notifier.
Last edited by felplacerad, .
felplacerad
S3 licensed
Oh, that's weird!

I can't find an instance of that happening, though?

I did note that Scawen quoted Flotch at least 10 times (for example in post 1951527 / guid 2293 - screenshot attached).

Would it be possible for you to give an example of this happening?
Last edited by felplacerad, .
felplacerad
S3 licensed
Gah, the SSL/TLS certificate expired almost a month ago and I forgot to renew it. All fixed now. Sorry about this.

Edit: Crontab added. We'll see in three (~) months if it worked (note to self: Thursday, December 19, 2019). Tongue
Last edited by felplacerad, .
felplacerad
S3 licensed
Quote from pedro.de.marco :I need to know what rules must be made in order to run a dedicated server.

Incoming: 63392 TCP & UDP (from "anywhere")
Outgoing: 29339 TCP (to 188.122.74.153 / master.lfs.net*)

* master.lfs.net or master.liveforspeed.net. I'm not sure which is the "real" DNS record for the master server, but they both resolve to the same IP so it doesn't really matter.
Last edited by felplacerad, .
felplacerad
S3 licensed
Hmm .... As I understand it, LFS doesn't know/care whether the PS3 controller is connected via USB or Bluetooth -- If the device is indeed properly paired and it works with other games with just a Bluetooth connection you should be good to go, without having to mess around with sixad/sixpair.


Can you please confirm whether jstest registers input from /dev/input/js0 (or whatever device the PS3 controller is registered as)?.
felplacerad
S3 licensed
Hello Caleb642,

If you have been able to successfully pair the PS3 controller as a device with the OS (you can test this with the "jstest" utility, for example), LFS should not have any problems using the controller -- But you need to configure the axes and buttons manually. Instructions can be found on the wiki.

I did a quick test with my Playstation 3 controller. With USB, it worked out of the box. But with Bluetooth, however, it would not pair without some hassle (this a problem with Ubuntu, not LFS).

That said, I was able to get my PS3 controller working with a patched version of the "sixpair" utility. I followed the "For older versions of RetroPie" instructions which were rather straight forward.

In the attached screenshot, LFS using using my PS3 controller connected via Bluetooth.
Last edited by felplacerad, .
felplacerad
S3 licensed
What do you mean by output, exactly? Are you simply referring to the physics simulation or are you thinking of OutSim and/or OutGauge?

As for the simulation, sure. Each tire may, individually, slip/loose traction when accelerating, braking or turning, and many parameters such as surface, tire type, tire temperature, whether the tire has dirt on it or not and so on may also result in loss of traction for each individual tire.

You can use the Forces View (F) and Tyre temperature/wear & clutch temperature display (F9) to verify this.

The Brakes section of the Advanced Setup Guide has an example of how the Forces View can be used to determine that the brake balance is set too low, forcing the rear wheels to lock up/loose traction while the front are still gripping, for example.
felplacerad
S3 licensed
Quote from Degats :Obligatory comparisons

Thank you for doing these! Not only do I personally enjoy these comparisons, but they, along with ScaViEr's progress reports, are also valuable when I (once a year) get in touch with the sponsors of liveforspeed.se. Showing them these comparisons and a summary of the progress since the year before is an effective way to show them that LFS is still very much alive and it's worth keeping the website online. Smile
felplacerad
S3 licensed
Quote from pedro.de.marco :I used 64bit as base image and had to add-architecture (it's in the instructions wiki)

Yes, I am familiar with the wiki instructions. I wrote the articles for running LFS on Linux and macOS.

It's good that you're making progress. I'll leave you to it, then. Smile
felplacerad
S3 licensed
Quote from pedro.de.marco :I will also try to run DCon.exe on docker image and try to communicate with that! The bad thing about docker is that, it's only an image. You should reinstall ALL after turning it off.

I'd suggest holding off doing an implementation in Docker until you you've got it running in- and feel comfortable with the ins and outs of VirtualBox.

One step at a time, you know.
felplacerad
S3 licensed
Quote from pedro.de.marco :/ip=127.0.0.1

127.0.0.1 (the loopback address) definitely won't as intended. With that configuration only the host itself (e.g. the guest vm) will be able to connect.

I'm off to work now but I'll try to walk you through this tonight. Smile
felplacerad
S3 licensed
Quote from pedro.de.marco :btw: There is an LFS linux version, available as a "snap package" on ubuntu. Which does not install properly at the moment.

We're aware.

So it's broken, huh? Would you please reach out to the maintainer (mmtrt) and create and issue describing the problem you encounter installing the snap? Having a broken LFS installer in the Ubuntu Snap Store doesn't benefit anyone. I suppose creating an issue in his GitHub repo is the way to do it.

Edit: As for this configuration:
// optional: local specified ip address
//ip=xxx.xxx.xxx.xxx

I haven't managed an LFS host in years, but I'm guessing /ip= is the equivalent of "listen on" or "bind to" configuration options seen in most server software. Meaning that you should specify the IP address of the interface that you wish to accepting incoming connections on.

For example, consider the following:
ifconfig | egrep 'flags|inet '

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33152
inet 127.0.0.1 netmask 0xff000000
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 213.x.y.z netmask 0xfffff800 broadcast 213.x.y.z
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255

In this case, em0 is my external IP. If I was to configure an LFS host to accept connections from the Interhet, I would specify that IP. em1, on the other hand (obviously) is the IP address on the LAN, so if I was to accept only connections from the LAN, I would specify that IP.

I'm guessing that since this configuration is optional, leaving it commented out would bind the host to 0.0.0.0, meaning that connections would be accepted from either interface. So I'm not really sure if it's necessary for you to worry about that setting at all.

Edit 2: Alright so I was right about the /ip= setting. the host does bind to the IP address that you specify, eg:

#//ip=xxx.xxx.xxx
netstat -tulpn | grep wineserver
tcp 0 0 0.0.0.0:63392 0.0.0.0:* LISTEN 5759/wineserver64

# /ip=213.x.y.z
netstat -tulpn | grep wineserver
tcp 0 0 213.x.y.z:63392 0.0.0.0:* LISTEN 5698/wineserver64

So, either leave it commented out or specify the IP address of the interface connected to the Internet. You can find out with the "ip addr" and "ip r" commands if you need to check.

Quote from pedro.de.marco :"v-box" network setup is: NAT, port forwarding. The same port number 63392 host and guest.
The connection type was "TCP" and I got the error.
Then I changed it to "UDP" and "ClientConnect : connect failed"

You need to forward TCP as well as UDP traffic. Or switch to "bridged" rather than "NAT" in the guest settings, then you won't have to worry about port forwarding in VirtualBox.
Last edited by felplacerad, .
felplacerad
S3 licensed
The site is down temporarily. It'll be back up next week. Smile

Edit: Should be up again. Sorry about the hickup. Smile
Last edited by felplacerad, .
FGED GREDG RDFGDR GSFDG