I really like this night-longway-shot of Kyoto.
Can't wait to drive there.
Can't wait to drive there.
yes pls, make it accurate place and time too. maybe we can have red super moons in LFS, and we can actually see them instead of clouds getting in the way like irl!
Live for Speed, the ultimate astronomy simulator. With the next update the Space Engine and Universe Sandbox would become obsolete junk on my SSD
by late 2026/early 2027 we'll be contacting alien life through LFS (though gabor exists already). If we hit that blackwood fence fast enough we can fly to kepler 22b.
Im actually curious why not just release it abit. These two track look wel dome and ready to go. Sure you may want it to be 100 percent perfect, but I guess many players would like it to just be released, and some tiny bugs can be fixed later.
You can even release it and when players are in the loading sceeen of the new south city or kyoto to show "THIS TRACK IS WIP" so people dont complain about minor bugs on these maps
You can even release it and when players are in the loading sceeen of the new south city or kyoto to show "THIS TRACK IS WIP" so people dont complain about minor bugs on these maps
Lighting would be a good potential example of an incompatibility. In our current version of LFS, tracks have a handful of prebaked lighting+skybox situations to choose from. If the new version has removed the way that works in favour of a dynamic solution for time then the old tracks straight up might not work or otherwise have massive issues until revised.
And no amount of "THIS IS NOT FINISHED" will silence people. Cyberpunk2077 had a ton of videos with "THIS IS PRE RELEASE FOOTAGE THINGS MAY CHANGE" and people still think that things like wall running was cut content/broken promises.
You could sell a car with some nice improvements and also a leaking fuel tank, some holes in the bodywork, faulty electrics and an uncomfortable seat. Or you could fix the known issues and release it at that point instead. Which is better?
This is an entirely new version. There is no compatibility between tracks in the old and new versions. The old version cannot possibly load the new tracks, and the new version looks terrible with the old tracks. Good news though, they have all been updated, as you can see by reading the previous progress reports I linked to above.
The new version is not a patch for old LFS. It has to be released all at once, and it will be released with flaws, in as a test version. But there is absolutely no point releasing it when it is not ready for testing and we are working full time trying to fix all the issues we already know about.
There is a point to release it before it is perfect (and will never be perfect anyway) but we aren't at that point yet.
EDIT: As mentioned, some important things are simply not done yet. Also, at some point I need to build a public version, actually exporting everything from the development version into a publicly releasable folder. Even that will take me a few days, probably a week by the time I've added some code support to help me build a clean version a few times during the testing stages. To move from a development version to release isn't simply a matter of declaring it ready. It's a careful process of exporting and encrypting the necessary files, possibly stored a bit differently from the current public version. It's not a big deal, I'm just trying to illustrate that there isn't a version to release yet, even if it was ready which it isn't.
This is an entirely new version. There is no compatibility between tracks in the old and new versions. The old version cannot possibly load the new tracks, and the new version looks terrible with the old tracks. Good news though, they have all been updated, as you can see by reading the previous progress reports I linked to above.
The new version is not a patch for old LFS. It has to be released all at once, and it will be released with flaws, in as a test version. But there is absolutely no point releasing it when it is not ready for testing and we are working full time trying to fix all the issues we already know about.
There is a point to release it before it is perfect (and will never be perfect anyway) but we aren't at that point yet.
EDIT: As mentioned, some important things are simply not done yet. Also, at some point I need to build a public version, actually exporting everything from the development version into a publicly releasable folder. Even that will take me a few days, probably a week by the time I've added some code support to help me build a clean version a few times during the testing stages. To move from a development version to release isn't simply a matter of declaring it ready. It's a careful process of exporting and encrypting the necessary files, possibly stored a bit differently from the current public version. It's not a big deal, I'm just trying to illustrate that there isn't a version to release yet, even if it was ready which it isn't.
I really want to add the moon, it seems quite wrong not to!
But don't worry everyone, this is obviously one of those things that has to wait until after the release.
I can smell some conspiracy theorists gonna use LFS as a proof of why the Moon does not exist
Is this the front of the vehicle before any damage deformation?
Also, would it be possible to get the offset of the front of the car (or better yet, extremities in general) in an InSim packet? Or is that only known client side?
the moon is not real
September Progress Report
(86 posts, started )
FGED GREDG RDFGDR GSFDG