granola1861

The R2800 has a supercharger so it should be capable of reaching 52" at sea level. I've read some of the manuals for the 47 but had missed the part of setting the turbo prior to increasing throttle. Makes sense as the B17 had a turbo dial and the throttle would go to max power and the pilots would "dial" the turbo for the appropriate manifold setting.

I may have put the wrong pressure on my post. I'm having issues even making 52 inches. Seems to stop rising around the low 40's. Not a problem with a light load but with ordnance it gets to be an issue.

Please correct me if this is accurate but did the Jug need turbo to make 61" MP at sea level on takeoff? I'd figure the supercharger could handle that much as sea level. Makes for an interesting takeoff run as the turbo kicks in about midway down my run and kicks the pressure up to WEP levels and I have to reign in the throttles to keep her near takeoff power and not nuke the engine. This is especially troubling since I'm having to go ahead and takeoff without the oil temp in the green (I see that issue has been already reported). Love the jug and she flies like the Cadillac she is known for. Good initial launch by DCS and hopefully these issues (numerous but small overall) will be addressed soon. Thanks in advance -Climber

I keep tripping the CB for the cockpit lighting. I'll notice when my oil pressure gauge drops to 0 and have to reset the breaker. It seems that cockpit lighting plus any additional electrical pull will trip it. If I turn on minimal electrical then it seems to solve it but have to wonder if this is accurate. FYI: I do have the generator on and it seems to happen even at higher RPM when the generator should be making appropriate power. I can understand too much pull when the generator isn't making enough power with a low idle engine but this seem excessive.

The temperature will not change from 0 deg C in the ME. I tried flying the Jug in a created mission and I seemed to have difficulty getting the oil temp into the nominal which is important for that engine. Thanks much,

How about having the ability to halt civilian traffic in a user defined trigger zone? This could add to the realism of having civilian traffic but none or even diminished traffic in a zone where battle is occurring and would also prevent traffic from interfering with units travel by roadways. Thoughts? -Climber

Now that the Anton is out of early access we have a whole bevy of new ordinance. Can someone help by going through the different variations and shedding some light on their respective descriptions/ capabilities? The encyclopedia isn't up to date and the flight manual isn't particularly helpful. The differences in SD250, SC250 and the suffixes for example. Which are cluster munitions, ship busters, bunker busters etc... Thanks as always, Climber

Now I have to read??? First off thanks for the quick response in getting the update done. I'm having issues with hearing other comms (ATC, wingmen, etc). I had things setup to hear my comms in my headset. I get the VA beeps (static noise) when I issue a command and responses are correct - on screen messages only. I'm not receiving any voice from ATC or my wingman. I've experimented with a variety of settings both in game and VA but nothing works. I can disable the redirect settings but then all is through my main speakers not my headset like prior to the recent updates. It seems like the comms coming in from DCS aren't playing when VA and redirect is active. I'd really like this to occur like before. Hopefully this helps with future updates. Again love the product and the immersion it provides. -Climber

Logs attached FPS dropped to severe stutter then hard crash. dcs.log-20200215-213408.zip DxDiag.txt

At the least maybe add a revision change list to this. That way when it’s opened readers know what to look for in changes.

I got it figured out. When it was first released I couldn't get it to work and now it works correctly. Finally getting some of the fiddly bits worked out on my controls settings for the viper. Thanks for the assistance as always everyone. -Climber

I appreciate the quick reply. I’ve never tinkered with changing setups that way but will try. Does anyone know of ways to get the existing in game hotas settings to work?

Sorry if this has been covered but I'm having issues setting the TM Warthog Idle detent for the viper. I can set it to return from idle to off but not the other way around for startup purposes. It works for other aircraft (hog, tomcat, hornet, tiger, etc) probably an easy fix but I haven't found it yet Thanks in advance folks. Climber

I'm having issues with getting Comm 2 to work on the F16 module. I can get the static beep showing that i have control of comm 2 but it doesn't register that I've said anything. If I use Comm 1 the correct button works and the command is issued and comm 1 "UHF" lights up in the cockpit showing it is in use but not for Comm 2. I've even pulled up the viacom window and the TX 2 (assuming that is the correct place for Comm 2) but alas not working. Am I doing something wrong? thanks much in advance.

So Wags recently posted a glimpse into the future of carrier comms. What are the chances of somebody adding these to the DCS voice attack profile for download? I may be able to do it on my own but not sure how to go about it. Thanks

So FYI I've set my ram frequency back to Auto in my bios (not sure why I made that change in the past) but haven't had any crashes since. I've ran some of my missions (sp) even the ones that were previously causing nasty crashes that were once taxing my system and not had any more crashes. Crossing my fingers that I've fixed the issues. I've kept the pagefile settings mentioned in other threads (32x1024) with no ill effects. Hopefully others can get a remedy soon as well. Thanks for the assistance and happy flying! -Climber

I had a stable flight last night (first in weeks) after setting my RAM frequency back to “auto”. I’m hoping this is my fix but further testing will tell. That may be something to check and see if it works.

Well I've upped my power supply to 850 watts and still getting same failures. Of my recent crashes DCS has not given me a crash report, so nothing to post here. I've attempted to post to the Fight-TDR-bug issue but DCS crashed with that change. Currently DCS is un-usable in this configuration. Hopefully a fix will arrive soon...

I’m running a 650 w power supply and pretty confident my graphics card is plugged in correctly. Could my power supply be a bottleneck here? I figured it would be robust enough since I’m not running dual cards or other power hungry peripherals. I could upgrade to a 750 or 850 but not unless I’m more certain on the limitations of my 650. I will check out the sticky on the recurring bug that seems eerily similar to what I’m seeing. At the very least I can provide some data to that study. Thanks much folks I really appreciate the assistance and hope I can get some resolve soon.

Having continual crashes. Made some settings changes and even upgraded CPU and motherboard thinking that could be my bottleneck. Seems to be more persistent. dcs.log-20190410-140737.zip dcs.log-20190411-000328.zip DxDiag.txt

I've tried that will go back and try again

I know I shouldn't rely on labels but I still use them, so sue me! The latest beta update with the label changes have left the option of turning labels on or off nonexistent. Cant use Lshift F10. I've had to go back into my own missions and re-check the label box. Can we get a campaign update with this box checked? Thanks much

M2000c Mission: French Red Flag I'm attaching a mission titled French Red Flag. You are tasked with flying BARCAP for Blue Force attackers. Read the Situation and Blue Force notes in the briefing for details. This is a pretty basic mission that I made and I think it is lots of fun. Lots of Mig-29's to kill, other flights doing their thing, tanker (if needed) and good scenery. I can usually survive 50% of the time and that is only with icons on. I'm psyched to hear of somebody surviving without icons. Give it a shot and let me know what you think. I'm not opposed to changes being made to this mission I only ask to be mentioned as the original creator. Best and enjoy! -Climber *edit* Something I just realized that I left out of the mission notes. Texaco is on TACAN 11Y ....I knew I had forgotten something.... French Red Flag Public.miz

So I figured it out. Something I should have done from the start. The BFVG Farp mod was keeping the doors from opening. Removed it and all is well now. Back to the campaign again!

So I finally figured it out!! :D The BFVG Farp mod was keeping the hangar doors from opening. I should have disabled mods first before going on the hunt for internal issues. All fixed now.