Yes, it would automate and save a lot of time for this kind of display:
Same gain for SimBroadCasts I imagine.
(I think it's one of the missing elements that brought Lazy to an end, even if not the most important one, to have the top view of any mod for the radar).
For my part, I've half-automated the process. I select the right car with the right skin in the garage, then the rest is automatic (capture, remove the background to replace it with transparency, then crop).
Okay, so you don't get anything in your interface (which manages cameras, seen player, etc.) to see what's being said, host messages, etc. ?
It can be an improvement to receive it by insim even if it's blocked on LFS client side (I know that our commentator - Hekatte - reads certain messages to find out what's going on)
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...
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...).
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.
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.
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