Thats not a bug that you get spawned back on the right track config.
And the same things basically happens when you are off bounds on the autocross for example, flipped over the fence. Cause you are out of bounds, you get a shadow like this.
I've tried in both versions (Z10 and Z patch) and can only reproduce it at the first corner (Aston Club), behind the tires, in both Z and Z10 patch.
Your report that is at the last corner near the barrier I can't reproduce either in Z or Z10 patch.
BTW, since this is clearly not a bug in test patch, but "old" LFS bug, we probably shouldn't discuss it here
Was this the crash that would cause LFS to totally freeze and take over Windows and require a hard reset? If yes, thanks! If no, then I can't work out what it is that is causing it.
I had that one as well, I think it was a 32 car grid at BL1 and other places, especially when a car flew into the air as a result of a crash - it would freeze, not allow itself to be closed when windowed, and had to be killed using process explorer after I press c-a-d a few times!
Yes, the bug I fixed was reproducible in two MPRs I have seen, and at least one of those did cause someone's computer to hang, so I think it is the same bug. It was related to shadows and LFS counting them wrongly, so it would try to draw too many shadows, overwriting the wrong part of memory, so causing some unpredictable error (crash, hang, etc.) soon after that.
That is not a bug, because demo users also need a user name and password, so "return to demo" does not clear the user name and password.
There us that bug I noticed, but I'm not sure it comes from the patch.
Basically, I am under the impression that the tires screeching sounds are inverted (I use the default ones).
I am using Sony Dynamic Stereo Headphones (MDR-V300) with an Acer Aspire 5610Z laptop.
I was surprised by my setup being more understeery than before though I didn't change anything. Then I realized (by switching to the force view by mistake) that my inside front was in the red grip level in the force view (I set up my car like this), but the screeching sound came from the outside front tire (no matter if the corner was a left or right hander).
I flipped my headphones (putting the left side on the right ear) and the sounds were perfectly correct. I'd like to kno if anyone experienced this before ?
EDIT : I said my setup as understeery, because I use the tires sounds as a reference to when I'm driving, so I was surprised by the outside tire losing grip that early. Nothing to do with physics.
i wouldn't say it's a bug because you have to remember that during cornering weight gets transfered to the outer tires and in many cases inner wheels can even lift off the track, if it's front or back depends of setup and becase inner tires do much less work then outer very loaded tires they don't make to much noise comparing to outside tires, i would say it's correct sound effect isn't it?
If you have a replay (or this happens again) use forces view (F). This will show you how much force is on each tyre. Anything up to green should be gripping and not make any noise, red means that tyre is sliding. The longer the arrow, the larger the force, so if it's slipping, a longer arrow should (I think) mean more noise from that tyre.
This should confirm exactly which tyres are slipping and making noise, and how much, then compare with what you hear etc.
Edit: also don't forget to test in Z if you have a replay. AFAIK, nothing in the sound engine has changed in the test patches, so any sound problems should be consistent with Z and therefore shouldn't really be in the Z10/test patch forum
What if people who have no idea what they're talking about would simply shut up for once?
DirectX is just an API to access graphics card (or other hardware) functions - the bug that has been reported countless times is located in the shadow code of LFS' 3D engine. Since that code is custom written nobody but Scawen can find out why it happens, but probably it's just something like LFS selecting the topmost drivable surface for the given car's X,Y coordinates instead of the topmost drivable surface with a lower Z value than the car has (= below the car). Depending on the actual implementation it might be easy to fix, or it might not, in any case it's a really low priority thing.
OK, I have implemented this because it was very easy to do in two minutes, and seems like a "bug" in cruise mode, because flags only work correctly when driving in the correct direction anyway...
Before I release it in the patch, is there any possible objection to the removal of blue and yellow flags? And (although I can't promise any updates in this patch) are there any other issues in cruise mode and should anything else be disabled, for example the lap counter / lap times?
No problem mate.
