You will always need lfs.exe to generate a RAF file. An SPR contains just the driver inputs. You then need to re-do the physics calculations to get the RAF data, and that can only be done with LFS itself.
It's thinkable that LFS will get scripting commands to generate a RAF file. (Or maybe the new patch already can - the RAF files for Victor's analyser are generated in an automatic process.) Another possibility is if LFS could generate the RAF data while you drive. (It would be optional, comparable with the option to auto-save replay files.) That can serve several purposes:
To generate many RAF files in one go, like you need for your planning tool.
To get a RAF file quickly (i.e. without needing to save & run the replay), thus shortening the drive - analyse - learn cycle.
If it is pitting strategy that you want to generate, then I have bad news for you: fuel, tyre wear, or damage are not included in the RAF file. (At the moment, at least. Scawen might be persuaded to add them.)
Then iRacing at least got a month of subscription fee. With a standard sim, if it doesn't deliver the customer will only download the free demo, so the developer gets no money at all.
That is the most useful variant. The line shows where one driver is gaining time on the other driver.
Suppose driver A focuses on braking late for a turn, and driver B uses "slow in, fast out". The time difference graph will go down at curve entry (A gains on B), and up (A loses on B) after the exit. By comparing the sizes of "up" part and the "down" part of the graph, you can see whose strategy was best.
Same here. I could understand it if the price was double that of any other sim, or if you'd pay extra for software updates. Or if it included significant services, like stewarded races (which appears not to be the case).
As it stands, you keep on paying for a product whose main cost is one-off (namely development). And you must pay for more content. That's extortionate.
Yes, but LFS also supports driving with mouse/keyboard. The changes in patch Y have made it harder to control the car for mouse/kb drivers (more than for wheel drivers). This suggestion would correct that disadvantage.
FYI: In Racer (www.racer.nl) you can set separate button control rates. It even has separate settings for pressing and releasing the button.
Radioactivity comes as atoms, and atoms tend to be pretty hard to destroy. Molecules you can take apart easily. But splitting atoms takes lots of energy and/or produces new radioactive atoms.
Yes, but that would make nuclear energy much more expensive. So expensive that solar cells would probably be cheaper.
There is a fair amount of Uranium in the Earth's crust exactly because it has a long half-life. All stuff with a shorter half-life has fallen apart after 5 billion years. (Except for material that is the result of a man-made nuclear reaction, but that won't solve the problem.)
I like the idea, but I wonder why you ask that this works through a separate LFSW application. I think it would be simpler if the team manager connects to the race server, spectates, and enters his comands from there. (So everything is done in-game, and LFSW is not involved.)
Did you know that none of those 70% lead to an actual increase of the amount of CO2 in the air, because it is converted into biomass again? (Except maybe where forests are burned down by humans.)
You seem to have enough expertise to see which documents are false and which are right. Yet you failed to see Becky's error in distinguishing between CO and CO2...
Oh, go on believing what you want to.
[/OT]
I have been car-less for 9 years now. Bike to work and shop, train or bus where practical, rented car otherwise. A rented car is more expensive per mile, but because you use it only when needed, it turns out much cheaper per year. (And you can adapt the car's size to what you need for the trip. And no worries about maintenance, tax, and insurance.)
Becky, think again about the moped. IIRC it's more polluting than a car, even if driven alone (dirtier fuel, no catalytic converter).
The standalone version is working fine here, except for two minor issues:
I have Firefox. When I have the analyser running and open a second browser tab, the window height decreases (because the tab toolbar is opened). The analyser does not respond to this change, and the bottommost 20 pixels become invisible. (This might be a quirk in FF.)
I'm missing a possibility to choose a different car/track combo. You can do that by refreshing the page, but it would be nice if the combo display (at the right of the analyser's toolbar) would be a button, leading back to the combo selection screen.
Some other suggestions:
Camber display (in a graph)
Possibility to move the cursor by clicking in the map
Possibility to reset the zoom of a graph (e.g. with a scrollwheel-click)
Why make such a fuss about the grid size? It's not a limit for eternity.
If I was iRacing I'd keep the grid size on the safe side too -- at least for the first release. Later, after some weeks/months of racing experience and subsequent tweaking of the net code, the limit can be raised.
It should also include the services of a hunter, to shoot every bird in the vicinity. Birdsong in the garden ruins your S/N ratio, as every audiophile knows. Can't have that, can we? (Maybe he should shoot the neighbours too, who keep playing their Tom Jones and Celine Dion records.)
I used to wonder if audiophiles were crazy. Now I'm certain.
Know your audience. You will lose readers if you insert unnecessary explanations, or if you use slang that only experts are familiar with.
Ask for feedback. And be selective in who you're asking it from.
Keep the reader in suspense. Announce some kind of "mystery" in the first paragraph, and reveal its details near the end of your article.
Be concise. Don't ramble. The more words you use, the more doubt is being cast on your expertise.
Work in advance. Don't wait for the deadline. Some writers even keep a couple of articles in stock, in case they catch a flu or run out of inspiration.
Not too close, I think. To have instant replays, LFS needs to save the full game state, so it can resume when you finish looking at the replay. This is the same as the "keyframe" issue that Scawen talks about in post #30.