Physics at 82.6% in compile says very full?

Discussion in 'Mapping Questions & Discussion' started by JustAHorrible, May 21, 2012.

  1. JustAHorrible

    JustAHorrible L2: Junior Member

    Messages:
    68
    Positive Ratings:
    1
    =========

    Object names Objects/Maxobjs Memory / Maxmem Fullness
    ------------ --------------- --------------- --------
    models 3/1024 144/49152 ( 0.3%)
    brushes 34/8192 408/98304 ( 0.4%)
    brushsides 208/65536 1664/524288 ( 0.3%)
    planes 344/65536 6880/1310720 ( 0.5%)
    vertexes 749/65536 8988/786432 ( 1.1%)
    nodes 337/65536 10784/2097152 ( 0.5%)
    texinfos 26/12288 1872/884736 ( 0.2%)
    texdata 7/2048 224/65536 ( 0.3%)
    dispinfos 60/0 10560/0 ( 0.0%)
    disp_verts 17340/0 346800/0 ( 0.0%)
    disp_tris 30720/0 61440/0 ( 0.0%)
    disp_lmsamples 335772/0 335772/0 ( 0.0%)
    faces 565/65536 31640/3670016 ( 0.9%)
    hdr faces 0/65536 0/3670016 ( 0.0%)
    origfaces 185/65536 10360/3670016 ( 0.3%)
    leaves 341/65536 10912/2097152 ( 0.5%)
    leaffaces 601/65536 1202/131072 ( 0.9%)
    leafbrushes 272/65536 544/131072 ( 0.4%)
    areas 2/256 16/2048 ( 0.8%)
    surfedges 3212/512000 12848/2048000 ( 0.6%)
    edges 1686/256000 6744/1024000 ( 0.7%)
    LDR worldlights 8/8192 704/720896 ( 0.1%)
    HDR worldlights 0/8192 0/720896 ( 0.0%)
    leafwaterdata 0/32768 0/393216 ( 0.0%)
    waterstrips 33/32768 330/327680 ( 0.1%)
    waterverts 0/65536 0/786432 ( 0.0%)
    waterindices 444/65536 888/131072 ( 0.7%)
    cubemapsamples 0/1024 0/16384 ( 0.0%)
    overlays 0/512 0/180224 ( 0.0%)
    LDR lightdata [variable] 1055508/0 ( 0.0%)
    HDR lightdata [variable] 0/0 ( 0.0%)
    visdata [variable] 5509/16777216 ( 0.0%)
    entdata [variable] 9866/393216 ( 2.5%)
    LDR ambient table 341/65536 1364/262144 ( 0.5%)
    HDR ambient table 341/65536 1364/262144 ( 0.5%)
    LDR leaf ambient 1648/65536 46144/1835008 ( 2.5%)
    HDR leaf ambient 341/65536 9548/1835008 ( 0.5%)
    occluders 0/0 0/0 ( 0.0%)
    occluder polygons 0/0 0/0 ( 0.0%)
    occluder vert ind 0/0 0/0 ( 0.0%)
    detail props [variable] 1/12 ( 8.3%)
    static props [variable] 1/2790 ( 0.0%)
    pakfile [variable] 54/0 ( 0.0%)
    physics [variable] 3463280/4194304 (82.6%) VERY FULL!
    physics terrain [variable] 0/1048576 ( 0.0%)

    =========

    What? See Physics? Is this normal?
     
  2. Faux Rhinoceros

    aa Faux Rhinoceros Also known as Dr. Element

    Messages:
    1,477
    Positive Ratings:
    1,367
    Well, its seems like you have quite a lot of physics in your map (yeah, really!)
    I'd like to see a screenshot of the map. There might just be something that doesn't need to be physics impacted.
     
  3. JustAHorrible

    JustAHorrible L2: Junior Member

    Messages:
    68
    Positive Ratings:
    1
    It's a payload with a bunch of displaced terrain. I can't provide you with one, as I'm playing on Ozzy Furocity's #6 VS Saxton hale server.
     
  4. Fr0Z3nR

    aa Fr0Z3nR Creator of blackholes & memes. Destroyer of forums

    Messages:
    6,391
    Positive Ratings:
    4,906
    It's pretty self explanatory. You have too many phys props, which in TF2 is a no-no.
     
  5. JustAHorrible

    JustAHorrible L2: Junior Member

    Messages:
    68
    Positive Ratings:
    1
    Like what? Rails?
     
  6. Fr0Z3nR

    aa Fr0Z3nR Creator of blackholes & memes. Destroyer of forums

    Messages:
    6,391
    Positive Ratings:
    4,906
    Rails shouldn't be phys props. NOTHING should be a phys prop, except the payload.
     
    • Thanks Thanks x 1
  7. JustAHorrible

    JustAHorrible L2: Junior Member

    Messages:
    68
    Positive Ratings:
    1
    Also, I can't get my cart to move, and it damages me when I follow the developer tutorial.
     
  8. Faux Rhinoceros

    aa Faux Rhinoceros Also known as Dr. Element

    Messages:
    1,477
    Positive Ratings:
    1,367
    Payload IS advanced stuff after all.

    The tracks should be prop_static's. NEVER use prop_physics in TF2 unless you are completely confident with it :p

    If the cart doesn't move, well, there are lots of explanations. The most likely one is that you've connected the path_tracks incorrectly, or made a typo in one of the O/I's
     
    • Thanks Thanks x 1
  9. JustAHorrible

    JustAHorrible L2: Junior Member

    Messages:
    68
    Positive Ratings:
    1
    How do I check this?
     
  10. Headhunter09

    Headhunter09 L1: Registered

    Messages:
    47
    Positive Ratings:
    6
    Go through each payload-associated entity and check all the settings and outputs.
     
  11. henke37

    aa henke37

    Messages:
    1,879
    Positive Ratings:
    442
    Also, the in game console tends to give you error messages when you screw up majorly.
     
  12. Idolon

    aa Idolon the worst admin

    Messages:
    1,525
    Positive Ratings:
    4,334
    If you want to check where your prop_physics are, click Map>Entity Report. It will give you a list of every entity in your map.