A lot of program features rely on certain memory layout which changes from build to build. I wonder how much usefull will LFSLazy be without proper memory access... Maybe it's possible to disable some stuff, but it is lot of work I guess.
I thought about this one before, but you know what I don't quite like that in real cars
Like when I do slight correction midturn or staying in traffic and moving my car to one side to let someone pass... and my indicator goes off :/ I prefer to turn them off manually myself.
At first I thought you want a sound when shifting gears (3->4, ...), but when saw you other post I think that refers to rpm. At which rpm it should start? Is it fine to use rpm when RPM gadget become red?
Also I really don't know which sound should I use there, do you have anything specific or should I make them costumizable by user (like you can do with turn indicators/handbrake)?
Like previous request, that is possible however I'm quite unsure about some stuff and there is already too much options which confuses people.
BTW, nice gauges
The optimum is both, but in my opinion the customisable is best. I think just a continuous "beep" is good (with the possibility of editing it like indicators).
Don't worry for that, to be honest it was more a fun request, a bit in reference to Initial D.
by sergey29 : Problem solved
Hey. I have a problem with Lfslazy. If i open it (write /insim 29999 at the chat) and if i click on "dashboards" at lfslazy, lfs and lfslazy is switch down. If im not use that "dashboards", its working good but i want dashboards. Anyone have any suggestion to that problem?
Making new dashes should be quite easy. Using "/o dash" you enter Dashboard Editor in which you can move objects around and configure behaviour of each object. In Gauges folder you can find installed dashes and modify textures in there.
Could you please try one more thing? Enable just Radar and see if it crashes, afterwards just Dashboard and see if it crashes. Or does it crash regardless in both cases? I'm trying to figure out in which part of code does it crashes, this should give me the idea where to look at.
Alright...so my method is 10 starts each, 5 of which when the option is already enabled at launch, and 5 when it is enabled after LFS launches. I will be going into a SP race each time.
Neither: No crashes.
Dashboard Only: Crashes most of the time on startup and when enabling it, but sometimes does work.
Radar Only: Crashes most of the time on startup and when enabling it, but it does sometimes work.
Both On: Crashes most of the time on startup and when enabling it, but sometimes works.
Sorry if know this isn't very useful, but if you want to know what happened on each specific launch then go HERE (google doc)
Thanks for detailed report
Random crashes are hardest to debug, especially the ones that I cannot reproduce on my PC. :/
I will try to go through code to see if there is any unhandled stuff left and in case I find something send you a build for testing
Lately I've been working on long requested TV mode, which should help in streams or if you just want something new. For now it consists of position list which is updated on each split, it shows positions and difference. Another cool thing about this mode are flags as you can see in preview below. Still unsure whether to include it to next build as its not finished and it requires you to install flags. PREVIEW
Last time connected to server and times connected now logged
Previously only time spent on server was logged (Time online, new version will also log last time you've been on server (Last online) and how many times you've connected to each server (Times connected).
Hope the names I've choose for each are fine.?
Encounters list - flags
Now in encounters list you can see tiny flags by country name.