The online racing simulator
to all ATI owners:
have you tried the omega drivers? they are more reliable and mostly there are less problems.
had an ATI card not far ago and i had problems.... installed omega drivers and i had no problems

BEFORE you download and install:
- the drivers are NOT compatible with Windows XP/Vista x64!!
- Radeon HD4XXX is not supported yet!!
- not supported by AMD/ATI

http://www.omegadrivers.net/ati.php
LFS Z10 just crashed, don't know excactly when 'cause i was downstairs.
Was spectating on the NDR Tbo Server and listening to internet radio at the same time
Attached files
appcompat.txt - 9.3 KB - 318 views
manifest.txt - 1.7 KB - 313 views
LFS Crash. Possible cause: Video Card.
Just had a Crash wile on a cruize server(was 185kms into a 200km bonus!:rolleyes.

Event Viewer says details:

Faulting application LFS.exe, version 0.0.0.0, time stamp 0x4958fd75, faulting module atiumdag.dll, version 7.14.10.636, time stamp 0x496d6d9d, exception code 0xc0000005, fault offset 0x0004ad03, process id 0x13b4, application start time 0x01c994835fa19755.


ATIUMDAG.DLL <==Problem?

My ATI 4870 graphics card? I just did an update for the driver 2 days ago...
Quote from Monkay :Just had a Crash wile on a cruize server(was 185kms into a 200km bonus!:rolleyes.

Event Viewer says details:

Faulting application LFS.exe, version 0.0.0.0, time stamp 0x4958fd75, faulting module atiumdag.dll, version 7.14.10.636, time stamp 0x496d6d9d, exception code 0xc0000005, fault offset 0x0004ad03, process id 0x13b4, application start time 0x01c994835fa19755.


ATIUMDAG.DLL <==Problem?

My ATI 4870 graphics card? I just did an update for the driver 2 days ago...

If you updated driver, try downgrading to version with which you had no problems.
For the people having problem with ATIUMDAG.DLL - do you have Catalyst AI enabled for the profile you're using with LFS?

If so, try disabling it - if that appears to work as a remedy then consider taking time to fill in a bug report at ATI's dev site.

For what it's worth, consider not using CCC and opt for the latest beta of the ATI Tray Tools instead which supports 38xx and 48xx series GPUs.
Yeah, when I reinstalled LFS and applied the Z10, sometimes it crashes just when I start the game, and sometimes during the game.

Quote :Aplikacja powodująca błąd lfs.exe, wersja 0.0.0.0, moduł powodujący błąd ntdll.dll, wersja 5.1.2600.5512, adres błędu 0x00011669

EDIT: oh, and few times I got ingame a shadow error[a red text message]. Before reinstalling LFS everything was fine.
Dunno if this is just me but i've set my G25 to the full 900 but when I put it as 900 in LFS it does full lock at 720, so on my wheel when I turn it like its on 720 it does the full lock in game, and the further rotation to 900 does nothing, unless I set the rotation in game to 90 then it does the full lock, dunno how to explain it really.

- Stick wheel onto 900 degrees
- Put wheel rotation in game to 900, it only moves to 720 then does nothing
- Stick the wheel rotation in game to 90 then it should do the full rotation at 900 degree
Quote from Mc21 :Dunno if this is just me but i've set my G25 to the full 900 but when I put it as 900 in LFS it does full lock at 720, so on my wheel when I turn it like its on 720 it does the full lock in game, and the further rotation to 900 does nothing, unless I set the rotation in game to 90 then it does the full lock, dunno how to explain it really.

- Stick wheel onto 900 degrees
- Put wheel rotation in game to 900, it only moves to 720 then does nothing
- Stick the wheel rotation in game to 90 then it should do the full rotation at 900 degree

Always was like that
Set the wheel turn compensation to 0.0
Anyway, wrong section.
-
(Chacall Br) DELETED by Chacall Br
when one server is in cruise mode the yellow and the other flags are there
i think they need to be removed from the cruise thing
@BOSCHO
Oh snap, wrong section matey... Just copy your language file and remove the YELLOW FLAG and BLUE FLAG text.
its not wrong section
for the next test patch to be without those flag things in cruise
Quote from BOSCHO :when one server is in cruise mode the yellow and the other flags are there
i think they need to be removed from the cruise thing

Thats not a bug (maybe blue flag could be), but in server config you can disable flags (I dont know how. I just know its possible)

Yellow flag works like in a normal race server, and prevent you when someones aproaches in front of you
not bug but its not for the cruise mode
BTT:


For some reason I cant watch my "own" replay...

http://files.filefront.com/so+ ... /;13371958;/fileinfo.html

Switch to Spectator/TV Camera-view and chase me or any other in the first 1/3 of the grid.
Lfs freeze (gfx still there, looping sound), infront of the "tunnel"/bridge every single time I tried. No crash, no BSOD...just a freeze.
For some reason all other views work on my PC.

Maybe it´s too much to handle for my hardware, minimum frames was at 16 at some point. Race was SO Town/TBO with a full grid. I´m on Xpsp3, X2-4600+@2,8GHz, 2Gb and Radeon X1950 Pro.

Anyone can confirm this..?
Quote from VoiD :
Anyone can confirm this..?

Yes,
at about 39 seconds into the replay
In both windowed mode or full screen mode.
e8400 cpu 9600GT 512 gpu 180.48 drivers
XPSP2

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="LFS.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="LFS.exe" SIZE="1843200" CHECKSUM="0x5C430AEA" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/29/2008 16:40:21" UPTO_LINK_DATE="12/29/2008 16:40:21" />
<MATCHING_FILE NAME="lfs_restart.exe" SIZE="77824" CHECKSUM="0x797215F0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/19/2007 16:46:10" UPTO_LINK_DATE="12/19/2007 16:46:10" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="985600" CHECKSUM="0xE7E1F9DC" BIN_FILE_VERSION="5.1.2600.2991" BIN_PRODUCT_VERSION="5.1.2600.2991" PRODUCT_VERSION="5.1.2600.2991" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2991 (xpsp.060907-0105)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF39C9" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2991" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2991" LINK_DATE="09/07/2006 11:59:20" UPTO_LINK_DATE="09/07/2006 11:59:20" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

You have to force close LFS because it doesn't crash out, so the crash address doesn't appear.

[SIZE=1][SIZE=2]Hanging application LFS.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.[/SIZE]
[/SIZE]

It doesn't crash in Z patch, only Z10
-
(MijnWraak) DELETED by MijnWraak
out of stash space
MP Replay - Out of stash space
Lost connection to the server


I've never received this message since I play LFS, so I think it might be a test patch issue.

PC Specs and quick stats
Windows 7 build 7000 - up to date
Pentium D 2.8GHz - 29% in use when received the error
2GB RAM DDR2 - 55% in use, 45% free
HD - 281GB free of 465GB
9800GT 512MB 181.22 (vista 32bits) drivers
Game didn't crash.
LFS Test Patch Z10
1680x1050, AA8x, AF16x, full textures/skies/etc. "Texture usage: 141MB in use"
Racing on NDR|Public Racing
Replay attached. Screenshot attached.
Attached images
enb2009_2_27_15_56_42.jpg
Attached files
temp_mpr.part1.rar - 1.9 MB - 206 views
temp_mpr.part2.rar - 263 KB - 209 views
I had that a few times on my old old old PC (~200MB free HDD space) and disabled auto-replay storage. That fixed it for me (Although I see HDD space isn't your problem). It's not test patch specific though
Quote from dougie-lampkin :I had that a few times on my old old old PC (~200MB free HDD space) and disabled auto-replay storage. That fixed it for me (Although I see HDD space isn't your problem). It's not test patch specific though

And I also don't have "auto-replay" enabled (it's on the default settings: manual).

And I had never ever received that message before, thus why I though it was a test-patch issue. What can I do to fix it then? Enough free RAM: check. Enough HDD space: check. Enough GDDR memory: check. "auto-replay storage" disabled: check.
Is folder on a partition with small space? Is there a windows backup on said partition? My win7 backup took up a bunch of space so i just deleted it.
I have 2 HDDs on this computer:
The first HDD (160GB) is only for the OS and programs, and has 2 partitions.
- 1st partition: Windows 7 and its programs only. 80,6GB free of 97,6GB
- 2nd partition: Windows XP and its programs only. 44,2GB free of 51,3GB

The second HDD (500GB) is only for games and has no partitioned spaces. 281GB free of 465GB

Both HDDs are well defragmented (0% fragmentation on both), last run was yesterday (about 12 hours before I posted about the message I got)

LFS is installed on the second HDD (games only). I have no Windows backups. "Windows Backup has not been set up."

Thanks for helping anyway
I used to get that when my page file got too big due to some bad configuration. (Grew to >1GB when playing LFS for long stints) Keep an eye on your page file when LFS is running.
Task manager shows it in performance tab (XP)

Your crash reason might be different however.
Hy when I started the lfs in full screen mod then jump back to small size and I pressed shift+f4 then lfs is died in windows vista aero theme but I changed the theme to windows vista simple theme then the problem is ceasing. The problem in my computer? Thx the answer.
Attached images
hiba.jpg
Quote from opela :Hy when I started the lfs in full screen mod then jump back to small size and I pressed shift+f4 then lfs is died in windows vista aero theme but I changed the theme to windows vista simple theme then the problem is ceasing. The problem in my computer? Thx the answer.

i have the same problem
This thread is closed

Test Patch Z10 (online compatible)
(533 posts, closed, started )
FGED GREDG RDFGDR GSFDG