i just cannot reproduce the error ind some points sometimes it happends sometimes not and in these time it does not happends the gauge overlay wont start and its telling me some other program is already hooked up in lfs but there is no other program as far as i can see it
so its mainly an problem with the gauges overlay i think i will test a little bit more
Just like main window can be green, pink, yellow, ... it can be black or very dark as well. Issue with update window is that there is a black text over that background and it would be really hard to read or not at all. Obviously I cannot leave it like that, so I'm thinking right now maybe I should enable dynamic background color of update window and color the text to white instead of black when background is dark enough.
Hi there Daniel, I have been using LFSLazy since about 2014-2015 Christmas but the day before yesterday and yesterday we came across three problems. The first being the in-game dashboard; our problem (Which I have fixed for myself but don't know how) is that he can't see the dashboard in first person/is staying as the default dashboard, and because I am also using the NTO Rev Bouncer it flickers when I use it.
The second which we found out is "Build 41" Which whenever I/we start LFS up is come's up with this: https://www.lfs.net/attachment/133761/thumb
But when I start up the LFSLazy program it comes up with this:
*EDIT - Also whenever I tab out of LFS with LFSLazy running, my screen turns black and stay's black until I close LFS.
Not really a problem for me to change a color. To be honest I don't really care much about appearance, functionality is more on my mind. I'd like to hear from others as well, is that light gray default color better?
Let me know if you find the cause.
Its like that from begining. Rev bouncer kills your ignition and therefore it has some effect on LFSLazy dashboard. You can modify dashes that you are using, so its not turning off with ignition.
Does the crash happen when you are updating to build 41?
When does it happen exactly? The moment when update window appears or when you click update?
I wouldn't mind getting a crash report.
For now you can manually update by downloading LFSLazy from the first post and replacing it in your LFSLazy folder.
Seems like you are still using build 40, that should be fixed in 41.
Try downloading LFSLazy from the first post and replacing it in your LFSLazy folder as I already said.
Especially important since I've made millions from LFSLazy sales
I'm glad to hear some input. Yeah, that Steam window is simple enough, but I still think I cannot leave out some vital things e.g. current version, newest version. What do you think about showing the size of a new version? Also current progress with the download, progress bar is nice IMO, are the numbers needed e.g. 1553/2893 KB ? Change log is also vital part which I don't think I should leave out now.
Any "complaints" to other windows?
Actually its great to hear some, it made me think how certain parts can be improved.
Actually, when I talk about Steam update window, it's not a static thing. Of course your need to ajust it to your needs !
EDIT : Always think that some people are actually afraid of informations, they just want that the app do it stuff and that's it, so UI have to be thinked to please everyone (more or less, from the "show me the new code un changelog, I want to know everything" to the "do your stuff, I don't care" peoples). END EDIT
I was thinking something like writing the download size (in Mo/MB instead of KB, because it's easier to read) where the "Extracting package..." is.
For informations about versions and changelog, I think and adding a button "Detail" witch deploy the changelog, show the current and new version. Here is a representation of it (don't mind the shitty XP theme and please don't reproduce it lol ) :
For the main window I have an idea but I have to go to work, so we'll talk about it later.