Emacs

Thank you all for the suggestions! The range is what I expected :) Are there any Quest/Link DCS players around who can say if there is enough lag, to be a concern? Would instruments, MFDs and HUDs still be readable? Cheers, Emacs

Hi there, I'm running DCS World (mostly P-51 and F-5E in multiplayer for now. A10C and F-18 later on) on a 4k monitor with about 60fps on P-51 and F-5 (vsync enabled). Machine is a i9 9900K with 64GB@3600Mhz. Graphics card is a RX 5700 XT (can't change that, because the machine is a hackintosh too - and a very nice one at that). This hardware will be here at least for the next three years. I feel I'm ready to dip my toes into VR but I cannot make up my mind. Ocolus Rift S? Ocolus Quest with Link? HP Reverb? I'm aware that all those headsets are going V2 in the next few month, but I want to go VR now. The Quest with link looks intriguing for OLED and simplicity. Then again I don't care about portability (have an Ocolus Go for VR pron already). The Reverb looks great for the much higher resolution but I'm not sure my RX5700XT can handle that. So, just a used Rift S from eBay? Best common ground. Easy to setup. Lot's of other players happy with it. I totally loathe the owning company though. I know the topic has been beaten to death. Still... Want to try DCS VR now. Would very much like to stay in the three-digits costs. I don't think I would do much VR beyond DCS. Maybe a round of Serious Sam VR here and there. What do you think? Cheers, Emacs

Hii ZeroReady, Thanks for the reply! Makes a lot of sense about the AI. I‘m pretty new to DCS and very new to the A10. Only did a handful of multiplayer missions, but understand multiplayer is the way to go. I‘ll watch out for the Georgia at War server for my next attempts. Cheers, Emacs

Hi there, are there any missions available somewhere which set the A-10C in the role of a forward air controller, assigning ground targets for other planes to attack and co-ordinating air strikes? Cheers, Emacs

Hi ! so, I've copied my DCS install directory and SkateZillas tool. The tool is currently updating the DCS copy to the latest open beta. But I'm not sure about \Saved Games\DCS . Do I point both "builds" from SkateZillas tool to the same \Saved Games\DCS, or should I rather have a copy of that too? i.e. as \Saved Games\DCSBeta ? Cheers, Emacs

Hi there, I'm dipping my toe first time into multiplayer and love it so far. I learned that some servers have a Discord audio channel, others use SRS. Question about SRS and the P-51: I understand SRS allows to use the planes radios to tune in to different frequencies and talk to different groups. But the P-51 radio freqs can't be set in the cockpit. They are pre-set in the mission planner. When flying online I don't have the mission planner. So, how does SRS work in a P-51? Cheers, Emacs

Tatsächlich L.Strng +Tab .-)

Ah -besten Dank !!

Hi zusammen, Ich war heute zum ersten Mal auf einem Multiplayer Server. Der nutzte SRS, ich hab aber aktuell mur Discord. Lange Rede, kurzer Sinn: ich wollte die Text-Chat Funktion von DCS nutzen, finde aber die richtige Tasten Kombination nicht. Die Anleitung sagt R_Ctl plus Apostroph. Das müste R_Ctl plus Ä sein auf einer dt. Tastatur... Hat aber bei mir nicht funktioniert. Kennt einer den Trick? Cheers, Emacs

Playing with the rudder axis configuration I see that my rudder doesn't cover the full range of values. Let me see if I can explain this. When I have my feet off the rudder the red dot in the DCS axis config is perfectly centered. No deadzone required. When I push the left foot down the red dot moves along the curve the left end of the scale. 100% left foot results in 100% left red dot. But when I push the right foot down, the red dot travels only about two thirds of the way to the right side of the axis. 100% right foot results in about 70% right red dot. My RCS doesn't give me full rudder authorothy to the right. That explains a lot of my awkward taxiing - particularly bad right turns. In other words, the maximum value generated by the potentiometer in the RCS rudder is not what DCS expects as maximum value (255 I guess). Can I configure that somewhere? Cheers, Emacs

Feels very good with a 10 curve and 100% saturation. I've just practised aerobatics for an hour and in this scenario the controls are very fine and lively. I see the onset of the stall/departure when the cockpit starts to shake a bit. Was doing mostly level stuff and never got above 4 to 4.5g in the turns. Keeping the ball centered requires very, very fine input with the rudder and sometimes a bit stick into the oposite direction (outside) to keep her from "falling" into the turn. That was very similar in the gliders back then. Slight pull on the stick, rudder a tiny bit into the turn and stick ever so slight crossed with the rudder keep her at a given turn rate. It is very difficult to do this tiny bit of rudder input on my RCS. The springs are still pretty strong and it requires some force to get it out of center. Maybe I need to give the rudder a different curve. Maybe 25 or even 35. Loops are much better now with the full pitch saturation! Quite a difference :) Cheers, Emacs

Thanks for the link and for doing the videos! I think I stumbled upon your channel before. Cheers, Emacs

Ok - thanks for the feedback. Yes, I do have rudder pedals (old TM RCS). It's not very precise anymore, but I'll keep watching the ball. Do you reset rudder trim before going into a fight? I have now removed the saturation limit and have set the curves on pitch, roll and rudder to 10. We'll se how that goes :) Sometimes I really wish for some forcefeedback in those Hotas sticks. A few decades ago I spent quite some time flying glider planes in the real world. You could tell so much about the state of your flying just by the way the stick "felt". And the subtle shaking of the plane when you got close to a stall. After some time I could even tell by the way a spot of rough air bumped the plane, if there was a thermal uplift hitting more the left or the right wing. Much much better feedback in the real world compared to any sim I've seen. Cheers, Emacs

Thanks to both of you ! So, roughly 160 - 170 GB. That's what my current Eagle Dynamics directory is. Cheers, Emacs

Hi there, being new to DCS and the P-51D I'm now starting to learn a bit of dogfighting. Mostly I use the 1 vs 1 mission with another P-51D as adversary. Although I rewatched "The Art of the Kill" (anyone still remember that one?) on Youtube I do get my a$# handed back to me 99% of the time. Got some maneuver kills though. The AI really likes to fly into the ground or collide with me. Anyhow, point of this is the question: should I limit the saturation of the Y-axis (pitch) in the DCS controls setup for the P-51D? All the time when I'm in a tight turn I pull a bit too hard and the plan flips over. It's really beginning to take the fun out of it for me. Should I stick with the original setting and wait until I have build up enough muscle memory, or should I limit the saturation? If so, which value would be good? I read something of about 60 - 65 % How have you set this up? Cheers, Emacs

Hi there, I'm pretty new to DCS. Currently have the stable version (2.5.5.41371) with a few modules installed. I'm interested in trying out the open beta, but I have a few questions about the organisation of both installations: When I add the open bata, is that a complete new install? Download of everything again? What about the modules I have (some planes, all maps, some campaigns)? Is their installation shared between stable and beta, or do I have to download them a second time too? Both questions a mostly because I want to calculate my diskspace first. Cheers, Emacs

I reflew the mission. This time no trouble at all 46" and 2700rpm all the way up to 32.000 ft. My wingman and me crossed the channel, found the 109 and I killed it. Then we flew back and I fu*#d up the landing :( Glad all those patterns and touch&gos tought me something... Anyhow, looking back at the procedures, I think maybe grafspee was right after all: > I would check Mixture handle position , often ppl switch it to emergency position not RUN position and this may cause troubles at high alt. It is difficult to spot if you are in RUN or emergency. Could very well be that I was in emergency on that previous flight. Cheers, Emacs

Yep, I keep fuel pump running all the time. Cheers, Emacs

Thanks a lot. I will do another testflight later today and will do exactly that. Cheers, Emacs

Thank you for that information. I wasn't aware that I need to monitor rpm so closely. Mixture was in RUN all the time. Coolers door were left in AUTO if I recall correctly. But I was mapping thise switches to my Warthog during the flight. Possibly I did something wrong. Is a constant 46"/2700 enough to reach 14-18.000ft? I remember I had to struggle to reach the altitude where the high blower kicks in. After that there was enough power, but the last one or two thousand feet to get there the 51 was barely climbing anymore. But looking at the recorded track, I may have had airplane damage from an earlier collision. I'll give it another go in another flight this afternoon, more closely paying attention to the rpm. Cheers, Emacs

Yeah... I was looking at that recording of my flight... Very, very embarassing. But hilarious too, so I'll try to add it here anyway. When looking at that track, please keep in mind, that I have logged 4 and a half hours in the Mustang and maybe total of 6 hours in DCS overall. Those four hours were spent flying patterns practising touch and gos. It is obvious, that the pilot of this track has no idea what he's doing. Please be gentle in your comments. The track is based on a small mission I created for me. I'm flying out of Tagmere with a wingman. There are some B-17s flying a big circle (to train escorting them), there are some other P-51s attacking a small german boat and some trucks (to join them and train ground attack). And there is a lone Me-109 waiting on the french coast. In this flight my idea was to see if I can find the Me-109 and see what happens. During the flight over the channel I'm mostly busy with modifying my Warthog buttons. When you see me drift, I'm probably fiddling with some switches and not paying attention. A number of remarkable things happen here, including the engine problem at 20.000 ft which happens between 06:59 and 07:01 am (that's 20 minutes into the track file) :doh: 1.) I remember that I wondered where in the world is my wingman... looking at the track file I see now, that I killed him first. Still on the ground at Tangemere. Ground collision. The guy taxied into my tail, cought fire, and died. 6:45am, 5:44 minutes into the mission. :music_whistling: I recall that I noticed a small bumb during taxiing. Thought I maybe taxied onto the grass a bit... This shouldn't be my last kill of the day. But more on that later. From the track review it looks like he took off my rudder. I'm not sure if that is just an optical detail, because I clearly remember that I did plenty of rudder trim all the time to fly straight. And that rudder trim felt perfectly normal. 2.) Next is my climb to about 20.000 feet. I struggle a bit around 6:56am but then the high blower kicks in and I continue to climb until I reach 20.000 ft at 6:59am (19:40 minutes into the track). At this point you can see the manifold pressure and the rpm fluctuating wildly until I decend a bit at 07:01am. This is the two minutes of the track I'm trying to understand. :pilotfly: 3.) I continue to fiddle with the knobs on my throttle and cross the channel. At 7:25am (45 minutes into the track) I have spotted the Me-109 some 3000ft below me, circled behind him and fire a salvo at 1000ft range at his six. Multiple hits. Iron ass. The 109 isn't impressed at all. We dance for maybe five minutes. Then my engine dies. I'm a few miles off from the french coast, so I try to sneak back to land to bail out. But I know I'm too low and too slow. And the 109 is still all over me. At 7:32am (52:38 minutes into the track), I've decided to bail out as I hear the 109 approaching. I'm searching in the DCS manual for the correct key to bail, when my P-51 explodes. Ok I thought, the 109 was attacking, probably hit a fuel tank or something. Looking at the track record, I realize, that was actually my 2nd kill of the day :D As my wingman did, Jerry collided with me too. Both planes exploded at that moment. If I continue to be this good, I'll be an ace by afternoon !! :megalol: The mission was fun, but looking at the recording was just hilarious. I'm glad I'm back into flight sim !! So, now let's see how I can attach a 4MB zipped acmi file here. Cheers, Emacs Tacview-20200328-152417-DCS-P-51D_Training01.zip

Hi there, I'm new here I thought these times are good to come back to flight simming after about 15 years of absence. Back then I spent quite some time with the various incarnations of Falcon 4.0 and the PMDG 737 in FS-X. So I got myself a i9-9900k, 64GB RAM, a Radeon Rx 5700 Xt (8GB) and a coulple Samsung EVO 970 SSDs. Added a TrackIR5 and a TM Warthog. Rudder is still my good old TM RCS plugded into the base of my old Cougar until I get something modern with toebrakes. Got DCS World 2.5.5 and bought a couple of the discounted modules and currently "learning to fly" again, mostly in the P-51D Mustang module over Normandy. I can fly and land the Mustang quite ok, but boy do I have trouble learning the engine management. Right now I can‘t get my head around the following: After take off I slowly climb with 2700rpm and 170 kts. I trim the rudder all the time to keep drag low. With altitude the manifold pressure decreases until the high blower kicks in. Pressure goes back up to 60. But shortly after, once I reach around 20.000 ft some wild fluctuation in pressure and rpm happen. I don‘t know what that is. It „feels“ as if the high blower cuts out and then back in again. I noticed the carb temp is at -50 °C. That can‘t be good, right? All other temps look fine and are mostly in the greens. Oil temp is a bit low with +40°C. But when I turn from RAM air to filtered, the engine sputters. I tried hot air too, although I understand from the manual, that should be automatic, but it didn‘t change anything either. Rpm and pressure keep fluctuating wildly until I sink below a certain altitude again - then the engine runs normal again. That process can be repeated. Climb and it begins again. I know I‘m overlooking something. Probably something simple. Any pointer into the right direction would be much appreciated :) Cheers, Emacs

Very, very nice!

Wow - thank you both ! That was already a great hint :) I'm running DCS now in the native 4k 3840x2160 resolution. MSAA and SSAA to off. In windowed mode fps were mostly around 50. Then I tested full-screen and the mouse does work as expected ! And it is a pretty solid 60 fps now. I say I'm a pretty happy camper now! Even manage to land the Mustang pretty well by now - well, most of the time. @imaken: one question: you said "I don't need or use MSAA or PD in 4K" - I fully agree with MSAA. But what is PD? Btw. I have AF at 16 and VSync on. The Vsync limits my fps to my monitors refresh rate and as I have no gaming monitor, 60 fps is what it is. @Art-J: thanks for the directory information too! C:\Users\emacs\Saved Games\DCS\Config\Input\ is there and writable for my user. But I think I found a possible explanation too. In that .\DCS\Config\Input I have two folders for the P-51. I have: Config\Input\P-51D-30-NA Config\Input\P-51D Config\Input\TF-51D I know the TF-51D is the free included trainer variant. I don't fly that. The P-51D contains files which are older. Around the time I purchased the Mustang module. The P51D-30-NA contains files dating from yesterday. I have no idea when or why this directory was created. But I guess, the config I'm looking for is in the P-51D folder. I will check that. Cheers, Emacs

Hi imacken, My monitor is actually a 4K Dell. I did set the resolution in Windows to 2560x1440 to help with gaming. The machine has been build and is used mostly as a hackintosh for photo and video editing. I installed Windows 10 64bit Home edition on the second SSD - for gaming and mostly for DCS. Cheers, Robin