So i tried this blender tool and it's kinda weird to me. I tried importing my Kitchen Rats map because it's kinda of a stress test and this is how it should look like:


But after i imported it, it looks like this:


I think it's mainly slab walls that are weirdly rotated, so maybe that object is not supported yet?
Also i don't quite understand what i'm doing wrong here:


(Ignore all the slab walls being weird) i rotated the selected piece a bit by Z axis which i should be able to do so, only this one object, but when i export it back to LFS somehow many others are affected as well? (different sizes, angles, etc.) And slab walls looking normal.

Ratings seems to be fine in-game, its only website not showing them correctly. I assume someone raited after reupload so main raiting is back on website except for other ones.

Now i know i'm really close to LOD1 limit but i'd like to know how this happened


Stock config which is closest to limit is the biggest one:


I've reuploaded it again, but not sure if that's gonna happen again or not and what was the cause for it.

Quote from Scawen :

Flame is correct. The hard limit that the exporter will allow for LOD2 is 8192, but it is a bad target. A sensible target is around 1000 triangles.

It is common (generally, not only in game editors) for a sensible target to be much less than the legal limit.

However, I am still considering the possibility of bringing the legal limit for LOD2 down to something sensible. In the early days I didn't realise how important it was to be strict about enforcing sensible limits. Maybe the LOD2 limit should really be 2048 or so.

Scawen, if you going to lower LOD2 limit to 2k then don't do it randomly whenever and at least tell when you gonna do it. Because I and probably many others have worked within current limit of LOD2 that is 8k and now mods would get unpublished which resets raitings back to 0 btw. I'm working on lower poly LOD2 but it will take some time as i don't want to just have a box LOD2 that will look shit for shadow and randomly change to box at further distance.

Vehicle mod: GHOUL 250RR
Details page: https://www.lfs.net/files/vehmods/EF6281

SHORT DESCRIPTION:

Quote :

250cc Sportbike

DESCRIPTION:

Quote :

Honda CBR250RR MC22 inspired motorbike made in Blender.

An iconic motorbike that revs to about 19,000 RPM

Highly detailed model with realistic LOD2 for shadows. Includes naked configuration and more to come.

Most textures are made by me using Gimp, Blender, some are taken from original LFS files.

Adjust inside camera to see the dials.

COVER SCREENSHOT:

Quote from AR92 :

I'm not really sure this fits to "way too smooth" definition:

Plenty to save there

Quote from AR92 :

One of my mods has 480 tri for single spoke and can't really find a way to reduce it more without losing details, and cuz of this, it only permits to increase it to 3 spokes yet i need 5 more to complete a old steel rim, and it looks like this:

You can surely optimize that a lot more imo. It's really simple design, it shouldn't need that many tris. Suppose the holes are way too smooth.

Quote from Scawen :

Have you learned to use the rim editor properly? This is not clear from your reply.

1600 triangles for some spokes is way more than enough.

I wouldn't call it "way more than enough", i'd say it's "just enough". I don't try to make them high poly, just to look good enough but it's always around the limit. One wheel i made for new mod is around 1400, so just enough, even though it's set as hub object anyway.

Also i never included the rim into the spoke model. Center core could be deleted but then transition from spokes to center core is sharp. Also this is rear wheel, front wheel center core is more exposed.

But anyway, for Chimera i relocated spokes to hub sub objects so all is good.

Can we have it at least double that for bikes? Because wheel is visible from both sides unlike cars and only 2 wheels instead of 4.

Some of my bike wheels are right on the limit while the more interesting spoke design of Chimera is double the limit. I could optimize it a bit more but not that much. Before i exceeded the limit on those rims i tried simpler design and it looked awful.

Quote from KiiT1337 :

On this last update, when changing lights from side/low beam/high beam, only one side light up, then the other, and when flashing high beam only right headlight really flash.

Well on real bike, left one is a low beam light, right one turns on when high beams are switched on. So i thought it's a bit more realistic. For flashing i don't know it might look weird if you don't have low beam on. Also i didn't really find how flashing high beams look like on this bike. I will add different modes to other configs that has both lights on with low beams and high.

Quote from Scawen :

Thanks. Can you think of any more info, were there other people there, were you in your own vehicle, what sort of things were on screen? Did anyone else get a crash at the time? Were you using any special draw modes?

I don't know if any one else got the crash but i just left pits with XRR and game sort of lagged for a bit then froze and crashed. It's nice that you found the issue

Had a crash on D64 in multiplayer

Faulting application name: LFS.exe, version: 0.0.0.0, time stamp: 0x657de650
Faulting module name: LFS.exe, version: 0.0.0.0, time stamp: 0x657de650
Exception code: 0xc0000005
Fault offset: 0x0017d1c1
Faulting process id: 0x25dc
Faulting application start time: 0x01da30ef3db70621
Faulting application path: D:\Program Files\LFS_0.7D\LFS.exe
Faulting module path: D:\Program Files\LFS_0.7D\LFS.exe
Report Id: 423208f2-00e7-4558-882d-243455909f7b
Faulting package full name:
Faulting package-relative application ID:

Small issue, but ignition switch test is missing in vehicle editor. I got one slider connected to that but in order to test it i have to change it to horn or something.

Quote from mwbeatzz :

Bro, its really weird the bikes in D63 Compared to D57, i dont feel conected with them anymore in my strering wheel, its light weight and not in a good mean, looks like a bug bc this thing has A kind of slowness to control, I don't know how to describe it well but it's strange, I don't know if you've seen anything on the bikes from D57 to D63 that changes this but it's very, very strange , you changed something in the steering correction? Ples, im really sad bc im completly fall in luv with the 57 handling i really aprecciate your work on this amazing game <3

D63 Is not a thing, also last bike physics update was patch D46. I drive bikes in LFS daily and i can assure u that nothing changed in physics since then. It must be on your end or it's mod related.

Mirrors doesn't seem to work on rotators. I've made wing mirrors but they just dark. I guess similar issue like mirrors on steering wheel.

Quote from Scawen :

That message is not per LOD, it is a total limit of triangles for a single object, including all LODs. I don't think it can possibly have changed in a recent version. Maybe if some parts of your object's LOD1 could be placed in subobjects you would not hit that limit?

I suppose i could relocate some parts into other objects it's just i was confused because D52 let me merge into main even though it didn't let me to duplicate though. So maybe it was a bug because i tested D52 how much i could merge into one object.

Unmirrored everything so only one side would be visible so limit should be 32768 i guess. On my Reaper when i unmirror everything and enable all layers, tris count is like this: LOD1-32201 LOD2-5198 LOD3-26 = 37425, way above 32768 because before it let me merge more than it should i guess. Also i tried merging as much as i could on D52 and it went to LOD1-60346 LOD2-5198 LOD3-26 = 65570, for single main object if i merge one more triangle, whole mesh disappears.

But in D53 it's fixed so i guess i'll have to figure something out. I was avoiding attachment objects because i thought they would disappear sooner than LOD2 kicks in but if that's not the case then it's good.

Can we get rid off this annoying limit/restriction message?

I'm trying to add few triangles to LOD2 and it's not letting me, i'm not breaching 8192 tris limit afaik. That's with all LOD2 layers turned on, wouldn't be driving with all of them on anyway. It gives same message if you try to duplicate triangles as well, even though there would be space for them.


Same for LOD1, can't add it, even though it worked in previous patch. I know because i already added those triangles before into the mod and i've tried doing same with D53 and it won't let me.


So i don't know what is going on, it's giving me a headache

Ye it turns off the light while indicator is enabled then turns back on. On american cars even the rear tail lights do the same.

Found weird bug with bike suspension. If you select stock set, make a new one and raise the front to max then pick color, front wheel moves back a bit. Click on setup and it moves forward. Wish it was only visual bug, but once you spawn, the wheel is slightly back. Resetting the bike fixes it, though after some braking, accelerating, not even 100 meters, it moves back.



For Chimera it does weirdly only on Standart and Custom 2 configurations. other 2 configs with golden forks spawn correctly, although they still have same moving wheel bug in garage while selecting colors and setups.

Also i'd like to point out that swingarm moves away from the wheel if you increase the ride height a lot. Well it moves a bit either way just less noticable. But i guess there is no way for it to know where the wheel should be attached to.

Quote from Slashpca :

On bikes they crash brutally on the high speed kink style corners on West Hill and the start finish at Blackwood on motorcycles for me. Seems as though they come in way too fast and start to steer way too late. If I lower them to level 2 or less skill they stay on track but they're hilariously slow elsewhere.

I've tested your bike on Westhill and they can't even make past the second turn without sliding off the road (out of 10, 2 crashed on the first turn). Must be issue with insane downforce on that bike.

I love these new physics now, thank you Scawen, i got no more complaints. Its as good as it's gonna get in these old physics. You can actually drive fast now without fighting the bike too much. Offroad driving ability also increased a lot even if as side effect.

Quote from kristofferandersen :

I'm not able to get the view low enough to see the dashboard gauges on the bike.

I use custom view so you can actually move it back a lot more in Y axis, sort of placing it inside the riders helmet so it doesn't obstruct the view and then pitch it down a bit.

Quote from Scawen :

To my mind, the D45 low speed model has many advantages over D44. So I would like to really understand what exactly is the issue you experience, what makes the "drunk rider" experience of D44 better (at low speed) than the more "in control" experience of D45.

While yes the D45 is a lot more stable at low speeds and it's harder to fall (i assume for people who use mouse or gamepad), it also limits you severely. With D44 i can drive through tight corners a lot faster by flinging the bike left and right. Yes it's a lot easier to fall but it's also a lot more maneuverable.

I've attached a layout and 2 replays one with D44 and one with D45 so you can hopefully understand my problem. If you enable virtual steering gauge, on D44 i don't even max out the steering angle on those corners while on D45 i max it out and then have to wait for the bike to actually do something. It's also a lot slower because of that.

In my mind D44 is more "in control" at low speed, as you do the driving, D45 sort of takes the control away from you because it expects you to fall and slaps some training wheels on I mean that's how it feels like.

Well i did an even faster lap on Westhill international (added SPR), could've gone faster but was a bit cautious with hot tires at the end there.

Really love the stability now, it's super stable on braking zones, fast corners, even bumpy roads are not a problem now. Before the bike would unsettle a lot if you tried to take a fast corner on a bumpy road. And it's still as nimble as before.

Quote from Scawen :

With such a report, it is better if you can tell me a specific bike and roughly what speed and what you were trying to do. Otherwise I really have no idea where to start.

I think what Marty is trying to say is that low speed model and interpolation between the low and high speed models have less sensitivity and you have to turn the wheel more. I don't really like it myself either. High speed model feels very responsive to controls so driving above 72km/h all is good but when you drop below that, sensitivity starts to decrease and you have to turn the wheel more to make the corner. I suppose it drops sensitivity gradually and that's why it feels weird and unresponsive and hard to know how much to turn the wheel at certain speed.

I'd prefer D44 low speed handling it was very responsive, doing low speed figure 8's or u turns on a small road was so easy. Good way to test that between the versions is to load Karting national it has plenty of slow turns. I'm sure most of the bikes act the same but i was using Reaper X1 for testing that.


Also, is tire digging into the ground will be fixed in the new tires physics? Kinda messes up wheelies and stoppies now

Last edited by Drifteris, Sat 28 Oct 2023, 15:09.

Quote from sinanju :

I get a 'replay OOS error' when I try to play both of your files.

I'm using 0.7D44.

It seems like SPR files don't download mods, so if you don't have it then you get the error. Try downloading it through mod browser in-game first then launch replay