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

add de_train map data #361

Open
wants to merge 1 commit into
base: 2.0.0b5
Choose a base branch
from

Conversation

smartbackwards
Copy link

Added de_train radar pngs and map data. Not sure if the map data is correct (on test plots the positions seemed always to appear on the lower levels, even out in A yard), here's the CS source code txt file I used:


"de_train"
{
    "material"      "overviews/de_train"
    "pos_x"     "-2308"
    "pos_y"     "2078"
    "scale"     "4.082077"
        "verticalsections"
    {
        "default" // use the primary radar image
        {
            "AltitudeMax" "20000"
            "AltitudeMin" "-50"
        }
        "lower" // i.e. de_nuke_lower_radar.dds
        {
            "AltitudeMax" "-50"
            "AltitudeMin" "-5000"
        }
    }
    "CTSpawn_x"     "0.860000"
    "CTSpawn_y"     "0.770000"
    "TSpawn_x"      "0.120000"
    "TSpawn_y"      "0.250000"
    "bombA_x"       "0.630000"
    "bombA_y"       "0.490000"
    "bombB_x"       "0.520000"
    "bombB_y"       "0.760000"
}

@JanEricNitschke
Copy link
Collaborator

Yeah, lower level is everything that is not in the tiny upper sliver in the halls. So it makes sense. For train most of the map is in the lower level, which is a bit different compared to e.g. Nuke or vertigo, where the default is the upper.

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

Successfully merging this pull request may close these issues.

2 participants