[RDSR] Lights v.1.4.6.9 [Siren/Strobe Program]

[[TC]►Wilczek◄]

Hello everyone,

Introducing: [RDSR] Lights
A little, simple alternative (not exactly) to [TC] Lights, with more strobe patterns.

Commands and keybinds are located in the console window when you open the app.

[[[ STROBES AND SIRENS ONLY WORK WITH [COP] [RES] [MED] [TOW] [VCU] [HwA] TAGS ]]]

Any suggestions/weird stuff/bugs go here or in my Discord DMs: luminary._

The file *might* be flagged as a virus - in that case you can add an exception to Windows Defender: https://support.microsoft.com/en-us/wind...01afe13b26

Download [RDSR] Lights v.1.4.6.9 from here

---

NOTE:

This application is outdated, please consider using [TC] Lights! http://city-driving.co.uk/tclights/

[7mar]

niceeeee

[[TC]►Wilczek◄]

[RDSR] Lights v.1.1

- now the app will notify when a new version is out

- changed default settings:
delay 60 -> 80
messages on -> off

- 3 new strobe patterns -> /o strobes 3, /o strobes 4, /o strobes 5

- /o msgoff & /o msgon is now one command:
/o messages

- will throw an error if it didn't successfully connect
- settings save now
- delay can be any number between 75 and 200
- strobes should turn off automatically after changing name back to civ

[[TC]►Wilczek◄]

[RDSR] Lights v.1.1.5

- cpu usage is always at 0% now
- power usage very high -> very low

- special characters in name shouldn't affect how the app sees it

[[TC]►Wilczek◄]

[RDSR] Lights v.1.1.6

- fixed strobes/sirens not working but it asks for your username now
- minimum delay is now 80

[[TC]►Wilczek◄]

[RDSR] Lights v.1.1.7

- the app wont delete spaces from your username

[[TC] Kyle]

Just had a play around with the program. It's not bad

A couple bits of feedback though:
- the strobes probably won't show up that well to other players at 200ms. Maybe you could set a maximum delay of 1000ms (1Hz)
- I'm not sure why the program asks for your username - you can find this out via InSim packets (unless there's another reason for this)

[[TC]►Wilczek◄]

hello kyle,

in Insim.NET (C#) there seems to be no other way to get the user's player name other than doing that.

it uses packets, but that's just what LFS sends back:

before it only worked for male driver models which had the PType 0 - if someone had any other driver model, the PType was either 1 or 2. resulting in strobes/sirens not working beacuse it can't find your player name to check if you have one of the tags: cop res med vcu tow

[[TC] Kyle]

You can do something like this (which I assume you are already doing) to get all connected players:

Code:

insim.Send(new IS_TINY { ReqI = 255, SubT = TinyType.TINY_NCN });

Wherever you handle your packet, you can then add a check to see if the connection is remote or not - of course, if it isn't remote then that must be the local player

Code:

if (!ncn.Remote)
{
    Program.myUsername = ncn.UName;
}

Of course this is just simplified.

[[TC]►Wilczek◄]

^^^^^ i tried something like that, 3 other players were being counted as remotes, i should be the only remote (which most likely is a insim.net bug)

[[TC] Kyle]

Yeah that's correct. A remote connection is an external player (e.g. not the local player).

[[TC]►Wilczek◄]

did an error explaining there, sorry
i meant, every other player SHOULD be a remote but not all of them were

elmo suggested doing:

if (npl.PType != PlayerTypes.PLT_REMOTE && npl.PType != PlayerTypes.PLT_AI)
checks if the player isn't a remote and isn't an ai

which technically should get only me, but it returned 4 players instead of one

---

i'd like to point out that same thing happened with trying NCN

[[TC] Kyle]

I've just tried the code Elmo suggested locally and it worked fine for me (AI weren't detected on my test server. Went on TC2 and other players weren't detected either). Are you sure you got your checks right?

[[TC]►Wilczek◄]

yeah, i was testing it on TC One.
i'm gonna try something different though and see if it works

[[TC]►Wilczek◄]

alright i got it now, no need for usernames anymore - update soon

[[TC]►Wilczek◄]

[RDSR] Lights v.1.2

- username not needed anymore, should detect automatically (thanks kyle)

- you can change keybinds now using commands:
/o sirenkey
/o strobekey
/o sirenoffkey

Download [RDSR] Lights v.1.2 from [RDSR] Forum

[[TC]►Wilczek◄]

I would like to point out that I can't do anything about the virus detection beacuse of the following reasons:

- I would have to buy an certificate which are expensive
- Updates are often at the moment and for the app to gain reputation in security systems it would require a lot of downloads.

[R e a l X]

Hello. Any idea why not work RDSR lights for me?

[[TC]►Wilczek◄]

(2022-05-14 18:13)Harii Wrote:  Hello. Any idea why not work RDSR lights for me?

Hello, try installing latest .NET Framework that you can find here:
https://dotnet.microsoft.com/en-us/downl...-framework

[[TC]►Wilczek◄]

Changes:
- Revamped strobes code, will allow me to make some more strobe-related stuff in the future
- If the app won't connect, it shouldn't say "Connected" anymore, instead show how to fix it.
- Should be able to bind stuff to controller buttons (let me know if it doesn't work)


New:
- Added 2 strobe patterns (6,7)
- Button stuff:

Will appear only when you have a tag. (COP,MED,RES,TOW,VCU)

---

1.2.6

- added /o buttons so you can change button visiblity