Search the Community

Hello! I have noticed that there is no difference in fuel quantity between 50 gal and 100 gal external tanks. Both types take same amount of time to deplete before outer tanks get into play.. I checked flight manual- Fuel System section, Cruise Flight and Limitations section. Nothing mentioned there about it. Am I doing anything wrong, such as flying above certain altitude or is it just pending bug? Thank you for help.

When you have a PDLT selected and have the PDLT mnemonic highlighted in the 2nd HSD Control page, the HSD should automatically increase (NOT decrease) the range when it's outside of the display, currently in DCS it does not do that, neither when you toggle on/off the PDLT mnemonic in the HSD control page. Steps to reproduce: 1. Select PDLT on HSD 2. let PDLT get out of range, HSD will not increase range regardless of PDLT mnemonic. Track attached HSD PDLT not range bumping bug.trk I can provide evidence in PM if required

South Atlantic map, multithead.

The HDU rocker switch for CONTRAST DECREASE is not working with keybind if you click it via mousebutton , all is fine. If you use the keybind, it won’t work. All other Rockerswitches are working fine on the hdu

Text just got deleted for no reason... D-28 and D-30 panels. Why do we have a D-30 early in game? It should just be a D-30 with a reflector sight. Also, no backup sight? No bomb release switches? This was from WIP, what happened?

2 issues: -When changing the HARM WPN display to POS mode, it appears to lose SOI -When switching SOI from POS mode to the HSD on the other MFD, the first depress of DMS aft doesn't work it requires two depressions of DMS aft. It may be in an in-between state. It IS possible to make the display SOI so that the HOTAS commands work on the WPN page for POS mode, but it won't have the box around it. Switching back to HAS mode can put the box back around it sometimes, the box definitely comes back if cycling SOI between MFDs once back in HAS mode. WPN_HAS_POS_MFD_SOI_switching_and_no_box.trkTrack attached. There are no mods installed on my F-16, full integrity checks pass for multiplayer on my install. Short video:

Changing tables on the HARM HAS page was updating the emitters on the left, but not the table number on the top. Switching to POS mode doesn't switch properly, and the emitters remain on the left causing a display issue. Track attached. HAS_MFD_strange_display_behaviour.trk There are no mods installed on my F-16, full integrity checks pass for multiplayer on my install. Video showing the issue:

In the Viper, having no weapons loaded, the Air To Ground radar is not available in A-G mode. I cannot select AGR modes. I can select those modes in NAV mode, but won't see a diamond in the HUD for whatever targe i lock with the AGR nor the TGP.

This one is pretty simple... On Vehicles with Machine guns Vehicle with less than a full belt of machine gun ammunition Press Reload Goes into reload sequence Vehicle doesn't actually reload anything On Tanks Press Reload on ready rack- Goes into reload sequence Doesn't reload the ready rack

In DCS 2.9.2.49940 the DTT scan volume is not being centered on the secondary non-bugged target, it should behave per the following: In the attachments the track shows a scan volume centered about the FCR cursor (which is correct only for SAM). I have a screenshot below showing the incorrect scan volume centering aswell. EDIT: You guys might have different info based on new documentation, but it's really difficult since I don't know what info ED has which I don't. It isn't really transparent. DTT scan centering bugbug.trk

Hi, I've recently finished mission 14 which I must say, was one of my favourite missions I have flown in a DCS campaign, head on a swivel for more than an hour. However, I was running on fumes at the end because bucket refused to give me more than 500 pounds at both the ingress and egress. In both cases Olive tanked first and got her 3k, and I was left with only 500 or so. He then retracted the basket, and disapeared from the comms menu.

Crossposting from the Heatblur forums because this might be an SC issue rather than a Tomcat issue. Track file and video in linked thread. Basically, the player aircraft has a shaking glitch when shot off the cat, and the shaking continues even once off the deck and airborne for a couple of seconds. This does not occur with AI, and for some strange reason it does not occur on night launches either. Also in the attached track, you can see the holdback bar doesn't drop, the two white-shirts by the JBD are stuck in their crouched position, and the shooter is later seen stuck in the runup signal.

I wanted to do a bit of research with regards to the Curtiss Electric prop as modelled in the DCS P-47 modules in order to ascertain what is going on with the blade angle limits, and whether or not the behavior of the automatic governing vs. manual RPM adjustment was correct as we see it in the sim. As modelled currently, the governing range of the blades in the automatic mode reach their limit at 48 degrees coarse. Yet, by going into manual mode, you can further coarsen the blades to ~88 degrees -- what would be considered feathered. But this does not make sense for a single engine installation. I suspected that maybe the devs had erroneously modelled propeller limits for a multi-engine installation of the Curtiss electric prop and set out to understand how the limit switches (analogous to mechanical high and low pitch stops in a hydraulically actuated prop) function and how they should be configured in a P-47. For this I started out referencing the P-47 series Erection and Maintenance Instructions handbook (AN 01-65BC-2) 10 August 1944, revised 15 December 1947: As you can see, the depiction of the limit switches (mounted on the aft portion of the power unit, which also contains the electric motor) specifies three limit switches: Low angle, high angle, and feather angle. It is important to understand that all Curtiss electric prop installations have these switches as the props can be fitted to many types of aircraft. Indeed, some installations would be for multi-engine aircraft (eg. the B-26), where a separate feather limit would be needed. If one were to look at the wiring diagram for the control mechanism, and also if you read the user manuals for the Curtiss electric props, you can see and read that while the manual increase RPM switch uses the same circuit as the automatic governor, the manual decrease RPM switch makes use of a separate control circuit, one that doesn't pass through the high limit switch, but instead the feather limit switch (follow the yellow line): Indeed, in the generic Curtiss prop user manuals, it mentions that pilots can manually decrease the angle all the way to feather limits (albeit, at a slower rate than using the dedicated feather control on a multi-engine installation) if they use the manual RPM decrease control. One must remember that these manuals (you can check one out here for yourself) are made to encompass general usage of Curtiss props across several types of installations, and so are a bit ambiguous in specifying whether this feature works for a single-engine installation. If this was all there was to the story, the DCS modelling is correct as is. However, we also have this description of the limit mechanism: It mentions that the switches are tripped by cam segments mounted onto the ring gear. It turns out that how those cam segments are mounted, determines when exactly the switches will be tripped. How should they be mounted in our P-47? Which Curtiss electric prop models are installed on our P-47s? Here's what the Erection and Maintenance Handbook says: As you can see, we're already getting some hints about prop pitch ranges, but seeing as how we've got specific models listed and they all seem to be variations of the C542S-A series, let's take a look at that manual: There's a ton of information in here about installation, disassembly and description of components, but we're interested specifically in those cams: Here's the diagram, parts labeled 7-11 are the cams that determine when exactly our limit switches will trip. Notice at the bottom, we've got a note about blade angles?? Hey, we may be getting pretty close here. Let's have a look: Here, I've cross referenced all the specific model numbers listed in the P-47 Erection and Maintenance handbook, and you can see that for each of them, the High and Feather limits are exactly the same -- this means that a manual decrease of RPM should result in the same blade pitch governing range as the automatic mode. But why is our high/feather limit different than what we're seeing in game? To shed some light on this, here's a technical order from June of 1945: As you can see, at a certain point, blade angles were increased (the procedure involves moving those cams by 5 notches towards a higher coarse limit). There is still a discrepancy between this technical order and the curtiss prop manual, but I am assuming that is because the curtiss manual is 5 years more recent (1950). The one thing this does seem to prove, though, is that in all instances the curtiss electric prop installation on the P-47 had the same coarse pitch limits, whether governing in automatic mode, or set manually with the decrease RPM switch in fixed pitch mode. Also worth noting is that the increase limits in the technical order were done to help prevent engine overspeed in high-speed dives. Lastly, would like to reiterate the fact that, as others have mentioned multiple times on this forum, that the allowable engine overspeed limit in the P-47 pilot manuals is listed as 3060 RPM, probably owing to the fact that you WILL exceed the RPM redline in a dive at high speeds with any power applied: I believe getting the proper blade angle limits implemented would be a great first step on the road to really tightening up the P-47 module. Thanks for following along and I hope the devs really consider taking a second look at this.

picture tells more than 1000 words. raven 4 relief flight does not take off, because the smart tanker collided with them on deck! VERY frustrating experience after i had to restart this mission 3 times already, every time because other reasons. DCS AI really really holds back this campaign. cant count the facepalm moments so far in this campaign in general. like wingmen flying straight into me after kiss off, etc......

As the title states. Using the ED created aircraft carrier mod,. add any prop ai aircraft via the saved games location. Spawn the ai on deck. All looks as it should so far. the deck crew get to the spinning hand gesture, but never finish with the launch gesture. The ai aircraft pops up like it is ready to launch, and sits there, with its engine running. This is the same with any prop aircraft mod. I have not tested and FC3 mods yet. Notice the wheels spawn in the incorrect position? This is new behavior. I changed the wheel location in the lua which fixed that issue, But she still will not launch from the ED carrier. Or any other carrier but one or two. And those are not quite right with strange runway behavior. This is all new since the last few patches. I hope the fix is a easy one! @BIGNEWY The report, as requested. If you want logs, or a mission and / or track, I will supply them. Thanks for the help!

After Twister cleans out the SAMs, Chevy 2 won't break off to go and engage their targets. Also Chevy 2 reports engaging targets once you get to the anchor point, not after twister tells them to do so. So essentially I still get stuck in the same place. EDIT: To clarify. After playing this a couple of times, it looks like CY2 runs one of its triggers too early...as soon as you reach WP3 for the orbit. And after twister has triggered all of its actions, CY2 doesn't have the trigger to run again AND that trigger did not work as intended earlier. Long story short, no action compels CY2 to unfollow the player.

I'm still new to DCS, and I realize there's a 90% (prob higher) chance my issues are user-errors... But, I really struggle to get TWS to behave like the manual and related videos suggest it should. Main issue: I see several Track Targets and from what I read, I should be able to TMS Right to convert all those to System Targets (empty boxes). That does not seem to work any time I've tried. Sometimes a TMS Up with cursor over a Track Target will convert it to Sys Tgt, but not reliably. And I can never TMS Right to cycle thru System Tgts, probably because I never have multiple, even though there are multiple radar contacts. Ad a result, I find myself way behind when I'm in bvr. Couple more questions, including how to achieve DTT, but I'll wait on that. Thx for any help.

I have finger tip laser pointer in ST mode, but not MT mode. I have verified no key binds to hand controllers., no mods, etc. This was mentioned some where else previously but have not seen any verification or acknowledgement from ED. Any help etc. appreciated. MT no Pointer dcs.log MT no pointer debrief.log ST pointer debrief.log ST pointerdcs.log

when in CPG select FCR scan msl selected RF mode sight select HMD game will crash

Wonderful mission, as the whole campaign, but ED seems to like breaking things When RTB, all AI planes were stacked above the carrier, performing wave offs. The reason was a wrong orientation of the carrier, 90° relative to strong winds. Not sure if this is a factor, but I performed an AAR with Texaco on my way back. I know this has nothing to do with the mission itself, but maybe someone has a workaround, cause I'm not skilled enough to snake between the other planes and recover with this crosswinds

I'm having issues with the magnetic compass and gyro heading indicator disagreeing by 15~20 degrees on ramp start, and even after calibrating the gyro heading indicator to match the magnetic compass, after takeoff they disagree by 15~20 degrees again, as if my calibration never happened. The specific conditions are: - cold ramp start - Channel map (High Halden) - mission date April 1, 1944 At first I assumed it was a magnetic declination issue, but the magnetic declination of Kent is a smidge over a half a degree, not 15~20 degrees. The second, and more worrying issue, is that the gyro calibration doesn't appear to hold at all.

The mach gauge below mach 1.0 should show the speed on a scale in 0.05 increments, not in a single 0.5 increment as it is now. It's correct in DCS F-5.

The tail wheel bounce got worse and worse. It's like bull riding. DCS - Fw190A8 - Channel - Spitfire Dogfight.trk DCS - Fw190A8 - Channel - Spitfire Dogfight.acmi

Hello. When spawning enemy AI (F16 & F18) only those two. since DCS 2.9.2.49629 Open Beta using Group coalition.addGroup(enum countryId , enum groupCategory , table groupData ) Only in the dedicated server atmosphere. The SA page in the hornet will show you the Datalink for the new spawned enemy unit, but when you get radar contact with that target, the SA page will not merge the newly radar contact which is now a trackfile together with the old datalink, instead it will show two contacts in the SA page. Just like I mentioned before (after the Link16 update few months ago), when spawning friendly units using the same method, they are two in the SA page, as for the friendly, they will always be shown as 2. Adding them to the member list won't work. Trackfile: https://easyupload.io/1r6t5p Miz for test : https://easyupload.io/acuyki Just to note that these issues, both of them are only related to dedicated servers, everything works perfectly offline. Thanks.

Hornet radaralt.trk Track attached. You can type in the numbers but it still shows 0, even after you takeoff. Only after you takeoff you can input numbers that then are accepted by the system.