mattag08

So glad DCS finally implemented this. It's unfortunate that it took this long to provide such a basic MP feature. Hopefully this has improved some of the MP servers.

Disregard, I figured it out. Here's the code if anyone wants to do something similar: local blue_pos = mist.getLeadPos('wolf1') local blue_pos_north = mist.projectPoint(blue_pos, 6000, mist.utils.toRadian(360)) local teleport_north = {} teleport_north.point = blue_pos_north teleport_north.gpName = 'north_mig23' teleport_north.action = 'respawn' mist.teleportToPoint(teleport_north)

Is there an "easy" way in MIST/MOOSE or the base editor to set up an F10 spawn relative to a player unit/group? I'm currently trying to puzzle out a way to create a BFM/ACM trainer mission. The goal would be to allow the player to select from options in the F10 radio menu such as "forward quarter", "beam quarter", "rear quarter", or "random" and have an enemy aircraft spawn in that area. I would need to be able to define a distance, range, altitude, speed, heading, etc. for the unit spawned and make all of those parameters relative to the unit (or preferably the centroid of the group) requesting the spawn. I'm sure this is possible with enough code, but I frankly don't have the time to write the entire thing from scratch. Are there any functions in MIST/MOOSE/etc that provide a functionality like this or has anyone been able to produce something similar? UPDATE: I've sorta got the logic of what I want to do down, but my LUA skills or MIST understanding are clearly lacking. Here's what I came up with, but can't get to run: blue_pos = mist.getLeadPos("Wolf 1") blue_pos_north = mist.projectPoint(blue_pos, 6000, mist.utils.toRadian(360)) teleport_north = { point = blue_pos_north, gpName = "north_mig23", action = respawn } mist.teleportToPoint(teleport_north) The goal of the code here is to get the position of Wolf 1, adjust that point 6,000 meters north, then create a table for MIST to use to spawn a Mig-23 group there. If anyone could help with what syntax or other error I'm making that would be super.

You need to rebind the command after restarting your sim. When you change values in the input files DCS reads that as a "new key" and all binds associated with it are lost. I just tried to edit the defaults.lua file and it works exactly as 450Devil described.

I have this same issue except all of the LODs are missing except the closest one. Did you ever find a solution?

Weird maybe I have them turned off.

Am I the only one that doesn't see a signature?

I wouldn't worry about it. Based on replies, he has no concept of modern BFM and the E-M diagram or else he would actually understand the relevance. Best to ignore and move on to more productive things.

Not to mention the flight models of most REDFOR aircraft stray quite far from reality in many regimes. Use DCS E-M diagrams, not real world ones. You must implement tactics that work in DCS because players do not need to worry about things such as G and physical exertion. Many maneuvers used in DCS would sling your head into the canopy and cause a concussion. On the other hand, you have people saying never go pure vertical, but that is exactly how Randy Cunningham defeated Col. Tomb in his Mig-17F. There's no absolute 100% winning strategy and you must adapt to your opponent, energy states, etc.

I was being facetious, but if you want to be serious all of the features you mentioned took ED approximately 10-15 years to implement, so expecting anything near term with them is a fools errand. Not to mention ED has a history of two steps forward, one step back when adding features to the game.

Absolutely nothing. There is no money in it for them if they update those AI. I mean there is in the sense that DCS would be a better sim, but they don't view things that way. They only care about short term cash infusions from new modules.

This issue is still open on the Leatherneck bug tracker...

Sorry, but you can't bully me by using terms you learned in middle school science class. Unlike yourself, I know better than to give ED even a single ounce of credit. I've been a paying customer of theirs for over 20 years and I've observed the glacial pace of development first hand playing each new iteration of this simulator since LOMAC. If they wanted us to have a DC, we'd already have it.

Whelp, it's been 13 YEARS since I posted in this thread: Interesting how we have made zero progress in that time. Someone could've programmed 2-3 full new flight simulators in that period. Will Nick and co. ever see the value in a Dynamic Campaign and invest the resources or will they just limp along and pump out half-baked modules to stay afloat? It would be fascinating to hear from someone at Eagle Dynamics why dozens or even hundreds of professional developers could not achieve what a single Microprose intern could over 26 years ago.

"Foe" responses don't really happen anymore from what I understand. That's only possible if one side has cracked the other side's transponder/DL tech and has developed systems for that. Almost all IFF is friend or nothing. The real reason for VID is because you don't know if "nothing" is a passenger airliner or an enemy bomber barring some other form of ELINT or SIGINT (or NCTR). In my previous group we started to place 1 or 2 civilian or neutral faction aircraft near or in the AO so that you couldn't know if a negative return was enemy or not. Sometimes I'd even make the neutral faction aircraft actually hostiles that would attack the players. That meant you couldn't trust the IFF to be 100% accurate and had to actually make decisions based on all available information. It took a few missions before people learned what that meant (2 or 3 airliners definitely went down in the Mediterranean ).