franx

Thanks gunterlund. I haven't done scripting. Anything advice about how to do this or where I can find good counsel?

Is there a way to make AI units (like tanks) that come under attack fight their way forward to their objective? I note that tank platoons or companies that disperse under helo attack simply stand still and don't resume attack. Or am I missing something basic?

Thanks, razo+r; actually I've been doing that all along -- using the three standard autopilot channels -- which is why I was surprised and frustrated when this started. I've tried it with and without flight director too. After recording the track I posted, I then tried again, this time explicitly giving the "hold heading" command on top of the three already active channels. That seemed to work, but I may be so screwed up at this point that I'm missing something basic.

Here you go. testtrk.trk

Will do. Away from game computer. Check back in a couple hours please. The problem is this: I overfly my targets, use the pedals to turn, then no matter what I do to compensate, the chopper continues to drift slowly in the direction of the turn and I can't stabilize for a shot. I'm sure I'm doing something simple, wrong.

No wind.

I'm sure this must be an easy fix and I'm doing something obvious, wrong . . . but when I hover, I've started to drift relentlessly to the left. No idea why. Any assistance gratefully accepted!

Thanks for the response The_Nephilim. Tried that to no effect. But I did solve the issue last night. In order to edit my View.lua file with Notepad++ I had to open an Administrator account on my Windows 11. So I did. Then I went in and did the edit. Then I signed out as Administrator and signed in again using my regular account. That's when the problem started. Apparently the computer remembers that someone else is also using the machine. So I restarted the computer, signed into my regular account, and no more problem.

I've been running WMR on my Reverb G2 for several years. Suddenly the WMR canned background music won't stop when I enter DCS. It continues playing in game and it's incredibly aggravating. I've checked all my sound settings and can't find a way to turn it off. Anyone have an idea how to fix this? Help much appreciated.

The very last thing I tried from the messages above was to do the "rename the DCS folder to DCS.OLD and transfer the Input folder therein to a new DCS folder" approach. That was it. Yikes. Dramatic improvement in load times -- in both 2D and VR. Many thanks Flappie and all. The sim is enjoyable again.

OK, I followed and applied what I could in Flappie's items above (many thanks Flappie). Note that I'm flying the Black Shark KA-50iii. The results: Opening DCS MT in 2D mode, the sim started noticeably more quickly with no "15 years of DCS" splash screen. That's an improvement. From the sim's main menu, I was able open my (simple) mission editor mission in two minutes, 52 seconds. For comparison, I was able to open the sim's pre-made Black Shark "shooting range" mission in one minute, 40 seconds. In VR mode (I use the HP Reverb G2 with Windows Media Reality), DCS MT launched much more slowly, the "15 years of DCS" splash screen was present; and from the sim's main menu, it took four minutes, 52 seconds to launch my mission-editor mission. The sim's pre-made "shooting range" mission launched in something more than two minutes. So a couple of questions: Should I be using DCS instead of DCS MT? Should I be restricting the number of cores my CPU uses? Are the extended times incurred just a function of VR? Or the WMR program? I don't remember things being so slow before 2.9. Any further counsel welcome and appreciated.

Thanks Flappie! Will review and test tomorrow and report back. Info looks promising.

No, I edit in 2D. The problem comes when I call the mission up in VR.

Thanks and great clip, but I've got 32 gig RAM, 16 gig AMD GPU, and an SSD. Also a good AMD CPU. I've been mission-making on and off for years. Problem appears mainly in VR, and it seems to be new with 2.9.

Is there are way to compact or streamline a mission-editor mission beyond just saving it? The missions I make are quite simple, but it takes a LOT of time for them to open -- five minutes is not uncommon.

I'm using the latest DCS 2.9 update, Windows 11, and the HP Reverb G2 headset. I can run DCS and the missions that come with the sim. But the missions I've made myself -- which run fine with TrackerIR -- begin to open and then default to a black screen freeze. Anyone have an idea of why this is happening? ADDENDUM: After further testing, the black screen does eventually switch to the mission, which is playable. But the delay between launching mission, getting the black screen, and then the mission actually showing up is very long -- literally several minutes. I've run a full program repair. Doesn't seem to help.

Thanks guys. Figured it out. Much appreciate the help!

Many thanks. But how are you doing this. Every time I try to add a different ship to Naval-1, the new ship eliminates the old one.

I've been using DCS for 15 years, created ground missions in CA, but never made a naval scenario. I'm finally getting around to using my Supercarrier module, so a simple question: Does each new carrier strike group need to be constructed ship by ship with independent routing? There doesn't seem to be an "escort" command for cruisers and destroyers as there is for planes and choppers in land-based missions. Any help or suggestions would be much appreciated.

Thanks fellas. This should help. Much obliged.

I've been away from the WW2 planes in DCS for a few years. Back now trying to fly the Dora. I'm using Saitek pedals for the Dora's rudder, but no matter how I fiddle with the Axis tuning, the plane pulls hard to the left. I can't even get to the runway from the ramp, let alone down it to take off. It's essentially unflyable. What am I doing wrong? I realize the prop does initially cause drift in direction, but this is ridiculous. The pedals have very little effect.

Many thanks draconus. Yes, I found that video about a week ago. The Grim Reapers' vids are very good. I'm just baffled that DCS spent so little time on the CA instruction manual. It's a great sim. CA gets treated like the illegitimate child of Arma 3 and an F-15.

How do you removed the CAS option?

I've been playing DCS since the beginning, but only very recently started trying out Combined Arms. It looks and feels terrific, but I'm new at it with some basic questions. I'm driving the Merkava IV tank, and I can't figure out why I can lock a target sometimes, but not others. The other Merkavas in my platoon seem to lock and fire much earlier than I can. Is it a range limitation? What's the firing sequence of orders: rangefinder on, lock target, fire? Do I need to use the laser? When do I turn on target tracking? Do I need to use the increase range command? And what's the difference between rangefinder and rangefinder combat? Sorry for the newbie questions. Any help much appreciated. The manual is less than helpful.

Fellas, I'm the guy who started this sad thread nearly a year ago. In frustration, I kept but mothballed my G2, and then my work interrupted any VR attempts in the interim until now. Recall that I have an AMD 570 board, 6800XT card, and 32 gigs RAM. So 10 days ago I decided to take another run at using my G2. I know the workarounds to get it functioning in an AMD environment, and it looks great playing various games. But it will not play nice with standalone DCS -- and I've spent somewhere north of 60 or 70 hours since I bought it crawling through Reddit, watching videos, etc. hoping to get it to work. WMR is a real disappointment and nothing but hassles. I know others have had a happier experience, and I'm glad for them. But short of taking my G2 to Lourdes for a miracle cure, I've concluded that nothing will work. I want to actually enjoy a headset and not constantly rage at it. Last week I bought an Oculus Quest 2, and despite one initial hiccup, it's been flawless and very easy to use. With the graphics properly tuned and tweaked (thank you, YouTube), resolution is excellent and DCS play is very smooth. So I'm sticking with the Quest 2.