FoolTrottel

17/03/45 2nd LT Herschel Lenko Air: 1x ME262

Yes...

I have since added a blue one, with some green parts on it? I think it's called "Synaigy"? 😁

14/03/45 2nd Lt. Archie Bunting died from critical AAA damage to his aircraft. Ground: 1x AAA Gun 2nd LT Herschel Lenko reporting for duty.

Wot? No Boeing P12E "Willy Nilly"? tskkk ....

16/03/45 2nd Lt. Archie Bunting Air: 1x Me 109 Ground: 1x Bridge 2x Truck

Grreat stuff...!! Found a bug though:

Our Open Beta server:

Can I have a P51 this time?

IAR 80 added to fighters base. Glider added to Bombers airstart. Have fun!

Our DCS OpenBeta Server:

Our DCS Stable server is not running at the moment, as it somehow interferes with the running of the Beta one. (I think it's something to do with the latest version, but I am too lazy to report it at DCS forums, it's not that big a deal any more, we used to have it for peeps only having stable. At the moment, all have Beta me thinks)

13/03/45 2nd Lt. Archie Bunting Air: 1/2x ME262 Shared with Red 1 [Fenrir] Damaged a FW190A-8 Ground: 4x Vehicle Transport 4 x AAA Guns 1x Searchlight 3x Facilities (Things I ran out of: Ammo, Bombs, Energy, Courage. Things I did not run out of: Fuel, Runway, Sheer luck)

As a pure spectator I have one thing to add...

(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...

Our DCS Stable Server:

12/03/45 2nd Lt. Archie Bunting Air: 1x FW 190D9 (Damaged an Me262 and a 190A8.)

Our DCS OB Server:

Hi!