Jump to content

Recommended Posts

Posted

I noticed that any time I use the "Reset" server button from the WebGUI, the server would load the first MIZ file in the list instead of loading the last/current MIZ file.

Has anyone else seen/experienced this bug?

Posted

I would also like to add that MIZ files are randomly selected after an automated server restart. For the record, shuffle and loop options are NOT selected in my server settings.

Screenshot 2025-02-26 104631.png

Posted
On 2/26/2025 at 4:25 PM, GeoS72 said:

I noticed that any time I use the "Reset" server button from the WebGUI, the server would load the first MIZ file in the list instead of loading the last/current MIZ file.

Has anyone else seen/experienced this bug?

Issue reported. 👍

On 2/26/2025 at 4:49 PM, GeoS72 said:

I would also like to add that MIZ files are randomly selected after an automated server restart.

What are you calling an automated server restart? How do you achieve it?

  • Thanks 1

---

Posted (edited)

Flappie,

Thank you for reporting the issue and asking about an automated server restart. If the server reboots and reloads the DCS server based on time, i.e. every day at 9am then the MIZ file would randomly change.

Edited by GeoS72
  • Thanks 1
Posted

Here is a message that I received from the automated server reboot. The message was sent to my Discord channel. The restart process automatically occurred at 05:04 EST. This MIZ file (BSGColdWar_025.miz) is at the top of list and is set in the Caucasus map. The MIZ file that was previously running was set in the Persian Gulf map. I manually ran that map at ~00:20 EST (3 Mar 2025). The server should have reloaded my Persian Gulf map when it automatically restarted.

Screenshot 2025-03-03 102915.png

Posted (edited)

I understand the problem but I cannot reproduce this issue locally on my PC:

  1. I run a Dedicated server.
  2. I change the mission from the WebGUI.
  3. I wait for the mission to be live.
  4. I kill the server.
  5. I restart it: the mission I chose previously is loading.
Edited by Flappie

---

Posted

Cannot reproduce it either. For me, also behaves like Flappie described. Probably need to contact your managed server provider about it.

  • Thanks 1
Posted

Aside from waiting in excess of 2 minutes for the server to refresh (covered in another bug I submitted), here are some screen shots that I took over the past 10 minutes.

The screenshots were taken at key stages of the restart process.

1. Server status prior to selecting Restart button.
2. Restart pressed, server indicates loading the last MIZ file.
3. While loading, the server now shows the 1st MIZ file loading.
4. While waiting ~2 min, I get a Server Not Responding error.
5. After waiting a bit more, the 1st MIZ file is now running; not my desired MIZ file!
6. I had to press the Run button on the desired MIZ file (last one), then waited another 2 min to have it load & run.

So, what is being done behind the scene? If it is potentially a server provider issue, then give me some information to bring back to them. Simply finger pointing will not help. Is there someone at ED that I could direct my provider's attention to address this issue? This really became an issue after the last DCS update.

Server Status01-Prior to Restart.png

Server Status02-Restart Pressed-Waiting.png

Server Status03-Loading 1st file.png

Server Status04-Server Not Responding.png

Server Status05-Running 1st file.png

Server Status06-Manually ran desired MIZ.png

Posted (edited)

Does Fox3 provide access to dcs.log? Preferably, with full debug logging enabled. If so, please restart the server (so you start with an empty dcs.log), document each step you take to reproduce the issue (with as few steps as possible), and post the dcs.log along with the exact steps that produced that log. The (debug) log should be considerably more informative than screenshots.

On 3/4/2025 at 6:21 PM, GeoS72 said:

Simply finger pointing will not help.

Absolutely. But that goes both ways. Therefore, I'd recommend you to install a dedicated server on your local computer*, apply the exact same configuration you use on the Fox3 server, try to reproduce the issue you have with your Fox3 server on the local dedicated server install, using the exact same steps. Finally, compare the logs to narrow down the cause of your issue. Best of luck and please report your findings here!

Edited by Actium
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...