Here is the new Watchdog
2021-07-22 update by Artist: Check TFS Resources for latest versions.
Here is the new Watchdog
2021-07-22 update by Artist: Check TFS Resources for latest versions.
Last edited by Artist; Jul-22-2021 at 04:39.
John Lydgate: “You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”
This one is for the new launcher 64 bits.
Forgive me for being a bit slow on the uptake. What does this do?
Thanks for getting this out so fast.
S!
Thx for the Job
Seems to work fine but i can't see anymore my server in the list.
Checked my ports and adress. I changed nothing since the 32 bits version.
The 32 version worked perfectly four our training server.
I can't understand why...
Any idea ?
Thx again
JP
Many Thanks.
System:Ryzen X1700 /3,7@4.0Ghz - 16 GB DDR4 3200 CL 14-14-14-35- AMD RX 480X OC 8GB - 960Evo M2 SSD 512GB - SSD MX300 750GB + Win7 64Bit -2 TB Seagate Barracuda 7200 rpm
System: i4790 /4,0@4.5Ghz - GSkill 16 GB DDR3 2400 CL 11-10-11-30- AMD Fury-X 4GB - 950Pro M2 SSD 512GB - SSD 840Pro 256GB + Win7 64Bit -3 TB Seagate Barracuda 7200 rpm
In the previous Watchdog thread, I mentioned that TWC uses a script to "watch the Watchdog". Basically it ensures that Watchdog starts whenever Windows starts up, and also keeps Watchdog running, restarting it if it ever quits for any reason.
It would also be easy to do a few things like check for .NET error boxes that pop up occasionally, and close them if they do. But, I haven't bothered with that yet.
Instructions:
1. Install AutoHotKey (http://AutoHotKey.com)
2. Copy/paste scrip below to a convenient location; update the location of your ATAG_CloDWatchdog.exe in the script
3. Place this script (or a shortcut to it) in your system startup folder so that it auto-starts when windows starts (instructions for locating your system startup folder here)
4. Run netplwiz to make the account that runs the Launcher/WatchDog/AutoHotKey system auto-login when the computer is turned on (instructions here). (Those instructions work for Vista and Win7-8-10; for WinXP the command to run is "control userpasswords2" and instructions are here.) Some discussion about this approach and alternatives here.
When the script starts (on Windows startup) it checks to see if CloD WatchDog is running. If not, WatchDog is started.
Then every 1 minute it checks whether WatchDog is running (starting it if not) and also clicks the "Start Watchdog" button to ensure that Watchdog is actually doing its job.
So, when the machine is turned on, the account logs in, AutoHotKey starts this script, and the script launches WatchDog and presses the "Start Watchdog" button.
Code:;;auto-start-atagCLODWatchdog.ahk auto-hotkey script. ;;by Brent Hugh, February 2018 ;; ;;This script ensures that CloD WatchDog is started and running ;;and that that the "Start Watchdog" button is pressed ;; ;;It checks every 60 seconds. ;;It will also check whenever you manually press ctrl-alt-shift-J, which is helpful for testing purposes ;; ;;To use it, You'll need to ;; 1. Install AutoHotKey ;; 2. Update the location of your ATAG_CloDWatchdog.exe in the script below ;; 3. Place this script (or a shortcut to it) in your system startup folder so that it ;; auto-starts when windows starts #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. ; #Warn ; Enable warnings to assist with detecting common errors. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. #Persistent SetTimer, StartWatchdog, 60000 return +!^j:: Gosub, StartWatchdog Return StartWatchdog: Gosub, RunWatchdog ; make sure Watchdog.exe is started & window open sleep, 4000 SetControlDelay -1 ControlClick, Start Watchdog, CloD WatchDog, Return ;;Make sure Watchdog is running & maximized (ie, window open & displaying, not minimized to tray) ;;Put the path to your copy of CloDWatchdog in the line with the XXXXXXXXXXX RunWatchdog: DetectHiddenWindows, On Process, Exist, 4.5 ATAG_CloDWatchdog 64.exe If (!WinExist("CloD WatchDog")) Run, "C:\Users\XXXXXXXXXXX\Documents\1C SoftClub\il-2 sturmovik cliffs of dover\4.5 CloDWatchdog 64.exe" Else DetectHiddenWindows, Off If (!WinExist("CloD WatchDog")) { WinShow, CloD WatchDog WinActivate, CloD WatchDog } Return
Last edited by TWC_Flug; Feb-05-2018 at 18:21.
After #$&*@#$&* Microsoft forced our Win10 machine to upgrade to Win10 "fall creators update" I'm having trouble getting CloD WatchDog to work.
It starts Steam OK, starts launcher64.exe Ok, but when it goes to send commands to launcher64.exe, nothing happens.
It will just sit there at the command prompt saying "4>" or whatever. And then after a while WatchDog will close the Launcher64 window.
A typical log looks like this:
If I go in & just manually type the commands to start a mission, it seems to work just fine (though WatchDog never recognizes that a mission has started, so it will close the window in short order to 'try again').Code:Sending stop command. Stopped **** Steam Start **** Starting... Started Waiting 30 secs. to start launcher **** Launcher Start **** Starting Sending Initial Commands... Launcher Start Sending common configuration commands Sending: Error Connecting to launcher. Error Sending common configuration commands. Closing Connection *** Launcher Stop *** Connecting... Sending stop command... Waiting for launcher to stop... Launcher stopped Failed to start!
Any thoughts?
It was working just fine until "Creators Update" . . . .
So, as noted above, I never could get 4.5 Watchdog to work on this machine. It's insane because it is working on our other, very similar server just fine & was working on this server just fine until the blasted "Creator's Update".
So I gave up on Watchdog for this server and instead expanded the Auto-Hotkey script we have been to start Watchdog & keep it running, until it does pretty much everything Watchdog does--but without requiring Watchdog at all.
Also it does a few handy things like zapping some of the most commonly encountered error pop-ups that Steam & CloD create. It's not quite as smooth & easy-to-use as Colander's Watchdog but it might be a helpful option for anyone who has trouble getting Watchdog to run, or would like something more flexible & scriptable.
Originally I posted all the code etc here but I thought it might make more sense to post it on its own separate thread instead of highjacking this TFS 4.5 Watchdog thread. The new thread with code, examples, etc is here.
Last edited by TWC_Flug; Feb-16-2018 at 01:17. Reason: Updated with link to new thread with code & examples
Thanks, this was very usefull!
Thanks for all information.
I tryed to lanch 4.5 Watchdog and have that
Server started OK and I see it on other PC, and can connect to the server. But......
[22:58:10] Loading mission ...
[22:58:11]
[22:58:11] =================================================
[22:58:11] System.Exception: File not found
[22:58:11] в ORusJ8aLdW0lLo13cpVbbtV43dm.UKDlEC8UawSvq4YsWKtl4J mNzDD()
[22:58:11] =================================================
[22:58:11]
[22:58:11] =================================================
[22:58:11] System.Exception: File not found
[22:58:11] в ORusJ8aLdW0lLo13cpVbbtV43dm.UKDlEC8UawSvq4YsWKtl4J mNzDD()
[22:58:11] в y7Wv0oLKq9Wow9J4KwK5CVZGuwq.teGNdPxlPycIzKUPlrEdvS 1obfV(zx6w9NLDDzK7dzCAUicIJ0aH0ZvA )
[22:58:11] =================================================
[22:58:11]
[22:58:11] =================================================
[22:58:11] System.Exception: File not found
[22:58:11] в y7Wv0oLKq9Wow9J4KwK5CVZGuwq.teGNdPxlPycIzKUPlrEdvS 1obfV(zx6w9NLDDzK7dzCAUicIJ0aH0ZvA )
[22:58:11] в y7Wv0oLKq9Wow9J4KwK5CVZGuwq.4XDoc1Sz95f08B7cicGLbo 2IxCd(zx6w9NLDDzK7dzCAUicIJ0aH0ZvA )
[22:58:11] в TDvcK9j62rPRnS3C16AJTcurgjW.LE3ACy0cUrOe12V5JnTEiR cbzcnb(String )
[22:58:11] =================================================
[22:58:11]
[22:58:11] =================================================
[22:58:11] System.Exception: File not found
[22:58:11] в TDvcK9j62rPRnS3C16AJTcurgjW.LE3ACy0cUrOe12V5JnTEiR cbzcnb(String )
[22:58:11] в dUMrl8pYRYuNyffzeHdlB6oGOnN.RopPvRaaBVDrD6qTNJpDjF mXo5Q(Dz4E9LPBAjPotiGbjq6rEjaFkEyA )
[22:58:11] в dUMrl8pYRYuNyffzeHdlB6oGOnN.9VgcPhPLsku3O9xDjuRYGE XJEGb(String )
[22:58:11] в 3Bua6OK7vC2E7cnFtxIbi6v37iQ.u8ob1Sbg3Afq0k0uFStJaW CxN8mA(String )
[22:58:11] в u7mRAv4sLKFSZB6M8LZBq0uzDdR.fSrC77ccFy4w5jBYVEvbhd CsYR9A(String , dCkAe0QLYwNICjESJvD8oJuT0KV )
[22:58:11] =================================================
[22:58:11] 8>[22:59:05] Server: Cassius Calhoun enters the battle.
[23:00:05]
[23:00:05] 8>[23:00:05] battle stop
[23:00:05] 9>[23:00:05] exit
[23:00:05] Server: Cassius Calhoun has had enough of this!
[23:00:05] 10>
And I notice, that those problem with System.Exception: is with old 32 Commander Repka, early worked perfect with 4.312, not now.
Only I did, install Blitz and Net.Framework 4.71
System Win7\64
Any ideas?
Search for this fact sends to
https://support.microsoft.com/en-us/...when-the-clien
In some cases, the lack of any answer, in itself, is already the answer.
Sorry this is out of my knowledge area. Hopefully someone can help you out.
The errors occur after/while the mission is loading. They are not server errors but mission script errors. "file not found" looks like the script is trying to load/launch a submission & not finding the file. The offending code is probably in the OnBattleInit() or the OnBattleStart() code routines. Either the sub-mission file does not exist, or perhaps the path to sub-mission file in the script is wrong. I'd be looking for a code line that has "postmissionload" in it & check that the file path is on that line.
Last edited by Salmo; Mar-01-2018 at 22:50.
Big thank you.
I'll try to launch simple mission without submission loading.
Spoiler:
.
Last edited by Cassius; Sep-24-2020 at 14:27.
.
Last edited by Cassius; Sep-24-2020 at 14:26.
I think that relates to old ATAG mission functionality that became unnecessary after scripting changes, I'm not sure if it can be re-enabled though.
EDIT:
Flug, just saw your post on Watchdog. I know this is a few months late, but did you make sure the port specified in the 'Launcher listen port' in the Watchdog settings is the same as the one on the 'IP=' line under [Console] in the confs.ini?
Last edited by ATAG_kiwiflieger; Dec-28-2018 at 00:49.
"Speed is life. Altitude is life insurance. Surprise is key."
~ AMD FX-4100 3.6GHz (OC to 4GHz) ~ 8GB RAM ~ ASUS GTX1050Ti Phoenix 4GB ~
T.16000M ~ TWCS Throttle ~ TFRP Pedals ~ DIY IR Headtracker
.
Last edited by Cassius; Sep-24-2020 at 14:27.
You could try and edit ClodWatchdog.ini, and change the values in there.
Now I am not sure whether it will work... I think it will.Code:[General] MissionTimeOut=245
Alteernatively, you could add a line to the file settings.cmd:
Where the number entered is the number of seconds that will pass before the command 'exit' is being sent to the server, and it will exit.Code:timeout 14410 sc exit
(14410 is about 4 hours...)
Good Luck!
.
Last edited by Cassius; Sep-24-2020 at 14:27.
.
Last edited by Cassius; Sep-24-2020 at 14:28.
Bookmarks