Quote from KeiichiRX7 :

Holy crap dygear is still here

Lol, from time to time. ;p

Are the InSim devs community going to get a chance to make feature request? I'd really love to see a packet for when a tyre touches different surfaces. For example, when a tyre goes from Asphalt to Paint, or Paint to Crub, or Crub to Grass. This would allow us to make our own rules very easily about the confines of the track. Within the engine it seems that it's possible to at least know when we go from Asphalt to Grass and back again.

Quote from R0ut66 :

Will be possible to change the time with insim without ending the race?

You sir, read my mind!

---

Scawen, I don't think the visuals are there for the headlights. It looks like the lights just apply a luminance value to objects around it based on distance. It doesn't feel like the headlights are really emitting light based on the screen shots, and the headlight paths in front of the car are a fixed texture. I need to see fluid motion to be able to say for sure.

Last edited by Dygear, Sat, 23 Feb 2019 19:42.

In general it’s considered poor form to call someone a liar. It makes other less likely to help you.

There is no way to modify engine settings from within InSim currently.

Is this limited to a single light source? Could you for example add track lights for night races? Can the sun ... set?

TAA, you mean this?

https://www.lfs.net/forum/post/1748707#post1748707

I would love to see an interface into the physics engine via InSim. I know this is not going to be something that would be a priority for Scawen, but damn it would be cool as hell! Allowing for something like LFSTweak, without having to reprogram the interface every time there is a new build of the game, would be pretty great for the community as a whole.

Giving us, the InSim devs, a chance to do things like DRS and the deployable part of the MGU-K / MGU-H would be amazing but would also allow for the game engine to know that it's being modified from an outside source allowing for proper checking of this information.

Quote from skirmantasLTUgamer :

The DDoser(s) already reported the file as dangerous in Avast.
https://prnt.sc/j1uw9o

That's a common false positive with NSIS / LZMA compressed installers.

I banned Legendlfs for a month, 95% of this posts are just trolling.

For more accuracy you should use Z as well.

I would think that you'd also need to populate the `ObjectInfo::$Flags` to be `0` as well within the JRR packet. (Not that I have any idea, I haven't used the JRR packet, ever.)

Hey man, nice work!

Use trigonometry to get the distance between two packets, just as Skinzinho said. You'll want to look up Pythagorean Theorem.

If you want you can send a pull request on github and I will merge it.

I'm pretty sure LFSWorld and these forums are written in PHP and they run great. For the most part, target PHP 7.2 if you're writing something new.

https://github.com/php/php-src/blob/php-7.2.0alpha1/UPGRADING

I think InSim applications are limited to LFS instances that have a license attached to them.

UCID is a Unique Connection ID. It's uniqueness is only for as long as that connection lasts for and the numbers are used over and over again. PName is not Unique at all and are set by the player. So one play could set their name to another player name after they have disconnected. PLID only lasts for as long as the player is actually in the game for. UName is the only that that is Unique to a client across sessions and across servers. You should always use that for saving information on a client.

I get a internal service error when I try to ban him. So, I think we will have to wait for Victor.

Quote from Scawen :

I was discussing with Geraldine... we reckon when the Scirocco comes out there will be all these posts like "WTF, it's just a medium powered FWD! Why have the devs been hyping this up for all these years?".

You sir, are a class act.

I think that's fine. It's up to us as InSim programmers to say that for this object in this layout file ignore the OBJ packet.

Sorry that I'm late for this.

I think that the hitting the concrete of the road with the car (tire or body) should not emit an OBJ packet. I think that hitting the curb with the car (tire or body) should not emit an OBJ packet. Everything else should because that's unexpected behavior.

http://techreport.com/news/31328/microsoft-releases-open-source-directx-shader-compiler

How helpful is this to LFS currently? Will it work on DX9?

https://github.com/Microsoft/DirectXShaderCompiler

GitHub link for those that want it.

I like this!

You know what would be cool to fix that? A fork command.