Jump to content

Exorcet

Members
  • Posts

    4771
  • Joined

  • Last visited

  • Days Won

    6

2 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. AI aircraft need waypoints and actions in those waypoints to function. If an AI has no waypoints or reaches the end of its waypoints, it will try to land at the closest non hostile airbase. You can find the actions by clicking ADVANCED (WAYPOINT ACTIONS) and adding them to the list. Some are added by default based on the TASK assigned to the AI. The default CAS action is a way to get the AI to act, but I don't recommend it. Most of the default actions give you limited control over the how the AI acts and can make them do weird things. Instead you can use tasks like Search Then Engage to give the AI a mission and better control how they operate by limited range of engagement, weapons used, targets assigned, etc. Keep in mind that the AI has to find a target before engaging. Detection abilities vary with different units. If the AI needs to search an area it helps to give it an Orbit waypoint action to make it fly around a specific waypoint or pair of waypoints. This can be a lot to take in if you're new to the ME, but if you provide more details someone can set up an example for you easily. Or you can share a mission file and have someone add units to it.
  2. You may not necessarily want to preserve the mission (and even if you do, opening it causes no damage, only saving does), but instead want to get information out of it. In that case being preventing from opening the mission is a massive hindrance. Keeping the mission open also makes sharing a lot easier since the person you're sharing it with doesn't need to know what mods are required. You obviously can't share for the purpose of running the mission, but you might for troubleshooting. I don't disagree that it can protect the mission from damage, but it's still a bad way to do it since it also keeps you from accessing the mission at all. Yes it would be frustrating to accidentally save over a mission, but preventing that doesn't require locking the mission. There should be protection of some kind, but I'd rather it not be totally preventing the mission from being open as that just causes additional problems/work. If the functionality is reverted, there should be a checkbox to disable the file locking at the very least. I like having the name changed to prevent accidental saving if the mission cannot be fully loaded, there just needs to be a way to make that clearly visible to the user. Maybe forcing the save button to show a dialogue that explains the issue with the mission.
  3. Having the ability to open any mission without needing to install additional files is very helpful. Locking the mission file completely isn't a great solution to preventing accidental changes, instead there could be a popup box warning about the missing mods as well as affixing a suffix to the mission file name so that if it's saved it can't overwrite the original file unless the user intentionally uses "Save As" (though if people don't notice the file name change, it could cause some confusion). A checkbox option like @Elphaba mention could also work.
  4. This has nothing to do with the MiG-29. It's the conditions that change how the vortices look.
  5. Since the hardcoded (assuming they actually are hardcoded) values were wrong in the past, the radio.lua is probably correct. You can report map issues here: https://forum.dcs.world/forum/520-bugs-and-problems/
  6. Unfortunately I do not. The ME entries may be hardcoded. There was an issue on this map where the ME frequencies did not match the actual ones in the past.
  7. This is correct. I was going to post this when I saw the thread earlier, but I didn't see any mention of the save changes warning in the original post so I thought it might have been a different issue. While it's unintuitive, I can see the mission zoom setting being a save feature. I think it also changes the default F10 map position when starting a mission. That said, it can also be annoying. I'm used to it so I don't find it a big deal but disabling the temp mission feature could be a useful option. Some time ago, the ME would auto open the last played mission in a session which was something I found helpful. It would even open the mission if you had not saved it. I think that would be a nice feature to have return as an option as well.
  8. Going only by the video posted above, at sea level and clean, the F-16 should at least equal to the DCS aircraft currently ahead of it. What you say is true about A, though the C is no slouch and does have more thrust. In fact as far as I know, I think the Blk 30 C's are generally considered the best anecdotally.
  9. It will depend on how deep you want to go. You can give a few groups a route that has them push toward each other, then copy and paste them, and you'll pretty quickly have a large battle. But the two sides will just be charging at each other until one side is dead (or gets stuck where the other side can't see them). A step up from that is to give the group multiple waypoints and then use the go to waypoint command to dynamically make them advance and retreat. The AI isn't going to do this intelligently, but it can increase their survival rate and prolong fighting. This isn't something I've spent much time on as I usually limit my ground units to smaller numbers. You can have large battles, but your PC hardware will have to be factored in.
  10. This is absolutely true, but the process is a bit tedious and without a detection trigger, you can't truly tie SAM behavior to sensors without scripting. I know the IADS module fell through, but some simple solutions for improved SAM behavior would help a lot. Things like a waypoint/triggered action to make SAM's flash on/off, an option to have them turn off in response to attacks automatically, and an option to link a SAM to EWR or AWACS and use radar for "attack only" like planes.
  11. Thanks for the confirmation. The F-16 model is quite good. This is not a massive error, and my flying wasn't perfect, so if it's deemed to be within tolerances I can understand.
  12. The disperse under fire is a very important option for ground units, I'd recommend considering how to set it for every ground group placed on the map. Luckily you don't have to check and uncheck it every time you place a group. I like to place a few groups down when building a mission, set their settings, and then copy and paste them as needed to save some time. DML's spawning tools can probably do something similar.
  13. A campaign built around exploring anti stealth tactics could be fun. I've had an idea for this using the F-117, but have not been able to devote time to creating the missions. AI F-35's wouldn't just have to serve as adversaries though, they could be interesting as allies as well. Fly with them deep into enemy territory and make use of their SA to survive beyond the range of friendly AWACS. Or you act as a supporting missile truck to offset their reduced weapons capacity when flying in a LO configuration. While there are a lot of AI assets that DCS could benefit from, I don't think the F-35 is that wild of a choice to add.
  14. That is an ammunition explosion. Certain buildings will detonate that way, I believe all the ammunition warehouses in the static object list. I don't think you can generate that explosion arbitrarily, but you can place a warehouse nearby and force it to blow up.
  15. This is still labeled as "PM Evidence" so I wanted to follow up. Do you need more source information?
×
×
  • Create New...