No, I will not respond. I have made a note of every bug posted on this thread but I will not write a message for every one "Hi, I've added it to my notes".
Thank you for the bug reports. The thing to do is just check when the next test patch comes out. At that point, please check that any bug you reported has been fixed. In the rare case that I somehow missed one and failed to fix it, please do remind me of the missed bug.
This is the way I have found is the most efficient way for me to work.
Haven't checked out the replay feature yet but I have a couple of comments:
a) I think the layout of the pages under the "Options" menu needs work. They're all a bit fussy at the moment and if you scroll through the pages things seem to pop up in random places on the screen.
b) I'm not keen on the buttons in the screen cornners. Don't like the way they are bordered by the actual screen edge, to me it makes it all look a bit unfinished. Also, I don't like the colours, I feel they're too garish, (especially the orange). Less saturated colours would look more sophisticated in my opinion.
Little things I know but they all add to the overall impression of a professional product. Not something that needs time now, but definitely before the final product.
I think the options screens are quite consistent, not *fully* consistent because each has its own special coding because of each one's different needs and purposes.
Sometimes it may seem random, for example "skins in memory" on the misc options page. But that's some spare space and there are skin related options on that page, so it's not really random. It would be quite a bad idea to make a special page for that info - which isn't the most vital info at all but is nice to know and is happily tucked away in the misc options screen. On the view menu there are a couple of things that appear on the right, but they are 100% related to what's on the left.
Anyway I have no real idea what you mean, I can only guess because you didn't give any examples. The options screens get a little rearrangement every now and then but I don't see any real problems with them at the moment.
Corner buttons are the easiest to click. It's mostly about ease of use and clear distinctions. I didn't design most of the colours but I am quite happy with them. I think the orange-red (cancel / back) buttons are designed to go with the logo.
Is it already suggested to add slow motion buttons to the replay bar? I just downloaded the new patch, tried it and it was the first thing that came to my mind.
And I'm not sure if I have edited background images, but the options menus could do without really. Makes a lot of stuff hard to read for me. I'm sorry if I don't have the original files, maybe the normal ones don't have this problem, but I can't remember
Hey, on-demand mpr-header creation is what i am currently working on for the next major release of mprEdit
Scawen, I'll let you know when I'm finished so you can take over my code (lol, just kidding :tilt
Glad i could help. Im just confused that im unable to reproduce the bug which i have mentioned in first place (yellow bar goes all the way to the end of the replay and it would not stop at the point where i have clicked to). Im 100% sure it was as i've reported it and now i feel a bit fooled since im unable to reproduce this again. Anyway, i guess when this is fixed it doesn't really matter anymore.
I've been able to reproduce this on Vista Ultimate 64 bit.
If I do a fresh install of LFS version Y, it runs ok, if I then update it to Y19, I get this error.
All previous installs of LFS will update without any problems, (I've been able to update from Y and Y18 without any issues), but I've now done 3 fresh installs and updated them, and got the same error each time. The fresh install will run ok prior to the update being run.
Screenshot of the error attached. Note - the mouse isn't visable in the screenshot for some reason, but it is bound to the lfs box in the top left, I need to use 'Alt-TAB' to be able to close the error box which then closes LFS.
OK found it
Y18 and earlier, LFS will run fine whether you run it as Admin or not.
Y19, you need to run the LFS.exe as Admin or you get the 'font not found' error.
This is on Vista Ultimate 64 bit, I've not tested it on other Vista versions.
This also only applies to a fresh install and update. Older installs will update without any issues.
Tested it now on Vista Home Premium 64 bit, works ok on that without the lfs.exe needing to be 'run as admin'.
Could someone else with Vista Ultimate test this?
Both 32 and 64 bit.
I've found that since Vista Sp1 (64 bit) I've had to run LFS as admin to get it to work. The same can be said for some other games as well, so I don't think it's got much to do with LFS.
Edit: Well (tested again), it seems I don't need to do that anymore. Heh, just adding to the confusion I guess...