Jump to content

SmirkingGerbil

Members
  • Posts

    580
  • Joined

  • Last visited

Everything posted by SmirkingGerbil

  1. Thank you Graf! You have shared a lot of knowledge about this warbird, and I appreciate all your input on various topics.
  2. Schwarzfeld, Thank you so much for this. The diagram you sourced is the best one I have seen to date, and I have researched this "exhaustively", pun intended! Your explanation is one of the better ones I have seen, and parallels what I have learned from other sources. Hopefully I can return the favor, here is the pressure switch (regulator) that achieves this function. A combination of hydraulic, boost lever, and evacuated bellows working together. One question if I may. A few sources indicate the Supercharger (Blower) is two stage, yet I can find no detail on gearing changes, or other mechanisms to change the ratio of the blower drive. Do you have any insight as to whether it is only a geared coupling with no ratio (gearing) changes and is only single stage? If it is two stage, do you know how the gearing ratio's were changed? Thanks for your write up, very informative!
  3. All, Thank you very much for your input. I really appreciate this. Based on the MFD and stick commonality, I am going to focus on the F-16, understanding it is not feature complete, but I am an original Kickstarter for DCS Warbirds so patience is one of my strong suits! Also, as I notch up on the F-16, will branch over into the F-18 more than likely anyway. Thanks for your time, detail, and suggestions.
  4. I am an A-10C and II guy. My main module and experience. All modes pretty competent. Weapons employment, usage of TGP, CDU, waypoint modification, weapons profile tweaking, radio setup, working with JTAC etc. Full TM HOTAS system, pedals, and I enjoy using JTAC too in single player. I have even suffered through AAR - but so far PIO is my nemesis. But, I want to branch out. Use my A-10CII knowledge to "ramp up" in another module. Main interest, something that has decent ground attack but mainly reach to deal with long range REDFOR Anti Aircraft missile systems. I have the Harrier (lots of love lately), the F/A-18 Hornet, and the F-16. I haven't really flown any of these modules to any degree except the F/A-18 and probably only 3 hours in it. Which of those three would allow me to feel at home so to speak, and use my A-10 knowledge overlap to get up to speed fairly quickly from the communities perspective? Not worried about BFM and BVR engagements (that can come later) more focused on ranged/weaponry to deal with REDFOR AA missile systems, and shipping as a nice second. I have a lot of pent up anger as a Hawg driver in regards to REDFOR missile systems, anything "SA" needs some payback - time for me to branch out! Thanks in advance.
  5. I have even popped some fasties with my AIMs. We are kinda like snapping turtles. Slow, and easy to get around, but get too close and BAM, jaws of steel clamp on and don't let go! Very True @Pikey
  6. https://www.thedrive.com/the-war-zone/38894/fighter-pilots-reveal-why-you-dont-want-to-mess-with-the-a-10-warthog-in-a-dogfight
  7. Nine, A before and after snapshot. Included a frame grab of my graphics settings. A-10CII test runs. Syria. Also, autoexec.cfg is set for true to disable hotplug per other threads. Latest OB as of this date. Running latest NVIDA driver for 460.89 for "Creator" - but I have also experienced this with 461 on this Beta version. The graphics settings are my "middle range" that I run for Syria. I run higher, almost everything on max, for maps like Caucasus, NTTR. The Channel I get some stutter, as well as Normandy with higher settings. Persian Gulf almost none, for any settings. Syria is a stutter fest - but only after I have had a few runs without deleting the FXO and metashaders2 folder. This is a run (current log file) after a real mess of a run with old log file included. The difference is night and day. I do the same test, and same sequence of events to reproduce. Load Syria A-G mission (stock in game, and selected from Mission) I fly to Aleppo, and do a city low level run around the ruins. I have modified this mission for personal use. The only change is time of day, dust, and clouds. This flight, after deleting folders, very smooth, only a few stutters, much much easier play and enjoyable. Old backup file is from my last attempt doing the same thing before emptying folders. Unplayble. Frame rate is the same in both instances, I never drop below 39 FPS even doing street level in Aleppo - but the stutter is atrocious before emptying the folders. Similar affect, but not as pronounced on The Channel and Normandy. NTTR and Persian Gulf not as much. Caucasus better than most maps, under any circumstances, but will get some stutter over time between folder deletes. Also, when stutter is bad, flipping up mirrors will give me about 5 FPS, and putting the TGP in standby will give me a solid 10 FPS increase; however, this still doesn't reduce stutter when it is at its worst. Hope this helps. dcs.log dcs.log.old
  8. Thanks for all this! I will say one thing about the P-51 with "ground loop" on take off (if that is what you mean). I discussed this effect with my wife's Uncle who works for the FAA, and also a crash site reconstruction expert. He rebuilds Luscombe's as a hobby. He recounted what he knew, from a friend that flew the P-51 in WWII (This was several years ago, when the P-51 first released), and he told me how to set the rudder trim, and other surfaces for take off. From that day forward, I never "ground looped" into the dirt again. Not saying that the effect wasn't too exaggerated on release, but I always found it fascinating I could describe the aircraft behavior, and a pilot, that knew a pilot who had heard of how he dealt with it in real life, and viola!! It worked for me. After that, I found new respect for our friends at ED and DCS, may not have been on the mark, but it was close enough that word of mouth allowed me to fly it and not flip right into the dirt on take off.
  9. Similar to what I have done before with the stock Caucasus DCS mission, slightly modified, time and weather. Plus no in game menus - all Voice Attack Driven. Tutorial? No intended to be one, but you can get a feel for the ebb and flow of Waypoint creation, and interaction with JTAC. I do miss a couple of cues, as noted in the video.
  10. Black Shark 2, A10C, A10CII, F-16, F/A-18, F-86, Mig-15, Mig-21, P-51, F-15, Su-27, Su-33, Mig-29, FW-190 Dora, Anton, BF 109, Normandy, Caucasus, NTTR, Persian Gulf, Channel, Syria, WWII Assets, CA. (WWII backer picked aircraft ME-262, P-47D).

  11. Good news! I do try to not end up with many overrides in NVIDA panel settings, but VSync is one of those things that can cause issues in DCS. I only went with "Fast" as it seems to be a good compromise depending on how high you set your resolution in-game. That said (as I have done this rodeo many times with DCS since 2012 ish) - the next update, for us Beta folks, may cause the issues again for some other reason. Such is the fate of Beta, but I don't bemoan it too much as this is the life we choose in Beta. Since last update I have had to modify by autoexec.cfg due to device scanning stutter, and moved my track-ir to a dedicated port as when I fire missiles etc. Stutter was through the roof. A few changes, all is good. I expect next Beta it will be back and I will have to fiddle with it again!!
  12. Caldera (Yellowstone or bigger??!) Sorry for late reply. Busy all week with security issues, Internet/software stuff. I would be hesitant to recommend any video settings as I am a noob, and just looking at mine - they are quite a bit different. A mix of mostly high/ultra with some other settings tweaked in NVIDA Control panel like VSync (Fast) for the game, but off in DCS itself. There are many more experts around here that can advise you on that. My system is kind of Frankenstein so I would be worried I would steer you wrong.
  13. No sir, it isn't normal. When I fiddle with Gain etc. it is the exception, not the rule. An every now and again thing. I only nuke the FXO and Meta folder on updates, I don't delete them every start. Honestly, I am flumoxed as to why you have this recurring issue. Possibly some other external factor like Nvidia settings?
  14. I have used the Panzer IV with other nations. Russia, Syria, etc. in ME.
  15. Caldera, Not sure how many hours you have in the A-10. I understand the drive to "fly like it is real" and it is frustrating to do immersion breaking things, but considering your post with ME and player controlled vehicles, I would cut yourself some slack here and do active pause. I only mention this, as I routinely fiddle with the gain etc. when needed and still manage to keep targets in my view, and locked, but I have a lot of time in the A-10 since about 2011/12 ish, also in the KA-50 from that time frame, so this kind of interaction and speed takes time to become second nature. Plus I have have the TM HOTAS, and it is second nature to put the A-10 in a large circular orbit with my TGP facing the bad guys. Plenty of time to fuss, fiddle, and still shack them. If you know all this, ignore, if any of it helps, then use it. Lol, I just saw your post, and I mentioned the same thing to him. Great minds . . . Yeah, going into orbit around a target to fuss and fiddle before run in is second nature now.
  16. All, maybe this is known, and I am in way over my head here. First thanks for all this information, very helpful. I have found though, that by selecting either BHOT or WHOT, and then adjusting Gain, or the Levels (found on MFD left hand side of TGP display), you can alternatively worsen or remove the effect of total occlusion. Meaning I jack with the levels until I can get a clear image through smoke. Guessing you guys have already tried this, therefore ignore. If not, give it a whirl. I know it means dinking around with knobs and dials, but it gives me consistent repeatable results, meaning I can eventually get a clear picture through a destroyed target and not have the sensor blinded by the IR intensity of burning wreckage/smoke.
  17. Alright, that seals it. When Yo-Yo weighs in, concurs, but also elaborates on how the forces are balanced against different sources of cylinder pressure and explains that one being out of sync or outside of nominal conditions, then you will overload the main/master bearing during hard windmilling and low throttle. I am going with this. Thanks everyone for the time and detail, fascinating and learned even more about my favorite Warbird.
  18. Well, that's helpful. Two diametrically opposed descriptions, and one that explains something in between. Guess I just need to slam the throttle to zero, do dives from 15K feet one after another, and see how many times I destroy the engine?
  19. Thank you sir, magnificent and easy to understand. Now I get why pulling the throttle back too far on a steep dive to compensate for engine torque (nose wobble) can lead to damage or worse. As to all the other posts regarding how the P-47 handles. Yeah, when I mention torque exclusively, I figure most folks would understand you must have dealt with all the other pitch and roll axis, just like any other aircraft. I fly the 47 with a short stick, and regardless of any OB patch, once you get a feel for the influence of torque, trim (axis), throttle speed, and engine settings you can easily hands-off fly this bird all day. Short stick, long stick, or tuned curves. The 47 can and does fly like a dream hands off. Smooth and trouble free.
  20. Gotcha! Probably more relevant now with the last update that included bearing damage. I will do a few bomb runs with "old habits" and see what happens. Makes sense, thanks for updating me!
  21. Zero-ish?? better to explain I pull it back till the nose goes where I want, probably more typical to be half throttle. Sometimes it is nearly zero; however, if it did go back to zero, I have had no ill effects - I am curious what should or could be the repercussions?
  22. She will spin easily due to the torque, always to the left (will pull nose to left, this causes nose wobble for some pilots on landing and hitting power to suddenly), especially during hard maneuvering and hard fire-walled throttle with Water Injection. You can lessen the this by rolling back on the throttle, especially as you bleed speed. I know this sounds counter intuitive, but to hold the throttle hard forward as you go into a climbing stall or hard G turn and you drop below 200 will almost certainly result in a flat spin of some kind. Ironically, very easy to recover, just pull the throttles back, and counter the spin with your rudder, and once you hit about 180 knots, she will line up straight and you can roll power back on. Very easy to recover from these erratic spins induced by the monster torque of the R2800. You can steer the nose of this plane on gun runs just by working the throttle to get lined up on the target.
  23. This is the Army Air Corp technique, that is recommended. I picked it up off of a video or post by 9line or Wags. I go to 8K+, nestle the target between my starboard leading wing edge and my cowling on the P-47D, roll in. Deploy anti-compression slats (bad habit, but works for me), pull the throttle to zero, and line up the nose K-14 gun sight on the target as I drop. You should have no stick input (nice and neutral, no forces on the bombs), the center dot should cross the target, then you let it drop to the 40 mil line, pickle!!! at about 1K feet or a little less, back on the stick hard but not jerking and panicky. hit the compression slats, and level out. Works like a charm, I hit about 80% of the time now.
  24. I own all the modules listed here, then some. I primarily fly the A-10C since 2013 ish. I just picked up the F5 for all the reasons you mentioned. Agreed on all points.
×
×
  • Create New...