Disablez

Custom radio preset frequencies, if edited in mission editor, will only be used by front seat player. The preset number itself will sync correctly between the seats, but in the rear seat it will always use the default frequency for that preset, i.e. 118 for channel 0, 119.1 for 1, and so on. Custom frequencies will be ignored.

Meanwhile, the russian store version is out for 8€ ...

I wonder how many program clones we got for exactly the same thing :) Anyway, from another this-ain't-TARS clone... when in a minefield, be sure others shared and share your pain.

Only located tars.log this time, it's quite boring... 17:43:31 *** TARS Loading *** 17:43:31 Setting dead/spectator status. 17:43:31 Waiting for connection to Teamspeak 3... 17:43:31 Dumping object IDs... 17:43:36 TARS update cycle scheduled at modeltime 1609.416 17:43:37 Connection to Teamspeak 3 established. 17:43:44 1 <lots of lines with just "1" follow, during 2 or 3 seconds... then...> 17:45:47 Connection to Teamspeak timed out. 17:45:48 Connection to Teamspeak 3 established. .. and more 1s, and again timeout. Note that, as others mentioned it "works" in single player... which means we don't hear anyone if in a SP game. In MP we hear ourselves all the time, even people who is not playing. Different servers played, export always activated.

Negative, we have exporting enabled, and same problem as others describe.

Hi, we recently launched a pair of test missions with 1.2.3 including naval units, tested both static and moving ones. We shot at some from our A-10s but it seems two of us were seeing them in a location half a mile away of where other clients saw them (so, for those clients, my bullets were hitting water in the location where "i" saw the boats). However, once I set the boat on fire, for them the naval units instawarped to the proper place. This happened in both a A-10C only mission (10 players and 6 players) and a typical test mission with A-10, FC3, BS2, P51 units. Number of extra ground units was around a hundred. Anyone else saw this problem ?

Today while testing 1.2.3 I put a humvee up a slope and entered it in observer mode; due to gravity it fell down the slope, and as it gained speed the motor sounded as if it was the motor working. As well, while 1.2.3 has proven quite stable, we have had a pair of app crashes (DCS stopped working) whenever the unit we're driving is destroyed and after that we try and enter an air unit.

Monday again... Waags, plz be a sweetheart and give the masses their weekly update-about-the-update

Anyway, monday already so ... buggin' time ! Hey ED guys, how is it going ?

Nah, tomorrow it'll be time for the next "weekly update about the lack of 1.2.3 update" nagging :)

Just say something... this week yes, this week no...

Angel, admit it, you're just sore after yday's spanking :P

Escuadrón 69 (DCS A-10C Wing) POC: Disablez

Actualy for it to work it's "DCS_update.exe update". You can also run DCS updater from Start menu. And an old friend from times past, you can change windows date temporally, which would make it work as well. But no longer needed.

Ok, and in the meantime could they like, express it in a short paragraph for people to know ? (Plssss)

Yep... is this supposed to speed-up minor patches in the future?

Well, for the same reason the A-10 has a knob for that, in the first place ;). Will try again.

In the intercom panel, one can easily turn off the annoying AIM-9 tone, but supposedly the knob can be turned to adjust the volume; this doesn't work for us in DCS:W though, it remains at same volume. Reportedly this used to work, so... is this a known bug?

If 3.0.6 temporary version would only bring TS 3.0.6 compatibility, then we'd rather wait for DCS:World compatible version. If, however, it'd bring us some extra bugfix/feature, wouldn't be bad to have it now.

Yup, they have messed up with the snapviews in DCS: World.

I did as well :)

Daribouca, we're having the same exact issue for some time, haven't found a solution so far. And it happens only sometimes, so no misconfiguration on your side.

Yep, it will state "10 points for 20º, 5 for 15-25º", but neither the cockpit or Tacview have an exact decimal indicator of the angle, so my question was at which point/error degree 20º stops being 20º. Anyway, the varying altitude/pressure is the main concern for us at this point.

Ok, one thing that has been bothering us for the past couple of weeks. How exactly will delivery altitude be measured via Tacview ? We have noticed the altitude between "external view/Tacview data" and the "cockpit data" differs up to 250 feet if we try to maintain the same pressure value (measured in the nearby airport) throughout the flight. The only solution we have found is to manually get pressure values for each of the events in order to match AGL and readjust all the time. And also, in deliveries that give, e.g. 10 points for 20º, what is the margin of error of such measure ? 1º ?

Yep... "operation not allowed due to anti-spam protection", accompanied by non-stop bitchin' betty "error, error, error". Although this only happens with 3.0.5 client.