- Un-mirrored rear side door to right side only
- Two base configs so far: passenger and van (more to come later with different headlights and grille)
- Two base configs so far: passenger and van (more to come later with different headlights and grille)
Optimized tris to fit within the limit, now beginning with texture mappings
Good that you got it sorted.
I'm wodnering, where did you find the download link in the end? It's quite surprising to me that you couldn't find the download link when there's a big button saying "FREE GAME DOWNLOAD" on the LFS home page, and a "DOWNLOADS" link as well.
I'm wodnering, where did you find the download link in the end? It's quite surprising to me that you couldn't find the download link when there's a big button saying "FREE GAME DOWNLOAD" on the LFS home page, and a "DOWNLOADS" link as well.
bad LOD2
Last edited by Flame CZE, .
Great mod! 
Please update the car screenshots, as Pasci said, it looks much better in game now.
Also, the engine sound is kinda clipping, it can get a bit annoying at times e.g. in garage or tunnels, do you think you can tweak it a bit?
Please update the car screenshots, as Pasci said, it looks much better in game now.
Also, the engine sound is kinda clipping, it can get a bit annoying at times e.g. in garage or tunnels, do you think you can tweak it a bit?
You can use the following InSim packets:
A car hitting a wall: IS_HLV
Car to car contacts: IS_CON
Layout object collisions: IS_OBH
A car hitting a wall: IS_HLV
inSim.connect({
// ...other connection options
Flags: InSimFlags.ISF_HLV // enable receiving IS_HLV packets
});
inSim.on(PacketType.ISP_HLV, packet => {
console.log(packet.HLVC === HLVCViolation.WALL); // wall hit
})
Car to car contacts: IS_CON
inSim.connect({
// ...other connection options
Flags: InSimFlags.ISF_CON // enable receiving IS_CON packets
});
inSim.on(PacketType.ISP_CON, packet => {
console.log(packet.A.Speed); // speed of car A
console.log(packet.B.X); // X position of car B
})
Layout object collisions: IS_OBH
inSim.connect({
// ...other connection options
Flags: InSimFlags.ISF_OBH // enable receiving IS_OBH packets
});
inSim.on(PacketType.ISP_OBH, packet => {
console.log(packet.Index); // object index
})
Can you please upload the images as attachments instead of using a 3rd party service (Imgur)? Then they will be stored here forever and won't be removed if the Imgur goes down.
The new steering wheel option works well for my MOZA R3 wheel, I'm getting the bump stops now. Thanks for the quick fix
I tried this and it didn't help - it still shows up as a joystick (first person controller in LFS).
This is the output from USBTreeView:
++++++++++++++ HID Information +++++++++++++++
Manufacturer : Gudsen
Product : R3 Racing Wheel and Pedals
Serial Number : 2A001D001151333033333434
UsagePage : 0x01 (Generic Desktop Controls)
Usage : 0x04 (Joystick)What if the "First person controller" text itself became a clickable button?
I unplugged the G27 so only the MOZA R3 is plugged in, but still I don't get any bump stops.
Okay, then something must be wrongly configured on my end and it's probably not a bug. Thanks, I will have another look. I have connected both my G27 and the Moza right now, maybe that could cause the issue?
When I set the wheel rotation manually in Moza Pit House software, it works perfectly as you describe. But I want LFS to automatically set the rotation for each car so I don't have to jump into MPH and adjust the rotation manually every time I change the car.
The wheel turn compensation set to 1.00 (max) makes sure the physical wheel turn always matches the in-car steering wheel, provided that the max is set to at the actual max angle or more.
Here's an exaplantion from Scawen. Point 1) applies in my case:
This worked well with my G27 - I could feel a bump stop when I reached the maximum lock angle of the given car.
For demonstration, here's a comparison of me turning the G27 wheel past its full lock and then the same with the MOZA R3. Pay attention to the FFB graph at the bottom right:
The wheel turn compensation set to 1.00 (max) makes sure the physical wheel turn always matches the in-car steering wheel, provided that the max is set to at the actual max angle or more.
Here's an exaplantion from Scawen. Point 1) applies in my case:
This worked well with my G27 - I could feel a bump stop when I reached the maximum lock angle of the given car.
For demonstration, here's a comparison of me turning the G27 wheel past its full lock and then the same with the MOZA R3. Pay attention to the FFB graph at the bottom right:
Last edited by Flame CZE, .
No FFB soft stop with a MOZA wheel base
I've upgraded from a Logitech G27 to a MOZA R3 wheel base and I found that I don't get the FFB stop in LFS anymore.
My settings are still the same as recommended:
- Wheel turn set to 1080° in the wheel software as well as in LFS
- Wheel turn compensation: 1.00
When I turn the wheel past the car's natural wheel rotation, there's no FFB stop at all.
I don't know if it's a bug in LFS or somewhere in the MOZA wheel's software.
My settings are still the same as recommended:
- Wheel turn set to 1080° in the wheel software as well as in LFS
- Wheel turn compensation: 1.00
When I turn the wheel past the car's natural wheel rotation, there's no FFB stop at all.
I don't know if it's a bug in LFS or somewhere in the MOZA wheel's software.
Last edited by Flame CZE, .
Button scopes
While developing an InSim app for myself, I needed to show personalised buttons to each connection and human player on track. To abstract away having to assign the button UCIDs manually, I've introduced scopes in the React Node InSim library.
Here's a demo video with two LFS users:
- the "React NodeInSim" button is the same for all connections (UCID 255)
- the username buttons are different for each connection
- the player name buttons are different for each human player on track
Example code:
Demo app source code
Here's a demo video with two LFS users:
- the "React NodeInSim" button is the same for all connections (UCID 255)
- the username buttons are different for each connection
- the player name buttons are different for each human player on track
Example code:
export function ScopesExample() {
return (
<GlobalScopeProvider>
<Button top={0} left={80} height={5} width={40}>
React Node InSim
</Button>
</GlobalScopeProvider>
<ConnectionScopeProvider>
<UserNameButton />
<HumanPlayerScopeProvider>
<HumanPlayerNameButton />
</HumanPlayerScopeProvider>
</ConnectionScopeProvider>
);
}Demo app source code
You can use data/script/[car name].lfs files to add /ff commands there (e.g. XRT.lfs). For mods the file must be named after the SkinID - C2EBCF.lfs for example.
In the modeller, when I select LOD3, the total number of output tris and points is different from the actual number of tris or points. You can see it in the screenshots where I select all tris and points. I think it should say 26 tris / 20 pts, but it says 36 tris / 46 pts. I don't know how those numbers are calculated.
There seems to be a bug when someone withdraws from an event, the forum post says there's total of 1 entry even though there are 42 entries.
https://www.lfs.net/forum/post/2116397#post2116397
https://www.lfs.net/forum/post/2116397#post2116397
FGED GREDG RDFGDR GSFDG