unstartable mission, Can't find maps/mine.bsp

[anonymissimus]

Attached is a save with a Herakles dropship holding over an "Old Mine" mission in southern Africa. Attempting to start that mission fails.

So this will be my first lost mission since I need to ignore it. Not too much of a difference, as this is one of the bloodiest maps. None of the civilians placed inside of the mine have any chance to survive. I only managed to save at least half of the civilians only once out of many times, since in that case there were only 4 and 2 of them on the surface.

[ShipIt]

Please note the sticky about reporting a bug.

[anonymissimus]

Please note the sticky about reporting a bug.

The only thing that's really needed is a way to reproduce the problem, provided by a short description, which should be as clear and easy as possible. Other than that, requiring to attach this or that is just useless work. You cannot expect bug reporters to do that.
For instance, I could have attached the log, but why should I have. Fixing the bug requires reproducing it, which will inevitably yield the log as well.
It makes much more sense to ask a concrete question, if one is unable to reproduce or so, instead of just pointing to bug report guidelines, in which case I have to wildly guess  what could be needed.

[Duke]

Do you have a file "base/maps/mine.bsp" ?

[anonymissimus]

Do you have a file "base/maps/mine.bsp" ?

No. Only mine.map. Should I ?
I also ran contrib/map-get/update.py after encountering this problem, to no avail (no self-compiled maps).
Do you have that file ?

EDIT
Okay, it seems that the *bsp files are under version control. As there are no local modifications in my checkout, someone apparently forgot to add that file to the repository.
However, I wonder whether that map appears in the official releases, perhaps it's only in what you get via the script ? If it doesn't, removing it may be considered, due to the problems which I mentioned in the first post.

[ShipIt]

This thread could really take one of those 'Not sure if serious' pics.

[Duke]

*.bsp are the compiled *.map files.
No idea why map-get didn't get that file.
But you can also compile the mine.map yourself:
"ufo2map maps/mine"

[ShipIt]

The map repo is for master. This thread is for 2.5, no?

The .bsp files are not under version control.

"ufo2map maps/mine.map" is windows only, and won´t work when he runs an installer. Oc it is entirely possible he´s running a Mac. Or building from source using a Unix system.

The only thing that's really needed is a way to reproduce the problem, provided by a short description, which should be as clear and easy as possible. Other than that, requiring to attach this or that is just useless work. You cannot expect bug reporters to do that.
For instance, I could have attached the log, but why should I have. Fixing the bug requires reproducing it, which will inevitably yield the log as well.
It makes much more sense to ask a concrete question, if one is unable to reproduce or so, instead of just pointing to bug report guidelines, in which case I have to wildly guess  what could be needed.

You get the point?

[anonymissimus]

The map repo is for master. This thread is for 2.5, no?

The thread is for 2.5 as I posted it in this section.
The map update script is intelligent: It detects which branch is currently checked out and contacts the corresponding map package. So apparently there exist map packages for each version/branch.

The .bsp files are not under version control.

Yes, I thought I had seen a bsp under version control. My bad.

"ufo2map maps/mine.map" is windows only, and won´t work when he runs an installer.

I just ran it on Linux, so it's not. I said something about version control above, so apparently I don't use an installer and seem to compile from source.

Anyway, ufo2map maps/mine worked.
Whoever maintains that map package should please add the missing mine.bsp.