Jump to content
Bohemia Interactive Forums

hon0

Member
 View Profile  See their activity

  • Content Count

    567

  • Joined

  • Last visited

  • Medals

Posts posted by hon0

  4. Posted

    I'm sure your macro must work for you but it seems a bit strange to switch back to radio 1 before releasing the PTT key. Wouldn't it make more sense to release it (v) first?

    +1 :cool: It was to check if you read it x'P

    Well you got it then. You should be able to do whatever you want with autoHotkey I think.

    whereas radio1 and radio2 at least stay constant per mission (unless I drop them of course!)

    That's the problem. If you take a radio then release it for X reason then take it back.. It will bug. That's why the swtich to next or preview radio is the best way to go. This way you're sure it will work

    Tell me if you succes or not. I'm interested.

  5. Posted · Edited by hon0

    Yep theses options :

    class PTTRadioAlternate_1 // Talk over radio 2nd radio

    {

    key = 2;

    shift = 1;

    ctrl = 0;

    alt = 1;

    };

    class PTTRadioAlternate_2 // Talk over radio 3nd radio

    {

    key = 3;

    shift = 1;

    ctrl = 0;

    alt = 1;

    };

    class PTTRadioAlternate_3 // Talk over your 4th radio

    {

    key = 4;

    shift = 1;

    ctrl = 0;

    alt = 1;

    };

    Aren't OK. It bug cause of ID or something like that. I can't explain it. That's why I suggest you to do this ;

    if (event == "G_PRESSED") and (arg == 27) then

    PressandReleaseKey("l-ctrl", "caps") // To switch to your other radio

    Sleep(10) // milliseconde So it's almost instant

    PressKey("v") // to use previously selected radio

    elseif (event == "G_RELEASED") and (arg == 27) then

    ReleaseKey("v") // Message over.

    Sleep(10)

    PressandReleaseKey("l-ctrl", "caps") // To switch to main radio

    With your software. I can't remember the name but i'm sure you'll succes this way. :cool:

    ---------- Post added at 10:55 ---------- Previous post was at 10:52 ----------

    http://forums.bistudio.com/showthread.php?137672-ShackTac-ACRE-Volume-Control&p=2238317&viewfull=1#post2238317

    Here it is. Niv use a soft to make some advenced macro, script.. That's the way to go if you don't have a Logitech Keyboard. Or other keyboard script tool

  6. Posted · Edited by hon0

    Doveman,.. Doveman Is it you I helped a bit on the St_Acre_Volume Topic?

    Anayway theses Push to talk on a specific radio are bugged. As you can see.

    I'm in AZERTY :D

    class acre_sys_core

    {

    class Interact // Interact with vehicule

    {

    key = 16; // CTRL+SHIFT+A

    shift = 1;

    ctrl = 1;

    alt = 0;

    };

    class InteractSelf // Useless

    {

    key = ;

    shift = ;

    ctrl = ;

    alt = ;

    };

    class PTTRadio // Talk over radio

    {

    key = 47; // V (please unbind from your useless Jump Over Key...)

    shift = 0;

    ctrl = 0;

    alt = 0;

    };

    class PTTRadioAlternate_1 // BUG

    key = ;

    shift = ;

    ctrl = ;

    alt = ;

    };

    class PTTRadioAlternate_2 // BUG

    {

    key = ;

    shift = ;

    ctrl = ;

    alt = ;

    };

    class PTTRadioAlternate_3 // BUG

    {

    key = ;

    shift = ;

    ctrl = ;

    alt = ;

    };

    };

    // Quick switch keys for radios

    class acre_sys_list

    {

    class Forward // Move forward through your radios

    {

    key = ; // I use Backward instead..

    shift = ;

    ctrl = ;

    alt = ;

    };

    class Backward // Move backwards through your radios

    {

    key = 58; // CTRL+CAPS

    shift = 0;

    ctrl = 1;

    alt = 0;

    };

    class OpenRadio // Open current radio

    {

    key = 58; // CTRL+SHIFT+CAPS

    shift = 1;

    ctrl = 1;

    alt = 0;

    };

    };

    //CTRL ; SHIFT ; CAPS LOCK must not be assigned to any kind of movement. For exemple with default ACRE key if you switch radio it will make you move.. Fail fail fail. The same happen in vehicule.. SHIFT+ALT+S.. Tadaaaa you engine turn ON. You're spotted !

    When playing on a normal keyboard. (Razer Anansi :cool:).

    Here is how I setted up my ACRE action. I'm on Azerty. Using ZQSD.

    CTRL+CAPS to switch Radio. //CTRL is my turbo key. So I don't sprint if I don't press Z at the same time.

    CTRL+SHIFT+CAPS to open the selected radio. // SHIFT is my key to alternate run/walk. CAPS is set up on "Return" and "Direct Channel".

    CAPS to use St_Acre_Volume (Direct Channel) + Return + Activate V.A capture profile

    V to use Radio

    V is usualy on "jump over". Just bind it on 2XAlt. So you jump and at the same time enable free look. When Releasing ALT it come back to center. :cool:

    So with this you should be able to fully use ACRE while fighting. Driving or flying even with Keyboard and mouse.

    And you SHOULD unbind mouse left and right from "selected action" and "return" So you can manage AI while fighting. To return just press CAPS..

    0 annoying keybind conflict.

    Isn't that cool? :yay:

    Acre Volume calibration.

    St_Acre_Volume tips.

    ---------- Post added at 07:50 ---------- Previous post was at 07:44 ----------

    It seems you know how to make macro or script, so what you need is a key that will do

    if (event == "G_PRESSED") and (arg == 27) then

    PressandReleaseKey("l-ctrl", "caps") // To switch to your other radio

    Sleep(10) // milliseconde So it's almost instant

    PressKey("v") // to use previously selected radio

    elseif (event == "G_RELEASED") and (arg == 27) then

    ReleaseKey("v") // Message over.

    Sleep(10)

    PressandReleaseKey("l-ctrl", "caps") // To switch to main radio

    This could be use on Logitech script. (LUA)

    http://www.logitech.com/en-us/product/g13-advanced-gameboard

  18. Posted · Edited by hon0
    ++

    Thanks for testing. So do you think it's realistic to be able to hear a conversation clearly (but quietly) from someone shouting 195m away? Obviously it's impossible to make it sound like they're shouting when they're actually talking normally or whispering (or vice versa) but I wonder if, in RL, at that distance you'd hear a babble of noise but not be able to clearly understand each word. If that is the case, perhaps ST_Acre_Volume shouldn't allow us to hear clearly at that distance either and either mask/distort the sound or probably better, just not let us hear it?

    I can hear them at 195. But without any others noises, as wind or ambiant combat. It seems legit to me. My problem is people don't hearing me during a firefight even if they're close to me <25m. Some people don't know.. Or can't equilibrate their volume to make TS's one prioritary. To set them up correctly I always recommand to make some noise with a chopper and set up the volume till you can hear people talking arround you.

    Try to fix that without having your headset or TS master Volume at 100%. So when calibrated you'll be able to turn them up or down depending on the situation.

    - Headset volume

    - Windows Master Volume

    - Teamspeak Master Volume + Acre Radio volume (Double clic on the plugin)

    - Arma 2 Effect Volume

    They're no specific hotkey for Short range or long range radio.

    class PTTRadio	// Talk over radio
{
	key = #;  	// CAPSLOCK (please unbind from your normal PTT key)
	shift = 0;
	ctrl = 0;
	alt = 0;
};

    // Talk over SELECTED radio

    I always had problem with "class PTTRadioAlternate_#".

    If you can do macro, script. You should.

    if (event == "G_PRESSED") and (arg == G_KEY_NUMBER) then

        PressandReleaseKey("The one you use to switch radio")
        Sleep(10)
        PressKey("The one you use to talk over SELECTED radio")

       elseif (event == "G_RELEASED") and (arg == G_KEY_NUMBER) then

        ReleaseKey("The one you use to talk over SELECTED radio")
        Sleep(10)
        PressandReleaseKey("The one you use to switch radio")

    Also if you use Shift and ALT in a combi. Be sure to desactivate the windows keybind that make you keyboard switch from AZERTY/QWERTY.

  19. Posted

    Thanks but I'm already using that and it only affects how loud (i.e. how far it carries) my voice is, not who I can hear. I guess it's possible that the other players have got this on Max but even so I don't think I should be able to hear people in that barn behind me clearly.

    I don't think the TS volume controls can be the issue as they should only affect the volume of what I can and should be able to hear, whilst ACRE should be controlling how far away I can hear people.

    While people shout (St_acre_Volume) I can hear them up to 195m. Tested with a rangefinder.

    Without St_acre_Volume I can hear people whispering in their mic at 50+ m....

    So for me that's normal.. You don't have a problem. All the others have one.

  24. Posted

    Hello.

    What's your joystick? Check in the command option if all the axes are well and logicaly set up. No conflict. etc..

    A way to get an idea of whether this is happening is by getting in a light chopper, looking at your feet, and twisting back and forth. Your feet should not be moving on the pedals except during the twist-phase of what you're doing, and it should be a slow, deliberate measured move. If you see the guy's feet jerking left and right, acting 'touchy', or in any way not matching EXACTLY the motion of your hand, you are suffering from this problem.

    +1

×