Joystick is past right stop.
Receives strong left force.
Accelerates left for a while.
No longer past right point, but still has velocity.
In split second, exceeds left end stop.
Receives strong right force.
Accelerates right until no longer past left bump stop.
In split second, exceeds right end stop.
etc...
The problem is that to provide a strong enough force to be felt, the acceleration is quite fast, if you are not holding the joystick. And a joystick can move to extremes so fast that there is no time for the game to react before it's already off the other side.
If you have tried making a joystick move to specific locations, you may have experienced the same trouble I have, with wild oscillations being the usual result. Personally, I have not been motivated to try to solve such an issue. The simple method (plain force, available on all FF devices) worked well for a wheel so I simply limited it to a wheel.
But this is really off topic, I'm not going to start trying to control the motion of FF joysticks of unknown mass, force capabilities, etc.
About end stop forces, I think you sort of missed my point. I'm not saying that end stop forces are dangerous for wheels, but specifically that they could cause undesirable effects for joysticks, because of the way joysticks can flick so fast from one side to the other. That's why I enabled them for wheels but not joysticks.
But you touched on a more important point about impact forces in conjunction with direct drives, though that is a different subject.
Anyway, I've thought of a possible interface, to allow the user to override the reported device type, see attachment.
The 'bug' is in the game controller driver software which is reporting DI8DEVTYPE_1STPERSON instead of DI8DEVTYPE_DRIVING.
LFS only implements self-centering when it is a wheel. There are two types of force that are only applied if it is a wheel.
1) After car is reset, the force slowly builds to try to centre the wheel.
2) Wheel out of bounds (end bump stops)
I believe I have done this as a safety measure or to stop LFS smashing up FF devices / children / etc. I don't really know what a DI8DEVTYPE_1STPERSON is but suppose it's a joystick, then applying a large force could fling the joystick right over the other side, when it could then receive the opposite force that flings it the other way, and you can end up with a wild flailing joystick.
I have to be a bit careful with FF devices and decided that these forces should be OK if the controller is a wheel. Of course we have a problem if the wheel manufacturers can't specify the correct device type.
Now I've got a vague memory of some direct drive wheels being reported as DI8DEVTYPE_GAMEPAD - not sure if I'm remembering correctly but I guess that will cause the same problem.
EDIT: Actually it was the Simucube, which was also reported as a 1st person controller. I got this as part of a reply when I contacted them in 2021:
EDIT2: I find it a bit frustrating that DEVTYPE is not a reliable way to recognise the type of device, despite the name, and that manufacturers basically aren't bothered about that. At the moment it looks like we will have to have some kind of override option:
FF device is actually a wheel although it is not reported as one: YES / NO
I wonder if you can think of a good way to add this to the interface, clearly, without taking up too much space, and such that users are unlikely to select it if they don't have a wheel.
hello first of all I played this game about 1 year ago and deleted it now I reinstalled it and my old settings came back but I didn't want it and I can't change it
my problem is I don't want to use the car with the mouse and I can't change it I set the car to automatic and the car doesn't go when I press w
please help
We learned about that from a technical support email yesterday. I've only come across this forum post now.
There was some kind of connection problem. The server was restarted and then the same issue came up a few hours later, was restarted again and seems to be OK for now (around 16 hours). We don't yet know why it happened. It has been running for 3 years without a fault.
Feel free to post here again if the fault comes up again. I should get the email notification.
The failed upload attempts don't all add up, they are overwritten by the next attempt, so hopefully you don't need another slot. I can't add an extra slot as we don't have a system to do that and I can't get into coding an exception.
About the Cloudflare upload timeout, I guess you have tried the option to not include the png files, to reduce the size of the upload? I can't do anything about that at this time because for me it would be a big project to make a new upload system, and Victor isn't willing to do it.
I don't think it's a bug, those higher numbers represent the output mesh.
Triangles should be relatively simple, I guess some of the ones you selected are mirrored, so the output number is more than you have selected.
Points are a bit more complicated and there will be multiple points where smoothing groups or mappings meet.
For instance a simple cube with one mapping would have 4 points per side, so there would be 24 points even through they are built on only 8 editor points. 3 points at each corner, which you can see if you turn on normals (nrm). Each output, game ready vertex can only belong to one mapping or have one normal.
This was not the mod team, I did this alone after we received a technical support email.
I shouldn't have included the threat of a ban, that final sentence was not needed and obviously annoyed you.
I wish we didn't constantly receive support emails about offensive political or religious logos and slogans, bad behaviour, racism, etc. We're just trying to make a nice game for people to get together and have fun.
Great bug finding again! Thanks for working out the reason. The car is probably a fraction wider in the later version, and at some point in the generated path the car goes right up to the driveable limit.
When dealing with complaints from users we would prefer not to get involved in political judgments, but instead LFS should be free from this stuff, so we asked you to remove the logo. Not such a big deal really.
I've just done that now.
Up to 3 in list will remain in a single column.
4 or more will split into two columns with the left column containing the first half of the list.
We received notification that our provider is moving our instances to a different Hypervisor on 5th February, to improve the service. That will mean some downtime.
This should be taking place at some point between 13:00 UTC and 20:00 UTC on 5th February, so that means late in the night in Australia, 5th to 6th February. So I hope that means minimal disruption.
I'd prefer our instance not to be shut down while your hosts are running, so I plan to close them by 13:00 UTC and stop the hosting system on the server. I'll check in occasionally and when I see the server has been restarted, I'll restart the hosting system and restart any hosts that I closed down. That it hopefully before 20:00 UTC otherwise I'll be looking in the morning on 6th February.
If that is OK with you, you can just leave the hosts running and they will be offline for some time as described above. If you prefer to avoid the downtime then you can move your host temporarily (to Hong Kong or USA, I guess).