TK-421

Any updates on this?

Did anyone test this out? Seems to be a point of confusion with the Mustang.

this is amazing, but it failed the IC today.... *update* deleted the zip file that was in there for some reason, restarted and it seemed to fix it. Honestly man it looks amazing, this should be standard!

is this still an issue?

a screen shot or photos would be great, hard to visualize

bump! atmosphere effects would be cool, it would give a reason to use those controls, as well as dust

bumping this, clusters would make attacking soft targets very fun

bumping this, it was a common sight on the jug

Had a quick look at the N model manual, it shows the current in game D-40 rocket panel which doesn't have a Jettison switch, the November manual also doesn't mention the ability to Jettison the tubes like the older manuals do, however the November manual only shows HVARs and doesn't talk about M10s. Puts further theory that the rocket selector panel we have in game is a very late model, which was only designed to be used with HVARs as the M10 went out of service by the end of the war. Also, on the point of the throttle and propeller lever, I think I was mistaken on it being able to be interconnected. The November manual has very good image showing the propeller lever. You can actually see the latch only exists on the leading edge. So you can't actually interconnect the throttle and propeller lever. You can only set it so the front latch drops, which means it supports the description in the manual where it will move with the throttle lever forward but not backwards. Also this also shows another method for sight controls, which I assume is a very late war K-14 gunsight. The control switches are mounted on a turn dial under the sight. I believe the correct method for the D-30 and D-40 is still the added box like the previous post image shows.

I think this box (see pictures) someone mentioned previously is the method used for the M10 bazooka tubes. The red switch is for the jettison. I remember seeing somewhere that not all P-47s were set up for the M10 launchers and were field upgraded to support them. Some even detailing only two per squadron, image below is from the Thunderbolt film, only the flight lead carried the tubes in that flight. I have a suspicion that the rocket panel in the D-40 variant in game is a very late model, which only worked with HVAR rockets, hence the missing jettison switch, as it wasn't possible to jettison HVARS so it wasn't needed after the M10 went out of service. I believe the correct version that could jettison the M10 tubes and work with both M10s and HVARs is the one with the jettison switch. This image is from a D-40, and shows the arming panel and the rocket panel with jettison switch. This would also explain how it was done with the earlier Razorbacks and the D-30 early model. All they had to do was add the rocket panel under the parking break and use the old pull handle method for bombs. For the late model D-30 which had the bomb arming panel under the parking break, I assume they mounted it to the side, this image shows an early P-47 with rocket panel mounted to the left. You can see it behind the flight stick, this one doesn't even have the bomb arming panel. I think the fix to this issue is; Change the rocket panel in the D-40 to this one with the red jettison switch Add this rocket panel to the D-30 late model mounted to the left and allow M10 tubes Add this rocket panel to the D-30 early model mounted to the left or under the parking brake and allow M10 tubes Add the ability to jettison the M10 tubes As a bonus, this image below shows the panel for the K-14 gunsight which is missing, it should have the same controls as the P-51 gunsight. This is from the same D-40. Also another bonus, the D-30 manual, (AN 01-65BC-1A, page 31) shows that the propeller lever has a function where the throttle will always push it forward, which simplifies engine management by making it impossible to push the throttle forward of the propeller lever. I assume this is a function of the interconnecting latch, so you could either lock it to the throttle lever with both front and rear latches, only put down the front latch so it moves forward with the throttle lever but not rearwards, or disconnect it completely so it moves independently.

In line with this request, those manuals clearly show the tubes on earlier versions of the P-47, would it not be possible to have the D-30 use M10 tubes as well?

I'm going to bump this, the M10 tubes should be available for the D-30 variants.

Howdy, so I've been working on a cheat sheet for myself with the DCS warbirds, for context I like to swap planes a fair bit on servers and these are the ones I use. I have been going through the manuals and posts on the forum here looking for data and I think I've gotten it right so far. I was just hope people here can verify if these details are correct and fill in the blanks. It's not meant to be a super detailed thing, just a quick reference card for when I forget. P-47 P-51 Spitfire BF-109 (MW50) FW-190 D-9 Warm up 800 - 1000 rpm 1000 - 1200 rpm 1000 - 1200 rpm 2000 rpm 2000 rpm Temp limits Oil - 40 to 95 Oil - 14 to 90, C - 60 to 125 Take off trim R - TO, A - Neu, E - Neu R - 6 right, E - 2 NH R - full right, E - 1 div nose down E - 0.5 NH Take off (5 min) 2700 rpm / 52" 3000 rpm / 61" 3000 rpm / +8 boost 2400 rpm / 1.35 ATA 3250 rpm Cruise (Rich) 2300 rpm / 35" 2400 rpm / 36" 2200 rpm / +2 boost 2000 rpm / 1.05 ATA Max continuous 2550 rpm / 42" 2700 rpm / 46" 2650 rpm / +7 boost 2400 rpm / 1.25 ATA 3000 rpm Mil/Combat power 2700 rpm / 52" (15 min) 3000 rpm / 61" (15 min) 2850 rpm / +12 boost (1 hr) 2600 rpn / 1.35 ATA (30 min) 3250 rpm (30 min) WEP 2750 rpm / 64" (5 min) 3000 rpm / 67" (5 min) 3000 rpm / +18 boost (5 min) 2800 rpm / 1.75 ATA (10min) 3250 rpm (3 min) Landing 2550 rpm / no less 26" 2700 rpm 2600 rpm 1000 rpm Any help verifying the info and filling in the blanks will be much appreciated, as I find things out I'll add them.

Howdy, So I've been experiencing a weird crash with DCS and the P-47 during single player. So far I've only tested this with the P-47, but it seems to occur on Normandy 2.0 whenever I try to do a single player mission or instant action. I just downloaded the wolfpack campaign and it happens every time after a mission loads. Issue also happens with the instant action fur ball or dogfights. Multiplayer for some reason works fine, I have no issues flying the P-47 on Normandy on the Overlord server. I have also tried the mission editor and that seems to work fine as well. Basically everything else in the game loads, but the cockpit and aircraft textures don't and just remain grey/black. The game still runs and I can fly around but I get the DCS crash report thing pop up, so I've sent a few reports on that system but figured I should post here as well. Super weird, specific only to campaigns and instant actions. I'll try it out with other aircraft and combinations and report back but for now I've attached the logs and a screenshot of what I see. dcs.log-20250515-053438.zip dcs.log-20250515-054046.zip

+1 vote, specifically the D-23-RA version, this is probably the closest to the in-game one already and the easiest to adapt for the flight model. It isn't as simple as slapping a razor back canopy on it either, the most of the cockpit would need to be changed/remodelled.

Is this still an issue or has it been fixed? Sorry to dig up an old thread but I was curious

I am pretty angry, flying today on contention in the Kiowa, infill for 60km and sneak within firing range of a KA-50 on the runway, lase target, fire a hellfire, waiting for impact and then nothing. Screen goes black, what the actual f*ck?! Take off my VR headset and see the "DCS login session has expired" message on my desktop. I've never rage quit before but that pissed me off.

Yeah, still experienced issues where I get no servers at all. For some reason going back to the main menu and back into the server list a couple of times seems to fix it. Basically if I don't see any servers within 10 seconds I back out.

So are the auto-hover and auto-slaved modes made up features?

Take some photos man, would be much easier to show something like this

As the titles says, this has been happening for as long as the F10 map issue. Yes, I have disabled hot plugins or whatever it is. Every time I go to the adjust controls menu in game it just laggs to hell and more often than not completely freezes DCS and I have to restart my computer. What on earth is causing this? I've heard some people say it's the Virpil stuff? It basically means anytime I play online I'm playing Russian roulette trying to figure out my control bindings.

*** update *** So I think the pimax is rendering so much higher than my valve index that I needed to pull the throttle all the way back. Going off some other info on the forums here I noticed an issue where it seems like the spikes were causing stuttering. Like I had excellent 60 plus FPS but it would constantly stutter when I moved my head? Super annoying. Anyway going on some advice I dropped the pimax render setting to low (0.8), and refresh rate to 72. Internal to DCS I set pixel density at 0.8 as well and reverted back to my settings I used with my index which gave me a stable experience. Seems to have fixed the stutters, but I'm still getting the barrel distortion effect. The graphics have been turned down slightly, so basically the Pimax at its lowest setting is still rendering higher than the index was. So to compensate I had to lower in game settings. Long story short, MSAA at 2x, DLSS off, textures med, terrain low, vis range med, everything else low or off. I'm not using quad views, instead only the pimax version of whatever it's called but is similar but not as drastic.

Okay I think what it is called is "barrel distortion", and it sucks. Although now my struggle is finding decent stable FPS performance. Honestly my old Valve Index seems to have been better atm. I had higher graphics settings, stable FPS and didn't even use foveated rendering. On the pimax device settings I turned on the 90 Hz Upscale(lab) refresh rate, render quality to high. I disabled the OpenXR quad view and central priority rendering as I'm using the quad view setting in DCS to get that running. I downloaded the Quadviews companion and have it set on default. I am also using the hidden area mask option on pimax. Smart smoothing is turned off. My openXR run time is set to Pimax OpenXR apparently. Also don't know if this normal but even if I have steamVR open if I run DCS it turns off SteamVR? I downloaded the OpenXR toolkit and the PimaxXR control centre but I don't think I need them? In game my pixel density is set to 1, and all other settings were low or off. I booted up the cold start in the f-4 on afghan and I get about 75 FPS just sitting there but turning my head it drops to like 50ish to 30ish and it feels laggy, like there isn't a consistent refresh or frame rate. In game it says it is only using like 44% of my GPU.

Yeah so something like this that was integrated into the ground crew menu, like removing chocks or ground power. It would be incredibly handy for places like the Heatblur and Shadow Reapers cold war servers. Even something as simple as "Do I need repairs?" with a "Yes" or "No" based on if there are any damages to critical systems.

I am experiencing the same thing, just received my headset today. Honestly the best way I can describe it is when you don't require glasses and you put a set of glasses on from one of your mates who is short sighted. This was just giving me a head ache, like as you described looking through the bottom of the coke bottle. I get this weird wavey spot in the centre, like it's lifting off the screen, like I am staring at a convex image... maybe it has something to do with foveated rendering? Like if I am still and I look dead centre the image is great, but anytime I move my head or the headset shifts a little I feel like throwing up. Mind you I have had a Valve Index for over 4 years and never had an issue. Any help from these issues?