Tried pressing Shift+F, or Space?

Was on BL1 with layout, pressed shift + U and LFS crashed, address: 0x000000000041dd13.

Crash on BL1r going to Shift-U - No layout (clear Day) Single Player

I was driving around and noticed the shadow behind the car flickering. So I stopped and took a closer look...

- My View Options
32 bit 1680 x 1024 AA-2 AF-Application managed. System specs in my signature.

However, when the shadow was clipped - I pressed Shift-U for a closer look. LFS closed instantly! BANG! No error messages. Shift U works fine when in the first picture. I can even drive over the clipping spot IN Shift-U mode with no problems. It's when I hit Shift-U right when the shadow is clipped LFS goes bye bye. These shadow clipping spots exist all the way around the track. Every 5 meters or so, depending on the incline of the track. (Flatter ground = more clipping spots) Sorry if I'm using the wrong terminology.

Tested using Hi-res textures and default textures, same problem. I tested it in highest LFS LODs I could select.

I tested this again in V5. The shadow still gets clipped - but shift-U does not cause a crash to LFS:


EDIT: The crash did not occur if I disabled Vsync.
EDIT: Correction Its happening with Vsync off or on.
It DOESNT happen when I use Shift-U from In-Car Cam. It happens when using external views. It happens on th start line after a shift-R, in Chase view BL1r without fail.

Quote from hackerx :

Was on BL1 with layout, pressed shift + U and LFS crashed, address: 0x000000000041dd13.

Thank you. Your crash address showed me axactly which line it was. The crash was an integer divide by zero and it's a very simple fix to avoid that. It was related to LOD so doesn't affect anything else.

Quote from JasonJ :

Crash on BL1r going to Shift-U - No layout (clear Day) Single Player

I was driving around and noticed the shadow behind the car flickering. So I stopped and took a closer look...

...I pressed Shift-U for a closer look. LFS closed instantly! BANG! No error messages. Shift U works fine when in the first picture. I can even drive over the clipping spot IN Shift-U mode with no problems. It's when I hit Shift-U right when the shadow is clipped LFS goes bye bye. These shadow clipping spots exist all the way around the track. Every 5 meters or so, depending on the incline of the track. (Flatter ground = more clipping spots) Sorry if I'm using the wrong terminology...

Thanks, this will be the same crash that hackerx reported. It's not reproducable 100% because you must happen be in just the right spot as you enter SHIFT+U mode.

The shadow clipping you see can come up if the track is aligned along the x or y axis and the sun is a bit low in the sky. LFS doesn't realise that the next track segment is in the shadow, because it's out of its physics range.

Quote from Scawen :

.....The shadow clipping you see can come up if the track is aligned along the x or y axis and the sun is a bit low in the sky. LFS doesn't realise that the next track segment is in the shadow, because it's out of its physics range.

Thanks Scawen - I drove around and looked for some other shadow clipping spots to try force a crash - but they all did not produce the crash when I hit Shift-U . So I got confused what was causing the crash. Your post has made that a little clearer. Dunno If the shadow fickering happened Pre V5. Guess if it was, I wasn't noticing it. It doesnt happen on all tracks all the time. Eg: I cannot get the Shadow to clip on FE Black.
Thanks again - best game eva !

Quote from hackerx in V5 thread :

Not latest test patch but maybe helpful... LFS 0.5V2, windowed (at the moment of crash it was hidden under other windows), shift+U mode, connected to LFS director, playing replay of race on FE4R. Crash address: 0x00000000004aa9b2.

Thanks for this crash address as well, I have now tracked this down and removed it. It was in some very old code that produced values that were not even used any more. So that's cleaned up now along with some other related old variables.

Great, V6 solved the V5 crash for me.

Hmm..
This is rather funny because I haven't seen anyone mentioning stuttering of frames and sound with V6.
However I have this problem on two different pc's since the upgrade from V5 -> V6.

System1; AMD athlon 64 3400+ and ATI 9800PRO
System2; AMD athlon 64 3200+ and ATI 9600XT

System2 is effected the most and you can spot some short delays in just a few seconds. The FPS however stay in the 75-85 range.

With system1 it's not so obvious, so maybe 1 min. it runs as it should but there are some definate, short delays in both sound and frames once in a while. The FPS however is in the 95-110 range. Vsync on, 93Hz, doesn't help.

I have used all the testpatches from V1 up to V6 with no problems. Before V6 LFS ran a smooth as possible on both pc's as you would expect from such FPS.

I know this won't be able to help you with something concrete. But I just thought I should let you know.

(All these observations have been made in single player mode)

Quote :

Vsync on, 93Hz, doesn't help.

So, have you tried turning VSync off?

Yes, I mean vsync on doesn't help the situation. Still the same stutters.

i'm having some problems.. i don't know if it's some button i clicked, but today when i was starting lfs, i had no sound
i tried shit+N like 100 times.. and nothing.. it only appeared on the screen:

SHIFT N - som - Não
(SHIFT N - sound - No)
(x the times i clicked it)

i have my sound options all to the max.. and it's not from my headset or something, because i can hear music from my music player..

help please!

Not often i post in here, if at all really, but some things i noticed that are in my eyes not correct.

on the fuel gauge we have the new little icon, very nice addition but on the left and right of that there is a '0' and a '1' wouldnt it be more correct to have it as 'E' and 'F'.

and how hard would it be to make this icon turn orange lets say when it gets less than 5% fuel left in tank

Crash address: 0x000000000041dd13

I was running Dr. Watson because LFS crashed, and I wanted to bag the error again. It says "No faults detected". Useful! LOL

I got the error, spectating on a V5 dedi host. First time was when I went to Shift+U. The second time (address above), I was just spectating in TV camera.

Thanks Sam, but already reported by hackerx and now fixed

Scawen, what is the new line "Refresh"? A noun, or a verb as imperative?

It's a command, I guess that means an imperative verb.

The new "Refresh" with a capital letter is just the same as the old "refresh" with a small letter. But this new one is for refreshing the host information after you have pressed the ? button in list of games.

There is a new test patch V7 with two crash fixes and one update for the colours of the pointer for cars which are more than a lap behind you.

Lfs crashed when I decided to swap cars on single player...Hope this report helps! (click attachment)



Maybe I should also mention this somehow corrupted my profile, and can't open it anymore...Have to make a new profile now...

Yes, that report did help, thank you.

I've fixed that rare crash and now the update is Test Patch V8.

I can't keep up with you can you put the lfs auto update back on.

Quote from Nathan_French_14 :

HOLY MOLONY! You Dev's are on fire!!

Nice great work. I got my mini map update.

The map update is small but it will be very, very handy.

Thanks for the mini map update Scawen. And also a very big thank you for everything you're doing for this great game. Keep up the good work, it's highly appreciated.

Quote from faster111 :

I can't keep up with you can you put the lfs auto update back on.

auto update is only for major patch releases, not these test patches.