Jump to content
NEW DISCORD SERVER DETAILS - SIGN UP NOW - Dogz Members Only Private Thread ×

FoolTrottel

1. DDz Quorum
  • Posts

    7,239
  • Joined

  • Last visited

  • Days Won

    362
  • Country

    Netherlands

Posts posted by FoolTrottel

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

    • Like 1
    • Thanks 2
  2. 15 hours ago, FoolTrottel said:

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

    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 :)

     

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

×
×
  • Create New...