reece146

I think that if people get frustrated with the Spitfire or others... take a break and go take the TF51 for a spin. I did this a coupple days ago when discussing things with a friend that was new to DCS. I hadn't flown it in almost a year. I was shocked/surprised at how docile and easy to handle it was on the ground and how it seemed to jump into the sky on take off. This is after after messing around with the other warbirds for the last year. So, if people could take a step back and fly the TF51 I think they would see concrete improvement if feeling discouraged. 2.5¢

I think it is just a matter of not bothering to put in the amount of time to understand how to fly this plane in DCS. Putting aside whether it is accurately modelled or not... There is no reason why anyone can't take-off and land like a "pro" in the DCS Spitfire as shown on countless examples on Youtube. That said, I'm suggesting this with the caveat that the user has a joystick, rudder pedals, and analog brake handle. I can't imagine being successful with a keyboard but there's probably people that have done it. If this old fart can do it with a T16000/TWCS set up then anyone can. There is a point where things "click" and suddenly you can feel (see actually) the momentum changes in the aircraft and are able to control it without thinking - once comfortable with the controls. Also, framerate, framerate, framerate! 2¢

Civ version with/without doors would be great.

This weekend LTT did a build with a Mini-ITX+ EPYC mainboard and the Asus 3090 they used (waterblock - stripped back) really got my attention.

If I was buying a GPU today I'd likely go for the 6800XT or 6900XT. The NVIDIA line up is all over the place with models being promised, cancelled, replaced, and generally just a fuster cluck of bad marketing / product development. This assumes you can actually find anything to buy of course.

OMFG! You just made my weekend (year?)!!!!1111!!!!

I always turn it on immediately after flipping the tanks open - one less this to forget.

How are you resetting the bios? Menu in the bios or jumper on the mobo? If you haven't tried it then clear via the jumper method. Also, running latest bios? No OC, right?

Interesting. Do you think you should be getting more FPS with MSAA off? What kind of FPS numbers are we talking about?

Tail dragger version of the Yak (Yak-50) could be a good dynamic stand in. It's not era correct or anything and it's not a two seater but between being an appropriate size, configuration it could be a decent stand in and provide a quick win and/or more variety to DCS. Just a thought.

"We heard you don't like root kits so we got you to download this root kit to avoid downloading root kits." Windows Defender is as far as I'm willing to go. I only use Windows for games - personal life/data is on Linux so my use case is not typical.

FWIW, I think GS totally lost SA at the beginning in that round. When he did finally pick out where the fight was he was something like ~15 mi away. He lost SA and ended up leaving the fight area. Beyond that - hard to tell if he could have picked out the other aircraft visually. Youtube compression makes a mess of things.

Never noticed/knew about the ID light. Interesting. Could this be implemented as a mod I wonder? For ILS there are mods to place ACLS on runways so from an operational point of view you can achieve it even if the technical details are different. For the LCD screens there are mods to modernize the cockpit also - I haven't tried them yet. The Sniper would be good. ED's tact has been only to model what was on the current in-game version of the Hornet and not deviate at all. As an example, in the past they have stated they will not do ILS on the Hornet (IIRC). Maybe this could be added as a mod a well. For the rest I doubt ED would want to go down the rabbit hole of forking their code base and adding the inherent maintenance/support work load to add those changes for such a small audience.

yeah, 0 to -1 range depending on how much of a rush I'm in to get off the ground (don't go into analysis paralysis to make it exact).

I find the intensity of the pitch/dip varies with the speed at which you slide the throttle forward. Torque effects I guess. FWIW, I typically slide the throttle forward slowly initially until I can feel the rudder "bite" and be useful against the air flow - then I start moving the throttle forward faster but not slammed forward. Runways are long - no reason for it. I spent hours and hours doing touch-n-goes to get the feel of it. It is very distinct/noticeable once you feel it. There's also the urge to over-correct regardless of curves - if you think 30% rudder is needed, try 15-20% and see if you can balance the "momentum" of the plane fishtailing left and right (with tail wheel off the ground I mean). Full disclosure: still struggle some days - not an expert DCS Spit pilot by any means - just sharing my experience in hopes it helps someone.

I'd try putting the pagefile on the NVME. The nature of swapping means that it potentially GBs of RAM are being swapped at a time so in theory this would allow the NVME to shine at the best bulk transfer performance possible.

Things cost money. Don't spend time justifying your purchases to random strangers on the Internet. If they have the Asus Strix and you have the budget then do that. Personally, for as much as I like flying in DCS I have no issues spending that kind of money on a video card if I get the satisfaction out of it. Time is limited and when I get a chance to sit in the pit I want it to be as awesome as is reasonable/practical. $0.02

Nah, I'm talking about benchmarks of 4 vs 2 sticks of like for like memory. I'll try to scare up where I saw it if I can find the time.

Another shout out for the "be quiet! Dark Rock Pro 4" - I have it on my 10700K but I haven't had a need to overclock in DCS yet (CPU effectively bored, 2070S OC is pinned). The cooler is very quiet so I have no qualms recommending it. RE: The power supply. 750-850 W is plenty. As suggested buy a good brand with a long warranty. I'll second the comments on the RAM speed. Get 3600 if it doesn't cost a whole lot more. Given a choice between say 3200-CL14 and 3600-CL18 I'd be inclined to go with the 3200. 3600-CL16 - depends on the difference in price. Supposedly there are performance differences with 4 sticks of RAM versus 2 sticks with 4 sticks being faster - but that is "bench racing" stuff - probably would never notice by the seat of the pants. That said, I did 4 x 16GB 3200 CL14. With the Channel Map in free-flight (Spitfire) using ~24GB by itself I thought it prudent to go straight to 64GB so I don't have to open the case again for a long time.

<the Mod Name> always matches what is in C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\<the Mod Name>

I'll try it again but that wasn't my experience last night. I set the covers down when first entering the cockpit and then turned on power.

So, it's still b0rked right? Was it ever fixed? Just flew for two hours. After take off, climbed to ~30k at 2700/46 and maintaining 180-170+ mi/h, cruised at various altitudes 2400/36, ran the fuselage tank dry and then RTB. When descending/ascending watched MP like a hawk to keep at spec at all times. At no point during this flight could I leave the cooling flaps in auto. Had to be continuously watching the temps and adjusting the cooling flaps manually. I'd try it in auto every once in a while. I could get into a manually set "steady-state" but of course that is not ideal if going into combat. I don't understand what is wrong with this module. It must be a coding issue? Some thermodynamic capacity value out of scale/scope or something? Cooling reservoir capacity divide by ten error? Opening the oil cooler makes the gauge swing quickly so that what makes me think there is a modelling issue. Of course without seeing/understanding the code this is just speculative BS - maybe they cool that quickly in real life with the door opened/cracked. Nowhere in the Mustang manuals (DCS, real USAF, or Chuck's for that matter) does it talk about having to manage the cooling unless a system has failed. On a different but related item: when you first get in the plane if you set the cooling flaps to both manual and then turn on the airplane, shouldn't the doors remain in their open position? I dunno. I tried this and then after starting the plane looked in the external view both flaps were closed in spite of the auto flippy lever thingies being in the down position.

RE landing... You don't so much land the Spitfire as sail it into the ground. Lined up, coordinated, flaps, ~110 and idle at the fence line and gliding in with a slow sink rate works with very little bounce. Keep some power on if you are doing touch-n-goes. This will reduce the amount of gyro effect from the engine when you start feeding in throttle again further down the runway. Once down pump the brakes like ABS would and pin the tail with the elevator to drop speed quickly in a straight line. Sorry if you already know this - just my experience within DCS. The rest of the warbirds (except I-16) are bush league simple to handle compared to the Spitfire - even the 109. The locking tail wheel on the 109 makes a huge difference.

I think maybe you need more control tuning as you are suggesting. It took me weeks (months?) to get it to a point I am happy. To me, the Spitfire in DCS flies like it's on rails - and is much less of a "b!tch" on the ground nowadays. I've never flown a plane in real life so nothing to compare against but re: the DCS Spitfire, it flies as I expect it should from all the accounts I've ever read about them the last 40 years. Not worth much as a comment, grain of salt, etc. but... FWIW, when I first got the Spitfire I was kind of deflated about how difficult it was to manage. Thought it was perhaps a POS software module and by extension DCS sucked. I was wrong. I noticed two things. Seat time with good controls and rebuilding my gaming computer into a machine that can manage to sustain over 60FPS really made the Spit feel alive in DCS. It made it very easy to handle because the screen allows you to react to what the plane is doing "now" versus what it was doing 30 frames ago or jumping into a "weird" state with no feedback in between frames of "now" and "before" to react to. At least that is my experience. As an experiment, maybe try dropping your graphics settings to get the frame rate up and and mess with the controls a bit more. There is a thread here that talks about setting up the controls. A lot of it depends on what stick/rudder pedals you are using. In my experience a curve around "20" (or similar hand tuned curve if your device merits it) makes a huge difference on the ground handling with the rudder/brakes. My joystick is 15/15 IIRC. Also, make sure you have a decent analog control for the brake lever. Switching the brake lever to the "flappy paddle" on my T16000M throttle made a huge difference. Maybe you have already gone done this rabbit hole. $0.02

Looks really good! Skins take a lot of time.