Jaksy commented 8 years ago

Tested on https://github.com/xenia-project/xenia/commit/5be1a24f7a32531c69381fd767331bf3daeed9b5

Issues:

Everything aside from splashscreen logos and videos appear in white.
When starting the campaign the audio narration plays before the video shows up. After the audio finishes it takes about a minute before the video that should accompany it starts playing, which you can skip.

Log:

Screenshot(s):

logos video ingame This white image IS ingame. The audio cue's clearly indicate that the game is running the match correctly even though nothing is being displayed.

I should note prior to Vulkan rendering being enabled by default, on older builds this game actually was quite playable. For example:

Labels:

I'm not sure if labels are only being given based on the state of the game with Vulkan rendering API enabled, but regardless of API it does reach a gameplay state just fine, only with Vulkan you can't see it.

I'm unsure what gpu labels this would be given.

noslyw commented 7 years ago

hey guys i tryed it but on my pc i get only white screen. the audio its fine and i also created a player pressing the butos aleatory . but dont give me no video at all.. only all white page!. what did you do to show this images in the pictures in this page?? my stuff is.. alienware win10 i7-2.4 8gb gtx765m . any help to get the images?

anonymice105 commented 7 years ago

have the same problem as noslyw. i meet the system requirements. the audio starts but there is no picture after the "gameplay might change during actual gameplay", hope this will be fixed soon

Urguwno commented 7 years ago

I'm seeing the same thing as anonymice105.

I get to the "gameplay might change during actual gameplay", but then the screen goes white and it doesn't update the graphics.

The game continues running though, as I can hear the audio and pressing buttons on the controller causes sound effect responses.

Urguwno commented 7 years ago

After a lot more trial and error, it appears compatibility with Culcept Saga was killed in version 1.0.447, which is labeled "Swap to using the Vulkan renderer by default".

The last Xenia build that would run Culdcept Saga is here. https://github.com/xenia-project/xenia/commit/54ba3480e471cc9d2fb8833c043d83725ebee70e

Urguwno commented 7 years ago

UPDATE:

You can avoid the "white screen" while running with the latest Xenia builds if you create a shortcut and add the -gpu=gl4 parameter to the command line.

e.g. "D:\Games\Culdcept Saga\xenia.exe" -gpu=gl4

Ongoing issues continue to be:

Fuzzy graphics during gameplay
Black screens (no graphics) when proceeding to the next map. Audio plays but it may take ~5 minutes before the accompanying scene plays.
A hang occurs during the cutscene if you save a game then try to proceed to the next map in the story. Closing Xenia and reloading the .ISO will work around the problem. This doesn't happen if you replay prior maps.

ghost commented 7 years ago

I think the reason is that OpenGL is deprecated and going Vulkan. It's going to take time to do this and most likely the issue this game and others experiencing. I think a lot of Vulkan work was done after this. Have patience.

SgtSalamander commented 4 years ago

Hello! I came upon this and decided to add to the discussion. I have this exact same issue trying to run Culdcept Saga on Xenia. I get the publisher splash screens, and directly after the warning about performance changes if I go online, I am greeted with the music and a totally white screen. I have tried a series of fixes, but none of them have thus far ended up working. I also tried Urguwno's solution, but it did not work for me, unless I messed up somewhere along the line. I want to help contribute to finding a solution as best I can, let me know if there is anything else that can be tried, or if there is anything I can do to help out with this. It's a long shot, but in my opinion its worth it, even if only to keep the thread alive.

Cecilliana commented 4 years ago

The game now goes into gameplay, just finished the Tutorialstage on the August 9th Master build without any major graphical or performance issues, trying to play Versus mode still freezes the game after choosing a stage though.

Wargamer3 commented 10 months ago

Adding an image for reference, based on the Sept 14th, 2023 build. This bug happen to multiple people running Nvidia cards but is working with perfect compatibility for AMD cards. The error seem to only effect solid objects like characters, terrain and cards but will display anything with transparency just fine.

And as confirmation that it works on AMD: Demo

Kaite20 commented 10 months ago

Adding to the above, as the person who took the NVIDIA screenshots, 2D textures and HUD are fine too. It is mainly 3D objects, and it seems to be specifically those that use shaders. Once again, it is specifically an NVIDIA problem, as at least AMD works fine.

If someone can look into this, that would be great!

medic777 commented 8 months ago

Any takers on a fix for this yet? Also getting the "lines through all 3d objects" glitch with nvidia GPU looking for a fix. Any help would be appreciated!

Kaite20 commented 7 months ago

In addition to the above mentioned texture glitching that is possibly a shader error since transparent 3D objects aren't affected, I am here with another report. Versus refuses to let me progress in it, even with just one controller. I am stuck in this menu, unable to enter nor exit.

Saga Versus Error

UPDATE: So, Versus works on Citra Canary now; thank you all so much! While the NVIDIA shader issue is still persisting, this is a step in the right direction! Consider this more of a status update than anything. # Sorry for posting yet again so quickly, but I found yet another bug! Just tried to suspend a game, and the game softlocked itself. It seems to be sporadic whether it works or not, since I did a suspension before this one and it saved fine. Perhaps I did something wrong, so I'm not sure on this one, but worth reporting anyway. UPDATE: This seems to be a rare occurrence? Either that or I somehow closed the overwrite save prompt, which closed the window and made it lock up? Regardless, if I'm wrong about this being a bug, I apologize.