I have found another bug with new path system, Scawen, please fix this, this is really annoying.

*grabs popcorn*

Nice one

Thanks Victor, so much time I was waiting for it !

Bug report, with high-res skin uploaded, skin preview in cars section is bugged, see screenshot :

Great to see you again Lynce

Quote from Ziomek21 :

I've noticed that my skins are visibly more smudged in newer patches, compared to pre-new Westhill releases. I've always had all the mip biases set to 0.0, to smoothen the background. Any chance to fix those skin definition problems (check the front of the roof area).

A bit off-topic and already known bug. Use NVIDA Control Panel or AMD Catalyst Control Center to force anisotropic filtering.

@Scawen : Nice, that's why we love you, no "quick fix that will make it work but create 3 other bugs", keep it up !

Quote from D.K.r :

NON OFFICIAL Live for speed for android [...] unity

And then...

Quote from D.K.r :

online still working (wi-fi)

Still working ? Please stop this bullshit please, you have at max one ripped track and one car converted from CMX ported to Unity, you just can make it work with actual LFS online.
But seeing theses "screenshots", I saying that it's just LFS screenshots with notification bar added. There is the same shitty vertex based shadows that Unity doesn't even have, and the same shitty sphere reflections while Unity can do real-time and use only cube-mapping.

Quote from D.K.r :

*conversion from CMX viewer*

Westhill is too from CMX Viewer ?


PS : I already ported old Westhill + XRT on UE4 and also done a CMX Viewer with Keiichi on Unity so I guess I know what I'm talking about.

Last edited by nacim, Wed, 15 Jul 2015 14:27.

Video or didn't happened.

There are also some lights at start of south city (in front of pits), when you pass on this section, interior blink 4 or 5 times due to theses lights.
Maybe it's a leftover or maybe it's intentional, but without shadow mapping lights and shader per-pixel lighting, theses are just weird.

Thanks

Quote from Scawen :

Most of the benefit of the H4 [...] when they are not visible.

Actually, that can be something to try but in my opinion, I don't think that much optimisations is a real priority right now.
I understand that improvements like the one in 0.6H2 with more than 100% improvements in some places can be a real benefit, but I also think that a 5% improvement optimisation can wait for lasts test patches (before stable version 0.6I). I guess it's more logical for me to add new content and features and then optimise it, so maybe you should release the real time reflections system before doing this.

Quote from Scawen :

Physics is computed in single player replays.

That's nice to know, maybe I'll try again later (if someone can send me LFS.exe from 0.6H, that's would be nice, I don't want to redownload the whole game for it).

No, I used a single lap of 5 IAs with FBM @WE1 with replay camera on first IA.
They have done the same time, and I don't think replay is accurate for a benchmark because it doesn't compute physics.

I'm back, with some benchmarks !

Sadly, I was expecting better results.
I don't have 0.6H to try between 0.6H and H4 (but I know there will be a massive improvement due to H2/H3 improvements). Check out PNG for quick results, or PDF for more details.

Thanks, I'll try when I get home (and benchmark it BTW).

@Scawen : I don't know if I reported it earlier, but when you set height at maximum with a custom view, there is clipping everywhere (I tested it with RB4 at Westhill). (I don't know if you fixed it in 0.6H4, but it's not on changelog)

Yep, that's not normal, with my old laptop with HD 3000, I can max out LFS @ 1336x768 and have a rock solid 60 FPS. And no need to talk about the HD 4600 in my new one.

EDIT : Install Intel drivers if you haven't already.

Disable Anti-Aliasing if it's enabled.

Definitely waiting to test it out.

Quote from Scawen :

The reason multithreading is not at the top of the imaginary priority list [...]

TL;DR: Multithreading is nice, S3 content and real-time reflections are better.

Quote from Scawen :

[...] I have to manually merge in all the changes from one into the other. [...]

@Scawen: I know it can be weird to change now when you have years of experiences like that, but I really think that switching to SVN or GitHub (or any other versioning program) will be better for you. You'll have much more control on backups (for example hosting SVN server on a home-made NAS to protect you from data loss on your PC), forks (for example S3 as a fork of current LFS developpement version), etc.

At least do some research on it, I'm sure you can benefit from what it offers you.

Just like the 2000 DEMO users with S2 content I saw before you.

Seriously, I'm getting tired of all these guys.

Quote from kdo :

He also have vobs mods in his profil picture.

And screenshot is in South City, which I don't think is available for DEMO users.
(And no need to say that the picture in itself is clearly ugly and not adapted for a profile picture, but that's my opinion)

Quote from Shirtkicker :

...or people are still working on their entries with a week to go.

Such work, very impressive, wow!

After some hours playing 0.6H2, I have too say that the game has some serious clipping issues since 0.6H.
For example, with FBM, I can see some part of track (especially Westhill) pop in front of me, and when I create a custom camera with max height (camera on roof), I can see clipping everywhere.

Hehe, it looks nice for a start, keep it up !
And thanks for the credits bro.

I understand what you mean now (and BTW, why float are so called float). Thanks for these very interesting informations.
I'll try to use it on my code as well now

Quote from Scawen :

It is metres times 65536. The high 16 bits are the whole metres and the low 16 bits are the sub-metres. So the smallest possible increment in position is 1/65536 m (around 1/66 of a mm). This notation can represent values from -32768 to 32768 m.

Okay, this range gives you way much than the necessary to work with. But what is the real use, what do you mean by "the same granularity regardless of their distance from the origin" exactly, I'm not sure to get the point about this.