[GC] Star Wars Rogue Squadron II: Rogue Leader

[JMC47]

Are you sure that RS2 doesn't just crash on its own? Things aren't too pretty with the Rogue Squadron games right now.

[dark2792]

(03-26-2018, 05:48 PM)JMC47 Wrote: Are you sure that RS2 doesn't just crash on its own?  Things aren't too pretty with the Rogue Squadron games right now.

Could you elaborate on that? My game is crashing frequently, too.

[FixRogueSquadronPlease]

so after a decade of dolphin updates this game is still unplayable for the most part? why? i cannot understand this, I played all RE gamecube games 7 years ago with no glitches and decent framerate (in 2011) but in 2018 Rogue Leader is still giving me crap with newer machines? like really?

[JMC47]

Resident Evil games = primitive ports of PSX games with updated graphics and one pretty decent game that still doesn't use any scary features adn was later ported to PS2.

Rogue Squadron 2/3 = Two technically impressive titles that push the GameCube to its very limit and use a bunch of hardware quirks to achieve what they do. Created by people with intricate knowledge on the GameCube GPU.

[Somakarma]

Just so I don't have to wade through a 168 page threadnaught, could someone be so kind to link me to the best possible settings required to give the game a slim chance of running? PC is decent.

[Kolano]

(04-01-2018, 09:42 PM)Somakarma Wrote: Just so I don't have to wade through a 168 page threadnaught, could someone be so kind to link me to the best possible settings required to give the game a slim chance of running? PC is decent.

Refer the wiki page shown at the start of this thread.

[Monyet]

What has happened recently that is making RS have a bad time? I'm just asking, I haven't even tried to play it in a while. I guess more accuracy things, accuracy usually makes things slower right? Also, Mr throwaway account up above, complaining like that rarely gets you anywhere, you just come off as an entitled brat. I mean, I'd be annoyed except that it's actually kinda pathetically funny. I will miss the days when everything works perfectly and there'll be no more forum drama.

Edit: Just to be clear I meant "FixRogueSquadronPlease", not Somakarma.

[Zeek M]

April 17 2018 Dolphin 5.0-7034
I feel locked out of everything so I pushed hard to be careful about singing up to the site and forum, I don't understand github sign up at all.
I want to fix rogue squadron REAL BAD, so I'm attempting to post any fix I can offer.

Let's deal with the first error on the list - ConfigLoaders\GameConfigLoader.cpp:127 W[CORE]: Unknown game INI option in section Core: MMU
Go to \Dolphin\Sys\GameSetting\GSW.ini
Put a pound and space in front of the MMU = 1

[Core]
# MMU = 1

Also uncheck forced MMU in the games property page making it a black square. MMU will still be active but the error in console should be gone, checked repeatedly to make sure.

I do not know how to fix PowerPC\Jit64\Jit.cpp:628 W[PowerPC]: ISI exception at 0x7fc0f7a4, when I do I'll try to fix it.
I do not know what this error is either, BPStructs.cpp:677 W[Video]: Unknown BP opcode: address = 0x00000069 value = 0x0000049e
I do not know what this error is either, IOS\IOSC.cpp:610 W[IOS]: keys.bin could not be found. Default values will be used.
Or these
45:48:210 FramebufferManager.cpp:358 E[Video]: Unhandled reinterpret pixel data 4
45:48:210 FramebufferManager.cpp:358 E[Video]: Unhandled reinterpret pixel data 1

I'm no expert on any of this I'm just pointing out the things I see in the console which cause stuttering.

It's 2018 , It's time to fix this game.

[JosJuice]

Keep in mind that not every log message that's listed as "warning" actually means that something is wrong. The MMU game INI setting not being recognized by the new config system and keys.bin being missing is completely normal and shouldn't prevent this game from working.

[Zeek M]

Here's what goes on in the console. Dolphin 5.0-7053

48:12:821 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ARAM management at 0x800ad3e0, effective address ARAM mapping at 0x800b1be0
48:12:823 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: 16777216 bytes of virtual memory setup at 0x7f000000 using 1572864 bytes of physical memory at 0x000d0000
48:12:823 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Copying 1603808 bytes of text section data to 0x7fc00000...
48:12:867 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Copying 90880 bytes of text section data to 0x7fd88000...
48:12:870 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Copying 297024 bytes of data section data to 0x7fd9f000...
48:12:880 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Clearing VM BSS area at 0x7fde8000 (224160)...
48:12:885 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: VM Data copy finished.
48:12:900 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: User VM heap reserved from 0x7f000000 to 0x7fc00000
48:12:900 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Truncated arena: 0x80250000 - 0x817ff900 <------------------------// Ouch! This can't be good.
48:12:900 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: --- GSYS VM init done ---
48:12:996 HW\EXI\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Calling static initializers (_ctors == 0x8005c360)
48:12:997 PowerPC\Jit64\Jit.cpp:628 W[PowerPC]: ISI exception at 0x7fc0f7a4 <-------------------------// Lots of these starting with 0x7

48:26:533 FramebufferManager.cpp:358 E[Video]: Unhandled reinterpret pixel data 4
48:26:533 FramebufferManager.cpp:358 E[Video]: Unhandled reinterpret pixel data 1

48:13:032 BPStructs.cpp:677 W[Video]: Unknown BP opcode: address = 0x00000069 value = 0x0000049e
48:13:032 BPStructs.cpp:677 W[Video]: Unknown BP opcode: address = 0x00000046 value = 0x0000024c

MISSION 4 PRISON LEVEL _______________________________________________________________________________________
47:03:221 OpcodeDecoding.cpp:241 E[Video]: FIFO: Unknown Opcode(0xd3 @ 0000015B2D4F0000, preprocessing = no)
47:03:221 OpcodeDecoding.cpp:241 E[Video]: FIFO: Unknown Opcode(0x43 @ 0000015B2D4F0001, preprocessing = no)
47:03:221 OpcodeDecoding.cpp:241 E[Video]: FIFO: Unknown Opcode(0x7c @ 0000015B2D4F0002, preprocessing = no)
47:03:221 OpcodeDecoding.cpp:241 E[Video]: FIFO: Unknown Opcode(0x3f @ 0000015B2D4F0003, preprocessing = no)
47:03:221 OpcodeDecoding.cpp:241 E[Video]: FIFO: Unknown Opcode(0x29 @ 0000015B2D4F0004, preprocessing = no)
47:03:221 OpcodeDecoding.cpp:241 E[Video]: FIFO: Unknown Opcode(0x6b @ 0000015B2D4F0005, preprocessing = no)
__________________________________________________________________________________________________
CRASH! lol
Video host application terminated as well.

0x7 is what causes the most stuttering and seems to be a Java exception on ARM
Could even be some locked memory flag for all I know.

All I'm attempting to do here is push the programmers to get this fixed since they know way more than I do.
I do retain some hope I will learn a few things from all this.