Updated classes info attached
Last edited by Racon, .
Stats at https://piranmoto.uk/events/150
Last edited by Racon, .
stats at https://piranmoto.uk/events/149
Last edited by Racon, .
You need skin 'slots', one for each skin. You don't get any with a demo account, but you get 25 for each level of licence you buy, and/or you can buy 50 slots for £1 if you put credit on your account.
https://www.lfs.net/account/skins
https://www.lfs.net/account/skins
Entry number: 28
Entry name: PiranMOTO
Car: Piran Firefly 200
Entered driver (Ingame name / LFSW name / Country): [PM] Jam 28 / racon / UK
Entry name: PiranMOTO
Car: Piran Firefly 200
Entered driver (Ingame name / LFSW name / Country): [PM] Jam 28 / racon / UK
Last edited by Racon, .
Assuming Scawen was OK with it, wouldn't you still need to redo this work every time there's an update? I don't know much about the practicalities of compiling source to an executable (mine are not-that-kind-of-compilation), but is it possible and/or practical to steer a compiler to store variables in a set place in an exe?
Same, if I use a radar it's more for other people's benefit than my own
I always preferred to use the AONIO radar over Lazy's because it was 'lower-tech'... but have to admit Lazy's was much more helpful (too helpful for realism, as you say, but it is nice to not be "that guy who doesn't know what's happening around him" now and then).
Stats at https://piranmoto.uk/events/148
Last edited by Racon, .
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, .
FGED GREDG RDFGDR GSFDG