-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACRE support #39
Comments
@Crowdedlight I would really love to see this added! Your modules are literally a godsend when Zeusing! |
Notes for self: [{
// ACRE signal processing
private _coreSignal = _this call acre_sys_signal_fnc_getSignalCore;
_coreSignal params ["_Px", "_maxSignal"];
// Modify signal (eg. zero-out if in jam area)
if (player inArea myTrigger) then {
_Px = 0;
};
// Return final signal
[_Px, _maxSignal]
}] call acre_api_fnc_setCustomSignalFunc; Then add handling for multipliers for jamming. Straight up multiplication. Send: 1, normal Send/Receive; receive 0, send 1: means can't hear anything, but still talk on comms. For ACRE that is more simulation-oriented, maybe consider the jammers to here only jam the Receive. As anyone within range of jammer would struggle to receive based on signal strength of jammer, however if transmitting within radius, it depends on if your signal makes it outside the influence of jammer, when received. Although for game mechanic maybe just let the transmitting be affected by 5-10% of the what the receiving jamming, to help indicate jamming to listeners outside?... Not sold on best approach here. Degrade signal so badly that being 200 meters away is already completely garbled on the 343: |
Basic ACRE2 jamming is implemented with #81 slated for next release. Currently, it only supports jamming radio comms. Tracking, listening in etc. are not currently supported. Might be supported at some point, but no promises. |
Not a pull request but might be useful for anyone trying to implement this:
https://github.com/diwako/ACRE2-Custom-Signal-Calculation#radio-jammers
The text was updated successfully, but these errors were encountered: