Tornado Outbreak: Difference between revisions

From RPCS3 Wiki
m (Appears to be fixed with the latest builds of RPCS3?)
m (Text replacement - "|multithreaded rsx notes = <!-- Audio configuration --> " to "|multithreaded rsx notes = |asynchronous texture streaming = <!-- On, Off --> |asynchronous texture streaming notes = <!-- Audio configuration --> ")
(2 intermediate revisions by the same user not shown)
Line 20: Line 20:
|preferred spu threads                = <!-- Auto, Single digit between 1 to 6 (e.g. 3), Range between 1 to 6 (e.g. 1 - 3) -->
|preferred spu threads                = <!-- Auto, Single digit between 1 to 6 (e.g. 3), Range between 1 to 6 (e.g. 1 - 3) -->
|preferred spu threads notes          =  
|preferred spu threads notes          =  
|enable thread scheduler               = <!-- On, Off -->
|thread scheduler                     = <!-- Operating System, RPCS3 Scheduler, RPCS3 Alternative Scheduler -->
|enable thread scheduler notes         =  
|thread scheduler notes               =  
|lower spu thread priority            = <!-- On, Off -->
|lower spu thread priority            = <!-- On, Off -->
|lower spu thread priority notes      =  
|lower spu thread priority notes      =  
Line 67: Line 67:
|multithreaded rsx                    = <!-- On, Off -->
|multithreaded rsx                    = <!-- On, Off -->
|multithreaded rsx notes              =  
|multithreaded rsx notes              =  
|asynchronous texture streaming        = <!-- On, Off -->
|asynchronous texture streaming notes  =
<!-- Audio configuration -->
<!-- Audio configuration -->
|audio out windows                    = <!-- XAudio2, OpenAL, Disabled -->
|audio out windows                    = <!-- XAudio2, OpenAL, Disabled -->
Line 116: Line 118:
|maximum spurs threads                = <!-- Unlimited, Single digit between 0 to 5 (e.g. 3) -->
|maximum spurs threads                = <!-- Unlimited, Single digit between 0 to 5 (e.g. 3) -->
|maximum spurs threads notes          =  
|maximum spurs threads notes          =  
|firmware settings                    = <!-- Manually load selected libraries, Load automatic and manual selection, Load liblv2.sprx only, Load liblv2.sprx and manual selection, Load liblv2.sprx and strict selection -->
|firmware libraries                    = <!-- Switch to LLE, Switch to HLE -->
|firmware settings notes               = <!-- Where libraries are manually selected, mention the list of libraries to be selected here -->
|firmware libraries notes             = <!-- Mention the libraries to be manually selected here -->
|read depth buffers                    = <!-- On, Off -->
|read depth buffers                    = <!-- On, Off -->
|read depth buffers notes              =  
|read depth buffers notes              =  
Line 149: Line 151:
|accurate ppu 128 reservations        = <!-- Always Enabled, Disabled, Value between 1 to 8 -->
|accurate ppu 128 reservations        = <!-- Always Enabled, Disabled, Value between 1 to 8 -->
|accurate ppu 128 reservations notes  =  
|accurate ppu 128 reservations notes  =  
<!-- Misc. configuration -->
|ppu llvm java mode handling          = <!-- True, False -->
|ppu llvm java mode handling          = <!-- true, false -->
|ppu llvm java mode handling notes    =  
|ppu llvm java mode handling notes    =  
}}
}}

Revision as of 13:29, 13 September 2021

Tornado Outbreak
Developer(s) Loose Cannon Studios
Release date(s) NA September 29, 2009
EU November 13, 2009
Release type Console exclusive
Genre(s) Action, Adventure
Mode(s) Single-player, Co-op
GameID(s) BLES00695 (IRD), BLUS30371 (IRD)
Quick links Check Compatibility
Open Issues
Search Google
Wikipedia Page

Tornado Outbreak is an action-adventure video game released for the PlayStation 3, Wii, and Xbox 360. The game revolves around using the destructive power of a tornado in an effort to save the world.

Configuration

No options that deviate from RPCS3's default settings are recommended for this title.

Known Issues

Crash

RPCS3 will instantly close itself upon playing through the level Camelot Falls with the dash move.

This issue appears to be fixed in later builds of the emulator.

Special Notes