Scawen
When you are in cockpit and adjusting FOV by keys 5/6, information about current FOV shows always only main screen FOV angle. If you have defined side screens, it should show overal FOV angle, or maybe both: " FOV 75° (main: 28°)"
i drived yday races in z30 host and those races not show on lfsword online race results yes there was layout but still that would be nice to show there
I've not got to test it (yet), but I've a question about open layouts. Is it possible to (for instance) use AS1 start with a grid but AS2 pits or not? If not would it be simple to add?
No, that is not possible and it's not easy to add. You choose start grid / pits / start lights together as a set.
I'm not sure what you mean, are you talking about the lights? I'm not going to support the red lights with this patch. Apart from that, the G27 should work well with LFS.
It looks like some points were detected as being in shadow. This kind of error can bee seen in many places in LFS. I hope to make a new rendering system one day, that can make accurate shadows under objects, unlike this system we use now, which often misses shadows where there should be, and puts shadows where there shouldn't be one. But that is not the subject of this patch.
No, I think that would have been the same with the old version. Watching frame by frame with forces mode on, I see that that front left wheel that has penetrated the wall, is (between the first and second collisions) too deep (downwards) into the wall to detect the top surface. But at some point, the wheel is high enough to detect that top surface. It thinks it is very deep into the object at that point and must provide a great upward force. You can see the extreme tyre deformation at that moment that the "second collision" occurs.
That's not realistic, but it's what is happening, and the contact detection is actually working as designed in that replay.
No, I'm sorry but that would start to make things complicated. I can't really take any off topic requests now. I'm just trying to get the patch finished. There are still a lot of things on my lists (6 pieces of paper beside me here) that will keep me busy for at least a week or two. I don't want to add anything, I just want to get the official patch out with its related updates.
Windows 7 is very strange about what processes it allows to write to either of the Program Files directories. It seems to only allow Setup programs of some type to do that. After that, it disallows anything else to write there programatically. iRacing has massive problems with this with regards to its updates and their tech support is clueless about how to fix it.
For most Windows 7 users, it is best if you create your LFS Program directory outside of the Program Files directory. Then, you'll have control and things like the unlock and updates can write to the directory with no trouble and you won't have to "run as Administrator".
Ah, very good. I had put a start position in thinking it was needed for an open layout. Thanks for answering.
Thanks for all your hard work, Scawen! I've yet to find anymore unreported bugs with z31 and the skidmark fix is working awesomely and not hurting the FPS in my crappy lappy.
It's not strange, it's actually a sound and simple concept. Point the tech support (and tell them to pass it on to the developers) to http://msdn.microsoft.com/en-us/library/aa905330.aspx and they shall not be clueless any longer.
Thanks for the link. And just so we're on the same page, all the User Account Control stuff that can be turned off is turned off on my machine. It's still best to put programs like LFS outside of the Program Files directory.
It is strange with regards to other versions of Windows though. That's why I used that word.
I've been "studying" the new collision system on BL1: I've always enjoyed flying into the air in the straight by hitting the banners. I tried doing it in Z30 and Z31 too (20+ times) to compare the car's reaction.
Here's my conclusion: the car seems to fly less, but still does. Watching the replay at x0.25 speed, I can see the car going right through the banner before being ejected (mostly with the tyre being extremely deformed).
Which leads to a little question: could this issue be solved by increasing the frequency of collision checks?
And on a little offtopic: when you drive on multiple ramp1 objects, the tyre tends to "fall" in the small gaps between the ramps, and makes the car jump (even with Z31). Will this be fixed in the physics update? (as well as unrealistic tyres bounces after a jump)
On FernBay X/Y the little "Loop Road" near the beachy area with that really hard to get out off stick sand, The loop road to the right of that (Or left) that goes up the hill and back down does not appear on the map. It just looks like someone is driving through thin air :P
