Results 1 to 9 of 9
  1. #1
    EmuTalk Member -indecisive-'s Avatar
    Join Date
    Jun 2004
    Posts
    69

    Why does ssbm run so well?

    What makes this one so much quicker than something like...mario party 4? SSBM isn't really a simple game in terms of its graphics, so what is the reason that it runs at full speed or higher even under the 32bit dolphin? Other games utilize more chips or more of the gamecube's resources?



    • Advertising

      advertising
      EmuTalk.net
      has no influence
      on the ads that
      are displayed
        
       

  2. #2
    EmuTalk Member
    Join Date
    Oct 2006
    Posts
    428
    Probably because it's more or less a 2D game that does not need very much power to run and the game levels are just lifeless backgrounds that never change.

  3. #3
    EmuTalk Member -indecisive-'s Avatar
    Join Date
    Jun 2004
    Posts
    69
    The levels are not vast, yeah, but they aren't basic or "2d"
    Also the character poly counts aren't low. Also, a game like mario party 4 is slow all the time, even when there isn't much being shown.

  4. #4
    (Y) Olly's Avatar
    Join Date
    Jan 2008
    Location
    Sutton Coldfield, Birmingham, England
    Posts
    42
    I get the impression they focused on getting SSBM up to speed for a while, as it's the most popular GC game out there.

  5. #5
    Emulation Fanatic EmuFan's Avatar
    Join Date
    Apr 2005
    Location
    Norway
    Posts
    740
    Sounds reasonable to me...Wasn´t it one of the earliest games they tried to emulate? TWW was the first, i think...

    If i ever disagree with you, it is not because i´m trying to be an asshole. It is just to tell you that you are wrong

    ____________________
    Asus P6T Deluxe V2, X58, Socket-1366// Intel Core i7-950// Corsair Dominator 6 GB DHX+ DDR3// NVIDIA GeForce 275 GTX 896 MB (Going to upgrade)// HDD space: About 3.5 TB// Realtek High Definition Audio//Power supply: Unknown, but packing lots of shit// Custom built PC.


  6. #6
    Sony battery Toasty's Avatar
    Join Date
    Dec 2004
    Location
    Oregon, U.S.A.
    Posts
    2,049
    Intensity of the graphics is only one factor. Remember, the bottleneck in Gamecube emulation is the CPU, not the graphics. So, scenes in which a lot of work has to be done by the CPU will suffer.

    For example, in Wind Waker when you're outside on an island, emulation slows down a lot. Let's think about why this happens. When you're standing outside, the entire map tile is being actively processed by the Gamecube: Somewhere, there's a map-drawing fish jumping around; somewhere else a flock of seagulls is flying; somewhere else there are some sharks waiting for you to find them; somewhere else a pirate ship is looking for a hapless victim to shoot bombs at; and who knows what else is going on on the island itself. All of this needs to be managed by the CPU.

    Now, enter a house and emulation speeds up. All the CPU has to think about now is what's going on in the house, which usually doesn't amount to much. Compare a battle on SSBM to that, and it's understandable why it would be fast. The graphics may look nice, but overall, what's going on is relatively simple: Up to 4 characters move around the screen trying to hit each other with attacks. Not too complicated compared to the processing that has to go on in some other places in some other games.

    Granted, that's an overly simple explanation of why it works the way it does, but you get the idea: More stuff going on = slower emulation.

  7. #7
    EmuTalk Member Nintendo Ace's Avatar
    Join Date
    Oct 2006
    Posts
    47

    Thumbs up

    Quote Originally Posted by Toasty View Post
    Intensity of the graphics is only one factor. Remember, the bottleneck in Gamecube emulation is the CPU, not the graphics. So, scenes in which a lot of work has to be done by the CPU will suffer.

    For example, in Wind Waker when you're outside on an island, emulation slows down a lot. Let's think about why this happens. When you're standing outside, the entire map tile is being actively processed by the Gamecube: Somewhere, there's a map-drawing fish jumping around; somewhere else a flock of seagulls is flying; somewhere else there are some sharks waiting for you to find them; somewhere else a pirate ship is looking for a hapless victim to shoot bombs at; and who knows what else is going on on the island itself. All of this needs to be managed by the CPU.

    Now, enter a house and emulation speeds up. All the CPU has to think about now is what's going on in the house, which usually doesn't amount to much. Compare a battle on SSBM to that, and it's understandable why it would be fast. The graphics may look nice, but overall, what's going on is relatively simple: Up to 4 characters move around the screen trying to hit each other with attacks. Not too complicated compared to the processing that has to go on in some other places in some other games.

    Granted, that's an overly simple explanation of why it works the way it does, but you get the idea: More stuff going on = slower emulation.
    Excellently put, and that explains why Zelda WW is running so slow for me, thanks.

    OS: Windows x64 edition
    Processor: AMD Athlon 64 3200+
    Motherboard: MSI K9VGM-V
    Memory: 1 Gig DDR2 RAM
    Graphics card: NVIDIA 7300 LE 256MB

  8. #8
    EmuTalk Member
    Join Date
    Jul 2008
    Posts
    523
    That's true, but I think it's also because SSBM and WW are priority numero uno for the developers. If they were bent on getting another game running it would perform just as well IMO. But everyone wants to play SSBM.

  9. #9
    EmuTalk Member -indecisive-'s Avatar
    Join Date
    Jun 2004
    Posts
    69
    thanks for the response, guys

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •