ENO

Many, many years ago I’d had a DCS server with some pretty cool folks. I called it the firehouse because irrespective of what our backgrounds were we all brought “something” to the table. I dropped off the DCS radar for awhile- but one of the dudes I used to see in my server popped up in another game I was playing. Long story short- he and I reconnected and decided to get back into DCS together but he passed away before we got the chance. Your online friends may not always be there- and this video is intended to remind us of that fact. Please take a moment to appreciate your online friendships…

Lost a wingman… A tribute:

Eh man... I just found the mod and downloaded it and I'm having the same issue. To @SMH- I don't know how to put THIS any clearer: Just because it didn't happen to you doesn't mean it isn't a problem. CLEARLY this is an issue that exists and isn't because everyone else on the planet is stupider than you. SMFH. Thank you to @nighteyes2017... That solved the problem. @Ghostmaker do what night says and you'll be able to extract all the files.

See you're still busy making miracles happen!

I imagine this has been done a million times but... I can't help it: The morning of December 6th, 1941.

Awesome!

Thanks Habu- worth a shot.

Okay well this is in line with an issue I’m having- I’d set a couple units to immortal with the intention of allowing them to close within a certain distance while fighting and not dying. I set a stop condition for the immortal as a flag set to true when pet the red group moved into a zone. Unfortunately it doesn’t turn off. I ended up deactivating the immortal unit and activating a mortal one and that works but I’d like to figure out the stop condition issue.

Well turns out it doesn’t matter. I’d read somewhere that they were only visible to the host- which I thought must have been a mistake. Tested it and... it wasn’t. So- doesn’t much matter anymore.

Eh guys... Still puttering away on my Zugdidi Loop concept and found the Helper Gates were a great option for leading folks through the proper path. They are aligned with specific waypoints and that works great now that I've figured it out. I'm trying to set them up to a radio item so that folks can turn them on if they're new to the route or even turn them on and off for reference if needed... I'm trying to keep everything to a "by unit" basis so that they're not distracting for the entire coalition. The issue I'm having is once the gates get turned on there is no "turn off" gate function in the ME. I've tried setting certain values to the flags and using "switched condition..." I've tried a couple other small things but once they're on they want to stay on... Any thoughts?

Hmmm in my experience with RTB in advanced waypoint actions the AI will just RTB when it hits that waypoint... It doesn’t make it run a check to see if it’ll make it another cycle and then send it home. Not sure if that’s changed?

This is the part about DCS and all of its modules that nurtures my apprehension about 3rd party modules. Of course I have the Tomcat because... well... duh but this is the same issue modders and scripters have trying to keep up with subtle changes. You guys (3rd party devs) smash modules out of the ballpark in terms of quality and then ED changes "something" and now you've literally compromised an entire flight model- at least insofar as its relationships with the core program. And there's literally nothing "proactive" that you can do about it. ED does their thing, whatever that is- changing an 0 to an O for example in some code somewhere, and then you guys are left scrambling trying to clean up your own module. I'd expect better coordination between the 3rd party developers and the developers but apparently that's impossible.

I’m not sure if things changed but you should be able to install each purchased module on multiple computers on a single account but you can’t play that account on two computers simultaneously online.

Look up The civilian air traffic mod and the MOOSE Random Air Traffic scripts- very easy to implement for random military and civil air traffic. Highly versatile and requires very little if any scripting knowledge with excellent video guides on YouTube.

I can't believe how relieved I am to see this again, finally. The switch out process was very easy and I thought there would be much more to it. If anyone has a similar problem and is concerned about the process just reach out to me and I'll walk you through it.

A quick update on this. They figure it was the main PCB that failed... or perhaps it was just the USB cord that comes connected to the replacement PCB. They sent me the part and it arrived in good order but without instructions. The instructions were forwarded later on request by email but were just arrows pointing to things that needed to be done and a list of tools needed (phillips head screwdriver and a soldering pen / iron). The video you posted shows everything except what I need to do with the ground wire- which is basically solder it into place. I'm going to be doing that shortly so wish me luck.

Don’t think it got mentioned but If you’ve spent some time placing static’s on a carrier and place one and switch aircraft type all of the statics you’ve placed will collapse to the center of the carrier deck stacked on top of one another. I’m also not sure if it’s a bug or intended but if you have copy and pasted a static linked to a unit, that pasted static shows that it is also linked however you need to click and select the unit again for the pasted items wings to be “stowed.”

Thanks yeah they're saying it's likely a board problem so the replacement is X amount of $ and they can ship it out. They say it comes with instructions et al so I guess I'll see. I've asked for expedited shipping since I don't want to be out of the saddle all month.

Eh Windy- I was encountering issues very similar to what you were describing... almost in mil power on my downwind just trying to maintain between 10-15 units AOA and flying the indexer. Unfortunately my Warthog HOTAS stick crapped the bed recently so I haven't been able to fly for awhile but with less than 5000lbs of fuel, 2 phoenix, 2 Sparrow and 2 SW for whatever reason my setups were all over the place. I'll keep my eyes open for your posts and see if you figure it out.

Yes.

This is undoubtedly the more elegant way to do it- if you have any scripting experience or someone would Help with something specific. I recommend the MOOSE discord. I used to run a number of explosions at mission start to add some sense of a war torn region to my missions... and it worked reasonably well and since it happens almost immediately nobody sees them. With that said Pikey definitely has the better solution and would be what I’d have recommended if I had his scripting skills.

Okay, well you shouldn't need the stop condition command to make the hover happen. All you need to do is set the waypoint where you want the hover to happen... set it for orbit... at 0kph or whatever and then set a stop condition for another flag. Once that "other" flag has been set the helicopter can move on to its next waypoint which can be a landing waypoint at your desired location.

My suggestion is to set a "stop condition" as I recommended in my response to your initial thread. Your "next" waypoint should be a landing waypoint at your desired point. If set up properly, the chopper should fly to the "orbit" waypoint with a stop condition involving the desired flag being activated after a "time since flag" trigger. The following waypoint should be a "landing" waypoint and the normal destination... the chopper would, when the stop condition was reached, land at the desired location. Feel free to post the mission file here and I'll see if I can put it in play for you.

I get a perverse pleasure in seeing that what little I know can still help people achieve their goals. I have no doubt that a script could help you achieve it more elegantly... but for now I'm glad you got what you were after! EDIT: Wait a sec... it looks like you started another thread... where are we at?

Thanks.