Content Type
Profiles
Forums
Downloads
Gallery
Events
Articles
Everything posted by FoolTrottel
-
DangerDogz Mission Services Proudly Presents "Operation Steel Sword"
FoolTrottel replied to Friar's topic in DCS Series
-
DangerDogz Mission Services Proudly Presents "Operation Steel Sword"
FoolTrottel replied to Friar's topic in DCS Series
(I do not think my I-16 even has any external lights? Oh, wait, it's Operation Steel Swordfish ... no worries ...) -
Timing is a bit off, like half an hour at the moment, but that will be fixed 'round midnight UK Time
-
Our DCS-OB Server now restarts at 1AM. 7AM, 1PM, 7PM CET. 12AM, 6AM, 12PM, 6PM for the UK. This can be changed for sure, just suggest a better time. I've tried to keep it as friendly as can be - though midnight for the UK, is that okay? There's also a check every 5 minutes, whether DCS-OB is running. if not, it will automatically be restarted.
-
Well, my my my... This was beyond silly, as in, I made a stupid mistake, a typo basically, but the result of the typo was like beyond silly. This is the relevant bit of code to start our DCS OB Server. start /min "" dcs --server --norender @Echo DCS will be started via a powershell script that is in TaskScheduler. So that is all. My mistake? Somehow I lost the line fine at the end of that first line, so it resulted into this: start /min "" dcs --server --norender@Echo DCS will be started via a powershell script that is in TaskScheduler. @exit So, DCS would start, then show a message that "Authorization has failed" and next a whole list of modules that would be unavailable. And next. "Unfortunately DCS has crashed" ... with some weirdo exception error in the log on the intel graphics card driver. Never seen anything like this happen. I mean, one would expect a message "incorrect parameter" at startup, or even a message in the log file. But no, oh well
-
Have been working on the process that re-starts our DCS OB server process. It will still run for 6 hours, but it will be restarted every day at 1:00AM and PM and 7AM and PM. That is CET. So in DogzTime it'd be 12:00AM/PM and 6AM and PM. For now that is. It may change when summer time comes back. Note: It appears I may or may not have broken the OB a bit for us. Oh well, will look into it later. There's always the stable one...
-
-
New P-38/Tiffie Campaign Debrief Thread
FoolTrottel replied to DD_Fenrir's topic in IL-2 Sturmovik: Great Battles Series
12/03/45 2nd Lt. Archie Bunting Air: 1x FW 190D9 (Damaged an Me262 and a 190A8.) -
-
Bulldog saying hello and getting the first round
FoolTrottel replied to Bulldog's topic in Recruitment
Hi! -
-
New P-38/Tiffie Campaign Debrief Thread
FoolTrottel replied to DD_Fenrir's topic in IL-2 Sturmovik: Great Battles Series
Sorry, but that is classified information. -
New P-38/Tiffie Campaign Debrief Thread
FoolTrottel replied to DD_Fenrir's topic in IL-2 Sturmovik: Great Battles Series
11/03/45 2nd Lt. Archie Bunting Crash landed in friendly territory. Wounded. Picked up by a Belgian farmers' daughter. Slowly recovering. Very slowly. Not to worry - no problem. -
New P-38/Tiffie Campaign Debrief Thread
FoolTrottel replied to DD_Fenrir's topic in IL-2 Sturmovik: Great Battles Series
10/03/45 2nd Lt. Archie Bunting Air: 1x Me-109 Damaged Ground: 1x Boat -
-
-
New P-38/Tiffie Campaign Debrief Thread
FoolTrottel replied to DD_Fenrir's topic in IL-2 Sturmovik: Great Battles Series
09/03/45 2nd Lt. Archie Bunting Air: 1x Me-410 Destroyed Ground: 2x Boat -
-
-
New P-38/Tiffie Campaign Debrief Thread
FoolTrottel replied to DD_Fenrir's topic in IL-2 Sturmovik: Great Battles Series
04/03/45 2nd Lt. Archie Bunting Air: 1x Bf 109 Destroyed -
Look here: https://forum.il2sturmovik.com/topic/85701-fortresses-and-focke-wulfs-announcement/ B17E, P51A, Typhoon, 190A ... And discussion here: https://forum.il2sturmovik.com/topic/85702-discussion-of-fortresses-and-focke-wulfs-announcement/ And at ATAG: https://theairtacticalassaultgroup.com/forum/showthread.php?t=37474
-
Well, if a missing jet disappears, then I guess anything goes. 😵