In M7 Polish characters are working correctly in VK.

Cosmetic note on ą character (a with ogonek/peduncle). In LFS font, the ogonek should be more aligned to the right.
www.twardoch.com/download/polishhowto/ogonek.html

Quote from matze54564 :

Edit: The Upgrade to M7 works not. The exe and zip, both are damaged.

I can confirm that. Both files are corrupted, cannot patch to M7.

Virtual keyboard is interesting. You can even run Window's task manager by clicking there on CTRL+SHIFT+ESC.

TIP on Polish keyboard.
Most national characters are typed by combining AltGr with Latin equivalent. The only one exception is źŹ (Z with apostrophe) it is made from AltGr+X beacuse AltGr+Z is occupied by żŻ (Z with dot above).

Hi Scawen

At work I have two monitors connected in unusual configuration. Left one rotated vertically and right one in standard horizontal layout. Resolutions are corresponding: 900x1440 and 1920x1200. Perfect testing environment.

As you can see on first screen-shot, LFS is incorrectly (or maybe it is the Windows itself) calculating screen object positions. Interesting thing is that when I press Win button and start menu appears, calculation of screent object positions is becaming correct. >:|
It does not matter if I set main display on left or right monitor. The same is also happening on normal window dragged to be visible on both screens.

It is Win 7 Enterprise 64bit SP1.

Last edited by yaper, Mon 25 Jan 2016, 15:43.

Scawen,
While playing with SHIFT + U one thing annoyed me more than others. I was unable to quickly change FOV. Could you make mouse roller working as FOV modifier (zooming) instead of moving back and forth?

Issues with tyres heating/cooling is the main thing which took me out from driving in LFS some time ago. Right now after few laps of faster driving tires are starting to sleep a lot and driver starts struggling to keep the car on the road.

Unfortunately new tyre physics is delayed and we see a lot of people leaving LFS servers. I bet tyre heating/cooling is the one of main factors for doing it. So maybe Scawen should really think about changing some coefficients/parameters in the tire heating/cooling model to quickly help in that department. This will be really helpful during wait for new tyre physics.

I'm also thinking that temp/grip ratio can be right in LFS. The main problem is related to the speed of heating/cooling process. In real life it is very hard to keep that high tyre temperature, while in LFS tyres are heating quite fast and after that it is very hard to cool it down. I also noticed that in cars with small wheels (UF1,UFR) this problem is less severe. Smaller wheels are rotating faster which helps cooling it.

Scawen
When you are in cockpit and adjusting FOV by keys 5/6, information about current FOV shows always only main screen FOV angle. If you have defined side screens, it should show overal FOV angle, or maybe both: " FOV 75° (main: 28°)"

That's why I'm not translating track variation names.
IMHO, it is better to always call it with original name, otherwise it is confusing and looks weird.

Quote from Victor :

As for fraps, I'm not sure you understand how LFS Record works. The point is that you don't need fraps anymore, because LFS Record will do the recording for you, albeit without sound for now. LFS Record does the recording in such a way that it allows you to set a certain FPS you want to record at and that _will always work_, as opposed to fraps where you must choose a resolution and quality that your computer allows to record realtime. LFS Record recording is not realtime.
That means you don't need to slow down the replay anymore. You can just keep it at 1x.

I know how it works. Just wanted to give possibility to record it with sound.

I can crash LFSRecord (2.0.3.0) when clicking on "Stop Watch" of LookCamera's property LookAt, which is bound to property Position of Null Layer made from car data.

My improvment suggestions for LFSRecord are:
- Make it able to start designed animation while being in LFS (some kind of hotkey maybe).
It will allow to start Fraps recording together with animation start (by assigning same hotkey for both programs).

- Add an option in LFSRecord to define camera animation playback speed (0.5x, 0.25x).
Then we will be able to record animation live with Fraps. By recording it in half speed we can reduce probability of shuttering, because LFS will have double the time to generate the frame. I'm using this mode to record fluid LFS movies. 15fps recording in 0.5x LFS playback speed. Then doubling its audio and video speed in VDub, making 30fps movie.

http://www.virtualr.net/iracin ... re-model-video-interview/

Very interesting chat. I can't wait to compare his and Scawen's tire models.

For me, ideal would be to add new inSim button type - hyper-link, which will allow to jump to another server.

It will be very useful for my future project (not started yet): Multi Stages AutoX, which will allow to compete in AutoX events spread across multiple servers in a stage-by-stage way. Just like in rallies.

Quote from Feffe85 :

But IRL you can get take it out of gear, without clutch and it doesnt damage the gearbox. So why should this "sim" be anyway different?

I wanted to say you can only get out of the gear, but not go into another gear in that step.

Quote from Degats :

Originally, LFS stopped you getting out of gear unless the clutch was depressed, but it was changed to allow the box to go into neutral without pressing the clutch pedal.

This was largely done to stop people cheating by putting the physical shifter into the next position early, then briefly mashing the clutch at the right time to change gear much faster and more reliably.

Short of FFB shifters, I'm not sure how this issue could be solved.

Yes, this problem is the biggest issue with present model in iR. In H dog box you can pre-set next gear while being on full throttle, and then just lift for a split second to have this gear engaged.
My idea to bring it back to LFS is to allow H pattern box to select next gear only in case when registered-physical position of the lever is on neutral position.
In other words:

• When you are on 2nd, LFS is registering current lever position, and you can only get out of gear in that case.
  
• When LFS will find out that you put stick into neutral position it will try to go out of gear. If transmission will be unloaded (lift, blip, or clutch depending on situation) it will go out to N and register that. If transmission still will be loaded, 2nd gear will still be registered.
  
• Next, the driver will push the lever into 3rd gear. Now LFS will check which gear is registered. If 2nd gear is registered (failed getting out of the gear) then it will switch to N (keeping the gear still registered until user will select N). If neutral was registered, LFS will continue to engage selected gear.
  

This will require to go through N in the process of gear changing.

Quote from Degats :

I know that would add a little realism, but would there really be any situation in LFS where you would want to turn on the ignition and *not* the engine?

Currently LFS simulates all the ignition stages that matter (stalling keeps ignition on and you have to reset to start the engine; pushing while on turns it off; pushing while off turns it on.

In the past (right before engine stalling was implemented IIRC) the starter actually engaged with the engine for a little while, and it was possible to move the car with the starter. I'm not entirely sure why that was removed. Ed: I suppose it's possible that the starter hasn't got enough torque to move the car

I was suggesting that just to remove need to double press of button to restart the engine in case of stalling it.

BTW.
You can still move the car with the starter.

Quote from scipy :

Imo, the only things to fix in LFS transmission modeling are:
[...]
3. Gearbox damage. Stresses on gear teeth and dog rings can be calculated pretty easily and a wear model could be introduced, this would be especially handy in endurance racing and it would force people to learn how to take care of their cars (and not skip blipping the throttle).

Sure, this is the item which has to be done. This will extort the driver to threat the gerbox more like in RL.

Latest build of iRacing has kick out LFS from the place where it was the leader of all sims - transmission simulation. This was another time when competition has proven that LFS had something revolutionary but wasn't polished up to the maximum. LFS still has advantage having engine stalling and clutch overheating, but pure transmission simulation is designed better in iR now.

First lack of the LFS transmission model is that we have only syncromesh H pattern gearbox. It is mounted in GTR cars (UFR, FZR) instead of H pattern dog box, where you can do clutch-less up/down shifts without need to exactly match engine rpm to gearbox rpm. LFS have dog boxes but only sequential one (you can up-shift just by lifting off, no need to wait till revs will drop to the level of next gear).

Second LFS' transmission problem is that you can get out of gear in H pattern box when transmission is loaded (full throttle or engine braking). Only in sequential gearbox it is implemented correctly, but I don't know why it isn't in H pattern one.

Of course gearbox grind noise should be implemented when driver wants to change gear and revs are not matched, but this was suggested many times before.

I have also suggestion for ignition switch button in LFS.
Short pressing of this button should just turn on/off the ignition. To initiate the starter driver should press and hold it for one second.

It should behave like below:
-> Short press
---> Long press

Ign ON -> Ign OFF
Ign OFF -> Ign ON
Ign ON ---> Ign ON + Engine starting (with starter gear grind against fly wheel)
Ign OFF ---> Ign ON + Engine starting

Another approach for favourite servers.

* Go to LFS World
* Click on Racers & Hosts Online
* Search for your favourite server
* On its Join column make RMB click and from context menu select Add bookmark for link (works in Firefox, not checked in other browsers)
* Make browser's bookmark folder "Favourite LFS Servers" and add there bookmark for chosen server

In case of having more favourite servers repeat the steps.
Enjoy you favourite servers in your browser bookmarks.

Quote from Scawen :

You are pointing out an issue with tyre heating / cooling that exists in the old physics and is not yet cured in the new physics. I found it was impossible to change a few numbers and fix that - I need to improve the tyre surface and rubber heating model.

Scawen,

Some people already had interesting thoughts about problems with LFS tyres heating/cooling. Maybe if you do some research on below posts/threads, you can find something that can help with your work.

http://www.lfsforum.net/showthread.php?t=5778

http://www.lfsforum.net/showthread.php?p=1148554#post1148554 The whole thread is interesting but sometimes you need to skip the spam.

http://www.lfsforum.net/showthread.php?p=769581#post769581 +next posts

http://www.lfsforum.net/showthread.php?p=819979#post819979

http://www.lfsforum.net/showthread.php?p=1210219#post1210219

I think that LFS can threat some national characters as white spaces, causing to wrap it just up to that character.

In Polish translation, I spot that it can sometimes wrap so unsuccessful, that the single dot is moved into the next line. See attachment.

So, looks like there are some bugs in word wrapping routines. For me, words should be wrapped only at SPACE, ENTER, TAB. But not at comma, dot, colon or national characters.

Quote from pasibrzuch :

First, (pic 1) in all languages the word 'Speed' is in the lower line. It could be more estethic if whole Live for Speed name was in the same line.

This is up to Victor, to tell us if we can use in our translations some special tags like for example "\n" for line brake.

Quote :

I've asked my ex, witch studies Polish language, and she says it can be just "LFS", without any letters.

You are absolutely right. It's corrected now.

Quote :

Another thing is .lyt files called KJS. It's very good because everyone here knows what to expect, it's the same as autocross. But .lyt files are used also to change runoff areas on tracks (forced by servers etc.) right? In this case layout has nothing to do with KJS, but I will just point this out, I've no opinion about this.

This is another story. The layouts was created to use mainly with auto-crossing. The other cases when layouts are used are only the exception confirming the rule.

Quote from Victor :

hm odd. It should remember the installation language and use it during the uninstaller. Not sure why that didn't work for you.

Right now I tested the latest version, and unistaller is showing text in Polish.

One note about language selection removing.

I tested installation on my corporate laptop. It has English WinXP installed, and LFS is choosing English as an installation language. I set all the regional and language options in control panel to Polish, but it doesn't help.

During installation I can thankfully switch to Polish language, but uninstallation is running only in English.

You probably forgot to unlock your calibration. Recalibrating without unlocking is useless.

This is how I'm calibrating clutch pedal in LFS to be working only in the middle of the pedal travel.
- Unlock the calibration.
- Press pedal to the position where I want it to the fully disengage
- Click C on the clutch axis
- Depress the pedal to the position where I want to have bite point
- Press a little to locate the pedal between above two points
- Lock the calibration.
After that I have the real behaving clutch.

Quote from AndRand :

I am really curious about description from experienced LFSer - I know FD301 and 401 are really light and servomotors driven so its quick. How about lags or unnatural feel of acceleration. I experienced driving in Michelin simulator based on Citroen C2 for demonstration of proper tyre pressure (and won key fob for driving the test ride till massive pressure drop ) - this simulator felt really laggy as its hydraulics moved the whole car body.

AndRand, You are probably talking about this simulator:






It was a nightmare to drive it. The lag was about 1 second, I turned into a fast corner, then straightened the car, and after that there was a feel of lateral g-force.

I have quick experience with FD301 too, and it was more shaky than gradual. Plus longitudinal accelerations was much stronger than lateral. I was working with the guy who owns (probably the only one in Poland) FD301 and we was trying to set up the parameters of the forces. We was trying to increase lateral forces but there was problems with it because it causes FD301 to do the oscillations (just like a FF steering wheel at high FF settings).
I was hoping that FD will help me to fell then my back is stepping away, but to be honest I wasn't able to feel that moment. Maybe that's why they introduced FD401, which has the yaw angle simulation.

Quote from ADX.14 :

Options - View

Look function: steer

Rotate view: doesn't work.

Probably you are using CamLevel.

You don't have to have more than one monitor to use multi-monitor functionality.

It does nice job with one monitor too, just add monitors in LFS and experiment with monitor angle. It can offer you fish-eye projection.
You can have the same FOV, but gain better visibility of the dials, or you can extend your FOV without long arms effect. It creates some barrel distortion, but this is better than long arms. And of course stronger videocard is required, because it eats a lot of FPS.

See and compare attached pictures. Parameters of the view are in file names.

Last edited by yaper, Thu 22 Oct 2009, 21:30.

I was mention about the similar system some time ago:
http://www.lfsforum.net/showthread.php?p=1288929#post1288929

I was even talking with Victor, about extend his autocross competition system
http://competition.lfs.net/lx_autox/
to be able to manage and run sequential server-layout event. But there was to many things to modify, and the conclusion was that it will be better to run such system from the scratch.

The plan for me was to write my first inSim application, which will be controling multi stages autocross event. But as always, lack of free time caused me to abandon that.

Maybe we should start the thread in Program / InSim requests part of this forum, to find someone which will be able to write this kind of app.

Quote from MudPuppy :

It should be set up so that no one would be able to practice a whole event in advance.

Unfortunately this is the biggest problem with it. We will need an server side option to disable layout saving at the client.