ah, sorry, I misread your question - I can't help with win11 as I'm trying very hard not to move on from 7 
I had the same moment of panic with my G29, I'm win7 and hadn't even considered the OS when I got the wheel. The box and the manual both say win 10/11 is required. But, good news, I installed "Logitech Gaming Software" from their site and the wheel is recognised and works perfectly on win7 (except for a row of LEDs)
You must also set your home IP address to be allowed to connect to the server.
In the control panel there is an 'access control' tab, inside there is a box labelled 'Allow IP addresses to the InSim port' - put your IP address in there and save changes.
In the control panel there is an 'access control' tab, inside there is a box labelled 'Allow IP addresses to the InSim port' - put your IP address in there and save changes.
Haha, I really, really hate fender mirrors 
If it's possible to do them as a config option, I will do them for the 500
If it's possible to do them as a config option, I will do them for the 500
Stats at https://piranmoto.uk/events/147
Last edited by Racon, .
Quick update to the development plan: Several attempts at smoothing the problem areas in the mesh have failed spectacularly, so it's time to bite the bullet and start out with blender, I think. If I can't fix the door outline that way, I'll just draw the $%*%& thing into the skin 
That pushes the mesh-smoothing part of the project to the longer term as I don't have much free time, but it will be worth it in the end.
I've added a GT-compatible 100 to the line-up, with an NA inline 4 and more basic styling (smaller bonnet vents, rear bumper, and the much requested exhaust at the back ). It seems to sit nicely between the XFG and XRG performance-wise, but is subject to tweaks with online testing. (test)
The 200 is staying as is, except mesh smoothing.
The 300 I'm still not happy with the tyres, there's just too much sidewall for that car. I will go back a step with that one soon, but much testing is needed as I want it to be the last physics change on that car.
To follow is the GTR-compatible 500. It'll be compatible in terms of performance but the lore is that it's a street car rather than a 'proper' race car. Reference images attached.
That pushes the mesh-smoothing part of the project to the longer term as I don't have much free time, but it will be worth it in the end.I've added a GT-compatible 100 to the line-up, with an NA inline 4 and more basic styling (smaller bonnet vents, rear bumper, and the much requested exhaust at the back
). It seems to sit nicely between the XFG and XRG performance-wise, but is subject to tweaks with online testing. (test)The 200 is staying as is, except mesh smoothing.
The 300 I'm still not happy with the tyres, there's just too much sidewall for that car. I will go back a step with that one soon, but much testing is needed as I want it to be the last physics change on that car.
To follow is the GTR-compatible 500. It'll be compatible in terms of performance but the lore is that it's a street car rather than a 'proper' race car. Reference images attached.
Last edited by Racon, .
No surprises to be found here
Stats at https://piranmoto.uk/events/146
Last edited by Racon, .
The default sets have very strong brakes, so it doesn't take much to get the ABS shaking - if you reduce them so that the ABS only just kicks in, that should help.
The 200 is now skinnable!
Attached are a default monochrome JPEG, and a layered PSD (zipped) with all the components used to make the default skins that come with the mod.
Attached are a default monochrome JPEG, and a layered PSD (zipped) with all the components used to make the default skins that come with the mod.
Stats at https://piranmoto.uk/events/145
Last edited by Racon, .
Awesome news I will definitely be there for that one. (Mondays are awkward for me, but I'm hoping to manage at least one other event before then too).
I have been working on the skin mapping recently, making good progress so far. LODs are all there. I won't make any changes to tyres/engine/suspension/etc before the race, so it will drive the same as it does now
I will definitely be there for that one. (Mondays are awkward for me, but I'm hoping to manage at least one other event before then too).I have been working on the skin mapping recently, making good progress so far. LODs are all there. I won't make any changes to tyres/engine/suspension/etc before the race, so it will drive the same as it does now
Last edited by Racon, .
Stats at https://piranmoto.uk/events/144
Last edited by Racon, .
In single player mode, in the mods screen. There's a button under the mods.
Sorry, I should have made clear: I don't use those automatic startup scripts - I'm not calling them, only LFS is (the automated calling). IE, whatever LFS does is triggering the warning.
I've just checked, and the script is still being run despite the warning.
I've just checked, and the script is still being run despite the warning.
I'm getting a notice about not being able to run the automated scripts that I don't think was there before:
I also got one for 'road', but not for 'ev'.
I also got one for 'road', but not for 'ev'.
Last edited by Racon, .
Stats at https://piranmoto.uk/events/143
Last edited by Racon, .
No problem, and good luck
There's some discussion/help about direct access on LFS discord programming channel sometimes... it's worth joining if you're going to go on memory adventures
There's some discussion/help about direct access on LFS discord programming channel sometimes... it's worth joining if you're going to go on memory adventures
Some programs use InSim to manage the interface, but also do direct reading/writing of the memory of the running LFS exe as well. That kind of thing is beyond me I'm afraid
You can't use InSim to set a rev limit, if that's what you mean - the OutGauge part is read-only. You could warn people about high revs, but you can't force them to be cut.
Yes, if other players want to use your app, they will need to enable OutGauge also before the app will receive OutGauge packets.
Yes, if other players want to use your app, they will need to enable OutGauge also before the app will receive OutGauge packets.
FGED GREDG RDFGDR GSFDG