Thanks for the help. I tried renaming the file and checking its properties but nothing worked. Removing it and creating a new driver profile with the same settings hasn't given me any more problems though, so it seems to be solved for now. I still don't know how the file got corrupted, but at least it hasn't messed with anything else from what i've noticed.
On that note, maybe make it so new setups are created based on a default setup (or [hard track]), rather than the last setup selected, unless you are the creator of that setup. That would be pretty much a foolproof way of blocking setup stealing.
Yeah, but it should be quite nice that every guy will go on one stricly picked set, that would be nice for championship and seeing who is really good locking setup in race should be a lot of fun. Ofc for AN options
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.
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".
Agreed. Some users may not read the release notes. They may Alt+F4 if they see a black screen with no logo or indication that something is happening- and no Alt+Tab ability. Then we can see some 'LFS broken posts' on the forum.
I am not coming up with an answer for that strange server issue. Has it only happened since you installed R12 on the server? If so, is it easy to revert to R and see if it makes a difference?
I'm guessing it has nothing to do with the new version, as I can't think of any related changes in the code. Does the same problem happen to all guests who join? Are there any other DCon instances on the same server computer? I wonder if it could be something to do with the computer time clock, running slow or fast. Can the server computer be restarted?
Well never had this problem before, so its strange that this happend on the R12 TestPatch. Just to be sure that it is a server issue, i visit other servers . It seems they do not have these kind of issues. So i think its a ISP issue or computer issue on the hostside.