I agree with cargame.nl here. Why urge him to show some restraint, when the whiners aren't showing any?
I never understood all the complaints about the lack of progress of LFS.
- If you think speedy, significant updates were part of the deal when you bought an S2 license: You didn't read carefully.
- If you think complaining, sarcasm, and ranting will stimulate Scavier to work harder: Think again, or perhaps get a brain first.
- If you think Scavier are doing a lousy job developing LFS: Go buy another sim, or create one yourself.
So if there's a progress report from the devs and the main reaction is whining, then I can only agree with cargame.nl's conclusion: Spoiled kids.
It looks like you were trying to read the SPR file directly. LRA can not read these, you first have to create a RAF file from the SPR. The LRA manual (included in the ZIP file) describes how you can do that.
Unfortunately, you can't. This is a limitation of LFS: it can not generate a RAF file for autocross laps, or in any case, a file that contains useful data (see also this post). For the first lap of a single-player race, there is a similar problem: when you instruct LFS to write a RAF file, the car must be some minimum distance before the start/finish line, and at the start of the race, your car is already too close.
People don't "battle" cancer, they are suffering from it. And if some people use the word "battle", then I suspect it's mainly as a cop-out, because they can not deal with the suffering that is involved. They twist the words so they can ignore the misery. They try to see purpose and meaning where there is none.
(Personal background: Two years ago my wife was diagnosed with colon cancer, with additional tumors in liver and lungs. Since then she has undergone surgery 4 times and has had 6 rounds of chemo. At one point we were told that a tumor couldn't be removed and she'd only have a few months to live; the doctor turned out to be mistaken. At the moment there are no tumors, but the long-term survival stats are pretty bad. Our kids aged 9 and 11 still face the prospect of losing their mother within the next coupe of years.)
Good question. And because most of us will eventually succumb to some disease or other, we're all cowards and losers in the end, right?
Um, no. As far as I can see, the RAF files that the current version of LFS generates are practically empty (for open configs, I mean), and can't be used by LRA or by any other analyser. But even if LFS would be updated, then it's unlikely that LRA will be able to handle them. I'll try to explain below.
In a RAF file for a closed config, each sample contains the car's distance from the start line. This measure makes it possible to compare two laps: if car A is at the same distance as car B, then they're at the same spot in the lap (though not at exactly the same X and Y coordinates), and it makes sense to compare their speed etc. For every closed config, LFS also has a PTH file that contains the "path" i.e. the standard trajectory for a lap. The distance I mentioned is measured along this path
AFAIK, open configs don't have such a standard path. So do laps on the Autocross track, BTW: the AU track itself is just a big square, and a lap is only defined by the objects in the layout.
LRA was built with the assumption that such a path is available. I have thought about making it suitable for Autocross laps, but there was no easy solution.
Furthermore, I've stopped further development of LRA (for personal reasons). I'm monitoring this thread only to provide support and to solve serious bugs, should they be discovered. The source code is available in the release, so others could take it on, but I know that that's not everyone's idea of a fun time.
All in all, the chances of being able to analyse open-config laps are pretty thin.
The error message and the grayed-out files both mean that those RAF files do not contain any usable data. The "block count" is the number of car states (= samples) that LFS wrote to the RAF file. You can check that by looking at the file size. If the file contains only some header data, then it will be a few 100 bytes. Valid RAF files are at least 100k, up to a few megabytes.
By "ride height" you probably mean the live height of the wheel, not the one in the setup. That is called "Suspension travel remaining" in LRA, the amount of vertical travel that is left before the wheel hits the bump stop.
Live tyre temps are not available, because LFS doesn't save them in the RAF file. (To be exact: there is one integer number in the RAF file that gives you the temperature in degrees Celsius, across the whole tyre.) In the Properties pane in LRA you can find these as the average tyre temp, but that won't tell you much.
That would be also great for a project I'm working on.
(Not really relevant for the test patch, but I thought I'd chime in with this request.)
I modified LRA, my replay analyser, so that it can grab lap data from InSim. The nice thing about this is that you can then also get laps from multiplayer races (live online races as well as MPR replays). And it saves he hassle of generating a RAF file first, so the drive -> analyse -> improve cycle is much shorter.
I've got it working, but for now it can only read the speed and position of each car. That's a bit thin for an analysis. To be really useful, the lap data should also include the pedals, steer position, and current gear.
You already can, by using the mouse wheel over the Driving Line pane. Clicking the mouse wheel resets the zoom to the default value. The context menu (= right mouse button) also offers the possibility to zoom in and out, although that is a bit cumbersome. But it might be the only possbility if you are using a touchpad.
Just like the previous poster... Very strange.
Again, I have no problems when I try it, so I expect it has something to do with overactive anti-malware apps, or possibly strict download settings in the browser.
I can only give the same suggestions:
- As a test, download some other zip file with an executable (like this one.)
- Try a different browser.
- Send me a PM with your e-mail address, so I can mail LRA to you.
And you like to stress that fact by adding more unfairness?
Funny remark, seeing as it's coming from the U.S. Ever compared crime rates, numbers of people incarcerated, and other statistics? Try it, then draw your conclusions about which judicial system is more successful (or perhaps I should say, less disastrous).
Why would immigrant be required to prove his high value to your society, whereas trash that just happens to be born within your country's borders can happily be a leech on society?
You mean that people from France are coming to my country (The Netherlands) to undermine society? That's news to me.
I can quite confidently say that any foreigner who comes to the Dutch border and says he is a car thief, will be sent away. And those who don't say so and enter the country will, when caught, get the same jail sentence as our native car thieves get.
You can't hear them because the reservations are so damn far away. The US government carefully chose the least habitable spots.
No idea, sorry. All I can say is that it downloads fine when I try it. But I don't have Norton. (Using Firefox, BTW.)
For comparison, you could try to download some of the other executables from this forum.
Or you can drop me an e-mail or PM with your e-mail address, and I'll send the zip to you.
The node is a point in the track; you could also call it a sector. Each track has a couple hundred nodes. The current node number of a car will tell you the rough position. But when the cars are lined up at the start of a drag race, I expect they will be at the same node, so a node number won't help to distinguish he cars.
To identify a car at the start line, you will need the X, Y, and Z coordinates. These are given in the IS_MCI packet. The cars in that packet are identified by the player ID (PLID). You will need to translate the PLID to a player name, and the IS_NPL packet will give you that info. Send a TINY_NPL packet to InSim, and LFS will send you a IS_NPL packet for each player.
But, to create InSim apps you really should study the InSim.txt file. If you have trouble understanding it, then you can ask your questions here. (It also helps if you give the programming language / InSim library you use, so people can understand your background, and perhaps provide code samples.)
Hate to be the bringer of bad news, but there is another crash-causing bug. When trying to send a TINY_RIP message, InSimSniffer crashes immediately after selecting the menu item, with this exception:
Version: 220.127.116.11 Date: 19-12-2010 20:37:06 OS: Microsoft Windows NT 5.1.2600 Service Pack 3 Culture: nl-NL Exception: InvalidCastException Message: De opgegeven conversie is ongeldig. Source: InSimSniffer.Library Target: System.String LookupMpr(System.Object) Stack Trace: bij InSimSniffer.Library.SnifferService.LookupMpr(Object value) bij InSimSniffer.Library.SnifferService.LookupInformation(String name, Object value) bij InSimSniffer.Library.SnifferService.SniffValues(Object packet) bij InSimSniffer.Library.SnifferService.SniffPacket(IPacket packet) bij InSimSniffer.Library.SnifferClient.HandlePacket(Byte buffer) bij InSimSniffer.Library.SnifferClient.OnTcpSocketReceiveCompleted(Object sender, ReceiveCompletedEventArgs e) bij InSimSniffer.Library.TcpSocket.OnReceiveCompleted(ReceiveCompletedEventArgs e) bij InSimSniffer.Library.TcpSocket.ReceiveCallback(IAsyncResult asyncResult) bij System.Net.LazyAsyncResult.Complete(IntPtr userToken) bij System.Net.ContextAwareResult.CompleteCallback(Object state) bij System.Threading.ExecutionContext.runTryCode(Object userData) bij System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) bij System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) bij System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) bij System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) bij System.Net.ContextAwareResult.Complete(IntPtr userToken) bij System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken) bij System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped) bij System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP) Inner Exception:
It's not unlikely that Dubya really thought he was using his power to right wrongs. And it's fairly likely that most U.S. soldiers under G.W.'s command thought they were doing that. (And so did <that bloke that Godwin's Law is about>. He was righting wrongs by committing atrocities.)
I pity the country where the only way to get ahead in the world is by being willing to kill other people.
Ouch. The Export function doesn't work anymore. It causes a crash as soon as I select "Export" from the menu. Here is the crash report:
Version: 18.104.22.168 Date: 12-12-2010 0:21:32 OS: Microsoft Windows NT 5.1.2600 Service Pack 3 Culture: nl-NL Exception: InvalidOperationException Message: Bestand InSimSniffer Export 12-12-2010 00:21 is een ongeldige bestandsnaam. Source: System.Windows.Forms Target: Boolean RunFileDialog(OPENFILENAME_I) Stack Trace: bij System.Windows.Forms.SaveFileDialog.RunFileDialog(OPENFILENAME_I ofn) bij System.Windows.Forms.FileDialog.RunDialogOld(IntPtr hWndOwner) bij System.Windows.Forms.FileDialog.RunDialog(IntPtr hWndOwner) bij System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner) bij System.Windows.Forms.CommonDialog.ShowDialog() bij InSimSniffer.MainForm.OnFileExportMenuItemClick(Object sender, EventArgs e) bij System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) bij System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) bij System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) bij System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) bij System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) bij System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) bij System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) bij System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bij System.Windows.Forms.Control.WndProc(Message& m) bij System.Windows.Forms.ScrollableControl.WndProc(Message& m) bij System.Windows.Forms.ToolStrip.WndProc(Message& m) bij System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Inner Exception:
Note for non-Dutch speakers: "Bestand [...] is een ongeldige bestandsnaam" means that the file name is invalid.
No problems so far, except for 2 oddities that already existed:
- When launching LFS, InSimSniffer is a bit too impatient. On my (admittedly slow) system, it signals failure to connect before LFS has fully started up.
- Tab order of fields in the InSim tab of the options dialog is messed up. Or should we blame MS VS Forms Designer?
- Pining for the fjords!? (OK, after clicking that button the app has indeed ceased to be. But WTH is it for?)