I have also reviewed the Danish translation and found a couple of typos and have a couple of suggestions for alternative formulations. Red words are to be removed, green words are corrections of typos or additions.
First screen:
Denne wizardinstallationsguide vil guidehjælpe dig gennem installationen af LFSLive for Speed.
License Agreement:
Velkommen til Live for Speed!
Inden du tager dette software i brug, skal du læse og acceptere følgende :
- Live For Speed er under udvikling. Funktioner kan til enhver tid blive tilføjet, opdateret eller fjernet fra tid til anden. Visse funktionelle men endnu ikke færdiggjorte funktioner kan være indkluderetinkluderet for at forstærkeøge variationen og indholdet i simulatoren.
- Der ydes INGEN garanti af nogen slags på dennedette software.
- Installation og brug af dette software er på eget ansvar. Udviklerne af Live for Speed tager ikke ansvaret for personlig skade som måtte forekomme ved brug af dette software, eller en hver nogen form for skade på dit pc-system inklusiv skadede filer, tabt data eller skadet hardware.
- DEMO indholdet i dette software gives gratis til alle til fri afbenyttelse. Det DEAKTIVEREDE S1 og S2 indhold i dette software er kun til brugere medS1 og S2 rettelicens. Du må ikke forsøge at opnå adgang til det deaktiverede indhold, eller hjælpe andre til at få adgang til det deaktiverede indhold, på anden måde end at købe en licens på www.liveforspeed.net og bruge aktiverings menuen aktiveringsmenuen i spillet.
Mange tak.
Shortcuts: Vælg viklehvilkegenveje der skal dannes :
Dan Opret genvej på skrivebordet Dan Opret genveje i startmenuen
I think the installer adds a more finished touch to the product. Keep up the good work.
amp88: Between the nodes you could interpolate with a 2nd order approximation to update the gaps more frequently. I would suggest updating the displayed gap at a fixed freqency always presenting an interpolated value which is calculated from a model that you update everytime you receive a node update.
Oh, I hadn't understood it as he wanted to know when one driver laps another instantly. I just thought he used a timer based update because it was easier than an event driven update.
The combination sounds like the perfect solution
/Morten
Because you're using the split times for calculating the gaps you could use the event that a sector is finished by a racer to update the gaps to the other racers. By storing at which lap and race time a sector is finished for all racers you can easily determine when racers have been lapped: If racer A has not lapped racer B, racer B will update sector splits before racer A, i.e. the lap counter for that sector is updated for racer B before racer A. If racer B has been lapped by racer A, racer A will update sector split before racer B. If difference in lap count of a sector split is 0 gap should be calculated as time diff by comparing the race times stored for that sector; if it is greater than 0, gap should be calculated as lap diff by comparing the laps stored for that sector.
I have no insim programming experience, so I might be handicapped by lack of knowledge. But it works in my head
/Morten
EDIT: My answer seems to have come a little to late...
You've got the right power adapter.
If the green lamp on the wheel lights up when the wheel is connected it receives power from the power adapter.
As suggested the FF may be switched off in either the Logitech driver or in LFS.
I also reccomend the latest Logitech drivers (5.02) since they resolve an issue with random FF jerks when using the Formula Force EX wheel.
avih:
Just thinking out load... With just 1GB of RAM you may be on the edge of what can be stored in-memory if a lot of background applications and services start up when Windows starts. Perhaps the memory usage has increased a bit from Z to Z13 causing Windows to swap more often. Further your HD may be badly fragmented which causes swapping to take even longer.
I have given it a thought on how to deal with the "abusive restarts voters" and have come up with an idea that may work.
I do not know the details of the voting system, e.g. if a vote is only valid for a certain period of time; hence I assume that a vote is valid until the end of a race.
If a racer votes for a restart it must be because the racer do no longer want to participate in the running race. Therefore if a racer votes for a restart and enough racers have not voted for a restart within some period of time, the voter should be sent to spectate, allowing the rest of the racers to finish their race.
Well, you'd better believe it, because a lot of the LFS racers are rather serious sim racers. And the target group of IRacing racers are exactly serious sim racers, who are willing to spend some money on their hobby.
The LFS racers who are facing towards IRacing I believe would be quite happy to pay an extra amount for new LFS contents, however there are simply not enough hands in the development group to make more frequent releases.
In a number og earlier posts complaints were raised against having decreased the text size in the menu screens. However, I think that the smaller text size it not the real problem; it is the poor rendering of the text. The text appears quite blurry as if anti aliased rather poorly. I discovered that by decreasing the MIP bias for text to -0.2 the text suddenly appeared crystal sharp. Maybe this should be the deafult setting if all others experience the same blurred texts?