Kondor77 Posted August 20, 2024 Posted August 20, 2024 Attached are the .miz as well as the trk file. No scripts, EWR does not respond/talk when the mission is run from a dedicated MP server. If I run the mission straight from the ME or from hosting on my own machine - it works. Very weird bug. SA_F4 STRIKE DAY 1_EWRAxe-20240820-133342.trk SA_F4 STRIKE DAY 1_EWRAxe.miz
Kondor77 Posted August 21, 2024 Author Posted August 21, 2024 After doing some more testing, it seems as soon as the EWR is used in a dedicated server - it reverts all it's settings back to default. So in this case if you had a different callsign, it'll always revert to 'Axeman' (which is the default and top of list of EWR callsigns). And it additionally reverts back to default frequency (124mhz). What is so weird that this works fine as it should in SP, or even locally hosted on your own gaming machine. But as soon as I drop this onto a separate dedicated server box, the EWR reverts back to default. @NineLine @BIGNEWY
Recommended Posts