Quote from dawesdust_12 :

Snazzy Vic

About the Mac version, it might need some touchy-feely by a OSX machine, else the permissions are a bit messed.

EDIT: This coming from the Mac user with a OSX so messed up, it dies on start up..

Well, don't forget that I originally reported it and my OSX is not messed up at all!

See that message, Victor. The problem and the fix are described there. I can fix your next versions in the same way, if you want. PM me, in this case.

LOL. That explains everything! Is that a brand new install?

OK, now to work around it: If you have a backup of your previous LFS folder, copy the views folder that's in its data folder, and paste it at the same place into your new install. If you don't have a backup:

1. launch LFS and go on track in single player
2. switch to the custom view (the one that shows only the wheels)
3. press SHIFT+O and click on Custom
4. change some setting in the view (anything) and click OK. LFS will then create the views folder (maybe you could create it by hand, but I'm not sure if it wouldn't cause permissions issues in Vista, so better go the safe way).
5. quit LFS.
6. Install FlipCams. This time you shouldn't get the error.

I have another feature idea for LFS Remote, triggered by the Masters of Endurance's 24 hours. Please see this post.

I was watching the Masters of Endurance's 24 hours race via both the live stream and LFS Remote, and seeing the mess that followed the server crash reminded me of a lot of similar situations when the grid had to be reformed for one reason or another. It always takes much longer than it should, and each time I get to witness such a situation, I'm quite glad that I'm not the admin.

It gave me a couple of ideas that I think could improve those situations a lot.

First, a "quick and easy" one: LFS Remote could be very handy in these cases if it had an option to automatically pause the playing when it loses connection to the server (instead of closing) and to keep it paused until the user presses a button to start playing again. This would allow an admin to keep seeing the timesheet and the position of each car on track at the time the server crashed. Of course it would still allow to "jump" to a given car by clicking on its name, to zoom in and out, and so on. It might also be handy if you could pause it at any point by clicking on a button (for example an admin could pause it at the end of the quali and start it again a couple of laps in the race when it's clear the race won't have to be restarted from the grid).

Second, LFS itself could have an admin command to restore the grid as it was at the end of a given mpr. By default it would use the last mpr it saved, but it should also have an option to select another one, for example to restore the grid from the last quali if the server crashed on lap 2 of the race). It would then provide two ways of restarting the race:

1. from the starting grid for a new start, or
2. from the last position of each car on track for a restart (in which case it would be absolutely great if the whole timesheet was restored too, with laps and times, like the server crash didn't happen).

In both cases LFS would put the cars on track and run the usual countdown to start the race.

Last edited by FL!P, Sat 19 Jan 2008, 20:22.

Sorry to read you're still having that problem, pastorius. I hope it doesn't look like I've been ignoring you, but unfortunately I cannot test it myself because I don't have Vista. I'm trying to get a couple of my team mates to run some tests for me, but they've been too busy so far.

One question, though: you do have a folder named "views" in the "data" folder of your LFS folder, right?

OK, then. Here's a fixed version for those not at ease with Terminal.

remote.app.zip 4.3MB.

Last edited by FL!P, Fri 18 Jan 2008, 04:00.

When did you download it, Dustin? Maybe I've got a more recent version, because I got it half an hour ago.

At first the standalone version didn't work on my (Intel-based) MacBook Pro and a "permission denied" error was logged to system.log.

I checked the contents of the remote.app bundle and found that for some reason the permissions of the included Flash player didn't have their execute bit set. I fixed it by running the following from Terminal:

% cd [whatever]/remote.app/Contents/MacOS/
% chmod +x Flash\ Player

Now it works fine.

Wow, this is brilliant, Victor! Quite impressive, too!

I'm using it on Safari on Mac OS X and it works perfectly. I just have a little bug report, in case it hasn't been reported yet: the text input box isn't displayed in full screen mode. Doesn't look like it's on purpose.

Also I was surprised to see on my screen the result of commands entered by others (like /?). Not sure if that's expected but it feels wrong.

Sorry if these have been discussed already, I didn't read the full thread yet.

Last edited by FL!P, Wed 16 Jan 2008, 00:56.

When some car lags, LFS waits a few seconds for the connection to be restored without changing anything. That is if it happens while exiting a corner, for example, the lagging car (as seen from other cars) might keep turning (I just got taken out in a league race that way, because I was on the wrong side of the lagging car). Similarly, if the lag happens just before a braking point, the car will not brake and might collide with the car ahead (happened to me a couple of times too).

I think it would help a lot if LFS triggered an AI to take the wheel of the lagging car on the fly, until it gets the connection back or gives up and times it out. I believe that would prevent many accidents that are due to lag.

I realize that the car might still have to "jump" from the AI's position on track to the real driver's position, when the connection is restored, but I think that jump would usually be smaller than it is now, and at least in the meantime the lagging car's behavior would be predicable.

Well, I think the error message should be self explanatory. Apparently the folder you selected as your LFS folder in FlipCams' installer doesn't contain a folder named data.

1. Make sure your LFS installation works as expected without FlipCams.
2. Make sure you select that LFS folder from FlipCams' installer (and not one of its sub-folder, for example).

If both these points are true and you still get that error, then you found a bug in the installer. In this case, please let me know so I can help you further and fix that bug. Thank you.

Flip

How many of us could honestly say that at one time or another they haven't felt sexually attracted to mice? I know I have.

Tu ferais mieux de bosser ton Anglais ! Mais OK, voilà ton mini manuel.

1. Décompresse l'archive de l'linstalleur, pour obtenir un dossier contenant FlipCams-Installer.exe et un dossier parts.

2. Sans le déplacer, double-clique sur FlipCams-Installer.exe. Il ouvre une fenêtre de dialogue. Sélectionne ton dossier LFS, les raccourcis claviers que tu veux utiliser, et clique sur Install.

3. FlipCams installe les scripts nécessaires ainsi que son exécutable (FlipCams.exe), et duplique le dossier LFS/data/views quatre fois. Quand c'est fait, quitte l'installeur et lance LFS. Pas besoin de lancer FlipCams.exe à la main, il sera lancé automatiquement par LFS.

4. Dans LFS, choisis une voiture et va sur la piste en mode Solo. Si nécessaire, presse V pour afficher la vue personnalisée. Par défaut elle ne montre que les roues de ta bagnole. Disons que tu veux garder cette vue.

5. Tape le raccourci "caméra suivante" que tu as choisi dans FlipCams-Installer (par défault CTRL+F12). Tu vas voir s'afficher FlipCams: CAM 2, mais la vue elle-même ne va pas changer. Ou plutôt elle va changer, mais comme elle a été crée par l'installeur en dupliquant celle qui existait déjà, tu ne peux encore voir aucune différence.

6. Tape SHIFT-O pour accéder aux options, clique sur Vue, puis sur Personnalisé. De là, définis ta seconde caméra (clique sur Chassis pour qu'il soit visible, active les rétros et le compteur, rêgle la position et le champ de vision de la caméra, etc). Quand c'est fini, clique sur OK.

À ce stade, les caméras 1 et 2 sont définies et tu peux passer de l'une à l'autre avec les raccourcis clavier caméra suivante et caméra précédente (par défaut CTRL+12 et CTRL+F11). Répète les étapes 5 et 6 jusqu'à ce que les 5 caméras soient définies.

Voilà, FlipCams est paramétré pour cette voiture. Mais il faudra faire ça (les étapes 4 à 6) pour chaque voiture.

Amuse-toi bien.

Quote from Lateralus :

Interesting. I have a Momo too so I use auto-clutch also. What advantage does the button have on starts?

I press both the clutch and handbrake buttons, switch to first gear, rev the engine, and when the light goes green I just release both buttons. It feels more natural to me and since the clutch slips a bit, at first, I expect the wheels to spin a bit less and therefore have more grip. Can't prove it works, though.

Also, it's probably faster to release a button than pressing the paddle.

Last edited by FL!P, Sat 29 Dec 2007, 02:28.

I have to use auto-clutch because my Momo has only two pedals. But I've also set the clutch to a button that I use at starts and when I have to rejoin.

The car that I find has changed the most is the FO8. Now I think it feels like CTRA's FJR (that has intake restriction and additional weight). I've never driven a Formula V8 IRL, unfortunately, so I may be completely wrong, but I found the FO8 more realistic in X than in Y. More exciting, too.

Quote from NeilPearson :

dont launch lfsrelax until the race and they wont be there. what does it matter anyway?

It matters because lfsRelax causes other buttons to be hidden. Like the grid in the lobby, or the controls in shift+u mode.

Sorry, this is not really an interface bug, but I didn't find a more appropriate thread to post it.

Running X33, I left a server during the first lap of a race, after I got crashed, and when I checked the replay (temp.mpr, which was saved automatically) I found that it doesn't end, like it used to do. Instead, at the moment when I left the server, the cars start displaying the lag label, with an increasing count that seem to never stop. See the attached replay.

This is on XP Pro sp2.

P.S. Thank you very much for the adjustable quick look!

Excellent! Good racing, nice cameras, nice editing, dramatic music... and it features me.

It'd be great if you could post a high res version somewhere!

Oh, I understand now, thanks for the explanation. It sounds like those new settings are saved in the custom view files, then. If this is the case, I'm afraid there's not much FlipCams can do about it, because all it does is renaming the view folders to allow switching between 5 copies of these files. It never opens the files themselves.

I can't try it at the moment, but I think I have a workaround, though. Go to ...\LFS\data\scripts and add the following to paddle.lfs, sequential.lfs and road.lfs:


That should make FlipCams switch automatically to CAM1 each time your car is put on track. Does that help? If it does I could update the installer and add an option to install that command automatically.

Thanks for raising this issue anyway!

Flip

I'm happy with whatever ScaViEr throws at me, in this regard. I think it adds to the realism, because if you were to drive a race car for a team, IRL, you'd (gladly) take what you're given and you'd eventually get used to it (or you'd better to).

Sorry but I'm not sure to understand your problem. FlipCams only affects the custom view and does nothing to the cockpit view (nor to any of the other views). Besides, the sliders of the cockpit view don't affect the custom views at all either, AFAIK.

So if you're saying that using the custom view resets your changes in the cockpit view, I believe that would happen even without FlipCams installed and therefore the bug should be reported to Scawen.

You can do it already. Press Shift+U and play with the settings.

You can move the cam with the arrow keys, rotate it with the mouse (right button), and press Tab for a bird eye view.

Oh come on! The map is the only substitute we have to pit radio and track marshalls.

Give me a pit crew keeping me informed of what's going on around me (is the car behind fighting me for position or is it a lap down, for example) and track marshalls that tell people when they can rejoin safely, and I'll be glad to see the map go. Until then, we need the bloody map!

Yes, this is with the FBM. I already use this method, pulling the paddle first and lifting off the throttle to switch gears, but thanks for the suggestion.

Dunno, maybe it's my throttle pedal that doesn't cut completely, sometimes.