Raf

Hey did you figure out how to do it properly? I am currently looking in how to make a binary lua module in rust to load it via require in DCS. My module checks out fine in a downloaded 64bit lua 5.1.5 interpreter, but when I run it with the one in dcs folder, it keeps getting 'The specified module could not be found."

Considering what I can guess from the lua code, I assume N would be a big change. (programmer here) But I don't think you need really a lot of them either. Even if the current neutral would be active and flyable, that would be already a lot.

I've wrapped up this single one that can be included in missions via the add script trigger at mission start. I'm using it to track which fuel, crafts and ammo were consumed at mission end, by looking in dcs.log when the mission is closed. consumption.lua

Yes, I know there is a neutral coalition, but that's not useable in multiplayer and probably warehouses won't work for that one too. Unless you can find a way to make that one work somehow also in multi. I wish there would be a 3rd coalition (green? yellow? whatever color!). With that available I could see how interesting a 3-way conflict would play out, as each coalition has to guard against 2, and their moves would be more careful.

Hi, in the hope it can be useful also to other people, I link over my script that I use to keep watch on warehouse usage: https://github.com/raffaeleragni/dcs-scripts/blob/master/ammowatcher.lua Not everything is detectable by dcs design, only ammo and fuel is. For fuel you will need to complete the section of vehicle tank size if it's not already in there, in the definition inside. Prints it out in the logs when mission is over.

Well, at least this gives me a better chance to organize my plans with squadron members on what's going to be available more or less in which order. I also think it's only fair that the 18 is getting finished first before pushing work into new modules that came after. I hope though that labeling something 'out of early access' is not an attempt to consider it finished, and taking advantage of such 'formal' state, when finished is actually not.

(found an alternative solution)

Hi there, I am trying to develop some tool that integrates integrate on mission creation. In order to do that I'll need to place units via the x/y coordinates, but all I have in my side are lat/lon. I have already been searching this for days: the only thing I found is coords.xxx method but those run only inside the sim. I even looked where that function is actually implemented, but I can't figure out exactly what is doing, my assumption is that it's using the terrain library too. I assumed later it's gonna be a different function for every map. I noticed there is a stretch+rotation for the LL lines in the map, right now I'm looking at the caucasus, maybe is enough if I calculate that somehow, the work seems tedious tho. Is the x/y always a distance in meters float? If so it could help a bit at least, because in such case I only need to take care of the rotation and not of the stretch, because I would use some known formula for earth-distance calculations.

Actually I noticed this since months myself, always thought it was some bug or missing implementation that I needed to wait to be done... Not sure why but yes it happens in very close range if you acquire (without approaching from afar). Especially with HMD boresight lock.

This behavior is a problem actually for other reasons too. Try to use a laser maverick from a slaved position on tgp when you have to lase. You are forced to undesignate or the mav won't work. Same with IR mav actually as you have to point the thing on it.

Even when the MAV is deselected afterwards? Because sometimes that also happens. Unless this post meant only when MAV is also selected.

Still happening, FYI.

Is it possible now to do it? To manipulate airfield inventory via scripting I mean.

Yes and it doesn't work

I would've thought the MSI bug (viewing only radar touched contact instead of all DL given ones) could have been addressed at least... oh well.