Pocket Sized

Vast majority of the files will be transferred from your existing install. Actual download is about 2 GB.

http://www.digitalcombatsimulator.com/en/downloads/world/beta/

1.5.4 Appreciation? From what I've seen, not many people seem to realize just how great 1.5.4 is. The problem is most of the changes are under the hood and hard to notice. Easiest way to see how much it's improved is to play a few hours on the beta and then switch back to 1.5.3... chances are it won't take long to go back. Summary: 1. New sounds. In the cockpit, it no longer sounds like the engine is being shoved into your ear. There's wind noise (which changes with AoA!), ground roll, buffeting, etc. The wind noise really gives the impression you're moving through a substance, rather than magically floating around. 2. Overall stability. I've had many cases where I'm doing a long flight in 1.5.3 only to have it cut short by a game freeze or crash. Worst feeling in the world. I'm not saying 1.5.4 never crashes. But you'll find a massive decrease in the number of crashes/freezes while flying. 3. Servers no longer accept inaccurate position/velocity data for aircraft. Instead, it uses the last known position/velocity and holds the aircraft there until good data is received. This is HUGE. Instead of warping 20 miles back and fourth during lag, planes will continue in a straight line until the lag ceases, after which they will move to the correct position (usually not too far away). This means you don't have to worry about parking too close to somebody while rearming/refueling. You'll never lose the lead aircraft during lag. The tanker will never freak out and kill everyone trying to refuel. Am I exaggerating how good this update is? Am I late to the party?

Whoa. One of the main reasons I fly the KA-50 is the gobs of excess power it has. Is the Mi-8 actually comparable? (I'm looking at getting it soon)

DCS is in a weird place right now. The Open beta is used for testing features and is generally considered less stable than the release version. But they're testing network improvements so... the open beta is actually way more stable than the "stable" version (1.5.3). Not saying the 104th should update though. (a lot of people don't have 1.5.4)

Other way around. Actual IAS (according to info bar in external view) is about 400 while the gauge reads ~450. The gauge has a large needle for IAS and smaller one for TAS, they overlap at sea level.

1.5.4.x (latest open beta at the time of posting) L-39C, not tested with ZA yet I have my units under gameplay options set to imperial and was surprised to see the ASI switch to knots. I like it a lot, but it seems to be very inaccurate. Full power at sea level grants an indicated airspeed of about 400 kts according to the F2 IAS. The gauge reads between 430 and 450. It's like that through the entire speed range, as far as I can tell. I have yet to test the metric airspeed indicator, but I have a feeling I'm missing something and there's no issue.

295 pages? ( ͡° ͜ʖ ͡°)

None of the usual binding controls show up. It acts as if I entered a key that belongs to somebody else entirely. (But it still says it's bound to my account, which is what's confusing me)

That's why I think it's a problem with the license itself. I could do that before, but not now. I'll try contacting the original purchaser and see if they can shed some light on the situation. But as I said in the OP, it's definitely bound to my account.

More poking, I'm pretty sure it's a problem with the license itself. Still have no idea as to how to fix it.

I cannot figure out what's going on. Somebody gave me the Hawk and it worked fine for a few months. Then one day, without me making ANY changes to my DCS install, it stopped working. My game is acting as if it's not bound to my account. I can't sign into multiplayer unless I uncheck it in the module manager even though the license checker says it's bound to my account. I deleted every trace of the module (including regedit) after de-activating it. I reinstalled it and got exactly the same symptoms. Weirdly the ED stats say it's not active but the Starforce stats say it is. Serial Number: XX-XXXXXXXXXXXXXXX Product:DCS: BAE HAWK Active:No Replaced:No Type:Release Bind date:03-06-2016 Bound to:P*** Star Force serial number parameters Product:BAE Hawk Activated:Yes Blacklisted:No Expired:No Number of activations has been exceeded:No Type:Release Any ideas?

That's the problem. Escorting strikers is boring. It always goes the same way. 1. Fly A-10 or K-50 and get blown out of the sky by eight billion AIM-120's 2. Switch to F-15/SU-27/MiG-29 3. Listen as your teammates refuse to get their asses out of the target area and get shot down 4. Discover fighter had an ounce of sense and ran home 5. Hang around and strafe things 6. Get bored 7. Go back to ground attack 8. Wait 20 minutes 9. See step #1 Unless somebody is okay with flying around in a fighter doing nothing but trying to conserve fuel for a few hours, this isn't going to change.

Operation bison is still half broken. A while ago the mission was broken because there were no loadout restrictions. It has been fixed so there are no 120's. But Red can still use extended range missiles. Gee, I wonder why the server is empty right now...

I would definitely say to keep it how it is. TS is highly recommended, but not mandatory. Plus the password would be leaked in a matter of minutes.

One very annoying limitation of DCS is that it won't let you assign multiple actions to one button. I've mentioned this and people tend to say something about a macro... I'm pretty sure making one would involve creating a lua script. How difficult would this be? I've stumbled my way through lua once and barely managed to combine two axis (not in DCS) by modifying somebody elses code. Could somebody point me in the right direction? Ideally just show me an example macro.

I'm probably missing something, but is there a place to see when somebody quotes me, mentions me, etc? Or is that not available on this forum software?

Am I the only one who fails to see any disadvantage to overriding the fuel control? It quickens throttle response by a huge margin (good for suprise TOGA). The manual states that quick throttle movements can cause compressor stalling and/or engine damage. Because planes in DCS are single use, we don't have to worry about maintenance. But I have yet to see any kind of compressor stall or overtemp, even if I take the lever from ground idle to full in less than a second or vise versa. Is this modeled? Will it bite me in the arse when I least expect it?

Rudder madness? That sounds like something I could get into.

True, I have noticed the 10C will lose most if not all elevator authority past barberpole.

I turned on the cockpit air, oxygen (blinker working), and the cockpit vent next to the gun sight. While I turned final on my second flight I noticed periodic hypoxia along with a static blinker. Did I run out of oxygen or something?

If you go full power and fly straight at sea level (no external stores): A-10A/C: Nothing F-15C: Nothing Mig-21: Engine stalls at 1300kmh Su-25: Mach tuck = uncontrollable dive if not watched carefully Su-27/33: Massive loss of control authority (IIRC) Mig-15: Massive loss of control authority, wing flex causes banking, nose comes up even with full forward trim Mig-29: Haven't tested F-86: Don't own M-2000C: Don't own So yeah. Anyone have insight on this? (I know I'm straying dangerously close to the "P" word)

When I got my pedals the right toe brake was DOA. Didn't bother returning them and took the back cover off. The pots are good, I tried switching them at one point and got the same results. Here's the weird part. Whenever I press the left (working) brake the right brake will "ghost" it's movement very slowly. Looks like some sort of capacitive coupling? I need to tear it open and do some more testing. In the mean time, has anyone seen this behavior before?

Test to make sure each of the data pins on the board connect to one of the inner USB pins.

I discovered why lots of people don't use the GBU-38. I read the 38 has an accuracy of some 30 feet and thought that's all I'd ever need... until I noticed hitting tanks was about a 60% chance which drops to 0% as soon as they move. Didn't want to mess with GBU-12's because of all the confusion involved with setting up the laser. Eventually I put one on the middle pylon just for giggles and didn't touch the laser settings. It worked very well. In fact, I tested a few more and found that they hit so accurately there isn't any visible offset between the crater's center and your TGP crosshair. Also you can carry an absurd number of them. I think I found my new favorite weapon.