fargo007

I think what's needed here is a trigger condition where we can test a group to determine if it's a client. So you could test for a group, or coalition in a zone, and have a second condition that a client is in a zone. Another one that would be great is a type trigger. Let's call it "OF TYPE" So helicopters can be distinguished from planes, from ground units.

Nice job on FARP Hollywood. It looks fantastic.

Confirm. That pilot is window dressing only. It's a shame we can't have him become a real ground unit because he actually looks really good.

Not sure how to run this down, but in missions on Caucasus that include Moose, Mist, CTLD and CSAR, after about 15-20 minutes, new clients that join are not getting the configured menu entries. This includes radio menu items configured within the ME as well. They're just gone. When I switch around to some of the other client slots, some of them will have SOME of the menus but none seem to have them all. Any idea on cause, or how to go about debugging this?

On A2G BAI tasking...... How do I shut off the map mark location for a task and disable the repeating status on screen? I'm sending guys out to locate and destroy a convoy in an area, and the task keeps giving away the location of the enemy quite directly. Is there a method to quiet the updates and one to disable map marks?

Had the same issue and that WILL fix it.

New behavior noticed: Start mission, fly two hueys for an hour. Sit idle on the runway, go away for 20 min. Upon return, the pilot is dead! Further attempts to get into a Huey reveal a xmsn chip immediately, and attempts to enter an Mi-8 result in immediate engine fire. Log messages: 2018-10-01 16:26:35.065 ERROR COCKPITBASE: devices_keeper::link_all: unable to find link source 'networkSynchronizer' for device 'HYDRO_SYS_INTERFACE' 2018-10-01 16:30:36.394 ERROR COCKPITBASE: devices_keeper::link_all: unable to find link source 'networkSynchronizer' for device 'HYDRO_SYS_INTERFACE' 2018-10-01 16:34:10.856 ERROR COCKPITBASE: devices_keeper::link_all: unable to find link source 'networkSynchronizer' for device 'HYDRO_SYS_INTERFACE' 2018-10-01 16:37:50.256 ERROR COCKPITBASE: devices_keeper::link_all: unable to find link source 'networkSynchronizer' for device 'HYDRO_SYS_INTERFACE' 2018-10-01 17:56:51.145 ERROR COCKPITBASE: devices_keeper::link_all: unable to find link source 'networkSynchronizer' for device 'HYDRO_SYS_INTERFACE' 2018-10-01 18:08:10.195 ERROR COCKPITBASE: devices_keeper::link_all: unable to find link source 'networkSynchronizer' for device 'HYDRO_SYS_INTERFACE' 2018-10-01 18:08:53.062 ERROR COCKPITBASE: devices_keeper::link_all: unable to find link source 'networkSynchronizer' for device 'HYDRO_SYS_INTERFACE' 2018-10-01 18:09:07.637 ERROR COCKPITBASE: devices_keeper::link_all: unable to find link source 'networkSynchronizer' for device 'HYDRO_SYS_INTERFACE'

In a Caucasus mission (most recent updates to date), all the Mi-8's were experiencing random issues as soon as the client spawned in. Right Engine Vibration Right Engine Fire... After flying a while, Hueys started losing inverters. I landed in a Huey, switched to the copilot seat and activated the flex sight. I looked to the right, and the pilot was suddenly dead! My wing man did the same thing. Switched to the copilot seat, and his pilot sadly passed away. I went to a different airbase, got in a cold Mi-8, started it, and the left engine vaulted to 110%, vibrating wildly. I took off to try and keep it all together, and started the right engine in the air. It eventually shook apart. I restarted the mission, after verifying that I had NO random failures configured, and have that box checked on the left and empty on the right in mission options (meaning 'I don't want this'). The only one on the server, it seemed there was no issue. Then another squad mate joined, and IMMEDIATELY I had a "Right engine vibration" followed very quickly by engine and transmission fires. .... Something's up. ETA: Restarting DCS on the server made this go away. Will continue to monitor. ETA: Has not returned after server running all night. It occurs that repeatedly loading missions from esc-select_role->change_mission may have contributed?

This got resolved a couple updates ago. Thanks ED Team!

Hello from BSD! Announcing our first inaugural BSD OPEN MISSION DAY. We have not selected a date yet. This is a pre-event announcement. TIME/DATE: TBD, in October BSD OPEN MISSION DAY (BSD/OMD) is our take on a traditional open house, or a public server, but with what we believe will be a very welcome twist. Instead of just opening the server up for public use and stepping away, we’re inviting you to do come in and fly some short missions with us. You will get to: Attend an aircrew briefing. Fly in realistic helicopter formations Communicate with, and work together with us. Execute realistic take off procedures Land in different types of hot and cold LZ’s…. See how our gunship pilots set their runs up See how our lift pilots shoot approaches into different kinds of LZ’s Get a look at the type of mission design going on within an active and organized squadron. The types of mini-missions we’ll be doing include: Rescuing downed pilots behind enemy lines Conducting VBSS missions by transporting teams to and from cargo ships in enemy infested waters Providing aid to ships that have been attacked Be on standby for hot extractions if special operations teams get pinned down If you want to just go kill stuff, we’ve got that too Conduct troop transports and air assaults Participate in shipboard helicopter operations with realistic procedures The technical details: We fly the most recent update of DCS Openbeta. Persian Gulf map Mission is daytime. All DCS helicopters will be available. BSD pilots will lead each flight, so you will always have some guidance nearby. This mission requires no mods. Communication will be via the BSD discord, for which we will furnish an invite. We usually use Simple Radio, but for this mission only discord. Attendees are responsible for having the latest updated version of DCS Openbeta installed and fully operational, along with a microphone that discord can operate with to allow you to hear us, and be clearly understood. You MUST have a push-to-talk configured in discord ahead of time. Being familiar with the radio menu, CSAR and CTLD use helps, but not required. You should have a reasonably fast internet connection. All skill levels are welcome, but if you have great difficulty controlling a helicopter, or flying level in a straight line, we ask that you respect the enjoyment of others and maintain a safe distance. ABOUT BSD BSD is an active rotorcraft only squadron chartered to fly cooperative combat-oriented missions in DCS. We are based on the East coast of the U.S., and we fly, fight, and train in all of the DCS helicopters. Our typical weekday training and mission flights are Tues & Thurs, 2100 EST and on weekends in the afternoon (CST and PST friendly!). Much more than just flying DCS together, we share a sincere appreciation for helicopters and have an annual reunion built around rotorcraft activity. This year, we chartered a Huey (itself a Vietnam vet) and got to study it for hours, and then flew on it for a half hour on it with an experienced Vietnam veteran combat pilot at the controls. We partner with other squads for joint missions, and hold regular internal training sessions on all helicopters and flight topics. If you enjoy this mission, our recruiting officers will be standing by to answer your questions about enlisting. We’ve made the process for becoming part of BSD even easier. REGISTRATION OPENS ONCE WE FIX A DATE This is a pre-register event only intended for those who haven’t interacted with or flown with us before in other organized missions. We will take 15 public attendees on this operation. Once we have a date fixed, we will post a registration link. In the meantime if you would like to comment or ask any questions, please do so. Thanks! /Fargo (BSD Mission chief)

Which aircraft? Try RAlt-\ as well. I suspect the binding for the command (keyboard) might be missing. Check that too.

I point out that you can either set USAF aggressors to Red coalition and have access to all of the objects, or you can edit db_countries where you are building the mission and add it yourself. Plenty of posts here on how to do this, it's simple.

I wasn't interested in the actual topic, but after looking at the lua, I like what you did here. Making a template table and then operating off a SET_GROUP prefix filter based on the values is something I hadn't considered. Thanks for revealing another kung fu move.

BWAAAHAHAHA! Bravo ED, these are excellent and you did not disappoint.

Would love to see a real naval base.

Bump - This is still occurring several updates later. Thanks for any effort put toward resolving it.

Hahaha! I love the criminal lineup of the three insurgent guys.

Preach. So easy to delete the wrong thing and then have to reload and lose all the work since the last load.

I have a modified version of it working where if over land it spawns the soldier, and over sea it spawns the life raft (a mod). The call for determining landtypes in multiplayer isn't returning in a completely reliable way so I am still testing. It seems to consider a good portion of coastline to still be water for some reason. Once I neaten it up I will contribute the code if Ciribob is interested in merging it. Essentially it would let you parameterize your wet and dry objects.

Exactly as title indicates. Turn labels off in the mission (enforce is checked, on/off box is not), start the mission and join the server and labels will be on/available. The enforcement actions are not working in MP.

Left Shift & F9. But I think there's a bug with labels now. They are enabling all by themselves in multiplayer, even when specifically disabled in the mission (enforce is checked, on/off is unchecked).

I'd REALLY like to see the dedicated server run on Linux. This would really open up new possibilities.

Where's v1.2? I only see 1.0 and 1.1 in the initial post.

Thanks for trying to help. I'm using 1.1 here. On OB, latest version. I have the folder "Desert Farp -By Suntsag" in my OvGME mods directory. It activates fine. It gets installed in \Saved Games\DCS, such that I see these folders there: \Saved Games\DCS\Bazar \Saved Games\DCS\Bazar\Textures \Saved Games\DCS\Bazar\World with their contents the same as in the mods directory. I've reinstalled it a few times. All I have available is the regular FARP, which lately looks like it's snow covered. /Fargo

It seems that in the latest version, these lines are different now, and none are commented out: --Night Vision Goggles {combos = {{key = 'H', reformers = {'RShift'}}}, down = device_commands.Button_5, up = device_commands.Button_5, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 1, value_up = 0, name = _('SA342 Night Vision Goggles On/Off'), category = _('Night Vision Goggles')}, {combos = {{key = 'H', reformers = {'RShift','RCtrl'}}}, down = iCommandPlane_Helmet_Brightess_Up , name = _('Night Vision Goggles Gain Up') , category = _('Night Vision Goggles')}, {combos = {{key = 'H', reformers = {'RShift','RAlt'}}} , down = iCommandPlane_Helmet_Brightess_Down, name = _('Night Vision Goggles Gain Down'), category = _('Night Vision Goggles')}, Yet the NVG's for the L and the Mistral are nonfunctional in the current version as of today. Anyone wrestle this down yet? /Fargo