Hi.
It's not a major thing... today I've found a small track name typo in the detailed Race Results report on LFSW. It's Fernbay, while officially it should be Fern Bay. Check the picture. (As long as I'm not finishing my next race, you can check it out on my profile on LFSW, clicking Last race information and then Details.)
Yeah, maybe a bit late, but I remember I got this error too while trying to update LFS to 0.6F using the automatic in-game updater. Running Windows 7 here, tho.
/off Scawen, I've found a small typo in the Oculus setup part of the 0.6F information page and in the Setup Instructions text on Oculus Share (here).
5. section, 2. paragraph, 2. sentence: "This mey be available when your desktop is set to extended..."
/on
It's been discussed already, just can't find that thread (As soon as I find it, I will add it here) (This should be in the improvement suggestions forum, imo)
Sorry for not being clear, I meant the default original textures supplied with LFS. The times I measured are from pressing OK to the disappearance of [generating].
Great one, fixed my crashes. Finally made the table, I hope I didn't mess up those calculations too hard. (edit: for example Blackwood 1 means BL1 (GP Track), Aston 7 means AS7 (North))
Prepared a whole Excel table to compare the original and the converted tex. speeds and the program keeps crashing at random. Sometimes it successfully converts 5 textures, sometimes 25, sometimes even 60. And some of them couldn't be opened.
Crashlog example:
Problem signature: Problem Event Name: BEX Application Name: LFS Texture converter.exe Application Version: 0.0.0.0 Application Timestamp: 53930a33 Fault Module Name: StackHash_0a9e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 10c05876 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1051 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Hi, noticed a small typo in the CMX Viewer 0.6A, see the picture. Instead of Cloudy Afternoon it's Cloudy Afternoo. It doesn't change if I select other cars or weather types, so more likely it's a typo rather than a programming bug or a text object bug.
I can confirm this, the track image became grey. Oh bro ... great job ... but ... how the hell do you spot these bugs?!
1. Singleplayer - 2. Track - 3. Select for example KY1 with clear day weather - 4. Press OK to load the track and weather - 5. Click Track again - 6. Write the /weather=2 command to change the weather - 7. the game hangs a bit and then the track image becomes grey.
Last edited by MandulAA, .
Reason : Added a more understandable method to reproduce it
Recreated the pics (at least tried to) on the cars' info pages on lfs.net in bigger resolution. Maybe The Devs will replace those outdated jpgs (don't ask why are they outdated, I just don't like them, they seem so noisy on my monitor ). All (20) cars pictured (order is like in the garage, starting with the first row). Feel free to use them for anything
Are you using the newest version of LFS (0.6E)? Could you provide us some more details and screenshots of the error? If you get a windows error reporting window (or what's that), click on details and paste the log here. Finally, you can try the newest test patch to find out if that's an error which is now fixed or not. (0.6E15: https://www.lfsforum.net/showthread.php?t=85807)
EDIT: I saw that you started a thread in which you ask for the original dds files because you want to install a night mod and so on ... Try reinstalling LFS completely, maybe you installed/replaced so many or important files that makes LFS unstable. Dunno.
Don't know if it's fixed or not:
Downloaded the newest SoftTH (v2.08b alpha test) from their forums, placed that d3d9.dll in LFS folder. LFS started up normally. Started connecting to a host, while connecting switched to windowed mode (Shift+F4), and then back to fullscreen while still connecting to that host, no crashes. Connected to that host, no crashes. Everything seems ok. Now I don't know what happened at Fordie, maybe you know what should and what shouldn't happen, just tested it.