Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Easy location input/transfer/scrape from .miz file #26

Open
Steveveepee opened this issue May 23, 2021 · 2 comments
Open

Easy location input/transfer/scrape from .miz file #26

Steveveepee opened this issue May 23, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@Steveveepee
Copy link
Collaborator

The mission planner should be able to get waypoint data for flight waypoints, target waypoints etc from the mission file.
see:
https://github.com/pydcs/dcs
https://github.com/Santi871/DCSWaypointEditor
for implementation details

@Steveveepee Steveveepee added the enhancement New feature or request label May 23, 2021
@jvanlint
Copy link
Owner

I think this needs some fleshing out. How is this supposed to work? Which values do we read from the mix file for example. Where do they map to?

@Steveveepee
Copy link
Collaborator Author

I've been tinkering on this recently, and it's pretty do-able.
It might be more beneficial to import the flight(s) data from the .miz rather than the waypoints. (both are available to import)
Thinking that importing multiple flights with multiple aircraft slots worth of info from something like a Liberation .miz file would be easier than having the mission maintainer manually building the packages/flights/aircraft slots.
However, the way liberation groups change multiple times before a mission is finally generated might make this unuseable, and a more generic mission sign-up system that then informs the mission maintainer what to set in liberation might be more in order? See Floydiis latest sign up form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants