Search the Community
Showing results for tags 'api'.
Found 10 results
-
getInventory gives a complete inventory for a warehouse, but seems to exclude items that are fully depleted, instead of returning "0" as the qty. If i use warehouse.getItemCount(wh, <depletedItem>) it will return 0, showing the warehouse has the item, but its qty is 0. why does getInventory exclude 0-qty items?
-
Hiya! When building multiplayer missions having runway strikes being done and available always adds quite a thrill. However, when it succeeds it's hard to continue to adapt the balancing. Currently runways are only repaired after 60 minutes (hardcoded) as far as I can see. What would be awesome if would for example be something like: ---repair the given runway for operations ---@param runwayName string @the name of the runway, as also specified in Airbase:getRunways() function Airbase:repairRunway(runwayName) end ---OPTIONALLY ---sets whether or not DCS will automatically repair runways after 60 minutes ---@param autoRepair boolean @true or false function Airbase:setAutoRepair(autoRepair) end The idea is that in bigger dynamic missions it would be awesome to balance the runway repairs ourselves. (eg. faster when the resources/personnel at the base are higher and slower when certain resources are lower). The second function would be to disable automatic repairs. This would be in line with the logic of airbase captures, where you can also enable/disable the automatic capture and then force the capturing yourself. PS. Removing the craters itself doesn't repair the runway it seems via world.removeJunk() as AI doesn't want to take off even when the runway is pristine after that. PPS. To all those having the itch commenting underneath here that it wouldn't be realistic. Please just don't. This would just add options, and options are what us mission makers can use.
-
DCS is actively trying to bring in more players / pilots. As mission writers and story tellers, the Mission Creation community is constantly looking to make more exciting and engaging content to be flown.. This "wishlist item" could be taken as an opportunity to review the API for known and reported defects and enhance it in a phased approach. This could include more event handling which will allow creators to embellish their ideas further and draw more attention to the DCS product: F7 troop management events (not limited by zone) embraking disembarking Cargo events (dynamic and classical "F6sling-load) including unhook (pure unhook, not limited to zone) Effectively any task to be paired with start/end events Review of existing events to identify those never raised and either remove or correct why they are not being raised Feel free to comment to suggest other API fixes, with links to the relevent forum post describing it and i will update this list
-
Overall, how well will the AIM-54 with the new API perform compared to the current AIM-54 that we have now? Will they have better CCM? Will they be harder to notch? Will they have longer range because it won't do the high-G turns that drain all its speed in the terminal? Will the AIM-54C-Mk47 be finally a viable alternative to the AIM-54A-Mk60? -
world.event S_EVENT_PARATROOPER_LENDING Warning in Log: CREATING PATH MAKES TOO LONG!!!!! -
Hello, So, i was messing with mission making and scripting and noticed that I cant use getLife call for object scenery, it was used to be callable on scenery. But now it returns just an assert saying the object does not exist. For example: SceneryObject.getLife({_id = 85296214}) which is this bridge south west of Aleppo in the Syria map: Returns this: The object ID is correct and is valid, but the error is there. Thanks in advance.
-
Hello, I have recently taken a real interest in making my own peripherals for DCS. Stuff like MFD, gauges, switches, collectives and stick. You get the point . I would like to export things from DCS to my hardware. Think about things like: -MFD screens -Gear status -Fuel status -Warning lights -CMS program info Now I saw there is some software for that, but it looked like a work around. I am personally not afraid to get my hands dirty with code. So I would love to have a official API for DCS that makes it so that I can extract information about the aircraft status. I know things like fuel status will only be used by more dedicated simmers, but exporting MFD screens is something a lot more people would do if it was officially supported. The reason I don't like work arounds is that they can break any time.
-
The lack of getters in the api means that we have to create additional look up tables for all scripting spawned units/groups etc... and have to keep going back to them. That's memory, processing overhead, just because of a lack of useful getters on Group/Unit objects. Please fix this glaring omission.
-
reported earlier Neutral units are always visible in F10 map
OzDeaDMeaT posted a topic in General Bugs
This bug has possibly been around for a considerable amount of time but is present as of 2.9.5.55918 Bug, when using the coalition.addStaticObject function command objects will ALWAYS appear on the map no matter what Map configuration you have set. (Map Only, A/C Only, Ally Only) The object always show up. Can you please fix this bug but if you could find the time to add the same functionality from the Mission Editor to the DCS Mission Scripting API to allow us to spawn new static objects as hidden I and surely many more DCS Mission Creators would be very grateful. Can create a mission example of this happening if required. -
Since the last BETA update, the event.dead isn't called, if a unit isn't immediately dead, see attached demo. The death is registered in the ME event log, but the API isn't called. Reported by dcs-online.de and [WP] Stingray in the Moose Discord. event dead test.miz- 66 replies
-
- 11
-
-
