But an incompatible patch doesn't necessarily imply an incompatible InSim update.
As NCI is the only thing that would need changing, we may as well get it over with now so future InSim apps should Just Work™ when the time comes.
For the record, the only things that aren't ready for IPv6 yet are consumer ISPs, short sighted/moneygrabbing router manufacturers and some software. All supported operating systems have had it working and enabled by default for years.
Neither of those threads mention the format that it would arrive as, so it's a bit irrelevant. But yeah, 128 bits would be fine, just means LFS would need to output IPv4 as ::ffff:a.b.c.d format addresses correctly.
No it isn't mentioned because it wasn't mentioned. If you do not mention what you would like (+ arguments) then it's pretty difficult to get what you want. If IPv6 was mentioned at that stage then it maybe got implemented differently ... Or... An explanation why it's not desired. Nobody cared about IPv6 back then, it seems. Or cared about the packet in general. Quite low amount of comments.
IPv4 wasn't mentioned either, nor was a 32bit IP representation. If they had, I'm sure someone would have pointed out IPv6. It only occurred to me because I saw the 32bit representation in the actual packet.
Either way, as this is an ongoing test patch cycle, things are not final and can (more) easily be changed before it's too late and 'official'.
It's just a suggestion and Scawen is or course free to make the change now or sometime in the future when IPv6 support is actually implemented into the core code.
The only real benefit of making the change now would be one less thing to break InSim applications/libraries in future (when they may not be so regularly maintained).
Thanks, I found a bug there as well! They were treated as restricted areas if they were floating, and as route checkers if not... completely wrong!
About raised route checkers and restricted areas, I have been trying something here. LFS must allow your car to go slightly below the route checker, because the ground may be uneven. I as thinking this should be OK if I allow the route checker to be ignored if it is more than 1.5m above your car's centre.
I am thinking about checkpoints too. Maybe LFS could ignore checkpoints that are more than 1.5m above your car's centre. Would this cause any problems?
Yes, I know what you mean. There is a problem with multiple object selecting and small heading adjustments. Because of the granularity problem, the selected objects would sort of move away along their groove. So in that case it's better to rotate them to where you want them and do the move just once. This is not the case with X/Y/Z adjustments which do not lose accuracy in that way.
I could make a single selected object be adjustable by clicking the heading button. But now it's too late and it will have to be in a later version.
I have fixed the problem of tree trunk / sign / bollard collisions extending into the sky.
Here are some more program fixes and improvements.
Please have a go and let me know if it works well.
There are also more updated translations. Thank you translators!
Changes from 0.6G17 to 0.6G19 :
Tree / sign / bollard collisions restricted to object size
Circles more than 1.5m above car centre are now ignored
Checkpoints / finish line more than 1.5m above ignored
FIX : Restricted areas and route checkers were not working
FIX : Error with the new Wedge objects at 90 degrees
INSTALLATION INSTRUCTIONS :
To install the PATCH using the AUTO UPDATER :
A FULL version of LFS 0.6G14 or later must already be installed!
1) Start LFS
2) Click Multiplayer... List of Hosts
3) Choose a mirror near you
Alternatively install the PATCH using the SELF EXTRACTING ARCHIVE :
A FULL version of LFS 0.6G17 or 0.6G18 must already be installed!
1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see "Confirm File Replace" select "Yes to All"
4) Now you can start LFS in the normal way
NOTE : You can see if the patch is correctly installed when you run
the program (LFS.exe). At the bottom of the entry screen : 0.6G19
I've updated my pc and one of my online servers to 0.6G19, but when I go online, all I can see are 0.6G17/0.6G18 servers - I suppose I could be very first, but my server doesn't show in list of hosts - am I going wrong somewhere?