Crash to desktop troubleshooting

Discussion in 'Mapping Questions & Discussion' started by bonestorm, Nov 23, 2007.

  1. bonestorm

    bonestorm Guest

    Positive Ratings:
    0
    Well you probably gathered by the thread title I have a couple of nasty issues. ;) So far I have found two things that crash my map to desktop:

    1) Changing teams during the round. It's fine during setup, but attempting to change teams during the round = ctd. This happens on several PCs I have tested on.

    2) Firing Demo sticky bombs. This only seems to happen in the outdoor sections of my map. Only happens on my PC, not on a couple of others I have tested.

    I have checked for problems (Alt-P) and there are none with the map. I don't have any leaks. I'm not sure what else to do to try and fix these problems, so any advice on pointing me in the right direction would be great.
     
  2. Snipergen

    Snipergen L13: Stunning Member

    Messages:
    1,053
    Positive Ratings:
    150
    i would love to help you but it sounds like you have a nasty error in your map that hammer doenst find. I cant think of anything particular that causes this crash, could be anything really :s

    I would say, i hope you have backups of older versions where it does work, than compare what changed and look for the error
     
  3. bonestorm

    bonestorm Guest

    Positive Ratings:
    0
    Yeh I figured it wasn't good. I'd probably have to go back too far, so I'll probably just start from scratch again. Thanks for your help.
     
  4. Snipergen

    Snipergen L13: Stunning Member

    Messages:
    1,053
    Positive Ratings:
    150
    i know man, i had that too one time, nasty bugs :(
     
  5. A Boojum Snark

    aa A Boojum Snark Toraipoddodezain Mazahabado

    Messages:
    4,769
    Positive Ratings:
    5,535
    If it's actually something IN the map causing it, you could attempt to locate it by compiling pieces at a time. Start by cordoning off half the map, compile, see if it happens. If it doesn't try the other half. If you find it happens in one half and not the other, then chop the half it occurs in yet again in half and try each one. Keep doing it and you'll narrow down the location of the problem.
    If it happens in both initial halves then either it's unrelated to the map, or you have multiple errors in which case you'd need to use a more complex method of the above.