gospadin

Out of curiosity, how would you know you were monitoring guard? There's no communications on that frequency without using something like SRS, which can implement that separately anyway, no?

I'm pretty sure the earth isn't flat in DCS.

use uboats' tool here: https://forums.eagle.ru/showthread.php?p=2662000

Yea, there's also an embedded PID controller or something on the parameter API that gives values "momentum" which is really annoying too. Makes for some VERY funky behaviors if you don't code stuff correctly. It was obviously intended for mechanical gauges, but we've extended it to all our inter-system communication. I had forgotten about using it to talk to the EFM, thx. --gos

FC3 is really a unique set of capabilities. They have simplified engine and systems management, but I believe that's a choice not a limitation. Weapon employment in FC3 (among other things) uses functions that don't exist in the SSM Lua API. As an example, I can change radio channels with Lua, but without the C++ API I cannot turn the radio itself on, thus preventing us from talking to ATC. --gos

We're not above walking through ED's Lua code in the base installation to see how certain things were implemented, which has helped us figure out how to define new weapons and certain other capabilities. We see reverse-engineering the C/C++ APIs as something that wouldn't be "right" and would likely jeopardize any potential future licensing from ED. If (no, this isn't confirmation) we decided to do EFM/ASM in the future, we'll apply for the license. If we get it, great, if not, we'll just stop work and move onto other things. No matter what happens, this has been a great educational experience for everyone on the team. --gos

My understanding (possibly wrong) is that we can keep basic LUA systems if we wanted to, but we would lose the ability to have systems influence flight behavior or vice-versa because we cannot share data between LUA systems and an EFM without knowing what the API calls are. Basically, the LUA systems calls are limited to the 25 or so primary functions, but if we were to have, say, asymmetric fuel drain due to a pump failure, there's no way to detect that from the Lua (and thus show it on the fuel level indicators) because the API is limited to C++/ASM. --gos

They were used extensively by the USMC at Chu Lai. About 9 months ago I added Leatherneck's MiG-21 JATO bottles to our A-4, and they shot a lot of flame, but didn't provide thrust. I don't think we can actually implement them without the SDK. --gos

Nothing. We created it from scratch and it is fully self-contained (except for weapons available in CoreMods, which everyone has access to.)

It won't shine like the F-86, because the underlying 3DS material is different. I think all this gets fixed with 2.5 with PBR, but will require an update to all models.

Thus far, we have done our best to push the limits, and we've gotten a lot of positive feedback that we appreciate. Our ability to do an EFM is probably there from a skill perspective, but to be honest, it doesn't seem that important to us right now since we don't also have SDK access for the advanced systems modeling. Maybe that's something that can be worked out with ED in the future, but for now, we're sticking to our original goal of "free release of SFM + as much systems modeling as we can do without the SDK." The SFM isn't perfect, but for most of the flight envelope it's pretty darn good. I also would like to point out however that most of the FC3 planes (except for the MiG-29 and Su-33) use PFM, which is a very advanced flight model. FC3 systems modeling is simplified, and they're not clickable, but they fly very accurately. --gos

You can definitely beat the AI, but you have to use your noggin. You can't just orbit at 25,000' like the A-10.

This, basically, everything but the terrain height map is transparent to AI. (And it was funny when that was bugged about a year ago)

They can only be applied to full-price offerings, sorry.

Those values are just passed to the module at initialization. They'd need to add keybindings/commands to support modification while flying.

it's broken at that point

Best of luck to everyone involved. Breaking up is hard to do, and I know you'll come out of it as a stronger team. --gos

This actually mirrors real-life ROE throughout history much more closely. There's been remarkably little BVR combat in the last 50 years as compared to WVR. --gos

So on my main PC now, and can't find any changes that would affect my mod. If someone has a bug or problem with the Nevada_v3 page I posted here: https://forums.eagle.ru/showpost.php?p=2957802&postcount=5 please let me know. --gos

Thanks for the update, we're hoping alongside you! --gos

True, but enough of us in the mods forum speak Spanish that for a mod-specific question, it's probably better answered in here. --gos

So I just updated 2.0.5 on my laptop (currently traveling) and it seems like the channel to frequency pairings are setup differently in the latest NTTR update. Since I don't have any modules installed on this machine (nor space to do so), I'll need to investigate when I get home and I have access to my main dev system. I'll get it fixed shorty though. --gos

We looked into how the S-3 was constructed, and are copying some of its techniques. Hopefully we can get it to work.

We've done a ton of experimentation, and no success thus far. It would appear to be an AI-only capability, or maybe requires something in the ASM that we don't have access to. We will have the D-704 buddy refueling store with drogue modeled, but don't expect it to be functional. --gos

I've updated the first FAQ answer (post #2) in response to your question: This mod will be free of charge, and you'll need to download it manually --gos