Screen goes black during Rogue Leader and Rebel Strike gameplay

[IronicProphet]

While playing Rogue Leader and Rebel Strike, the resolution changes during gameplay. When you reach the edge of the play area, a cutscene is triggered that shows your ship turning around. This causes the screen to go black at the start and end of the cutscene. This also happens when your ship explodes.

I have experienced this issue on both 3.0e and 3.1 firmware with the Retro-Bit Prism. While I have not tried it, I have seen it mentioned here and on Reddit that this issue does not present on firmware versions 2.3 or 2.4c2 (I am not sure that the Retro-Bit updater includes firmware older than 3.0e).

I have a US non-modded GameCube.

Reference Link: #46 (comment)

Thanks

[Nonstiq]

I don’t think it’s a resolution change in and of itself that causes this blanking. The US version runs at 640x450p60 during normal gameplay, then cuts to 640x304p60 for those cinematic cutscenes. There is a drop of signal when the cutscene starts, but there’s no loss when cutscene ends and the resolution reverts to 450p. My TV confirms it’s a loss of signal entirely when it blacks out.

Games like Eternal Darkness used to drop video as well when you entered/exited the menu, but “Force Video Active” in Swiss - made redundant by the recent change in GCVideo 3.1 - fixes this. This wasn’t caused by a resolution change as the game and menus are the same. Why this fix then doesn’t work for the Star Wars games, I don’t have an answer for.

I am curious to see if the older GCVideo firmware didn’t have this issue, though. I might have to find a programmer and see if I can drop my Carby down to an earlier version, and then use that programmer to bring it back up again.

[KainCo]

I have a Kaico plug that had fw 2.4d until 3 days ago. I'm playing Rogue Leader 2 intensively and before the FW change I was about halfway through the game. After the update to 3.1 I also noticed the problem described here. My verison is the PAL version forced to 480p

https://youtu.be/CCEI2Y4iMjU

[tqhoang84]

Just following this issue since I also have it with the GCHD Mk-II. Only the 2.4c.2 firmware works with this game, but we lose out on all the advancements of the 3.x firmware series.

I have the "Fix Resolution" option enabled and output set to 480p.

[Galaxy366]

Can confirm the issue also happens for me. I'm using the Retro Bit PRISM adapter running the latest firmware 3.1

Issue occurs when the game switches to cutscenes. Hope this can be resolved as these two games are the ones I want to enjoy the most.

[dragoncity17]

No solution for fix that ?
Many people say 2.4c firmware... but not possible to add an fix in last version ?

[KainCo]

I would like to report a quick update on this issue. Since Swiss version 1420, the resolution change (Video dropout) seems to have improved. it's still noticeable, but less often and the timeout is not for as long. it would be nice if someone could confirm that. Thx

[dragoncity17]

No exactly same problem (no change...), you can test with Star Wars - Rogue Squadron II - Rogue Leader.

There is blackscreen when the ship has an impact.

[KainCo]

OK thank you.
Then it may have improved for me because I changed the screen and it copes better with changes in resolution

[KampferWolf]

Anyone manage to figure out a fix? It is beyond agrivating seeing these blank outs.

[link266]

I ended up buying a Kaico HDMI adaptor which is easily able to put the v2 firmware on it (downgrading from v3). Since v2 doesn't have the blank out issue I can now play both Rouge Squadron games perfectly (though I am of course missing out on the various other improvements/fixes in v3).

So my solution isn't really ideal and is only a work-around until (hopefully, one day) a future iteration of the v3 firmware includes a proper fix.

[KampferWolf]

I ended up buying a Kaico HDMI adaptor which is easily able to put the v2 firmware on it (downgrading from v3). Since v2 doesn't have the blank out issue I can now play both Rouge Squadron games perfectly (though I am of course missing out on the various other improvements/fixes in v3).

I hate that approach cause a Prism is 80 dollars and shouldn't be having an issue like this really. Having to invest in another device and just seeing this be useless kind of sad

I do appreciate the knowledge though, I'll need to look into it.

[XNINEZERO]

glad I caught this before purchasing the Carby. I do play these quite a bit. Tested on OEM component cables and there are no video blank-out issues - and my OSSC's front panel readout doesn't show any changes in resolution at these points.

I wanted to move toward pure HDMI solutions for all of my 5th and 6th gen machines (along with non-composite audio in the case of the Cube), but I'll stick to my current setup until this is resolved - if it ever is.