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

Select pre-existing map military installations for deployment locations #3

Open
jmlane opened this issue Sep 7, 2018 · 6 comments
Open
Assignees

Comments

@jmlane
Copy link
Owner

jmlane commented Sep 7, 2018

MOBs and FOBs might be placed in pre-existing military installations on a given map. This needs to be addressed as an exceptional case for the position selection algorithm for the owning elements.

@jmlane jmlane self-assigned this Sep 7, 2018
@jmlane
Copy link
Owner Author

jmlane commented Sep 7, 2018

Let's discuss approaches. I'd prefer map-agnostic solutions that don't rely on design-time objects added to missions.

@jmlane
Copy link
Owner Author

jmlane commented Sep 10, 2018

@Diffusion9 I think you have some experience with figuring out map military installations based on world objects. Your advice is appreciated here.

@Diffusion9
Copy link

I would also generally prefer a map-agnostic solution.

There is so much inconsistency and variety in those bases it is difficult to programatically populate them without just doing something really vanilla and bland like spawning units inside the existing buildings and just calling it a day.

We could try a hybridized approach; Del could manually mark locations on certain maps, we could store those positions in an array, and he could make one (or a variety) of different base styles that would go into each special location.

Then we could do a check at runtime, figure out what map it is, if those positions apply, and then execute appropriately. That way we're not relying on needing to use a specific mission.sqm, and if Del makes a couple of different styles for each base then there is at least a little variety there.

@DEL-J
Copy link

DEL-J commented Sep 10, 2018

My plan was just use system markers to mark existing base locations, and have them populated in a bland manner, but we'd also have convoys originate at the marked locations.

@jmlane jmlane assigned jmlane and unassigned jmlane Oct 2, 2018
@jmlane
Copy link
Owner Author

jmlane commented Oct 2, 2018

I'm assigning this to @DEL-J. For the ASG MVP, we'll go with whatever works best for him. In the future, I'll want to cook-up a map/terrain independent system, but that's out of scope for this issue.

@jmlane jmlane changed the title Select preexisting map military installations for deployment locations Select pre-existing map military installations for deployment locations Oct 2, 2018
@Diffusion9
Copy link

Diffusion9 commented Oct 2, 2018

Re: marking the existing base locations using markers: Instead, maybe try using createLocation for @DEL-J's custom locations as we discussed one day in the Boardroom chat.

createLocation :: createLocation [_className, _position, _sizeX, _sizeY]

Creates a location of the specified class and dimensions at the specified position. Classes are defined in CfgLocationTypes.

_location = createLocation [ "NameVillage" , [4035,2151,10], 30, 30];
_location setText "Player town";

This would let him create his custom locations, and you can programmatically generate your system that is map-independent, as all things should be /thanos.

@jmlane jmlane self-assigned this Oct 2, 2018
jmlane added a commit that referenced this issue Oct 15, 2018
Save the output of fn_deployForce.sqf to some persistent store and feed it as the input ORBAT for identical deployment. This resolves #5.

The position array can be pre-populated for as many or few formations in the ORBAT as desired (useful for #3).
jmlane added a commit that referenced this issue Oct 15, 2018
Save the output of fn_deployForce.sqf to some persistent store and feed it as the input ORBAT for identical deployment. This resolves #5.

The position array can be pre-populated for as many or few formations in the ORBAT as desired (useful for #3).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants