Statua

@NineLine Bumping this because scripting is what is keeping DCS alive. There is not one single popular public server out there using vanilla DCS mission editing. Moose and Mist developers have gone above and beyond what is provided to us in the API and have made insane workarounds to do things that would be easily done with a simple API call. The modding support in DCS is pitiful compared to the industry standard of mod-supported games and it is up to you guys to fix that. If you genuinely put playes first and money second, then go look at MIST. Go get involved in the Moose community. Talk to these people who are working hard to make this game fun for people and find out what they need.

If ED staff is relying so heavily on the community to support this airframe during EA through mods and scripting, why are they not involved very closely with these communities? I do not see a single staff member actively engaging with members in the Moose discord, one of the most popular and versatile script libraries. Providing more API access to in-game elements such as sling load events and having a more reliable multiplayer aircraft crash event are a few of the most critical features that are holding the scripting community back. We want to fill in these gaps while we wait for an official logistics system to be produced. I'm also wondering where community feedback and direction for a logistics comes from as I have not seen ED ask about it in the Moose discord or any of the rotary wing communities.

Still having issues with the updater throwing a 'File Already Exists' exception. This is the behaviour: -If I open the updater and leave the Presets on Default, it works as intended. I can switch between MT and ST as well as use the VR ON/OFF buttons. -If I change the Preset to something else like VR or one of the other 4 presets, it throws the exception and does not launch DCS -If I restart the utility after the error, I have to change my preset back to default for it to launch DCS again I don't know where to find the folder that contains these files. In Saved Games\DCS Updater Utility, I only have logs, THEME.xml, and an empty Backup folder. Idk if this is relevant or not, but my DCS root install is on E:\ whereas the updater utility and SavedGames is on C:\

Any chance you could get this fix pushed out soon? There's like an 80% chance that I get the "File already exists" error when I try to launch the sim.

The overlays which are used to indicate farmland on the map (ALT in the ME or F10) are great, however they lack countour lines which makes working in those areas very difficult. The contours really help with working in the ME and planning things like LZs for helicopters. Here's an example of this being a problem: Say I want to build a FOB for helicopters to refuel at and I find a nice little spot in this town. So I place all of the objects there: null Now I load into the sim and I find out I have to go find another spot because this one is no good: For anyone else who has issues with this, you can disable the overlay for now: 1) Go to DCS World OpenBeta\Config\terrain 2) Open terrainoptions41.lua 3) Search for hiddensemantics 4) Remove the -- from in front of "Field" It isnt perfect and I really would like to see the field overlay again, but it works.

Waiting for the day ED realizes these should be in the base game... In the mean time, is it possible to separate your infantry from the sweedish pack? I really want to use these guys as transportable troops for our helicopter squadron, but cant get behind making everyone download 12gb for it. If not, it's cool. You have made some phenomenal assets for the community here and I can really appreciate that.

debugtext3.mizHow about an empty miz to test with? I'll also attach the log and trk from our testing. dcs.20230422-221221.log dcs.20230422-221221.trk

When you delete a textToAll() F10 marker using the removeMark() function on a multiplayer dedicated server, it causes the server to crash. -Deleting standard DCS F10 markers is fine -Deleting circleToAll() is fine This was tested on a dedicated server using the latest version of MOOSE to access those functions in a bare mission.

Man I would absolutely love this to be available for scripting. Bumping in hopes that this may be seen.

Amazing thank you!

Hi are you still keeping this updated? I'd love to use it for our persistent campaign server, but your forum link appears to be dead.

Yeah this is hella broken. Working on a new mission. Created a late activated unit with a single triggered action of GO TO WAYPOINT. When I try to set it up in my triggers, it has a few issues that you can see in the attached image:

Having this issue as well. Exactly as described. Except after I remove the unit, the bug still persists. It seems to affect all units with triggered actions and they all must be deleted first. EDIT: It might be more than the static template. I have several groups with triggered actions to SET FREQUENCY and TRANSMIT MESSAGE. I noticed the triggered actions disappear sometimes and I have to double click or triple click on the unit to select it when this happens.

Having this issue with ground units too. Only way to move the actual unit is to restart the mission editor.

Been over a month and no reply so bump. This issue bothers me as I use a nice shiny paint job on some training helicopters that is ruined by this bug because we don't use hardpoints.

Thank you for fixing this! Us rotorheads at BSD are extremely grateful

Good find! I hope this applies to the forest layer in general across the map.

Bump again. Recent update made the workaround no longer work for the F10 view. It is now impossible to see any contour lines on the west coast of Syria while flying!

When you remove the hardpoints from the airframe, the tail reverts to the default specular rather than the modded specular. Can be replicated by using the Royal Australian Navy skin and removing the hardpoints. This happens on all liveries with a modified specular. Hardpoints removed (bugged) Hardpoints added Here is the code from DCS World/Bazar/Liveries/uh-1h/Australia Royal Navy/description.lua

Bump. I realize this primarily only affects helicopter operations but we're paying players too!!! Really hard to make a flight plan when the entire valley is solid green with no contour lines.

I believe this mod is causing a crash to desktop when someone joins your helo or you try to join someone else's helo.

1) Do not allow artillery or bombers to create a large mess of bomb craters. These are highly unoptimized overlays that exponentially eat away the framerate as they multiply. 2) Be stingy with the deck crew models. They seem to impact framerate quite a lot. 3) Only use small details like traffic cones, signs, ammo boxes, etc in locations where the player will be stationary or not moving around much. Examples include the parking spot. Rearming area, or near any helipad. 4) Use low quality airplane models for background parked aircraft. (such as the f-18 and f-16 low quality models) 5) If you are using rain, be extremely vigilant with everything else. The particles in DCS are also very framerate heavy and rain has no shortage of that. 6) Consider splitting groups of 12 or more aircraft to two or three different starting positions to minimize "base lag".

Rivers don't have anything to clip into at the bottom so vehicles just bob along or get eaten by the river and disappear entirely.

Flappie has brought some insight to this issue with a temporary workaround. This is honestly the most ideal view of the forest layer in my opinion. You can still see the trees at higher zoom levels and the terrain underneath. I hope for the sake of everyone working on missions in the mountains this gets implemented in one way or another.

This is immensely frustrating and I'm concerned it's not being addressed. This first image is of a mountainous area in the ALT view. Imagine trying to place a FOB or SAM site here, not knowing if its in a valley, on the side of a steep hill, hanging off a cliff, or at the top of a peak. This second image is a cropped and blown up photo of the same area zoomed out to the point the green layer no longer shows. As you can see, it is immensely varied with very important contour lines finally showing up.