JimTM

They must have fixed the training missions. I tried a few and made it to the cockpit, although the Introduction mission mentioned the A-10C II during the outside view and then did not go further when I expected to enter the cockpit. I'll have to test this one again and try a few others to see if there is really an issue. However, between the manual, Grim Reapers, and Bunyap, I'm getting up to speed well on the A-10C. As to your question, back in January, I had "A-10C" on the training menu and the missions were in the correct place, although they were updated to a more recent date (Nov/Dec 2020?). Thanks.

Is there any way to access the original training missions for the A-10C? I haven't got the A-10C II and it appears to be required for the current training missions. Thanks!

I'm having the same issue. If I run the beta updater, I see a very quick dialog box and then the game starts (v2.5.5.39384). Update: I ran "dcs_updater.exe repair" and then I ran the updater again. The update is now running as expected.

I have the same problem as described in the opening post. I believe it happens when I join a relatively busy server such as Aerobatics Online (Caucasus). If I join a non-busy server, I am successful on the first try. I've attached a log file for my unsuccessful attempt at joining Aerobatics Online (Caucasus) with 35/45 slots full. I restarted DCS and I was successful on my next attempt to join the same server, which had 28/45 slots full. Windows 7 Home Premium 64-Bit 6.1.7601 SP1 CPU: Intel Core i7-3770K 3.50GHz GPU: ASUS GTX1080 VRAM: 8GB Driver: NVidea 398.11 Mem: 16GB DDR3-1600 dcs.zip

Thanks Ayindi! Your fix that you linked to worked well for me. I tried the Spit and Huey in single-player and multi-player (Aerobatics Online) on the Caucasus map. In single-player, only a few 1/2 second stutters over 10 or 15 minutes of flying and fps in the 70-100 range. In multi-player, a few 4 or 5-second stutters and a couple of 10 to 15-second freezes that resolved themselves. I flew the Spit and Huey for about 20 minutes each and I had fps in the 50-90 range. UPDATE: Well, looks like it's hit or miss. I tried an off-line, low-level F-86 run along the water in the Caucasus map and was getting great frame rates (70-100 I think) when the game froze solid.

Thanks Ayindi! Your fix worked well for me.

UPDATE: I installed the latest NVidea driver 390.65 and tried the Spitfire twice again on the Caucasus map in single player (Instant Action, Takeoff). Logs for test 1 and 2 are attached. Test 1, FOV=140 The screen froze after 30 seconds of looking around before takeoff. Test 2, FOV=125 The screen froze after about 4 minutes of flying in formation with one of the AI Spitfires. dcs logs.zip

I have three monitors (1 camera, 5760x1080) with conservative graphics settings and I too get freezes after 10 minutes or so on the Caucasus map (multi-player or single-player). It runs quite nicely (40-90 fps) until it locks up, with the sound still running. FOV: 140 Def. Shading: On HDR: Off MSAA: Off SSAO: Off Aniso. Filter: Off Terr. Shadows: Flat CPU: Intel Core i7-3770K 3.50GHz GPU: ASUS GTX1080 (8GB VRAM) Driver: 388.13 (latest is 390.65) RAM: 16GB I haven't played around with other maps a lot yet or installed the latest driver yet; that's my next goal.

I read this and this and this, went out and practiced the advice, and I like the Spit just fine. Once in a while I scape a wingtip, but only because I neglected one of the basics.

I viewed your track several times and the only thing that I can think of is that you may have stayed on the rudder just a little too long during the middle portion of your landing. Maybe if you come off of any particular rudder input a little before you see the full result it may help. I'm running into the same problem now and then, but the vast majority of my landings are OK. Attached is a track of a circuit that I did (pardon the view adjustment at the start). Note the air speeds and trim settings in addition to the control inputs at the lower left. I aim to approach at 95 to 100 mph, but I was slightly slow just before the flare. JimTM Spitfire IX - 2017-03-22 - Circuit Practice.trk

I always stay off the brakes just after touchdown, unless the plane is strongly veering off the runway. If my landing is relatively straight, and while there is still good airflow over the rudder, I use short, quick stabs on the rudder pedals to immediately correct any deviation as soon as it begins. Then, when the plane slows, I use short, quick brake inputs to immediately correct any deviation as soon as it begins. That said, I still have the occasional wing scrape on landing that leaves me a little mystified. You mentioned the "rudder dancing" so it may be that you're doing all of this correctly already and there is some other problem. If you still have issues after your online tutorial, maybe posting a video or track would help us spot any problems with technique. Good luck!

Make sure to read carefully the three-part essay in the sticky section of the SpitFire forum. That's how I figured out the Spitfire (and a bunch of other "hard to handle" taildraggers).

Did you try clicking on the yellow refresh icon at the top right? ...and, of course, scroll down the list. :-)

I was having the same problem until the "nose wheel catching" concept clicked during some test runs. So if you are steering left without the nosewheel button pressed and you want to go right: 1. Press and hold the nosewheel button and apply left rudder to match the position of the nosewheel (catch it). 2. Apply right rudder until you are heading in the direction that you want to go. 3. Center the rudder and release the nosewheel steering button. Probably the best method is to always keep the nosewheel button pressed when turning and only release it when you are going straight.

Ah, thanks. Once upon a time, all the labels in my A10C cockpit were blurred and I changed "RES. OF COCKPIT DISPLAYS" to fix it. I guess something else that I did fixed it.

As an alternative to the mods mentioned, try increasing the value in "RES. OF COCKPIT DISPLAYS" in the Graphics tab to 1024.

As a non-RL helicopter pilot, I tried the technique that Jay43 described and it works fine for me, with a 3kt loss of airspeed in a 10 degree bank turn. I never touched the collective (27 psi) or moved the pedals (the ball stayed centered) and used a bit of back cyclic to maintain altitude. I tried the same technique with 20 and 30 degree banks and lost 5 kts at the most. The small loss in airspeed seems to me like a better option than playing with collective inputs. However, I would make collective adjustments to maintain formation in a turn.

Thanks! I'll give the folder copy method a try and see how it goes.

See http://forums.eagle.ru/showthread.php?t=162870, which includes a video link on how to adjust controls with new releases.

BIGNEWY, in the past, people have warned against just copying the control files over to the new build. Is this no longer a problem then with the new .diff file format? Does copying the input folder over allow you to skip all the clearing and importing business? I have 14 planes and adjusting controls for every build is a bit of a pain. It would be nice to have a utility that would handle the clear and import automatically. Thanks!

Can someone please enlighten me on the current process for keeping controls up to date as DCS is updated. I have 14 planes and it's really a lot of work to keep my controls up-to-date. As far as I know, for every DCS update, I have to do the following for each of my 14 planes: - For keyboard, joystick, and six-axis throttle quadrant, clear the control category and load my existing profiles for each controller. Of course, rudder is not a problem. - Manually correct any key bindings that were changed by the update (e.g., F-86 speed brake extend/retract now assigned to keyboard even though my existing profile has them bound to a joystick button). - Bind any new functions that I need to the appropriate controller. Is the process just a fact of DCS life right now or am I missing something that would save me lots of time. It would be great if there were some sort of utility to update existing control settings. Thanks! Jim

Love the server! With the latest DCS 1.5.3 release, I was wondering if "Imposters=Large" is still required so that everyone on the server can spot well? Would Imposters=Small work? I find the large setting creates massive fuzzy imposters for planes that are quite far away. Is this what others are experiencing? Cheers!

- Readings are in kph. - Add zero to each number (e.g., 10 = 100 kph, 100 = 1,000 kph). - Thick needle is indicated airspeed, thin needle is true airspeed. - Small window at top indicates mach number. - Not quite sure what the yellow arc indicates (flap down/flap up stall speeds?)

Thanks NightRush. Well worth watching.

Maybe start with a Tiger Moth as a trainer for the WWII stream to start and move into WWI planes based on that experience. My dad trained in the Moth, so I'd love to see one in DCS some day.