I am late about this but still would like to comment about it. Lots of people with powercards forget to realize that LFS is pretty GPU friendly, in a way that the GPU goes into sleeping mode by clocking itself and its memory down if it detects it has not have to do much. Without monitoring GPU-Z (which has a clock history graph) its impossible to say what is going on. When in fullscreen or windowed/borderless screen and post processing on/off the drivers can decide to be in a different power state and therefore cause the 10x framedrop. Its then your card which is "sleeping" but to be sure about this; monitor GPU-Z.
Especially when you you use the frame limiter or V-sync function in LFS this happens.
1685 < 1943 This is at the default clock, turbo frequency is even much higher.. Besides; single core != single thread. Any IGP is incomparable with a dedicated GPU. You are talking about a Graphics 620 IGP, it has 24 pipelines to begin with, it's nothing. I do not know if you have read about this project as a whole but this is based on VM's and splitting/assigning CPU&GPU power to individual threads so thats why I refer on (basic) benchmark numbers.
edit; but I now realized that the mirror update was long(er) ago. In this video it's already visible, so never mind. I think not much has changed on the performance of LFS in the meantime.
Depends on the CPU power you can give it on a single instance. Since the new mirror routines my mobile CPU is maxxing out on a single thread on various spots. Especially with multiple cars around. If you can get a passmark beyond Intel Core i7-3630QM @ 2.40GHz 1,685 (<= single thread) you probably will be OK.
LFS is currently CPU limited it seems, GPU is not that important. This CPU limitation makes LFS a bit undriveable at this point (I am sorry to say).
Which has been discussed before. It's all nice and stuff but it still wouldn't be something which moves the world. Only one thing can do this which is called tire physics.
The DDossing started a full month ago, so another month is lost due to these clowns. Also, any major change without introducing a more advanced/secured online environment will only boost illegal activity more then it would help the legal community.
Me neither.. The only problem which I had during the update was the quite long black screen while it was converting stuff in the background. Not sure why this took over a minute or so (maybe because of mobile processor on a single thread) but this is the only problem I guess with this update. Not be able to see whats going on and "assume" something has crashed and close the LFS screen. While it actually was not crashed, just "doing stuff".
This testpatch is only a minor update, mainly to prevent master server take down.
This patch is not to for requests like setup expansion/protection which involves days or weeks of coding -and- testing. With the release of new tyre physics all setups would be useless, it makes sense to focus on the setup system at that point in time, huh.
... LFS still has a problem, a CPU problem. I have a 965M but the screen is lagging on various spots because the CPU cannot handle it. Well, it can handle it, it's just LFS which doesn't make use of today's multicore CPU capabilities. It's a bit of a shame that LFS doesn't run smoothly on my i7 3630QM, it is not that this CPU is very old, its LFS which is very old in handling multicore CPU's (it basically doesnt handle it)..
If LFS doesn't get this problem sorted with multicore CPU's then I do not think it has a big future for the masses which want to try VR. The early adapters of course all have massive desktop systems but the bigger part doesn't have this. Sure a graphics card can be upgraded, but a CPU is more difficult. Especially when it is not needed and its just the software making bad use of the capabilities.