fargo007

Pointing out that much of what's being asked for here is already possible through the scripting engine. The new CTLD and CSAR available through MOOSE open up tremendous possibilities. We've been deploying Fat Cow style FARPs, airframe recovery missions (Snake Doctor) as well as a fully operational Rotary Wing logistics network for quite some time now. I'm not opposed to ED building some rudimentary stuff in, but you will always get a far better experience with scripting than something from a box. This is why nobody uses the in-sim troop loading, though it's always been built in. For the Fat Cow, after deploying, we use an AI 47 to sit there. It's hard to find a pilot that wants to fly to a location, and then sit there for 2 hours, waiting for someone to need fuel. Now the cargo objects (artillery,scout vehicles, armor, etc) and the FARP ground objects (now the job is done with mods) OTOH, that would be excellent. Some of the other interactions I'm looking forward to creating is having a C-130 Squadron land on a makeshift airstrip, forward deploy four OH-58D's for us, and then have a ch-47 Fat Cow come in and fuel/arm them up, and away they go.

< .... //// - - - *** This might be when it's coming. Better reactivate Bletchley Park.

Hi, we're setting up a dedicated server and are stuck at an error involving netview. Instead of getting a true condition here, it's throwing this error. Does anyone have any advice or hints on what to check? Was caused by attempting to use a pretty old version of slmod. Leaving the post in case this helps someone.

Nice work on this guys. Looks really good!

Absolutely still works great, and also with newest MOOSE version. dcs.log will always show you what's up.

How about supporting Troops in Contact? You will probably want to change the makeup of the enemy to suit. https://forum.dcs.world/topic/286538-troops-in-contact-v10-released-now-on-github/

Honestly any medium or heavy lift helicopter is going to be celebrated like there's no tomorrow. CH-53, CH-47, UH-60, SoopaPuma, Sea King, UH-1Y. This is where the gap is. A fast, Western lift helicopter will close it.

It's not the UN/PW that is at issue here but the hardware ID.

Thanks man, was hoping you would pop in. That certainly simplifies things but brings some other considerations. Does the dedicated DCS even run on Windows Server 2019 or 2022, or does it HAVE to be Windows 10? The license fee for windows server editions makes the cost/benefit no longer worth it. Outside of Azure, I don't see hosting companies even offering Windows 10 as the native OS.

Hey yall, looking for some pointers from others who have set their squadrons up in a fashion like this. We're considering moving up from self-hosted desktop computers acting as BSD's dedicated server base to getting our own Linux server and running 3-4 DCS instances on Windows VMs there. I'm a Linux guy by trade, so I am not unfamiliar with setting up and managing that part of it. I know some have used promox for this. Is there any advantage to it over kvm? I'd prefer kvm personally as I'm very familiar with that. Aside of using virtio drivers, what are some other performance vagaries you've watched out for? If there is any other guidance, tools, or resources you can point me to I would appreciate it. Thank you!

If that were changed to match the coord format the map is already in (e.g. MGRS) it would be a platinum level improvement. But the other improvements suggested are really good too in terms of making them act like IRL. Being able to adjust bracketing rounds in, then fire for effect etc.

This is reaching to extremes in order to position a fringe, edge case as the center of gravity for mission designers. The people commenting on this here ARE mission designers and code maintainers of various projects, and are speaking in general support of what is being requested. If you read more carefully, every single static and unit from EVERY coalition appear this way. It's ABSOLUTELY TRUE that people who actually make missions do not want every friendly, neutral and enemy unit and static recorded in the internal systems of their aircraft, by DEFAULT. There is no credible use case for this. Please, let's allow the thread to get back on track.

Thank you! Is that done in the (unpacked) mission file?

This affects more than the Apache, that's just the easiest example to point out. Which aircraft do you believe benefit from having every single blue, red, and neutral static and unit consumed into their internal systems, and would be harmed by this? I cannot think of a single case. The "Default" we're speaking of here is this - assuming that a mission designer wants every friendly, enemy and neutral static to be automatically visible to internal systems unless those manual checkboxes are checked. Nobody creating missions wants this. The default behavior in this case is literally the opposite of what it should be. I trust ED to determine the best way to handle it.

To be clear, I'm asking for either the boxes to present themselves as checked when the unit is put on the map, or to have a mission level option to apply that to all. It's literally filling up the TSD's memory on the Apache with every single unit and static on the map. It can't stay this way.

This is a key reason why mooti-CRU has been far superior to a single crewed Mi-24 or AH-64D in terms of mission performance, survivability, etc. A person will always be better, but this will help a lot to close the gap. Very much looking forward to it.

Hopefully this one gets picked up!

Sadly I think the Cobra has already been hard nacked. But one can dream.

Current behavior creates a Control measure in the Apache TSD, and a point in the KA-50 ABRIS for every unit, and static on the map, even if late activated. This fills up the available entries with eight pages of garbage and prevents new points from being entered unless others are first deleted. Either make Hidden on MFD/Hidden on Planner default to checked, or offer a global override setting that permits all to be hidden on MFD and Planner. Mission designers would never want every static and every unit from every coalition populated into the aircraft's systems this way. The default behavior should follow what people are doing nearly 100% of the time, and right now that is reversed.

Right now, the default behavior is that every unit and static on the map gets represented as a control point in the AH-64D or as a point in the Ka-50's ABRIS. Statics, Units, and even late-activated units. From any coalition. Since it's obvious that almost no mission designer would ever intend every single asset to be treated this way, has anyone requested yet to: 1- Add a checkbox/feature be added to the ME that would check these options at large for all assets. 2 - Alternatively, pre-check "Hidden on MFD" and "Hidden on Planner" such that they are hidden by default. I've searched around and haven't seen this as a request yet, but this would be huge. I know it affects the Black Shark as well as the Apache, and likely others too.

What Coalition? It needs to be in the blue coalition.

Yep, they don't fire and are not indicated on the F10 map on Caucasus. They are not floating though. Bizarre.... @currenthill dcs.log sent in pm, thank you!

Can someone else check please? I've reinstalled it and same behavior.

Hope this helps with testing but I tried out the RBS 58 guy, and they are neither showing up on the F10 map nor firing. Sometimes going "airborne."

I actually prefer a separate structure, as I can pick and choose which ones our squadron wants to have.