The use of VOB mods is forbidden for now, hence the fact that LFS is still in development, and MAYBE, in the near future, after 1.0, modding will be supported, thats why I hear and read about it. I can be wrong tho, but for now, it is better to keep LFS as clean refering to VOB mods. Still, textures and sounds are ok.-

Quote from DANIEL-CRO :

Having LFSLazy.exe.update.exe in your LFSLazy folder wouldn't suggest that your update went fine. First thing that LFSLazy does on start is delete update.exe, that means it doesnt even trully start (trying running it as an admin).

Anyway here is version 55:
https://www.dropbox.com/s/dmzvclq2105ijco/LFSLazy%20v55.exe?dl=0

Just to verify, which LFS version are you using?

I'm using version 0.6K.
Running as an admin doesn't fix it.

But in the mean time, i'll stick to the updt 55 and looking forward for a new version and see if the prob persists. I'm starting to think that I will stick to official versions only, mostly to avoid this problem/issue, until 0.7 and so on gets released. It seems like my lfs doesn't like test versions

Quote from DANIEL-CRO :

I cannot reproduce nothing like that as well as some other people I asked.
Some things to try:
-redownload LFSLazy from OP and replace it with yours
-move your LFSLazy folder elsewhere in case some of your LFSLazy files got bugged


That change relate to when your start LFSLazy and LFS isn't running.
Having multiple .exe's in LFS directory doesn't affect this feature, as LFSLazy remembers only latest one used.

Already tried both of those tips to try, but nothing changes.
Also, it seems that for some reason, there is a LFSLazy.exe.update.exe in LFS folder, the update went fine, from downloading to install, it never stopped nor I killed the process, and since there, it doesn't start.
If I run that .exe, it loads some seconds and then there's an Error:

"Update Error
Can't write LFSLazy.exe"

Regarding of Whiskey's reply, no, I don't have any extra .exe.
This problem began from 0.6J5 test version, and it only happens with test versions. But, since I was confused if files from LFS were from the official versions and not test versions, I installed a new fresh copy of LFS last week. Update 55 (31/12/15) runs perfectly, even with the "frankestein" LFS I had.

The only thing I wonder is if you have some tipe of Archive folder, with older versions of LFSLazy, or if you or someone upload LFSlazy.exe updated to version 55 (31/12/15) so I can have a "backup" exe and wait for a new version and see if this persist.-

Quote from DANIEL-CRO :

Never heard of problem like this. Do you first start LFS and let it autostart LFSLazy? Or maybe you first start LFSLazy and when it asks you to start LFS you click Yes? If you are doing first I'd guess each of your LFS instance start separate LFSLazy. Did it only start occuring after updating to latrst version? I doubt it could be due to LFSLazy there werent any crucial changes.

What I do since I have LFS Lazy, I first start LFS from a shortcut with the /insim=29999 added and then, Manually start LFS Lazy by clicking the exe.
It doesn't even open at all, there's just 3 lfslazy procceses on the Task Manager. Already tried to kill it from the Command Prompt, but only one is killed, and the other two just stays there in the TM. And yes, it is the first time this happens with LFSlazy, with today's update.

Hey Daniel, I updated lfs lazy to Version 56, but, when I try to open it, it opens multiple times (3 times to be exact), but doesn't even open, and it just keeps "loading" forever, until I reboot my PC. Also this happens with latest test versions of LFS, but only with LFS, everything else runs perfeclty. I already tried re-installing but it keeps happening the same. I discard the possibility of having a virus tho.

Quote from Shirtkicker :

Quote from Ibtasim6781 :

Quote from LuisYeg :

this is my skin

AutoCross track on demo, stolen skin, worst edit possible, deleted the "SKIN BY BURN" on top-right, next to the roof and the upper trunk. Nothing else to say, ma' cracker boy

Actually, anyone can drive around in the BL carpark, and there are no signs of any layout objects used. I agree about the skin theft - very clumsy attempt - but honestly, you need to get your facts straight before tearing into somebody and accusing them of being a cracker.

Mouseman, you should know better too.

If you look more deeply, you can clearly see that is AutoCross track, which is S2, look for pictures if you still have doubts about what I said. I'm only judging by comparing HIS screenshots, with, for example, this layout (made by Mr_Lonely). Compare both pictures and tell me if he is not a cracker (ignore the layout, just look on the parking lots and the yellow line. And BL car park is not even close to that.

IMG: http://img704.imageshack.us/img704/8580/lfs00000036.png

Quote from LuisYeg :

this is my skin

AutoCross track on demo, stolen skin, worst edit possible, deleted the "SKIN BY BURN" on top-right, next to the roof and the upper trunk. Nothing else to say, ma' cracker boy

Quote from czarekHD :

hi i can't beat my 1.34.75 on rev blackwood.
Maybe someone has good setup for it. thanks

Ehm, isn't Blackwood Reverse part of S1?.

oh wait: "Im playin on another account" excuse incoming...

Quote from 125 al sopi :

Upload skins please? Thank you so much

Stop asking about Uploading skins ffs. Either Buy S1, S2 or Buy a Skin Slot and stop begging everybody else to make them upload ur skin because that won't happen.-

Yeah, would like to see those skins on the FBM! Hope someone got these on their hands and working :b