KKR75

I agree and sincerely hope this gets fixed in future releases.

Just as an FYI, being Lebanese living in Beirut I can chime in a few words here. Yes I do agree this needs to be fixed, but just as an FYI: 1. Over 95% of the takeoffs and landings happen from the north towards the south, due to prevailing winds. 2. RWY 17/35 is pretty much never used. 16/34 is used for landing (mainly 16), while 21/03 (mainly 21) is used for takeoffs. 2. When and >IF< prevailing winds are from the north, takeoffs only happen on RWY 34, while landings happen on 03. KKR75

thank you :)

Hi, In the debriefing data, I see a whole lot of engine startup / engine shutdown messages, even though not once I had to do a mid-air restart. I am using a hotas warthog with 0/100/100/10 "slider" as my throttle axis, and 3/100/100/20 as my pitch/roll axis. What am I possibly doing wrong? Regards

I would love this as well ! One of my favorite modules to fly and it is sorely lacking in missions and campaigns. The "Stillness in Time" absolutely sucks (the edited version is marginally better).

UPDATE: I tried to connect to my work VPN before starting the update, and it works ! It's updating as I write this. So I assume my VPN network is using a different route to connect to the DCS servers than my home network. Maybe a mirror problem ?? UPDATE 2 after reading c0ff's message above: Indeed my home ISP is using some sort of PROXY, whereas my work VPN does not (straight conn to internet).

Hi guys, I tried exactly everything on this thread (updater without a number, with a number, etc...) and have the same problem. HELP ! :D

Here are some of my crash logs, they're all pretty much the same: # -------------- 20121113-200931 -------------- # C0000005 ACCESS_VIOLATION at 3FF4C95E 00:00000000 00000000 00000000 0000:00000000 3FF4C95E 0017F100 0000:00000000 3FEE3CA4 0017F170 0000:00000000 3FEE238E 0017F2D0 0000:00000000 3FED8DFE 0017F300 0000:00000000 F2438721 0017F390 0000:00000000 F2438BEA 0017F3E0 0000:00000000 3FFBF029 0017F470 0000:00000000 3FFC193D 0017F4D0 0000:00000000 3FFD9684 0017F500 0000:00000000 3FFD9579 0017F560 0000:00000000 40060498 0017F5D0 0000:00000000 400618D8 0017FAC0 0000:00000000 400642CF 0017FB70 0000:00000000 77A6652D 0017FBA0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 77B9C521 0017FBF0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 # -------------- 20121112-214524 -------------- # C0000005 ACCESS_VIOLATION at 3FE8C95E 00:00000000 00000000 00000000 0000:00000000 3FE8C95E 0012F4D0 0000:00000000 3FE23CA4 0012F540 0000:00000000 3FE2238E 0012F6A0 0000:00000000 3FE18DFE 0012F6D0 0000:00000000 F0668721 0012F760 0000:00000000 F0668BEA 0012F7B0 0000:00000000 3FEFF029 0012F840 0000:00000000 3FF0193D 0012F8A0 0000:00000000 3FF19684 0012F8D0 0000:00000000 3FF19579 0012F930 0000:00000000 3FFA0498 0012F9A0 0000:00000000 3FFA18D8 0012FE90 0000:00000000 3FFA42CF 0012FF40 0000:00000000 77A4652D 0012FF70 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 77C7C521 0012FFC0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

@Salvador, we've just been able to reproduce the problem time and time again in our squadron. It seems to happen as soon as a client opens up their ladder door. It might be the animation of the ladder coming down that's causing the server to crash.

Had the same problem crop up yesterday as fmsam's, i.e. no sound when in cockpit, but sound okay in menus. Tried the following: - Switched from headphones to speakers, on same sound card. No Go. - Switched from sound card to onboard. Works. - Reinstalled the game and revert back to sound card. No Go. - Uninstalled and reinstalled sound card drivers (SB XFi Titanium). Works. So go ahead with a full sound card driver reinstall, and report back. It should work. It did for me.

"THAT'LL BUFF RIGHT OUT" ;) nice pic !!!

yes correct. When you get the red triangle on the TAD, you will see a "NEW TASKING" message. Press TMS LEFT short to clear the message, press the corresponding OSB next to "WILCO" on the TAD, then hook the red triangle on the TAD by moving the green cursor up to it and pressing TMS UP short, then set this hooked object as SPI by pressing TMS UP long. You can then slew the TGP to that object using CHINA FWD long.

I assume you're playing the Georgian Hammer campaign. Yes, the F10 options will only be populated with entries when you are in the air, usually once you pass waypoint 2 or a little bit before it. Basically, if you look at the mission(s) in the editor, there's a hidden COMMS trigger zone that sets up the F10 entries once your plane flies through that zone.

That's great to know, but I never thought this wouldn't work as you described. After all, they're 2 separate entities working on 2 different frequencies. All in all it's the same as a player doing A-A refueling while another does JTACing.

yep, that would be the white triangle on the TAD