Do you mean something along the lines of the following video?

Thanks for the reply Scawen, and thanks to Flame CZE for the link, I had forgotten about that post.

Quote :

Only with the current tyre physics, we had to use unrealistic setups to make the car handle well. That's the good thing, it showed up flaws in the tyre physics

Just curious, what in particular is wrong with the current tire physics, if it's something you're willing to talk about currently?

Ah, didn't even think about trying that. It worked perfectly, thanks!

Got a bit of a problem with my Logitech Dual Action gamepad and the current test patch: When setting a dead zone with the Logitech profiler to clean up the slack around the center of the thumbsticks, LFS sees the center position as -8 instead of 0. I'm not sure if that's a bug with the profiler or not, but it wasn't an issue before these test patches as you could just use the center button and then lock the axis settings.

The look-while-steering doesn't work here only because of the way the little demo program overrides the camera in LFS, if it was properly implemented in LFS itself it'd work just fine.

Ok, here's the same replay with head movement enabled:

I seem to remember Scawen saying he was interested in this, but that was a long time ago so I figure it might be a good time to bring it up again.

For me, it feels much nicer when the camera is more or less stabilized to the external world, not just fixed to the body of the car:

[

I use Laimiss's WR hotlap replay on Blackwood rallyx as it's got lots of big bumps and jumps which show the effect off well.

Just tested it on both my Win10 laptop and Win7 desktop and it seems to be working correctly on both systems and in both cases of full-screen alt-tab and windowed minimized.

In full screen, using ALT+TAB to switch to the desktop with LFS running results in both higher CPU and GPU usage. In windowed mode CPU and GPU usage go down as expected when one minimizes LFS.

Sorry, didn't seem to fix the high cpu/gpu usage, at least on my system.

Last edited by Rotareneg, Tue, 11 Aug 2015 20:23.

On my Windows 10 laptop (with Intel HD4000 graphics) I don't get any lag when jumping to the pits with H6. I do have the high CPU/GPU usage when alt-tabbed from full-screen, even when LFS is just sitting on the title screen. The thumbnail that comes up when I mouse over LFS on the taskbar is black when alt-tabbed, and contains whatever was last displayed in LFS when minimized from windowed mode.

Odd. I'm using Windows 7 with the 353.62 nVidia drivers and a GTX 760. I tried custom resolutions at 1280x720 and it displayed 50, 60 and 75 Hz all just fine. However, at 1920x1080 only 50 and 60 showed up, 70 Hz wasn't on the list.

Ah, I hadn't seen that new graph! This time I dropped the frame rate down to 15 fps to make it more visible, and also included a 100 fps sample. Also, I recorded this with vsync and the frame rate limiter both off in LFS and used my capture software (Dxtory) to synchronize the display frame rate with the recording frame rate. Oh, and this was the AI driving each run new, not from a replay.

My monitor doesn't present any 50 Hz resolutions on my system, but I can add custom resolutions with the nVidia control panel which LFS picks up fine.

Here's a video demonstration the difference between 50 Hz and 60 Hz in LFS, made by taking two recordings and changing the frame rate to 30 Hz for both to make the difference more visible. For me at least, the video playback in Firefox tended to stutter slightly, ruining the effectiveness of the demo, but Chrome played it smoothly so that you can see the difference.



Oh, and if you think it's annoying having to use a multiple or fraction of 100, I have a tank sim, Steel Beasts, that wants to run at 62.5 FPS!

Last edited by Rotareneg, Fri, 7 Aug 2015 04:10.

LOL, I was going to post a snarky remark along the lines of "Wow, why hasn't anyone suggested this before?!?", but then I discovered I had already done so, FOUR YEARS AGO.

Bumping the physics engine up to 120 Hz would make it run smoother for both 120 Hz and 60 Hz displays, which would mean virtually everyone. Probably the only people who would find that change a negative would be people who play on a television that only runs at 50 Hz, which probably isn't very common at this point since, as far as I know, most modern European TVs (LCD, plasma, whatever) support both 50 and 60 Hz.

Quote from ToxicKlay :

Blah, blah blah...

Someone at the gas station asking you how to use some obscure feature of your car's stereo might seem a little unusual, but perhaps they have the same car at home or something.

Someone knocking on your door one morning asking how to use the stereo they just stole out your car is a tad different.

It might be a good idea to try a Linux live-cd or thumb drive and see if it acts the same.

You used a tweak program to remove the turbo and magically increase the engine power to the same level, what did you expect to see? And yes, the turbo (and engine in general) model is simplistic and could use a bit of work.

I just played around with the XFG and it couldn't even climb the hill at the start of BL1R in first gear at idle, which seems fine for a small 1.3L engine.

Electronic fuel injection engines try to maintain idle speed by either using an idle air valve that bypasses the throttle or by directly opening the throttle (like my car, it uses a DBW throttle and tries pretty hard to not stall.)

There's no point to upload videos with frame rates higher than 30 as YouTube will always decimate down to 30 or 25 if the input is 60 or 50 fps.

This is why I find Steam so much better than actual physical copies of the games that can be played without depending on a online service of questionable security.

Oh, wait...

:gnasher:

I think the current sound system, with just slight modifications, would probably work a lot better if there was a "map" of the settings at various engine speeds and loads for the program to interpolate between. At the simplest you could have just have two points for no throttle at idle and full throttle at the redline to replicate the current system (after removing the idle volume boost and off power settings.) If you wanted to give an engine a "VTEC" sound one could add some extra points at high throttle/RPM combinations to make the engine tone change appropriately.

It would seem to be easy to implement, with the GUI elements being even simpler, probably just RPM and load sliders and add/remove and next/previous buttons and a numeric display of the current data point.