Hello,

Do you know how to block message on screen for streaming ("/block 2" seems to be the best way to achieve it) but to receive all messages by insim to display them outside of LFS screen (players messages and systems messages ideally)) ?

Hello Scawen,
are you considering adding the new 7D information "engine damage" to insim (more globally, perhaps a new "damage" or "car condition" package with clutch slip, bodywork, suspensions, etc.)?

Hello,
Sorry, it's a huge job to find all the addresses in the exe of each new version! So I can't do it every time and wait for the "official" versions (and even then, it will take me some time).
I'm making the code evolve so that I don't need to read data from memory (the most requested data that used to require it is now displayed in LFS, like engine damages for example) but this takes time and motivation...

Isn't that enough ?

Hello,
As described in the other thread here https://www.lfs.net/forum/post/2056084#post2056084, Bass-Driver's proposal is close to what I would consider ideal.

Having done it in Detect&Monitor, the only tricks needed are the nodes lines.

So no problems for officials tracks !

For layouts, the best thing would be to be able to insert node lines (to have live deltas in Detect&Monitor and/or in my broadcast/stream application, I have insim circles added to the layout track or perform 3d distance calculations – this being rather consuming and not very precise, even random...).

It doesn't disappear when you uncheck there!?

You've created a new host with a password, and insim requires this password.
2 solutions:
- go back to "Multiplayer / create new host" then delete the password
- open the Detect&Monitor.cfg file and replace the "null" in "Admin Password: " with your host password.

I can confirm that it never worked for me either.
Here are the logs, but there doesn't seem to be anything interesting (but I'm available for further tests if necessary). (I changed the "log" extensions to "txt", "log" not being accepted)

LFS crashes (closes itself) when you switch to 3D.

Quote from mbutcher :

All of the data in our broadcasts is pulled via InSim, but that car graphic is generated before the broadcast from the skins teams submit.

It was the idea of this suggestion (to automate it a lot) : here

Last edited by KingOfIce, Thu, 27 Apr 2023 11:37.

Sorry to find myself in this debate...
I have indeed used this memory reading technique due to the high demand for certain information present in Lazy AND with the agreement of the developers!
As said recently on the Detect&Monitor thread here : https://www.lfs.net/forum/post/2039663#post2039663 I intend to stop this practice which costs too much time with each new .exe and which does not seem necessary to me any more following the recent evolutions brought by Scawen.
Detect&Monitor will continue with some less informations, now available natively in LFS.
Hopefully this will be my only post here to leave Scawen alone to other more important things...

A feature much requested when Lazy disappeared was the radar (I didn't read everything but I imagine that already asked several times here).
For me, it already exists in LFS even if it is not exploitable (except Detect&Monitor where I created 3 types of "insim" radars as I could with the "basic" features of the insim buttons): the mini map!

Can we imagine 2 modes for the mini-map :
- the current one = zoomed out, whole circuit
- a zoomed mode (of a 10 or 20 m area - configurable) which corresponds to a radar ! The 2 other conditions (than the zoom) are : centered on the current player + rotation to have the front of the car up.

Yes the average can be interesting for long races with refueling or for endurance races.

Congratulations ! Very beautifull video !

So cool! Scawen just implemented something that looks like my original request in 0.7D14.
Thanks!
Suggestion closed.

Hello pilots!
I haven't had much time for the app lately but I'll try to get back to it.
Small survey please: Scawen having implemented the engine damage and the gearbox speeds in the incoming version, it seems to me a good opportunity to stop the memory reading, very constraining, to go back to full "insim".
The impacts would be :
+ compatible with any new version of LFS (except big update to come if insim modifications are necessary on the tire information side !?)
+ no more time wasting or waiting for each version
- disappearance of "engine damage", "gearbox speed" and "tire thickness" I think

Do not use, it can disappear overnight!

OK, thanks for your feedback. Added in my to do liste.

Great job ! Congratulations

Resolved by IS_CCP update in 0.7D9 I think...

I don't think the decimal point matters much in terms of performance, but seeing it is very useful to realize that your shifting is a bit too aggressive.

Hello Michal !
Thanks for your help.

I regularly check what's in /docs directory! A little less the scripts (even if I have already seen them on the forum).
For me, it's not suitable for my case.
e.g.: I want to change the rear camber, this system requires the following script on the UF1:

But if I use this same script on the FXR, it changes the type of tyre (because of the different number of lines!)

Also, are the scripts "keyboard safe" (well, I don't know if the expression exists but if I called this script and at the same time I press the button on my button box showing me the tyres = F9, no impact on my running script !?)

Add a control system for all live actions would be really useful with today's Button Boxes and steering wheels full of buttons!
eg: /liveupdate brakingbias 55
/liveupdate frontantiroll 45.0
/liveupdate frontwing 8
or by increments
/liveupdate brakingbias more
/liveupdate frontantiroll less
You get the idea, I know you'd implement it much better than my description here...
(I'll let you delete if it's really too off topic)

Quote from Scawen :

Thanks for the feedback about engine damage. It looks like most people would like it displayed (as a number).

I can confirm that the engine damage was the most requested feature in Detect&Monitor (implemented by reading in memory as no other way).
A gauge like CT would be nice (+ a light when you perform a damaging action as bonus) (and of course from my point of view, an access to this info via insim or outgauge)

Last edited by KingOfIce, Sun, 15 Jan 2023 14:45.

Quote from gernoff :

Will reshade work in VR. .
Pimax in particular?

Yes ! Pimax