Yo, still around too, visiting the forums from time to time. Still having my G27, still waiting for some spare time and new content to revive my old gaming pc. :-)
According to VW technical data the 2.0 FSI (147kW) can do 235kph which is 146mph. The 1.4 TSI (118 kW) can do 218kph (135mph). I don't know which engine the VWS in LFS will have.
Maybe you can change gear ratio in LFS, I think you then could gain some more speed.
No need to insult me here. I know how to install/use Windows very well.
Edit: And don't alter my statements when quoting! This is not very fair! I have written "most mac users _don't want_ or even are not able..."! (The word "even" was meant to soften the "most", sorry If anyone got me wrong there.)
Haha. Are you serious?
Yes, others have said this, no need to repeat them. I replied to this issue.
Wow, finally a wise argument from you.
This came to my mind, too. OS X does support FFB since 10.2.9 or so, don't know how it will work with a decent wheel.
Logitech doesn't have mac drivers, I could imagine there would be some problems (setting max rotation, spring and strength settings). With EA releasing NFS for mac, maybe Logitech wakes up and provides drivers.
Naaah. If I've understood cider correctly, the cost would be minimal, like 1d of additional work per release. (You just have to compile the same sources with some cider-tool.)
While 10000 being a bit too optimistic, 1000 (in a short term, i.e. a year or so) sounds quite realistic.
You are totally right, because mac users who want to sim race do not have another option at this time.
But there are a lot of mac users who don't know that they want to sim race, because they don't know LFS. If there would be a mac version of LFS, they would know.
Might be true for games making heavy use of directx librarys. But I think the most CPU intensive stuff happening in LFS is physics, and I can't believe that they use any MS library for complex calculations like this.
True. More Exactly: It would be slower than running native. But as all intel macs have decent processors (core duo 2GHz and up), this wouldn't be an issue I think.
False.
First, you have to buy a Windows licence (or be a pirate).
Then you have to install and maintain it on your system. It does not only cost several GB of harddisk space, most mac users don't want or even are not able to install/use Windows properly.
with EA releasing their major new titles (Command and Conquer 3, Battlefield 2142, Need For Speed Carbon, and Harry Potter) for mac in July, I want to point the devs to Transgaming's "Cider" (which is also the thing EA will be using), which is an engine to port games to Intel Macs running OS X without touching the code.
Of course cider isn't for free. I don't know how much it costs, but a statement in their "Sales sheet" lets me believe that an inquiry (by the devs) could be worthwile. It reads:
I think there are a lot of mac users out there who would be interested in LFS, if it was available on their platform. Especially in the US, where macs are more widespread than in europe, LFS could gain quite some marketshare.
Yes I've also found that screen capturing is deadly slow.
As I have noted above, the shoutcast-streaming of vlc is undocumented. In the vlc forums I've read that you have to use the command line to use this feature.
I don't know exactly if you could use another container format than nsv for your shoutcast server.
The solution I proposed earlier simply doesn't work with your current infrastructure. What you would need is a (virtual) server with a high traffic volume included. On this server you run vlc as a relay, connecting to the stream on the broadcasting pc, and let many users connect to it.
I grant you that this proposal wasn't something to be implemented immediately. If you plan to improve OLFSTV in the future, it could be something to take into account.
VLC, like I said. You don't need any other app with this setup.
This server is theoretically able to handle 100 people watching with this quality. As this would cause 44GB of traffic per hour, and this server don't have any traffic inclusive, this would cause me some money.
Tys already noted that he has a server with some spare-bandwidth available?
Thats not true.
First, VLC is able to play everything encoded with VLC.
If you choose for example WMV2, I think quite everyone is able to play this just with any videoplayer on windows (windows media player, for example).
If you choose any another codec (say mpeg4), they just have to install VLC (which they should do anyway, because it's the best and most compatible videoplayer out there)
I've just played around a bit, here is what I've discovered:
VLC is a really neat solution for this kind of tasks. I hooked up the TV-Out of my graphics card to the video input of a rather old TV-Card, and was able to capture, preprocess and encode the stream with various codecs (mpeg4, divx3, wmv2), and providing a http-stream. All on my PC, everything with one single instance of VLC.
The result was really great, although only 320x240 (limitation of my crappy TV-card), but smooth 25fps and 92kbps mono audio (mp3).
I've also tested relaying the stream on a server with higher bandwidth availability, also with VLC, which worked out fine.
I would really encourage you to give this setup a try.