-
Notifications
You must be signed in to change notification settings - Fork 169
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
Zeus frequencies #982
Comments
another problem is when we have defined the encryptionkey in this array and the curator unit doesn't use this settings, zeus is not able to communitcate with anyone via radio. |
Hm... Looks like Zeus not supports such logic currently.... |
I'll check later in more details - please ping me if no result for 1-2 days |
friendly ping |
Oh, looks like not easy thing.... Currenty Zeus just uses frequencies settings from radios... So, you could try yo do a trick. [TF_curator_backpack_1, "TF_curatorBackPack"] |
I'm sure you will find a way in the future :) Thanks for your great work on this Mod! regards |
@dedmen I saw that you pushed the development a lot, maybe you could have another look at this issue Our Problem is that frequencies set for the factions are not set for the curator(s). Also if we don't use our frequencyset and instead using the tf_same_sw_frequencies_for_side setting the curator has it's very own. Currently I solved it by this bullshit https://github.com/quies-in-proelium/qipTPL/blob/master/Functions/zeus/fn_tfrZeus.sqf |
That really shouldn't happen :x |
Confirmed Now to the Real problem.. Frequencies are assigned by Side. There are West,East and Default.. Default the Frequencies of Independent side. @NemesisRE your script is crappy and actually causes performance problems.. Here is an improved version https://gist.github.com/dedmen/3a9f7a23ce21d971c1a60555af04d8ec |
It's a bit ugly but it works. Fixed in 1.0. Remember Changed API in 1.0 for default Frequencies.
turns into
If you want to use these changes earlier feel free to help test us Pre-releases. 1.0-dev.139 should have the fix. For better contact to Devs see #1116 |
Former-commit-id: acf555d94af002f910e03913b7255e8eb8c25c4d [formerly 894ef3972f44ab92a463f9e87c27c7801019d6c3] [formerly d3242e01dfef282310bd6b9dc153299957760db2 [formerly 69277397ebbff1efbe91773078d7c7c2e52c6fd5]] [formerly 69214660409aee4c948d2ec7e390ad2f9dbed825 [formerly 5d671b88a8aa3abb907ead0b8ff117eb9b1fb34a] [formerly d9dfcb19cbd1acda22fa93ff2f1dfd5b4580e24f [formerly 2b6ce51f1622fd46adf254bb2f8f7e1c2a0b19e2]]] Former-commit-id: f3c56331a20f2ffb0d8b053f1d136c0b43c1e425 [formerly a03324497092595720d1ab77b38a22c403071674] [formerly cfc947761ace1da68baea5af7e7ac6b443d9b0db [formerly b837fff35ce71db3615ca162c961833dda2fae39]] Former-commit-id: 19efbced191341bae6cd886aed687d24bd82d001 [formerly 8aa9ea577d8c5c33abb7ed05b5fd497eaf58dbf9] Former-commit-id: cdb960c249daaf4600f1d62ef40fb89f4748f59c
Former-commit-id: acf555d94af002f910e03913b7255e8eb8c25c4d [formerly 894ef3972f44ab92a463f9e87c27c7801019d6c3] [formerly d3242e01dfef282310bd6b9dc153299957760db2 [formerly 69277397ebbff1efbe91773078d7c7c2e52c6fd5]] [formerly 69214660409aee4c948d2ec7e390ad2f9dbed825 [formerly 5d671b88a8aa3abb907ead0b8ff117eb9b1fb34a] [formerly d9dfcb19cbd1acda22fa93ff2f1dfd5b4580e24f [formerly 2b6ce51f1622fd46adf254bb2f8f7e1c2a0b19e2]]] Former-commit-id: f3c56331a20f2ffb0d8b053f1d136c0b43c1e425 [formerly a03324497092595720d1ab77b38a22c403071674] [formerly cfc947761ace1da68baea5af7e7ac6b443d9b0db [formerly b837fff35ce71db3615ca162c961833dda2fae39]] Former-commit-id: 19efbced191341bae6cd886aed687d24bd82d001 [formerly 8aa9ea577d8c5c33abb7ed05b5fd497eaf58dbf9] Former-commit-id: cdb960c249daaf4600f1d62ef40fb89f4748f59c Former-commit-id: c888155
We have set our frequencies by defining the tf_freq_* variables
and want that they are set for our forced curator too, is this possible?
If it is possible then how?
regards
NemesisRE
The text was updated successfully, but these errors were encountered: