fixed ARC Frequencies

[Alpenwolf]

Works in singleplayer, in the mission editor and multiplayer. However, not on a dedicated server as it is with the Cold War 1947 - 1991 server.

As a mission editor you can create trigger zones and use them to set up ARC frequencies across the terrain to help with better navigation. Also, and as many of you know you can add a sound file to simulate the sound of a transmitting beacon. All that works just fine but as stated above not on a dedicated server.

I use these frequencies in almost all my missions which is a nice thing to get players to play around with, plus of course arriving at the desired destination precisely.

This issue has been going on for at least a year and I did report it back in the day. Maybe it was overlooked or something, so please check it out.

 

Thanks in advance and as always, Godspeed, ED!

Edited December 11, 2021 by Alpenwolf

[Alpenwolf]

Would be great to fix, please.

[Alpenwolf]

This is still an issue and here's a mission to confirm it.

 

So, again, it works when running the mission through the ME and when running the mission through multiplayer by starting a new server, but NOT through a dedicated server.

I've included two sound files. One is for the R-828 channel 5 (32 MHz) and one is for the ARC-15 (610 kHz). Run the mission and see for yourself that it doesn't work on the dedicated servers.

 

Please, fix. Very urgent.

Good luck!

 

Beacons Don't Work on Dedicated Servers.miz

[=475FG= Dawger]

I second the request to correct this. It would be nice to be able to navigate.

[unhappytroll]

Third. Exceptionally frustrating bug.

[Alpenwolf]

Is this even reported, ED? Usually, it would say reported/investigating or the like. Please, guys, don't keep me in the dark like this. In terms of navigating properly this issue here is really vital for multiplayer, so I really need this to be fixed. I mean, it is a bug after all. A couple of posts above this one is an attached example mission.

Godspeed!

[HC_Official]

Is this bug related to the radio bug where IF you are connected to the dedicated server and the beacon starts you can hear it BUT if you connect after the beacon has started you do not hear it ?

 

EDIT: Yes this is the same bug as I have listed above,  once I tested the supplied trk / miz file I have confirmed this

Edited December 11, 2021 by HC_Official

[Alpenwolf]

On 11/9/2021 at 11:47 PM, HC_Official said:

Is this bug related to the radio bug where IF you are connected to the dedicated server and the beacon starts you can hear it BUT if you connect after the beacon has started you do not hear it ?

You don't hear it and the needle doesn't rotate towards the beacon, be it a trigger zone or a ground unit.

[HC_Official]

1 hour ago, Alpenwolf said:

You don't hear it and the needle doesn't rotate towards the beacon, be it a trigger zone or a ground unit.

Ah ok, so different then, it just does not work at all, regardless of when it is triggered

[Alpenwolf]

Just now, HC_Official said:

Ah ok, so different then, it just does not work at all, regardless of when it is triggered

Exactly. Lots of things don't work when running a dedicated server. That really ruins things in the missions.

[HC_Official]

1 minute ago, Alpenwolf said:

Exactly. Lots of things don't work when running a dedicated server. That really ruins things in the missions.

Yeah, dedicated introduces a lot of ballache,

eg

smoke needs to be refreshed every so often, if a player joins after it was triggered == they no see it

Radio homing beacons (ADF) need re-started every so often (30 seconds or so) , if a player joins after the radio beacon was triggered == they no hear it and needle doesn't move

the list goes on

[Alpenwolf]

An example mission was already attached (see the third post) and now here's a .trk file in case you didn't have the time to test it out yourself.

Fix, please, and Godspeed!

Beacons Don't Work on Dedicated Servers-20211209-235414.trk

server-20211209-235914.trk

Edited December 9, 2021 by Alpenwolf

[HC_Official]

On 12/9/2021 at 11:09 PM, Alpenwolf said:

An example mission was already attached (see the third post) and now here's a .trk file in case you didn't have the time to test it out yourself.

Fix, please, and Godspeed!

Beacons Don't Work on Dedicated Servers-20211209-235414.trk 559.47 kB · 0 downloads

server-20211209-235914.trk 410.38 kB · 0 downloads

 

Yeah I will have a quick look, weird that your server cannot get radio beacons working at all , but they have been working ok on the Havoc Company servers for past 4 years (within the afore mentioned limitations)

[HC_Official]

On 12/9/2021 at 11:09 PM, Alpenwolf said:

An example mission was already attached (see the third post) and now here's a .trk file in case you didn't have the time to test it out yourself.

Fix, please, and Godspeed!

Beacons Don't Work on Dedicated Servers-20211209-235414.trk 559.47 kB · 2 downloads

server-20211209-235914.trk 410.38 kB · 0 downloads

 

Edited the mission to add a 60 delay before beacon starts and as I said  initially said this is the same problem that has been about for many many years with radio beacons

The beacon works , ED do need to fix it so that IF you connect after a beacon started you can hear/tune to it, but restarting the beacon every so often works around this, thats what most of us server hosters have been doing for years now

 

 

Beacons_need_refreshed_on_dedicated_servers.miz

Edited February 17, 2022 by HC_Official

[Alpenwolf]

6 minutes ago, HC_Official said:

Edited the mission to add a 60 delay before beacon starts and as I said  initially said this is the same problem that has been about for many many years with radio beacons

The beacon works , ED do need to fix it so that IF you connect after a beacon started you can hear/tune to it, but restarting the beacon every so often works around this, thats what most of us server hosters have been doing for years now

 

 

Beacons_need_refreshed_on_dedicated_servers.miz 370.9 kB · 0 downloads

Bless you, mate.

I'll use that for the time being and hopefully it gets fixed.

[HC_Official]

and another TIP better to use mono OGG files for audio etc as they are a lot smaller in size

[Alpenwolf]

On 12/11/2021 at 1:24 PM, HC_Official said:

and another TIP better to use mono OGG files for audio etc as they are a lot smaller in size

Yeah, I always do that, thanks.

[HC_Official]

12 hours ago, Alpenwolf said:

Yeah, I always do that, thanks.

I figured you were unaware of that,  as the demo mission you posted used WAV files

[Alpenwolf]

2 hours ago, HC_Official said:

I figured you were unaware of that,  as the demo mission you posted used WAV files

True. I convert the files online to ogg in my missions. This one here was for highlighting something else, so I didn't bother converting the sound file.

[Alpenwolf]

In some missions (or maps I should say), the 60 seconds delay doesn't help either. It really is a thing when unable to use beacons to navigate properly.

[Sedlo]

Ok, I am just dipping my toes into multiplayer missions, but what about a small script that detects the event when a player enters a unit and reloads the sound file and pushes the transmit task again?

if it is a small audio file I think maybe it won’t be any lag when it happens. 
 

i mean, it should be a core function but until then, it might work?
 

 

[Sedlo]

Hey, @Alpenwolf So, first thing I would do is add the sound into your mission editor and set to a flag that will never fire.  This will put the sound file into the .miz so anyone loading the mission will have it.

So instead of delaying the transmission 60 seconds and starting it, this will start a new one each time a player joins.  That "should" ensure that everyone on the server can use the beacon.

TRIGGER	CONDITION	ACTION
ONCE	FLAG = 9876	SOUND TO COUNTRY  ELT.ogg

And on the Mission Start trigger, add this script:

Handler = {}
function Handler:onEvent(event)
    if event.id == world.event.S_EVENT_BIRTH then --whenever a unit is spawned
	trigger.action.stopRadioTransmission('ELT') --whenever a player joins an aircraft, it will stop the previous radio transmittion which will start a fresh transmission
    trigger.action.radioTransmission("l10n/DEFAULT/ELT.ogg", {x = -318078, y = 25, z = 00635675}, radio.modulation.AM, true, 032000000, 10000, "ELT")  --name of soundfile/position of transmission (y=altitude), modulation, loop or not, wattage and the name of the action
	trigger.action.outText('Beacon Trasmit Reloaded 32MhZ', 5) --this line is just to show the transmission has been reloaded remove at will
    end
end
world.addEventHandler(Handler)

I tested this on my dedicated server and it seems to work well.  

Of course, I'm band new to all of this, and this might not be a good answer to your problem, but it seems to work on my limited testing.

[Alpenwolf]

Thank you very much for your time and offering a solution. I'll check it out tomorrow once I'm back in the ME.

I'll let you know of the results.

[Alpenwolf]

@Sedlo :

I got it working now after 2 hours of testing.

Thank you for your patience and all the pm's back and forth until we got it working.

Now, that's a lot of work for me in the many missions I have featuring so many beacons.

 

Godspeed, ED! Really hope this get fixed ASAP.

[Sedlo]

Awesome, I hope it works well!