All Activity

Hi Together, I have DCS World Version 2.9.19.13478 installed with some add-ons such as the FA-18C, F-16 etc. I'm currently facing the problem that I loose axis control after take-off from the super carrier. Throttle and stick are not working any longer. This applies only to carrier take-off. I recall having had this issue already previously but blame on me, I can't remember the solution. Does anybody have an idea of how to fix it? I recall that it was only a minor setting in another program which has to be changed. Many thanks for your help. Achim

+1 (or video training with startup, procedures etc.)

Ah, you're correct. The Warthog was basically made for DCS, so the TM peripherals get "locked" automatically. The TM MFDs behaves the same way, as there should be no reason to change anything. Sent from my SM-A536B using Tapatalk

Yes, when other non English users use translators the quote will be in the translated version. Happens all the time. [emoji6] Sent from my SM-A536B using Tapatalk

I can't wait!!!

Yeah, it's not the LUA. It's the folder with the textures in it for the Hook. I created a copy of that ZIP folder so whenever I update, I just have to copy and paste the file and I'm good to go.

You don't need to look for RTB in the F10 menu. All you need to do is switch the radio station to the desired channel and the dialogue will take place. Sorry if this point was not made clear enough. See my screenshot.

Will you be adding a waypoint property that enables direct fire engagements vs indirect fire? If so that would be great and if it can be added to the rest of the ground units.

Seeing Mossul mentioned, did the team have time to add some landmarks in the coming update? Asking for a friend... https://forum.dcs.world/topic/371325-details-and-landmarks-in-mosul/#comment-5630236

Here are my tests so far:

The tutorial has been bugged for a couple years now. Try it on another mission.

Same issue and also use task manager to close DCS in desktop. Not 100% sure but my issue seemed to start a few months ago when quest 3 stopped launching Link/PCVR without stop/starting Oculus service, this is widely reported in a lot of Quest forums and Meta seem to have no interest in fixing. Love my Quest 3 but willl be moving to another headset shortly due to poor PCVR support - probably PCL or S.

I use OVGME to install and remove the mod. So whenever I do an update, it's from a "clean" state. So the missing textures were a mystery to me. That's why I dug into the LUA file. I previously created a grey skinned mod for the HH-47G and green for the RAF Chinook HC.5

Not entirely correct. GT is quite correct when he says higher speed will be obtained for a given manifold pressure at a lower propeller RPM. However, lowering RPM at high manifold pressure increases the torque. A while back I posted a simplified explanation in the P-51 forum So manufacturer's are going to err on the side of not over boosting the engine and give the pilot numbers that avoid damaging the engine. I got a personal demonstration of this over three decades ago. I went missed approach on a localizer approach in south Arkansas in a Beech 18 (twin Pratt and Whitney Wasp, Jr's). About 200 feet above the ground on the straight ahead missed approach procedure I entered the moderate downdraft of a heavy rain shower. I applied "radar power" as we used to say to avoid settling into the ground. The engines were over boosted for probably 30-45 seconds until I cleared the downdraft and started climbing again. About 100 hours later, one of the jugs on the left engine separated, head from cylinder barrel, breaking the oil lines between the jugs. It took about 15 minutes to pump the 8 gallons of oil out, forcing a low oil pressure engine shutdown. I landed at my planned destination off the same localizer approach with 300 ft overcast and rain showers. If the rubber oil lines had been less ancient, they probably would have stayed intact and avoided the need for a very exciting single engine approach. A lot to take away from that experience with regard to how piston engines are modeled in DCS, especially radials. The damn things can take some severe abuse and get you back home.

@GTFreeFlyer, That is easier said than done. One may not be able to adjust wind parameters in a multi-player server or single-player mission. For example, playing on a 4YA server or running a training mission. From my experience, having a small wind component at 33 ft will help to dissipate any smoke that is on the airfield. For example, an aircraft running a smoke canister will create a large cloud of colored smoke if it is turned on while the aircraft is on the ground. Wind set 1 kt or above will cause that cloud to blow away over time. This is very helpful when someone forgets to turn off smoke when landing. Talking about adjustments to wind values in a mission diverges from the primary purpose of this thread. I do not want to lose focus on the Corsair's differential braking performance. I hope that @-Rudel- and his team of programmers will soon tackle this problem with differential braking. I appreciate his candor and ability to share the list of bugs that require attention.

Yes, that's right, in the description I mentioned the unreality with the seasons in the Caucasus, which has been present for years, except that now the summer season has been shortened by a month...

Historically the Marines used two seat hornets for some missions. My question is how hard would it be to add a second seat to the hornet we have

Hey first of all thanks for responding and for making the campaign, I'm really enjoying basically all of it except the dogfights > It should also be noted that the F5s are armed with Aim9ps so rear aspect only compared to your 9Xs which are all aspect. Maybe this got changed by an update or something, but they have AIM-9Ls now (this is in Mission 6 I think, the first 2v4 you have to do?) which are all-aspect. Yes I'm obviously still in a better plane than them in the 18, but going into a merge with multiple bandits with Fox-2s is always going to be a risky thing. I eventually managed the fight since I knew exactly where they'd spawn on my second attempt, but without the benefit of hindsight you have very little SA with them spawning so close. It's pretty tricky to manage all that on your first try to get your one Fox-3 off, then you have to try to survive the merge. The time I actually beat it, I had to survive an AIM-7E and an AIM-9L shot straight at me just to get to the merge. Track attached in case you don't believe me about the 9Ls (ignore the fact that I generally suck). PL Mission 6 I think.acmi Love the campaign, just wish I didn't keep having to deal with these very risky dogfights at the end of otherwise good missions. Mission 6 isn't even that bad since you get to the fight pretty quickly, but some of the later ones make you do these dogfights after a lot of ground action. Difficulty of the ground vs air sections is really out of whack. It also ruins the vibe of doing thought-out, professional strikes when you're repeatedly waltzing into these bad situations without support or modern missiles. There isn't any air-to-ground at all in Mission 6, why don't I have a reasonable anti-air loadout?

Great thanks!!!

I think it's a problem with using Meta Quest with turbo mode active in openxr toolkit. Same with the game crashing when you take your headset off

You may already be aware, but when you activate autopilot on the ground the stick trims all the way forward and the key-bind will not switch the A/P off, you have to throw the switch by clicking on it with the mouse. I use a FFB stick and I believe this problem may be related to two others: Iceman trimming all the way forward when you jump in the back seat. ACLS nose-diving you into the sea when activated. For FFB users these related A/P faults are among the last remaining 'major' issues with the F-14. With the imminent and eagerly awaited release of the early A, it'd be nice if this bug was weeded out once and for all. These probably have already been covered in separate threads, but not sure these three problems being related has been brought-up before. If they have, my bad.

Hi ESAc_flankercobra, It was because the Essex has 14 wires... I just fixed, now it should work. Have a great day! Hi fagulha, Sorry for the delay, to fix the problem I need the debrief file that crashed. By the way I just uploaded a new version with some fixes related to the corsair and the Essex, it may also solve your issues. Please let me know, Have a great day!

How about the Cessna T-41 Mescalero (It's basically a 172 used as a trainer). Seriously while I think there is little market for this commercially this might be good as a mod. Though I would side with the O-1 Birddog

I run at 2700 (or whatever is the max rpm) and expect high speed, because this is what the real aircraft manuals tell me. You may be overthinking it a bit. While there are many factors that go into propeller design, and efficiency changes with speed and altitude, ultimately these things are considered during aircraft development. In service, the max performance is meant to be achieved at max power/max rpm setting. Even if there is some efficiency loss on the propeller, it is offset by the engine producing considerably more power at higher rpm. If a different RPM setting was required, it would at least warrant a footnote in the pilot's operating handbook. Here's an example speed chart for the Corsair, not the exact dash we have in DCS, but you get the idea:

Hi guys, I have a problem shortly after joining any multiplayer server. Usuallly after selecting dynamic slot or when I already spawn and textures are loading my PC completely freezes. My screen goes black and the only thing I can do is to reboot PC. I have already reinstalled the whole system including all drivers. I tried to increase page file, repair DCS, run in ST mode, with or without game mode or hardware accelerating. I really don't have any other ideas. Problem exists only in VR. My spec: Ryzen 7 9800X3D, RX 9070XT, 64Gb RAM 6000mT CL30, Meta Quest 3 dcs.log