Reaper51368

I forgot to mention we may have found a possible workaround until it's fixed. We did one test where he hooked up and launched before me successfully. Since it only seems to be happening when the host puts his launch bar down (hypothesis only, needs further testing), the people who join should be able to hook up and launch before the host. Granted, we only tested it once on a barebones mission, but at least it's something to try.

I am the one that hosted the mission Spectre reported. One little tidbit.......in one of our testing scenarios, it appeared he had good tension and didn't glitch out until I received tension on the launch bar. I believe that may even be in the track file he posted. I remember saying "oh there ya go, you have tension", then looked away and maybe even extended my bar, then he popped.

Does unit culling work for anyone? I started a Syria Allied Sword and set the unit culling in the campaign settings to 200km. When I get into the mission units 270 miles (~430km) away from my carrier are spawned. Any suggestions? EDIT: Disregard, I did not understand what the exclusion zones were and how they worked.

Is there a way to delete target points?

Thank you. How does the Sight Select Switch affect this process? Has to be in TADS?

I'm having trouble creating a target waypoint. The videos I watch say to lase the target and hit the store button. I have tried this on both vehicles and points on the ground and do not get a T01 on the menu or on the TSD. I have tried with the TSD in nav and combat modes. I just realized I have only tried this using the TADS and haven't tried it using the IHADSS. Can it only be used with IHADDS? Any special modes I didn't set?

Moxica, some content creators, such as Growling Sidewinder add sound effects into their videos for entertainment purposes. That may be what you're referring to. I believe what Razor18 may have been trying to say was there is so much noise in a real apache, and with the helmet, the pilots don't actually hear much of the outside world sounds.

I get the cat and mouse theory of having enemy units spawn in towns, but this kinda kills the immersion..... Not the best place for an SA-5 launcher. If there is no better way to put the vehicles in cities, can we just have them in unpopulated areas? This happens in every A2G mission I have checked. Sometimes multiple vehicles in buildings.

Is culling broken, or am I not understanding it correctly? I have the checkbox enabled in the settings and have tried various distances up to 150km, currently set to 100km (which is the default I believe. I start up my mission from Ramat David and have every single unit on the map show up, some up to 245nm away (close to 400km). Is there something I'm not understanding about unit culling? Is there another option it's dependent on or overriding it? Edit: So I found the map filter to culling exclusion zones. I double checked and there are definitely some units outside of those zones, but it does seem to be removing some of them. So 2 questions: 1) is there a way to force all units outside of the exclusion zones to cull? 2) Is there a way to edit the exclusion zones? If I'm working on the forces in southwestern Syria, why do I need a culling exclusion zone in northeast Syria approximately 250 miles away? Thx.

Does anyone know when a new version will be available with SA-5 support? It's been 2 and a half months since the last update. Hopefully it's still being worked on.

It doesn't sound like something they would intentionally implement into an aircraft. Do you have any dead zone on your rudder axis? I usually put a dead zone of 2 or 3 on my rudders.

Anybody have any instructions or links for a how to change the family photo?

So I've been doing the liberation campaign on Syria and noticed my ground vehicles utterly defeated by the orchards on the map. One of the vehicles enters the orchard and begins running around in circles while the other vehicles in the group simply stop and wait. This is a killer then you are about to take an enemy airfield but your guys can't get there because they get "trapped" by enemy orchards. I don't believe this is an issue with liberation because I went into ME and created a new mission with 4 tanks and set them to drive through an ATO (anti-tank orchard). I have tried setting them to follow roads in the ME, but they won't enter and capture the base when I do this. Any ideas? I've attached a very simple mission demonstrating this behavior. It's best if you speed up time!! :megalol: antiarmor orchard.miz

Is there a way to make your wingman calm down? He spends several minutes calling out "2, contact 273 for 78" over and over and over ad nauseum. There is a radio call option in the settings, but that seems to only affect other flights. It seems he is calling out each vehicle in each group. Obviously I can just turn the radio down, but that just feels like a bad solution. So is there a way to tweak this, or is it something ED has to address (hopefully already in the works)?

MeatBall, that is very weird. I run a 2080ti and an 8700k and have good frames. Try playing around with unit culling. Syria full campaign does give me stuttering, but I set the culling to about 200km and it seems to help.

I am having an issue with starting from an airbase in v2.1.5. Posted earlier about start times, if I start on a carrier, I always start first, even if I have CAP flights set to take off before my strike flight. When I try to fly a viper or hog from an airbase, it always tells me my flight is delayed and I have to wait. I have verified my start time is set to 0 minutes. The only way I can make sure to start without having to accel time is to be the only flight taking off from an airbase, which sucks if you're in a hog and have no cap. Anybody else having a similar problem or have a workaround?

Two things: 1) How do you set it so AI flights take off before you. I delete a flight on the CVN, make a flight with the free up planes with the task I want, set the departure minutes to several minutes after 1 or two of the BARCAPs, set client slots to 1, set loadout, set flight plan. When I launch there are no BARCAPs up, and they launch however many minutes they were set to after me even. Say they are set to launch in 4 minutes, I set me to launch in 12 minutes. I launch, then they launch 4 minutes later. 2) This might be a DCS/ME issue. Is there a way to stop the system from spawning SAM sites in the middle of forests? I'm not talking about in a clearing in the forest, I mean there are literally trees over the launchers. This was an issue I had with Through the Inferno mission as well, so I tend to believe it must be an inherent problem in the DCS/ME logic. Anybody know any workarounds? As usual, I apologize if these topics have been covered. It's just not feasible to check this whole post. Thanks.

Anybody else having issues with the TGP not loading on the F16C? I use custom loadout and put it on the bottome hardpoint in the list (the only one it shows up on) and when I get in the mission it isn't loaded on the plane. There is a workaround to go in an load it in the ME before launching, but would be nice to not have to do that. Or is it something I am doing wrong?

Is there a way to remove the TGP symbology from the HUD once I'm finished with the TGP? I turn the TGP off, switch the HSI to a different focus like waypoint or tacan, master arm off, switch back to NAV mode even. I still get the diamond on the heading tape and the diamond pointer on the HUD.

How do I remove the green smoke from the airbases?

Well, son of a gun! I never even thought to try the Off/Idle with the detent. How embarrasing!

How do you do it?

Any plans to implement the throttle off and idle positions for the TM Warthog throttle like in the A-10C?

The 2 position switch was in the patch notes.

TRIG won't be available unless the LTD/R switch is on. Switch probably turns off automatically so it doesn't burn out.