Jump to content

Heaney

Member
  • Content Count

    226
  • Joined

  • Last visited

  • Medals

  • Medals

Posts posted by Heaney


  1. @Qazdar and others some simply not realize you can use cluster of HC within shard or whole datacenter ...

    it's not limited to just 1 computer with some CPUs ...

    plus separated process which can start as needed or/and terminate separately to the server binary

    has much more uses than you can see ...

    Why not both? Build the HC technology directly into the server exe, running on another CPU core, and then allow for expansion through separate HCs.


  2. Microphone quality, volume etc all factor into how 'loud' a person is, turning off the teamspeak auto balance and using the curve model will lead to a lot of people constantly shouting(while they're talking quietly) and others having to shout to be heard more than 3m.

    That's not how volume works. Microphones have been able to detect volume (you know, in decibels as well as in arbitrary values) for decades.

    TeamSpeak auto-balance makes someone who is shouting loud have a lower volume so as not to annoy people, or talking to quiet it will increase them.

    By turning this off, you can get a decently accurate idea of the volume at which someone is speaking, and with this, you can increase the speaking range based on the dB value returned.

    I play with this setting on EVERY DAY on my server and in every Operation.

    There are anomalies with some microphones, but for 90% of people it works. I've tested it over and over. You whisper in the corner of a room and you aren't heard in the next building. You shout as loud as you possibly can and everyone in the town can hear you.

    I realise there is a lot of controversy around this: but for my group, it works.

    ---------- Post added at 02:02 ---------- Previous post was at 01:57 ----------

    I would be happy with some russian radios....

    They could be used by all OPFOR factions

    Well there aren't squad level radios for any "OPFOR" nation (excluding special forces), so just a manpack is needed.


  3. I will tell you your problem here.

    YOUR VIDEO SETTINGS.

    For ACE reticles, you need to have interface size to NORMAL, your 3D and interface resolution at the MONITOR'S NATIVE, and the aspect ratio correct.

    ... or some combination of these. Not sure. But if you do all that, ACE reticles will be fixed.


  4. Features/fixes I hope will be in 2.0:

    * Easy to use way to have different frequency nets for different factions

    * Fix the bug where if you disconnect while using vehicle radio, no-one else can use that vehicle's radio for the session

    * Vehicle intercomms

    * ACRE setting to remove "Lower Headset" from action menu

    * Fix the radio manipulation functions

    * Fix [this JayArma2Lib script error](http://tracker.idi-systems.com/issues/294)

    * Function to return the user's channel ID

    * Easier to make custom radios

    * Better, CURVE_MODEL_AMPLITUDE, and have it as the default mode again (so that people realise that ST volume adjustment is redundant)

    * Cell phones for Insurgents. Use the ACE cell phone model if needed.

    Beyond 2.0:

    * Unique aircraft vehicle radios

    * Command radio station (basically, static vehicle you can get in and use very powerful radio)

    * Static radio on a table, usable (for civillians/insurgents)

    * Signal extenders for same channel

    * Interference

    * More variety of backpack models for manpacks

    Just thought I'd post here as the tracker is... very messy.


  5. Amazing! Will be using this immediately. :)

    Btw, you say "realistic pack capacities/weights for man pack radios", but what about the UK/PRC-354 (an item, not man pack). It shows up as 1kg, while in reality it's about 2.5 kg with all equipment attached. Small detail but important.

    Also, will you add a mission variable to turn the icon in the top left off? I appreciate the work, but that's a bit annoying.

    Thanks again for the great mod!

×