X

Rayman 3: Hoodlum Havoc Latest News - PC

Rayman 3: Hoodlum Havoc
Game Description:Adventurers beware - Rayman's universe has exploded into a wacked-out world of cartoon mayhem and mind-blowing battles! When Globox accidentally swallows the Lord of the Dark Lums, a fanatic army of trigger-happy Hoodlums wreaks total havoc to get their Lord back! Rayman's only chance? Journey the vast reaches of the world to purge the Dark Lum Lord from the manic Globox, scour the lands for unearthly new powers, and do battle with hordes of Hoodlum soldiers, contraptions, and maniacal bosses. This time, it's war!
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Rayman 3: Hoodlum Havoc News

Displaying 1–1 of 1 articles

  • Rayman 3: Hoodlum Havoc HD Release Date Announced

    I really dig the Rayman games, so I'm happy to report that Rayman 3: Hoodlum Havoc HD will hit the PlayStation Network and the Xbox Live Arcade on March 21. I like the cartoony platforming action of those games so much, I'm just going to stare at my desk calendar until the "Big Day." This is a high-definition update, so better...

    Posted February 2, 2012

    Rayman 3: Hoodlum Havoc HD Release Date Announced

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>