3 Commando Brigade

TFAR radios & Armoury saved loadouts

TFAR gives unique ID's to all radios when they are created in-game.  TFAR uses this ID to store the radio parameters e.g. frequencies, channels, etc.

If two players have a radio with the same ID, then when one changes a channels, it will change for both players.

Unfortunately when you load a loadout from the Armoury, it does not reset this ID.  The ID is the one you had when you originally saved the loadout.  In all probability, especially for larger ops, this will mean you now share a radio ID with another player (which is bad).

So, you absolutely must not save loadouts with TFAR radios in them.  If you do, then once loaded, throw the radio away (drop it on the ground --- do not put it back in the crate), and get a new radio from the armoury.

I'm not sure why the LR radio is reset when you open the armoury, possibly because its a backpack?  I'll experiment, next time I'm online.

Exactly what lifetap said. There was some talk that the issue had been fixed but judging by the comms crosstalk yesterday it is still very much a problem.

The public server has been very busy (25+ players on occasion) for the last two weeks, with many newcomers on the server who are unaware of previous radio ID issues. A large majority of these players (including myself) save/load their loadouts (including radios) using the Arsenal half a dozen times a day. I've not had, nor have I heard any complaints of, any issues regarding the radios.

As far as I know, the TFR radio ID issue was fixed a long time ago (according to the changelog). Judging by the fact that the server last night was already experiencing issues and wasn't running correctly at all (i.e. we had to emergency Zeus in enemies since none were spawning), then I think it's much more likely that the radio issues last night were in some way a result of this. I could be wrong, but looking at the facts it does seem like a bit of coincidence.

Sorry but as above, the error is still there - radios are assigned a unique code when you pick them up. If you subsequently save this radio as part of a loadout it will save the code too. Therefore why I was having issues last night as someone had the same code as me and each time I set my radio channels up - someone else was setting them back to the wrong channels.

Just as a point of good practise - do not save radios, long range, short range or backpacks as part of a load-out. ALWAYS grab a fresh radio from the armoury.

Cheers

Lifetap, assuming that we do prove this issue still exists, could we add something to the config mod that deletes radios as they are loaded from the VA?

Exactly what I was thinking.  I'll investigate.

Failing that I could disable the 'load' button on the arsenal  :)

Don't disable it or change it's label, just change the action to 'delete'.  ;-)

If the way radio IDs are handled is exactly the same, then what an earth does this mean:


How do we know that the radio IDs aren't client-side only now, or that having duplicate radio IDs is no longer an issue now since they're handled differently? We just don't know. Further testing/investigation is required before we jump to conclusions.

As I said in my previous post - it just doesn't make sense that the public server has been running for weeks, with people saving/loading their loadouts with radios dozes of times a day, with no (reported) issues at all. Yet one night, when the server was already bugged out, we get a couple of people (or was it just Serjames?) with radio issues and auto-assume the old radio ID bug (which hasn't bothered us for months) is back. Like I said, I may be wrong, but I want to confirm the assumptions first before we start force-deleting radios from loadouts etc.

Thanks for doing thoses tests Ronin
I'll see about doing some sort of further stress testing and seeing if I can replicate the issue from Sunday night.

lol It wasn't just me.. Lifetap, Howl Dogbadger all had the same issue - and those are just the ones I heard.

On the normal Public - people wouldn't notice. We don't all log on at the same time. and most people would just think "oh that's odd" and change back.

It's broken - trust me - but feel free to test away

SJ

You're probably right James - but do you wanna guess and possibly be wrong, or do you wanna know for a fact? It's the same with when we used to run loads of mods - do we wanna guess that mods aren't what's causing our crashes, or do we wanna know for a fact (by checking RPTs, logging crash reports, server frames, etc).