(2019-11-19 07:04)Ghutra Wrote:  First of all, amazing work!.

But would it be possible to add a new siren cycle the same as W>Y>P Cycle + Bullhorn but have the Piercer be in a constant loop instead of 5 secs?. Or maybe an option to change if the user wants a constant loop or a 5 sec duration (if it is doable)?.

(2021-10-19 17:01)Latvian Video Wrote:  Hey, I have discovered a bug, I would suggest to remove the function, which adds /insim 29999 to autoexec.lfs, because it bugs out LFS, and all apps which want to use it, cant. It shows
InSim - TCP : bind failed
InSim : not initialised
When I launch LFS, or type /insim 29999. The only other app which uses insim is LfsLazy[/img]

(2021-10-20 11:45)Elmo Wrote:  

(2021-10-19 17:01)Latvian Video Wrote:  Hey, I have discovered a bug, I would suggest to remove the function, which adds /insim 29999 to autoexec.lfs, because it bugs out LFS, and all apps which want to use it, cant. It shows
InSim - TCP : bind failed
InSim : not initialised
When I launch LFS, or type /insim 29999. The only other app which uses insim is LfsLazy[/img]

Having /insim <port> in the autoexec file shouldn't prevent any other apps using InSim as long as they all use that same port and aren't doing anything strange themselves. If you want to use a different port, just change the port in the /insim command in autoexec and TC Lights will use that port instead.
This is a very common way of setting the InSim port automatically and you should never need to use the /insim command manually once everything is set up.

From your screenshot, it looks like TC Lights managed to connect to LFS OK.
Does everything work after closing LFS + TC Lights + Lazy? Some people seem to have to do this after the first run.

Lazy seems to be a common denominator of problems and I know it does several things strangely/differently to other InSim apps, though many people have no problem running both.
Several people above have said that it works fine if Lazy is not already running when LFS/TC Lights starts. I've never used Lazy, so I'm not sure how it works at startup.


I am aware of some situations where TC Lights can cause the "Bind Failed" message once it's lost connection, although closing/restarting TC Lights should always fix it. I am currently working on a new version using a new connection system, which will prevent this.

(2021-10-30 14:46)Elmo Wrote:  What's in the start_LFSLazy script?

Edit:
If there's an /insim 29999 line in start_LFSLazy.lfs, delete it from there and add it above the /run start_LFSLazy line in autoexec.lfs

(2021-12-16 14:22)Cyanide Christ Wrote:  I have an issue where I try to add binds for headlights etc. but the menu says "Please release all keys & buttons" and I can't bind anything, and afaik I'm not pressing any buttons or anything.

(2021-12-16 14:52)Grizz Wrote:  

(2021-12-16 14:22)Cyanide Christ Wrote:  I have an issue where I try to add binds for headlights etc. but the menu says "Please release all keys & buttons" and I can't bind anything, and afaik I'm not pressing any buttons or anything.

You're opening TCLights as administrator? If you weren't, try it.

(2021-12-16 14:52)Grizz Wrote:  

(2021-12-16 14:22)Cyanide Christ Wrote:  I have an issue where I try to add binds for headlights etc. but the menu says "Please release all keys & buttons" and I can't bind anything, and afaik I'm not pressing any buttons or anything.

You're opening TCLights as administrator? If you weren't, try it.

(2020-06-22 20:05)Moonlight.Neko Wrote:  For those that use button boxes or apps that are macros, can we get the sirens to be bindable? For each tone. Like able to assign buttons to them in the config. And still have it flash faster on Yelp and still have it only like 5 seconds on Pierce tone. Also able to change that name as I use hi-lo on h5. So want to be able to name the tones in config also.

Thanks!