HeadHunter52

I've met a couple Jug drivers, and seen plenty of interviews. With the paddle prop and crew-inspired WEP settings, it was a beast. If it is left to factory specs in the sim, it WILL BE inaccurate as fielded in combat except as represented by dead pilots all over the sim-scape. "Now, if you want to argue that DCS WW2:1944 is supposed to cover the Normandy landing period, then I suppose there is slightly less impetus to model the higher boost... but in that case, they would have to remove the Dora and Kurfurst outright, as the models didn't even exist at the time of the Normandy landings;" ---THIS is an excellent point. I don't give a rat's arse about getting everything down to the niggling picky details that so many test-jockeys seem to thrive on. Variances between groups or even squadrons were many. The GENERAL widespread experience is what is key - and the point of the sim. In general, field mods of the most popular variety should be included because they represent the real-world application of the technology actually used in the war effort. It would have been a wholoe lot better to field the 109-G variants and leave the K out of it. Have a squadron that brewed their own fuel, and modified their WEP independently of the rest? Nuh uh.... no-go. Have an Air Force that generally introduced fighting tunes above factory spec? You damned well better include it. Those boys in the field know a hell of a lot, and some are still around to talk about it. Makes we wonder about the behind-the-scenes reasons for some of the devs' decisions. And yes, if the Axis fan-boys were neutered, I'd be howling for their side, too, so don't go there. As much as I hate everything those bastards stood for, and will personally never fly an Axis aircraft in a sim, crippling a historical representation in the face of historical application is just pointless.

Slugging along with a Logitech Attack 3. It will be a hall effect device of some sort that replaces it. I think I'm done with pots.

P-40, P-47 are in the works. At some point, a Hellcat and Corsair. Much as I hate Axis forces, there has to be some sort of Jap plane to balance the load. I just hope it isn't some sort of superbird. As for bundles? I think a good map with opposing planes is a good idea. And yeah, the newer birds can wait. :D

Did some testing on my system this week. Core 2 Duo 3.0Ghz E8400 6GB RAM EVGA GTX 750Ti SC My GPU won't heat more than 43c with BOOST 2.0 implemented via DSR RAM has at least 1.5GB free available CPU - BOTH cores flying along above 90% I didn't think both of them would be running so hard. Audio on one of them? Not THAT wild....

Yeah. I watched all of his vids on the subject. Excellent study. But my system is very limited compared to his. I had to play with what I thought were the best options regarding capabilities. That said..... I did use the Task Manager panel and System Performance (Win7) last night. My findings... Both CPU cores are close to max. Strange, since I thought only one core was for game play, and the other for sound. Couldn't imagine sound being quite so busy. RAM was not maxed at any point. Temps on my GPU are completely within normal and safe range. In fact, I never hear the fax spinning up to speed. I would appear that my limitations are almost entirely in my CPU clocking at 3.0GHz. Unfortunately for me, there are no BIOS options in my HP business class workstation to overclock. Not ready for a MOBO /CPU upgrade, so.... I'm going to stick with DSR and 8Q MSAA. Visibility is much better with it. I just need to learn where to actually lOOk with TrackIR5 so that I have a correct focus.

LOL Noobid is as noobid does.... Some things can be found with good ole search, some by asking the same question for the 10,000th time.... and some by digging into to it yerself. But I do appreciate what I manage to locate here. Good info. Some of it ports over to the little guys.

I let go of the stick for a couple seconds, unless the nose is up, in which case I try to get it down and remove any left/right input. She straightens out well, unless some Jerry Can blows your wing off in the middle of this. When your angle of attack is harsh (yanking the stick), your wings are at the edge of stalling, which is a loss of lift. They won't stall at the same time, so you will get a nasty roll. Try to keep your speed above 225. 250 and above would be the safest speed. When you pull back, don't do it all at once. You can pull fast, but increasing the speed of pull. Watch for the buffeting as your warning that you are about to be screwed. Don't try to stay at the edge of a buffet. When you're knocking and rocking, you've already gone into it too far. Stangs need speed to live. If you have to run away to get it and come back, give it a shot. You have a speed and turn disadvantage built into the 51 because of its original mission - which you're not likely to see much of at all in this sim.

I'm sitting here laughing, marluk. Been a victim of post-collapse before! I actually had a chunk of it copied to notepad before the crash. Slap to side of head, some repentance for my stoopid ways, and I do it right, now! :thumbup: It does suck. Shoulda thought of the task manager.... but the one thing I've leery of is switching aps while flying. Maybe because DCS crashed. Maybe because..... oh heck, I'll do it. ;) I wish my board was Z79 or whatever-the-heck-it-is that OCers use. HP workstations BIOS are locked down. I read the E8400 can OC from 3.0 to near 4. Wouldn't that be nice!? Then again, DCS running multi-threaded would be nice, too. Eagerly waiting for EDGE. This year, right? :music_whistling:

UPDATE: Increased Visibility Range with DSR and MSAA 8Q UPDATE re: visibility range with DSR and MSAA 8Q Ran an MP mission against an airfield many miles away. Had a nice level flight to it. Since Tracks now work in MP, - I was able to replay the flight and take advantage of the F3 flyby feature as a starting point for measurements. - As the plane was parallel to the camera, I started a stopwatch. - I then recorded various key events as the plane flew away. - I recorded air speeds prior to the F3. The first flyby was at 225 mph = 3.75 mpm = .0625 mps The plane grew smaller and smaller, wings discernible from the fuselage. At the 31 second point, the plane, which was TINY, turned into a block 4X as large. It transformed into a black square. This 31 second point was 1.93 miles away. I could see it grow smaller, and slowly turn to the left. I stopped watching at 90 seconds (at which point it was at 250 mph). Calculated at the original slower speed of 225, this visible plane was 5.625 miles away. Hitting F3 again, now at 250 mph = 4.16 mpm = .0694 mps, the plane "blocked" out at 26 seconds, 1.8 miles away. I stopped watching at just 60 seconds, which placed the plane 4.16 miles away. It's not that it couldn't be seen, it's just that I was sold on these settings and growing tired of watching. With my 1080 monitor, running DSR 2X and MSAA 8Q, I can see a prop plane against the sky out to just about 6 miles. This is, of course, against a blue sky. But the theory plays out - DSR took a vanishing act and turned it around. Oh.... 35 to 52 FPS, too. Just a refresher, I run a basic nothing-special noob rig. HP workstation with Core 2 Duo 3.0Ghz E8400 working with 6GB RAM, and an EVGA GTX-750Ti SC. I'll be at 8GB by next week. Not sure if that will help things much, but I'm curious to see if my CPU anchor is in any way caused by a RAM deficiency. Without going to a new rig, I may try an SSD for the game and swap file.

UPDATE to the recent UPDATE:: GeForce Experience ShadowPlay failed on the recent settings. I had to remove it and reinstall. Good news is, it's fine after ward. Running DSR on 2X. Actually set MSAA to 8Q! Cleaned up the instruments quite a bit, to where I have no trouble reading them at all. I get some tearing, but it's not a deal breaker. OOn the MP server list, my FPS shows about 138. It has to be a misreading, though, because in-game on MP, I'm pulling 33 on the field, 52 at 8000' and 25-30ish on a full guns blazing dive run on AAA emplacement at the enemy field. The neat thing, contrary to what nay sayers say about DSR, I can see the gunners down there a lot earlier, and clearer. For the first time, I saw muzzle flashes from 3000 or so (guessing, since I wasn't looking at my altimeter.)

I set up DSR yesterday, independently of this thread. Wrote it up one another. Yes, it helps. Cuts FPS a bit, but I determined that my bottleneck is my CPU, not my GPU. Things do wake up.

From what I hear, the AMD GPU cards don't get along as well with DCS and NVIDIA GPUs. That said, 5FPS is dismal. My processor is a 3.0Ghz Core 2 Duo, and I get 50ish with a GTX 750Ti. You CPU will do a lot better if it has its own 6GB of RAM to play with. If you can get a better card, NVIDIA-based is my recommendation, you'll see instant improvement. 2GB RAM on the video card is a must. More the better. You have 1/8 the vid RAM you need...., and I'll bet that GPU's bus is seriously thin.

NVIDIA DSR Increasing Performance Firefox crashed, and blew my previous post all to pieces.... starting over. Grrrrrr UPDATE: In an effort to increase frame rates, and more importantly, object detection at a distance, I did some reading. My 1080 display is a lot better than the previous one, but pixels are pixels, and if something can not be resolved larger than 1 pixel, it may not appear. My search took me to NVIDIA's DSR, Precision X-16, Control Panel and weird results in DCS. While studying articles on resolution I discovered DSR, Dynamic Super Resolution. Put simply, it is NVIDIA's method of simulating a much higher res screen, namely, 4K. What it does is simulate the higher res, and then "down-samples" it to your monitor's native resolution. By selecting DSR in the Global tab of NVIDIA's Control Panel, you gain access to resolutions higher than you normally have, if you are like me and have noob equipment. I hoped this might get my detection distance stretched a bit. It looks like it has. At one point, ShadowPlay was reporting 137 FPS before loading in MP. It dropped below 60 after that. Gremlins, I'm sure. In my quest to retain quality, I played with other settings in NVIDIA CP and DCS Options. I took screen shots of CP for you to review. This combination is getting me over 60FPS (reported.... screen is only 60Hz) in SP, and 50ish in MP to start. FPS drops lower quickly, as usual, in MP (but they seem more constant and smoother, if that makes any sense.) I tried really maxing things out and discovered that MP loads your CPU. My issue isn't really with my GPU. Loaded up Precision X-16 and bumped my stock temp setting from 80c to 93c. Boost 2.0 is an overclocking method that relies on target temps as a limiter, rather than clock and power. Clock and power are automatically bumped up until the GPU is cooking at your set temp. I like the idea. After a hard session in MP, I quickly looked at my temps - 48c. Hardly even warm. This is how I came to believe my CPU is my biggest limiter - Core 2 Duo E8400 3.0GHz. My card isn't being pushed hard enough by my CPU to really suffer. Too bad DCS runs on one core only. The 3rd attachment shows where to find DSR if you've never seen it. DCS Option settings are high for visible distance, and medium for textures.

Both you guys get my vote. I want my 150 fuel..... And WEP to produce speeds that are greater than tested MIL.

K4 wings get fixed, Dora gets a WP50 correction but still flies like a kite, and the 'Stang? lumbers along....

"With the paddle-blade prop, they could easily out-climb the Bf 109s & FW 190s. They could also out-turn the German fighters above 18,000 feet. And they knew that they could always break off the fight by hitting WEP & dropping the nose. Absolutely nothing in the war could catch a Jug in a power-dive. Not even an Me 262. And that's without cranking-up the boost. When the crew-chiefs cranked up the boost, the plane became all but invincible in the hands of a skilled pilot. They said the same thing that my dad had told me when was a little kid - hitting hitting the water-injection & pushing the throttle past the stop to full war-emergency-power shoved them into the seat so hard that they felt like they'd been kicked in the ass by a freight-train." THIS is what I heard years ago. Almost to a word. Juggernaut wasn't a play on words for their pilots. I don't really believe it will be modeled this way, with "field fixes" included, but I can hope. I'll tell you this, though - if it is a given to us as a tub that can't take a hit, I'll go away. The Mustang model suffers from problems that are not being addressed - and I'll not run the Jug for long if it's discovered to have some silly-assed concessions to playability against the Hun.

I wonder how it will affect Axis aircraft? Detonation in general comes on more quickly in a hot engine. Unless oil is used as a jacket cooling medium, it isn't as important as water temp. Water-cooled cylinder heads will develop hot spots that are hard to cool when the red line is flirted with. Speaking from my drag racing days, I'll say that I hope this leads to some better fuel. Going to suck hard being a hot-engined pony driver. Methods to getting detonation under control: Opening the cooler door manually. Automatic control can lag. (Slows the aircraft, though) Enriching the fuel ratio. Will lower performance, but hopefully keep it alive. Clean up the trim. Avoid hard pulls on the stick when heated. Prevention? Stay high, and fight high. Come down for A2G and to bounce some Jerry can. This last week, altitude missions were a cool engine's dream. Let the Hun come to you if he wants to tango that bad. (We really need some bomber escort missions....)

I get 60-62 in SP. 47-52 with a busy screen. In MP I get 40ish, and it can drop to 30 something. 18 if really busy. BUT, I'm a Core 2 Duo at 3.0ghz, 6GB ram and a GTX-750TI SC. I think you have some system settings issues. Doesn't sound much better than my underpowered rig. Anything else running on your machine? Driver settings set to make sense? Can you benchmark it?

Politics (and sales pressure) being what they are, I wonder if the 109 will ever get to where it should be. I think those saying the 51 drivers are whining too much would start their own symphony of complaints and walk away to play something else. Bad for Eagle...... Personally, I think the G would have been a better airplane for our gaming purposes. A lot of griping would have been prevented. I do believe the 109 and 190 are over modeled for advantage. But, I'm no expert, and have to fly what we are issued. The Jerry can be beat - with the right tactics. Speed, position, altitude. Have any two of these and you stand a great chance of winning. BUT YOU HAVE TO MAKE YOUR SHOTS COUNT. I try to kill the pilot each time.... In a recent MP session, we were at 8K waiting..... waiting..... and eventually, a few came up to play. Up there, I experienced no overheating, lots of power, better performance overall. It was as if an upgrade were sneaked in while we all slept. Whole nudder ship. The Jerrys had a more difficult time with it. ::shrug:: It is what it is.

As with killing a man, it is shot placement that matters. I'm sure the DM could use tweaking.... it's a sim after all, but placement (and its role in the DM) are important. If nothing vital is hit, don't expect massive damage. Cannon shells with crush fuses have to hit sufficient structure to detonate. Even if it hits this, the explosion has to happen near critical parts. 1 shot kills. Damn. You'd think we were talking USMC Scout Snipers....

Been keeping some speed in reserve. It's possible to start a climb after a Dora and force him to stay vertical. If I go into it faster, say using WEP on the down leg and then following a climbing Dora, I can close the gap in the vertical, and still get a tag on him. Takes a good D pilot to pull out of that and get position. Fight to your ship's strength, and land punches when it really counts.

I made a few adjustments to the Options in-game settings. Clutter to 0 Trees vis to 6000 Preload radius to 75000 Shadows to low. All my tests are with the P-51D Instant Actions, "Free Light over Poti" My method is to bank right and pitch down till I'm just right of city center, and pull up with a left bank to that I get a lot of ground filling my screen, buildings, trees, and some sky. I starts at 63 FPS now. Drop to 52 on approach and feet wet, and stay above 42 and as high as 50 on over flight. It's a bit of a let down to drop my preload radius, but I must keep in mind my system's limitations. I run a 3.0ghz core 2 duo.... slow processor, and since DCS runs one core for game play, this hits me. GTX 750Ti SC, which hates overclocking further, by the way. Based on Mack's studies and examples, screwing with the GPU doesn't help much anyway. CPU is the key, here. 6GB RAM, with 2 taken up by security camera software running concurrently. I'm good where I am. Hope this helps.

I just watched the first 3 videos from Mack, and they are EXCELLENT. I'm not anAMD user, but he showed how DCS setting adjustments can help with micro stutter and frame rates. Some of what he tested, I've already done. Going to try a few more, such as limiting shadows and tree distances.

Thanks Tiger, that's what I needed to know! You're a pal. :thumbup:

A question regarding upcoming P-47 and Spitfire modules.... How soon after they are offered for sale will they be on the DoW servers? Does each mission need to be modified to allow them, and is that a headache to accomplish? I'd love to have "Hun Hunter VII" on the nose of my Jug. :music_whistling: or "Bury Jerry"