@DANIEL-CRO

1. For LFSLazy dashboards, (specifically on XRG) would it be possible to have oil and engine temp needles next to the dials?

When I try move them they only show either between the dials, or above the shifter (middle of car - XRG).

2. If it is not possible to fix (1.), would it be possible to add linear oil and engine temp gauges? (so they can be used as OilLin and TempLin, displayed where the dials typically are in XRG).

Screenshots of the WIP (with permission from Vano Paniashvili):
a.) as you can see the oil and engine temp gauges underneath the RPM dial doesn't have the respective needles. I'm trying to either add needles to both of them, or make them lin-gauges.
b.) I don't want to have to edit the .dds files as well, as its nice to keep the whole mod within one gauges folder.

Yes WHERE is the fix for the run-time 429 ERROR?!

Why leave us at this point, when we're 1 fix away from getting this to work.

@Scawen

Glad to hear, as most of the players I know who play on cruise servers (both demo and S2) have pretty dated pc's.

I really appreciate the dev's going out of their way to keep LFS running on older systems, while pursuing development of nicer graphics and better performance optimization. This looks like a rather risky update though, like you mentioned, each system has to calculate which objects are lit from the headlights of other cars, at night. There seemed to be a lot of optimization needed...

Can't wait for the next major update, thank you for your time and effort

Last edited by alau07, Fri, 1 Mar 2019 15:11.

Rip all players with potato PC have to play during day times only because of a drop in FPS at night.

Hey thanks guys for getting LFSLapper to work again

Couldn't have done this without you Victor!

Also thanks a lot to Bass-Driver and LakynVonLegendaus too for the troubleshooting <3

Last edited by alau07, Mon, 4 Feb 2019 22:44.

Basically the scripts I can access are limited to what is already in their list, any new files created by Lapper don't show on the list, and I can't access the file system.

The developer's definitely need to add the \bin\default\logs folder... I agree that the logs are essential to diagnosing the problem properly.

Given it's a Saturday hopefully the dev's can get it sorted by next week...

Background:
1. I bought a server slot from the LFS website.
2. Lapper worked, but only once.
3. I can use Airio but I don't want my server to just be restricted to lapping/racing.
4. I've tried resetting the "Admin app" used by the server in "Your host" menu.
5. I've already contacted LFS Dev team about this and they referred me to this forum if problems persist.
6. Also LFS Dev team will not grant me local file access, which is fair enough.

Scenario:
1. As stated in the subject, LFS Lapper doesn't connect to the server when I click on "start" on the "your hosts" screen within the LFS.net website.
2. It kept going "LFSLapper in standby state" then when I typed start it would show "LFSLapper in work state".
3. NOW it DOESN'T even show "LFSLapper in standby state", there's just no response to any of the "!" commands.
4. The only commands that do work are the "/" commands, and the server recognises me as admin.
(Note: I already tried changing "Admin app" to "None" to reset the LFSLapper, unless it didn't reset..., I also previously tried copying and pasting the Lapper code into each file individually from the newest release, which only gave me the "standby" and "work" statements above.)

Question:
How would I go about fixing this? The aim is to get LFSLapper working on my server again.

I've read through most of the code of the base file (LFSLapper.lpr) and I can't find any errors (although I just have basic knowledge of C++).