EinsteinEP

I'm having the same issue. MP was working for a while, then I started getting CTDs after connecting to Master. No change in PC configuration.

That's a puzzler, Chair. I see that you're using more manifold pressure than RPM, which isn't good for a real engine, and your oil temp redlines for a bit, but when I take control of this track and just cruise moderately around the map, I also get the engine failure. Seems like plenty of fuel, radiator settings correct, mission doesn't have any failure flags set, no system failure triggers...hmm....

AWESOME

This is broken for me, too. I thought I read somewheres in these here forums that "Prepare Mission" functionality doesn't work for the current gen DCS. Eddie, if it works for you, I'd love to see a sample mission that's been prepared so I can look at the folder/file structure.

The forward cyclic input needed to go from on the ground to hover is due to the fact that the helo is not actually "level" when on the ground, but is pitched forward. Level trim on the ground is different than level trim in the air. Conversely, if you land while trimmed for level hover, the helo will try to roll forward (don't forget to release your wheel brakes!).

IIRC, after being dispensed, the BLU-108 skeets will detonate when they find a target (each skeet has a coning search pattern, so there's no assurance of 100% coverage or that multiple skeets won't go after the same target), or when they stop spinning (i.e, hit the ground).

@paulrkii, Great to hear, thanks for the vigilance! @Deadman, Which switch panel is installed on A-10Cs with the ARC-186, then? Or do those aircraft still retain the Radar Beacon SINGLE/DOUBLE switch?

A couple of these have been mentioned in old posts (~2010) but are still present in the 1.1.1.1 cockpit. Armament Ground Safety Switch - FROM "SAVE" TO "SAFE" Antenna select panel: - Should be "IFF ANT" UPPER/BOTH/LOWER (this switch is correct) "SAT ANT" HIGH/BOTH/LOW "EQI HQ TOD" ARC-186/OFF/ARC-164 (switch is currently a two position and is labeled for the old radio beacon select switch) Intercom panel: - Swapped "UHF" and "VHF" text labels - Missing the selection indicator stripe for the selector dial Oxygen system panel: - FROM "TEST MARK" TO "TEST MASK" HARS Panel: - Missing the indicator triangle underneath the "LAT" text Photos from an actual A-10C cockpit attached for reference. a10c_panel_shots.zip

Seems that the change after re-installation was that I forgot to set the broadcast capture mode to "game" from "desktop", so I was really broadcasting my desktop. Worked well, but I'm still confused as to why Procaster doesn't recognize the DCS.exe process. It's not listed in the ignoreprocesses section of the .xml...

Hmm...I can't seem to get Livestream to hook the DCS.exe process: A-10C or Black Shark 2. Do you know if there's some special config step or option needed to get it to work correctly? [edit: an uninstall/reinstall of the Procaster tool seemed to do the trick!]

Additional info: Based on reading this post here, I recall that it was getting dark in the mission when I left. Maybe there is a night-illumiation related issue?

Bug description: When joining an MP server I got repeated CTDs from the multiplayer client (see attached .crash logs). I was playing on the same server same mission 30 minutes earlier and had exited the game to go AFK. When I came back, I experienced two crashes, then restarted the PC and got another two crashes before giving up on BS2 and trying A10C (which resulted in several back-to-back Client Update Timeout errors). Steps to reproduce / Conditions of occurence Joined stallturn server, Rampant Bear mission, played for ~60 minutes, exit game (shut down application), attempt to rejoin. PC Configuration i7 920 6 GB RAM Velociraptor 300GB 10KRPM HD EVGA 470GTX (nVidia 290.36 drivers) Dual monitors (1920x1200, 1280x1024) Attachments 4 .crash logs Hope this helps! Logs.zip

Bushmanni, Yo-Yo specifically said the flight model change affects only the vertical hinge (aka flapping hinge) dynamics and any other effects are placebo.

Fantastic, Yo-Yo! Thank you for the clarification! A+ work, as always.

http://forums.eagle.ru/showpost.php?p=1321466&postcount=1 OK, I'm intrigued. What parts of the flight model were changed/tweaked/updated?

Those are boombox speakers to play Ride of the Valkyries.

Whether or not it's approved by Real Life Black Shark Peoples, you can perform an engine re-start in flight, given that the engine is still operable. The process is the same as on the ground - start the APU, set the engine selector switch to the correct engine, hit the start button and wait through the start up process. Don't forget to double check fuel quantity and fuel pump/cutoff valve switch statuses before attempting the restart though (more on that in a sec). And shut off the APU after the engine has stabilized. The Real Life Black Shark Peoples have a good point, though: if you don't know why an engine stopped, just trying to start it again right away probably isn't a good idea. While, in the sim, you don't have to worry about having to explain engine damage to an angry crew chief, if the engine stopped because A) a fuel pump/valve switch got accidentally turned off, B) the feeding tank ran out of gas, or C) there was an unauthorized installation of 20mm holes in the turbine disk, etc, the time/effort you spend trying to start the engine will be wasted. Troubleshoot the cause first, if you can, then fix it before attempting a restart. For example, if your engine in your example really had stalled due to ice (clogged inlet is the root cause, IIRC), and you had attempted an in-flight restart, the engine wouldn't have lit off. You would have needed to engage the anti-ice devices and probably even drop a few 1000 m to get to some warmer air and ensure the intake was clear. If you can't figure out why an engine has stopped, RTB on the single engine ASAP (your other engine may be getting ready to go, too!). Dump stores, if you need to. If you absolutely have to have the second engine (to get over a ridge, etc.), then you might as well try it anyways, but I would also start looking for a place to ditch.

Hence the wax pencil. Wonder if anyone's tried dry-erase markers. Hope they don't get a Sharpie by accident!

R5 is the button on the right of the CDU at line 5, while L7 would be the button on the left side of the CDU at line 7.

The load button stores the current frequency to the selected preset. It's not required to use in manual mode.

Out of curiousity, what controller are you using and which button did you assign to "mic switch up"?

Hmm...could be that TrackIR is using a different profile than you are expecting. While in game, alt-tab out and open up the TrackIR window to see what profile it's using. I know mine detects A-10C as Black Shark and uses the profile I've specified there.

AFAIK, all you need to be a player ATC is to join a multiplayer game as a spectator and participate in comms. The player JTAC feature was removed from DCS A-10C.

In testing F16s at Edwards, we had relatively frequent FCC failures - maybe two or three over a 6 month period? It would be interesting to know what failure statistics are being modeled in the simulation - it sure seems a lot higher than I would expect.

Sweeeeeeeeeet!