X

Yoostar 2 In The Movies Screenshots and Images - Xbox 360

  • Publisher: Blitz Games
  • Genre:Party
  • Developer: YooStar
  • Release Date:Mar 8, 2011
  • # of Players:1 player
  • ESRB:T - Teen (Alcohol and Tobacco Reference,Language,Mild Blood,Mild Violence,Sexual Themes)
  • Platforms:
Game Description: Yoostar2 Combines The Power Of New Console Platforms, Top Hollywood Movies And The Burgeoning Social Media Phenomenon Monday 14th June/... Everyone now has the opportunity to become a global movie star with Yoostar2. In an instant you can step into the shoes of famous characters from hundreds of movies, play out the part and then share your performance with the world.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game
  • Yoostar 2 Xbox360 Dev Diary 3 Trailer

    Posted: March 2, 2011

    539 Views | 03:08

  • Yoostar 2 "Choosing An Actor" Xbox 360 Developer Diary

    Posted: February 10, 2011

    1,423 Views | 05:33

  • Yoostar 2 "On Xbox Kinect" Trailer

    Posted: January 5, 2011

    1,829 Views | 04:33

 


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>