4D5307DF - Blue Dragon

[bdeimos]

Marketplace

Tested on (xenia-project/xenia@ab2edf9)

Issues:

(starts gameplay with corrupted graphics)

Log:

xenia.zip

Screenshot(s):

Labels:

(state-gameplay gpu-missing-drawing gpu-corrupt-drawing)

[Razzile]

half duplicate #110 will leave open as have different IDs

[Celvox]

Tried playing this game in November but it's still corrupted. R.I.P hope it's fixed soon cause I really want to play this.

[ZolaKluke]

The game now runs and renders though if you don't skip cutscenes the game will lag and shortly crash after

Must be run with the Directx 12 version of the emulator

[ZolaKluke]

I tested this on commit: xenia-project/xenia@21def8a

The game has mostly been fine though after the first boss fight visuals start to glitch out, however reloading a save will fix this, but when moving to a new area the textures break completely.

My log: xenia.zip

Screenshots:

Before going down stairs (loading lower level of building)
https://i.imgur.com/XpT1rIg.png

After going down stairs (lower level)
https://i.imgur.com/XpT1rIg.png

[bkawarsky12]

Once i get to the drill machine and go up to the second level, the textures and graphics are so scrambled. I've tried reloading but it doesn't work. Not sure what else i could try..

[ZolaKluke]

So this needs it's labels updated as gpu-missing-drawing is no longer an issue as long as you use the D3D12 build.

Labels: remove gpu-missing-drawing

[ZolaKluke]

Also since it doesn't have XamSwapDisc it also has unimplemented kernel features

Labels: kernel-unimplemented-feature

[bkawarsky12]

Exactly how? Because it crashes most of the time on d3d12?

…

On Wed, Jan 2, 2019 at 2:46 AM ZolaKluke ***@***.***> wrote: So this needs it's labels updated as gpu-missing-drawing is no longer an issue as long as you use the D3D12 build and also I would recommend this being considered state-playable as I was able to beat the whole game although there is tonnes of rendering issues sometimes it's 100% beatable Labels: state-playable, remove gpu-missing-drawing — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#988 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AovqZ9mrolxmexdX5wgdAbN-V44yvf3kks5u_HHegaJpZM4U1hK1> .

[ZolaKluke]

I haven't had this game crash once a part from screwing with game files and loading saves with the wrong disc this game does not crash at all, sure it has some visual issues, but hasn't crashed during proper gameplay yet

Exactly how? Because it crashes most of the time on d3d12?

[ZolaKluke]

You can play the game, but it's not playable yet. It's current issues is the audio is out of sync by about 2 seconds and the true killer is the performance killing vertex explosions after about 2-3 hours of gameplay which can be bypassed temporarily with an actual save from a Xbox 360

[illusion0001]

few examples

[XiangZone]

I will be trapped here.
Then can't continue

[kanelakis]

https://mega.nz/#!RpZFnAqC!A6W6HZAUYXhkfTkEJzUqwrtkMfZpG2Nv9x1hiNsk6V4
This problem happens to me after the footage of the shark, when I take control of Shu's grandfather.
I attach the log file in Mega because it is 77 mb big.
OS:Windows 10 Pro 64 Bit
Processor:Intel core I7 3770 3.40 Ghz
Ram:16 Gb
Video Card:Gigabyte GeForce Gtx 1060 6gb
Send a video:
https://youtu.be/hOeyqbZs29Y

[ZolaKluke]

So if your unaware I recently made a discovery that is a workaround for the graphics glitches that occur, pretty much when they do occur you can click GPU > Trace Frame on the Xenia window (see screenshot below) or simply press F4 which creates a trace frame and also resets graphics memory resulting in making the game semi-playable again. I've also linked 2 videos below which you can see the trick being used.

Screenshot:

Videos:
https://youtu.be/YY7qG3pLEzk
https://www.youtube.com/watch?v=RAyNTPf7b1A

[kanelakis]

So if your unaware I recently made a discovery that is a workaround for the graphics glitches that occur, pretty much when they do occur you can click GPU > Trace Frame on the Xenia window (see screenshot below) or simply press F4 which creates a trace frame and also resets graphics memory resulting in making the game semi-playable again. I've also linked 2 videos below which you can see the trick being used.

Screenshot:

Videos:
https://youtu.be/YY7qG3pLEzk
https://www.youtube.com/watch?v=RAyNTPf7b1A

I did as you said and improved, now I'll see later.

[kanelakis]

Then you can play by pressing F4, anyway if the game is still without moving the character, after a while the screen darkens, and I didn't put it in fullsceen.
I had to restart my computer because it didn't accept any commands.
I left it on the small screen and it gave me a graphic device lost error, but I updated the card to the latest driver version.
Send Log file big:
https://mega.nz/#!csJESKqB!hYwAuWw6uXTc9ang6eD81UQMKpZD9S0F5Am2DRNTgj8
I did a third test, but the video card crashed very badly.
It would be better to wait later, I wouldn't want the video card to damage me.

[kanelakis]

I updated my hardware and tried the December 4th version but nothing has changed, there is always the graphic problem, and if I press F4 the game graphics not resolve and crashes after a while.
Also in battle i've fps problem.
https://mega.nz/#!4pwnjaTY!GRtFrRcabl5YjnO6xo9_tHUPs4JMglULo3cf5M9rPDI
Intel core i9 9900k 3.60
Ram: 32 Gb
Videocard: Gigabyte GTX 1060 6gb.

[ZolaKluke]

I'm testing the game with the canary version December 29th, pressing F4 when there are those graphic problems works.
I use Direct3D 12, also because I don't know how to change in Vulkan if there is one.
Every now and then I get the video error derived from the gpu and it closes.

There is no 29th December build, the last update to Xenia was 25 days ago

I have tested the game with the canary version that bears the date 29 December on the emulator.
Then if the files are 25 days ago ok.

This is the Xenia Master branch, there is a separate github page for Canary

[darkdarkai]

Hey guys, kind of out of topic question but I just tried on the latest version of xenia and now that it's at least playable i'm wondering if there's a way to get japanese audio because I only have english,spanish and german.
Does it comes from my iso of the game or could it come from the emulator and could be fixed ?

[ZolaKluke]

Hey guys, kind of out of topic question but I just tried on the latest version of xenia and now that it's at least playable i'm wondering if there's a way to get japanese audio because I only have english,spanish and german.
Does it comes from my iso of the game or could it come from the emulator and could be fixed ?

The voice options are region specific, my Australian copy is limited to English, French and Japanese

[NemesisSama]

My Game is Crashing when I Try to enter the "Deep Zone" and here is the crash log for it
xenia.zip

[Jdbaii]

I just want to register my interest, and say that the vertex explosion bug still happens, but F4 indeed fixes it. If F4 fixes it though, surely it can't be too hard for someone to develop a quick fix that does this automatically. Anything that improves the experience in the short term is better than nothing, right? It only seems to happen during scene changes (especially after a cutscene), which should narrow it down.
I've played through the game on console a couple of times, but having a powerful PC capable of 4K, it would be nice to see what the game would look like at a higher resolution.

[CaelThunderwing]

just tried on Canary build 15d561f1d (Jan31st 2021) seems like the Video corruption and vertex Explosion bugs are (only played till just after the landshark dropping you into the caves)are mostly down to just the CS's, Shu's "Scrap" greatsword still has a garbled texturedurring the first cutscene, (more pronounced in the latest Nightly build and that still requires manual trace frame/Clear frame cache to fix the problem temporarily vs just skipping the CS in canary.)

Seems far more playable but yea Performance tanks when the vertex explosion bug occurs.
(Specs)
32GB DDR4-3200 Ram
AMD Ryzen 5-3600
Nvidia GTX 1650 Super

[AzarathAzzy]

I just want to register my interest, and say that the vertex explosion bug still happens, but F4 indeed fixes it. If F4 fixes it though, surely it can't be too hard for someone to develop a quick fix that does this automatically. Anything that improves the experience in the short term is better than nothing, right? It only seems to happen during scene changes (especially after a cutscene), which should narrow it down.

I've found that it happens consistently when moving between the 1st and 2nd floor of the moving mech base. The one that travels in a circle around the ice protrusion in the top left corner of the map just before the point in the game where you would enter the deep zone.
Accompanying game logs, if it makes any difference:
https://drive.google.com/drive/folders/1ET96GPgZjuzkLwskWLqCo-XzEmle9ec1?usp=sharing
https://youtu.be/6rUTDWe7dZE

Not like I can get any further in the game because when I try and enter the deep zone, the game crashes as soon as the landshark vs mechat sequence begins. I have a few instances of it crashing, but one where the entire emulator just close and didn't state that it paused itself or anything, so I saved that log seperately from the others if it happened to be a special case.
https://drive.google.com/drive/folders/1hgiMebuh5ZCRxTDsu4rdxsScHrG235KA?usp=sharing
https://youtu.be/zsEckdJjlXY

(Spoilers, if anyone cares.) Another place the general texture glitheyness happens consistently is when Zola starts talking about her seeing the blueprint for the planet splitting in half when trying to escape nene's base. displayed in the first video.

Here's my game save if it happens to help anyone at all with figuring out these issues:
https://drive.google.com/drive/folders/11X9xf4-RoSm7KpeE6eVP54CkhWKzhG4Q?usp=sharing

[HydroCG]

As of 4th Aug 2021 Canary build the crash at the deep zone no longer happens. Have been able to complete the game, though vertex explosions were fairly prevalent at the end.

[FFRyu]

The game crashes randomly when loading any cutscene or loading another area.

[MysteriousSheep]

Using the below settings and using Xenia Canary Build: canary_experimental@fac2a89d0 on Oct 24 2022 I was able to discover that the setting d3d12_clear_memory_page_state = true nearly completely fixes the random vertex explosions (and the random crashes) in roughly 99% of the game. F4/F5 is no longer required to be pressed every single time you load a zone/cs. (It also fixed the vertex explosion/terrain issues when flying the mechat.)

Random crashes and 'Random Vertex Explosion' fix:

Expand

That said I want to point out there are 2 different types of vertex explosions. Random and Consistent. The random ones that happen during cutscenes and loading zones are fixed with f4/f5 and the d3d12_clear_memory_page_state setting. However certain areas (3 civilian houses in Pachess Town for example) have consistent vertex explosions and weird shading issues that don't go away with f4/f5 or the d3d12_clear_memory_page_state setting. I have not had my game crash in these areas, you can run around and move the camera, if you move the camera just right they will even go away.

I also want to point out that the random crashes are seemingly caused by the random vertex explosions. If you leave a random vertex explosion on the screen, each frame being drawn has a chance to crash the game with the error Graphics device lost, probably due to internal error. Noticeably, the more intense the zone, the more likely they cause a crash. This is a significant problem when trying to explore Jibral Castle and Town, as simply exiting a shop into the city had a roughly 75-90% chance to crash the game.

I used the following configuration to complete a playthrough and had no crashes and only had to push F5 a small handful of times to fix some rare minor texture issues now and then. (With these settings, random vertex explosions are gone but there are a handful of areas with consistent explosions that this wont fix.)

fullscreen = true

texture_cache_memory_limit_soft = 768             	
texture_cache_memory_limit_soft_lifetime = 60   

texture_cache_memory_limit_hard = 1536            	
texture_cache_memory_limit_render_to_texture = 48 

d3d12_clear_memory_page_state = true

Remaining Issues:

Expand

• Shading issues on Furry/Feathered characters. The fur appears to show correctly when close up, but becomes solid black from far away. (Any of the sheep tribe, Rat Monsters, Cat Monsters, Kluke's Shadow, Marumaru's Shadow, or Zola's Shadow)

• 'Consistent Vertex Explosions' and shading issues in some side houses. (The 3 Civilian houses in Pachess Town for example)

• Texture caching/swapping/pollution issues:

  • Navigating through the accessories menu will consistently show the wrong texture for the current selected accessory.
    (ie. a Dog Collar shows the texture of a Black Belt or something else.)
  • On rare occasion terrain and various battle UI elements will also show some texture swaps.
  • (All these texture issues can be fixed temporarily by pressing f5, but whatever is causing the problem will ultimately happen again eventually requiring another f5 press)

[CaelThunderwing]

Using the below settings and using Xenia Canary Build: canary_experimental@fac2a89d0 on Oct 24 2022 I was able to discover that the setting d3d12_clear_memory_page_state = true nearly completely fixes the random vertex explosions (and the random crashes) in roughly 99% of the game. F4/F5 is no longer required to be pressed every single time you load a zone/cs. (It also fixed the vertex explosion/terrain issues when flying the mechat.)

Random crashes and 'Random Vertex Explosion' fix:

Expand

Remaining Issues:

Expand

looks like your settings w/ the Jan 23rd 2023 Canary build introduced a new texture Issue.

[DaSk79130569]

First cutscene after Blue Dragon title drop exhibits massive flickering (all settings at default, Canary Feb 17 2023 build).

[dmjohn0x]

Tested on the main branch and Canary... Lots of display issues in this game. F4 sometimes fixes the issue. And after a while, the game innevitably crashes. (Usually within 20mins on Canary, an hour or so in the main branch.). Performance seems higher in Canary, but due to visual bugs on both branch's as well as crashing, the game isnt actually playable.

My PC: Ryzen 2700X, Windows 11, 32gb DDR4 3600, and RX 5700XT. Running latest builds of both branches as of 4/12/23.

[Elzarke]

Hi

, it's the first time i'm using xenia and i was hoping that you could help me. i went trough this and i don't know if it's because i missed something in the settings or anything. It seems like the only moment it occure is when the texture is like furish. Thanks in advance. my setting:xenia-canary.config.txt

xenia-canary.config.txt

[bferguson3]

Game is unplayable in newest Canary. Triangles everywhere flooding screen any time you load more than 1 scene (vram overload? Pointer math error?)

Either way, still works on regular xenia.

[giaxxx3]

Game is unplayable in newest Canary. Triangles everywhere flooding screen any time you load more than 1 scene (vram overload? Pointer math error?)

Either way, still works on regular xenia.

am sorry to ask, but im having freezes entering in a specific area in disk2 of blue dragon and i dont really know what is getting me the problem. Am playing via steam deck, xenia canary

[Sebbo401]

Hi

, it's the first time i'm using xenia and i was hoping that you could help me. i went trough this and i don't know if it's because i missed something in the settings or anything. It seems like the only moment it occure is when the texture is like furish. Thanks in advance. my setting:xenia-canary.config.txt

xenia-canary.config.txt

Hi, have you found a solution for this bug? I have the same problem running the game on steam deck. Seems this problem only happens if fur or feather textures are used.

Kluke's Shadow Phoenix has the same problem like the sheep people.

My graphic settings:

gpu=d3d12

vsync=true

clear_memory_page_state=true

texture_cache_memory_limit_hard=3072

texture_cache_memory_limit_render_to_texture=
96

texture_cache_memory_limit_soft=1536

texture_cache_memory_limit_soft_lifetime=120m