SmirkingGerbil

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!!

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.

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?

I have used the Panzer IV with other nations. Russia, Syria, etc. in ME.

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.

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.

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.

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?

Oh. My.

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.

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!

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?

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.

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.

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.

Yeah, I emailed IIya as the first drop (P-51) had some install issues, and we interacted for a bit before he went dark. Have been through this since the beginning. Very grateful for what ED did . . . which is why I kinda shake my head, and give rage posts about these developments a bemused smile. It will come, when it comes, and the P-47 will keep me plenty busy in the meantime.

This happens off and on for me, usually because roll axis is simultaneously assigned to my rudder pedals. If you go into control menu, select A-10CII Real, and select axis, you can check your Stick along with Rudder Pedals if you have them, and check if they are not dual bound to the same axis. I know you mentioned repair etc. But this little problem still crops up every now and again for me, now I just check it first.

Well, since this is from the AH-64D cannon, I figured apropos to this post, and the 2021 leak vid! Another round for scale.

Oh, nice catch!!! That must have been it. I totally overlooked this, pretty sure you are right, because I manually added the last two modules today (F-16 and A-10C not the II), and the files shows modified at about that time, with these two listed last. I just recently did an entire new download of OB, only manually downloaded the few files I mentioned as recognized, then copied all my other modules and terrains over from the "junked up OB" that I have drug around for years. This explains why when the new OB dropped literally the next couple days after I did this, the autoupdate.cfg was only referencing those few modules. Now that I have manually added all of them, it is up to date. Thank you! I feel stupid for missing this, but the light bulb just went on, many thanks! FYI, this clean install netted a noticeable improvement for me, as recently using the TGP would ding me for 10-20 FPS in the A-10CII, so I did a new OB download, and clean install earlier this week after the big OB drop, but before this small one. Probably more detail than you needed, but my OB install was several years old and cluttered up, so during the fresh install, I missed copying the autoupdate.cfg file! Again, many thanks, good find!

@Rudel_chw, thanks so much for your advice, I managed to fix it before I saw your post, as follows: Out of curiosity I did a command line re-install of one of the affected modules i.e. "I:\ED_OB_Clean\DCS World OpenBeta\bin>dcs_updater.exe install MIG-29" - I then ran OB with latest patch, and this module was available. So I went line by line by line for every module and terrain I own (about 26) and after each install run, they worked. In each case they would download anywhere from 4M, 8M or a few times about 39M and after each instance, the module was available again. The only module I am having difficulty with is the F-16 as I cannot seem to find the syntax for the install command line name, none of the variations I have tried work for me. I just ran a few modules, on different maps, using built in, and missions I have created, including mods installed such as the VIRPIL NATO airfield objects, and everything is working now. Not sure what happened, but it "seems" like when I updated with today's OB patch, it only did the core modules, and didn't hit the bulk of them. Running each module manually seemed to fix it. Appreciate your response . . . hopefully this information is helpful.

I am authorized, I can log into my account. All modules show as activated. After I updated to this OB, all my terrains are unavailable except Caucasus and Nevada. All my aircraft modules are un-authorized, except A-10CII and P-47D. I will attempt a repair and report back. P.S. - did both a quick repair, and full (slow) repair, same issue, 80% of modules disabled. Log files from both repair attempts: 00000.076 --- Log file: I:\ED_OB_Clean\DCS World OpenBeta\autoupdate_log.txt 00000.000 === Log opened UTC 2020-12-23 19:28:34 00000.020 INFO : DCS_Updater/2.10.6.63 (Windows NT 10.0.19041; Win64; en-US) 00000.020 INFO : src-id: baf92d0a5bb967be5dcb68784e54459d083e8c3d, lib-id: bae3744c50d64647d7c5ee5a1236d3ae42dbbb1e 00000.020 INFO : cmdline: "I:\ED_OB_Clean\DCS World OpenBeta\bin\DCS_updater.exe" --apply repair 00000.074 STATUS: Initializing... 00000.075 INFO : basedir: I:\ED_OB_Clean\DCS World OpenBeta\ 00000.075 INFO : dcs_variant.txt: openbeta 00000.077 INFO : DCS/2.5.6.59625 (x86_64; EN; WORLD,A-10C_2,P47D30,WWII-ARMOUR,NEVADA_terrain) 00000.077 INFO : branch: openbeta 00000.077 STATUS: Connecting to update servers... 00000.630 INFO : Got reply from www.digitalcombatsimulator.com 00000.806 INFO : Got reply from www.digitalcombatsimulator.com 00000.809 INFO : Showing the repair mode dialog 00016.377 STATUS: Verifying cached version info... 00016.833 STATUS: Verifying installed files... 00024.452 INFO : 0 files are changed or missing. 00025.833 STATUS: Preparing download... 00025.838 INFO : To download: 0 bytes in 0 files 00025.838 STATUS: Searching for already downloaded files... 00025.840 INFO : Found 0 local source(s). 00025.840 INFO : To download: 0 bytes in 0 files 00025.886 STATUS: Removing obsolete files... 00026.037 INFO : Removed 0 files. 00026.390 INFO : Kept 43773 files. 00026.390 INFO : Nothing to install. 00026.409 STATUS: Installing runtimes... 00027.885 INFO : distr/vc_redist.x64.exe succeeded with code 1638 00028.037 STATUS: Scanning for extra files... 00051.764 STATUS: Cleaning up... 00052.292 STATUS: Successfully repaired version 2.5.6.59625@openbeta 00054.782 === Log closed. 00000.000 === Log opened UTC 2020-12-23 19:30:42 00000.020 INFO : DCS_Updater/2.10.6.63 (Windows NT 10.0.19041; Win64; en-US) 00000.020 INFO : src-id: baf92d0a5bb967be5dcb68784e54459d083e8c3d, lib-id: bae3744c50d64647d7c5ee5a1236d3ae42dbbb1e 00000.020 INFO : cmdline: "I:\ED_OB_Clean\DCS World OpenBeta\bin\DCS_updater.exe" --apply repair 00000.075 STATUS: Initializing... 00000.076 INFO : basedir: I:\ED_OB_Clean\DCS World OpenBeta\ 00000.076 INFO : dcs_variant.txt: openbeta 00000.077 INFO : DCS/2.5.6.59625 (x86_64; EN; WORLD,A-10C_2,P47D30,WWII-ARMOUR,NEVADA_terrain) 00000.077 INFO : branch: openbeta 00000.077 STATUS: Connecting to update servers... 00000.632 INFO : Got reply from www.digitalcombatsimulator.com 00000.825 INFO : Got reply from www.digitalcombatsimulator.com 00000.828 INFO : Showing the repair mode dialog 00007.128 STATUS: Verifying cached version info... 00007.582 STATUS: Verifying installed files... 00284.846 INFO : 0 files are changed or missing. 00286.226 STATUS: Preparing download... 00286.232 INFO : To download: 0 bytes in 0 files 00286.232 STATUS: Searching for already downloaded files... 00286.234 INFO : Found 0 local source(s). 00286.234 INFO : To download: 0 bytes in 0 files 00286.280 STATUS: Removing obsolete files... 00286.431 INFO : Removed 0 files. 00286.782 INFO : Kept 43773 files. 00286.782 INFO : Nothing to install. 00286.802 STATUS: Installing runtimes... 00287.306 INFO : distr/vc_redist.x64.exe succeeded with code 1638 00287.711 STATUS: Cleaning up... 00288.244 STATUS: Successfully repaired version 2.5.6.59625@openbeta 00539.862 === Log closed.

Voyager - bad habits! My bad. Carryover from my A-10C - I deploy them just to slow things down - but of course for all the wrong reasons. I need to stop doing this, and thanks for pointing out. I haven't really noticed easy rudder damage - but I have noticed bearing, and overheating damage if I don't pay attention to the temp gauges, which is a must, because I will lock the turbo with the throttle, and use the Water Injection off and on. Overall still very happy with the outcome and the latest updates . . . but that is not to say I am missing some things others might observe or pick up on.

Yeah, I love the new cockpit, and all the updates, but that stipling/button pattern in the APU gauges from the CDU drove me nuts the other day. It was all I could see once I noticed it.

Thank you. I understand, business needs change. I very much appreciate the forthright answer. Hopefully, at some point, focus will return to this module. In the meantime, I will enjoy flying the spectacular P-47D, and other modules. Regards,