Note: Add the flag --gpu=vulkan to enable the Vulkan backend!
1.Dragon Ball Z: Battle of Z- https://www.youtube.com/watch?v=lI7i18Q8DQ0
2.Fist of the North Star - https://www.youtube.com/watch?v=i_l1SwB-ebw
3.Rayman Origins- https://www.youtube.com/watch?v=jkcWgQxLB7M&feature=youtu.be
this log is for halo spartan assault AMDGpu
xeniaamdHSA.txt
I haven't got any logs or videos, but I've noticed that many games have inverted colours on the vulkan build. Seemingly only effecting red and blue colours.

opengl left, vulkan right

vulkan left, opengl right
admittedly my OpenGL build of xenia is relatively old.
alright > http://pastebin.com/Ve0j7Nis
Okay that's not too good - it's crashing trying to compile a shader. I wonder if it's related to this.
Edit: On second thought - it isn't related to that thread. It's crashing trying to compile simple shaders.
Ok so what can be done I'm on mobile right now
ok im home i compiled the new build and still crashes > http://pastebin.com/U0Lun7Js
@Gamedev1909 Okay, make it crash again then go to Debug -> Save Dump As..., then save the minidump and upload it.
Could you select "Minidump" in the save-as type instead of the one with the heap?
didnt know that was a option i updated the link with the right one
Awesome - thanks!
anytime my amd gpu is at your command
Can you regenerate the dump using the build I provided here?
yup let me boot into windows 10
https://www.sendspace.com/file/0oag1y here ya go
The red/blue issue looks the same as xenia-project/game-compatibility/issues/206 and #460
F> 00000024 Device::ResolvePath()
G> 00000004 Generated pixel shader (36b) - hash 52910627A8EDB5CE:
/* 0.0 _/ alloc colors
/_ 0.1 _/ exece
/_ 1 */ max oC0, r0, r0
that last build got a bit farther i checked the last few logs and this is new
@DrChat Crashing with Jun 6 build (attempting to load Red Dead Redemption).
Screenshot: https://dl.dropboxusercontent.com/u/91292881/ShareX/2016/06/2016-06-06_19-35-09.png
i7 4790k
gtx 980
I also have been trying Vulkan on AMD.
Tried today with the latest everything. (Xenia-vulkan commit b01903cc and Crimson 16.6.1)
Some quick observations (that you may already know):
cmp byte ptr [rax+20h],sil, where rax is NULL. When the 2 immediate drawer pipelines are created, this value is obviously not NULL. rax comes from another memory area that really looks like an internal data structure of the driver...Anyway, I'm not that surprised Vulkan crashes. The GLSL version of the translated shaders on AMD still have issues (see #416 for example). As the generated SPIR-V shaders have a very similar approach as the generated GLSL shaders (I assume, unless I'm wrong?), my guess is that it is the same bug, but manifesting differently because of the different backend.
@sephiroth99 If you can figure this out - that would be wonderful. I can't install AMD drivers on this computer which cripples my debugging capabilities.
Set a memory breakpoint on that internal data structure and see if you can find where the drivers touch it. May not be too straightforward unfortunately if it's allocated in different regions of memory every time Xenia is restarted.
If it's touched by another API call - wonderful! If not, we might need to submit a dump to AMD and get their help.
Download GPuOpen there might be a few things you could use or download the mesa drivers for linux they are open source and have vulkan in them as well those guys could help also
Hey. I tried Bomberman Live! and results:
http://imagehost.spark-media.ru/i4/BA2BB199-C99D-1EB9-B174-C666818D74D3.jpg Original Xbox 360 Picture
http://imagehost.spark-media.ru/i4/11B2A8AA-3016-8E0F-B4D9-FE95808E4713.jpg OpenGL Picture
http://imagehost.spark-media.ru/i4/BEC1F320-3435-B932-31D3-29E5E2802584.jpg Vulkan api Picture
Xenia builds from June 6, 2016
p.s. 'Bomberman Battlefest' on Vulkan make crash after load game level (OpenGL work equally Bomberman Live!)
@sephiroth99 / @Gamedev1909 Can you generate a crash dump from Banjo Kazooie/Tooie and upload it with amdvlk64.dll?
I'm gonna try and collect some information to post a thread on AMD's forums.
https://www.sendspace.com/file/u4ahyz you need the crash dumb from the other guy as i dont have that game but here is the amdvlk64
@Gamedev1909 The file you uploaded appears to be corrupted - could you try it again?
amdvlk64.dll.zip
compressed on os x so please use winrar to unzip
@Gamedev1909 Thanks - but looks like your drivers have been updated since you created that last dump. Can you recreate the dump and upload it again?
@DrChat Mafia 2 demo goes in-game in latest "master build". In "vulkan build" it's just black screen (no intro + no gameplay but it still goes in-game)
I tried to see from where the NULL value came from, but it does not seem straight forward, at that point it's practically reverse engineering AMD's driver...
I tried the trick I try with the OpenGL backend to disable the geometry shader (on OpenGL AMD it shows something instead of a black screen), but it did not change anything on the Vulkan side (still crashes).
I don't have Banjo games, I do my tests with Forza 2. If you have it I can send you a minidump and my vulkan dll.
@sephiroth99: I've got forza motorsport 2 - Go ahead and send me a minidump and amdvlk64.dll
@DrChat
I generated a crash dump from Banjo Tooie. http://www88.zippyshare.com/v/e1oNUIE2/file.html
Also I have a amdvlk64.dll - http://www63.zippyshare.com/v/2QLUcdfc/file.html
Drivers are newest (16.6.1). My gpu is R9 290.
@krzysztof860 Thanks! But I also need xenia.exe and xenia.pdb too since you built it yourself :P
@DrChat
Here you go: http://www69.zippyshare.com/v/Yk64As64/file.html (exe and pdb)
I also tried Banjo Kazooie. Dump: http://www52.zippyshare.com/v/wEwWOePP/file.html
Excellent - thanks.
@krzysztof860 If you can - do me a favor: set a breakpoint in amdvlk64.dll where it crashes and restart Xenia so it hits the breakpoint before it crashes, then dump that.
I see a pointer to pVertexInputState right before the NULL pointer making me think this isn't the shader compiler.
Okay AMD people - try it again with 7ef7cc39f586f4c06f0801955bcbac243f32b46a.
What games are you trying? For now you should keep it limited to games that are proven to work already.
red dead im about to try halo wars and minecraft and halo 4 all known to work
vulkan no difference on my gpu. it crashes on vkCreateGraphicsPipeline
GL4.5 shows black screen with sound. gpu amd radeon 8750m game Sonic CD
@DrChat
I don't know if I did it properly (Debug>New Breakpoint>Function Breakpoint and I entered pVertexInputState in Function Name).
There is dump from Banjo Tooie: http://www107.zippyshare.com/v/DQRaCUQN/file.html
Exe and pdb: http://www18.zippyshare.com/v/G2gLHKwl/file.html
@Gamedev1909
@nulcearc
@krzysztof860
thats a no go but thanks seems xenia busted vulkan on my system
Whilst probably not related directly to vulkan, I've noticed in the latest code audio is quite a lot slower than before. This is odd as there hasn't been any commits to /apu for 6 months. Sorry I can't provide any more info on that
@razzile Could you clarify which games you're seeing this behavior on? Does this slowdown also happen on the GL backend?
Forza motorsport 2 and 3D Ultra Minigolf 2 are the games I tested, both didn't have audio slowdowns previously. let me just test opengl quick
Okay I rebuilt xenia using the exact same commit and it's suddenly full speed again. Was likely a problem my end
hey if i make a thread about getting a game working would you help me collect everything i need to help you code for it
Upon investigation I found the specific commits that messed up numerous things in almost every gameplay accessible game.
From commit #518 fixed some shader issues in spyro which was amazing however commit #514 caused the viewport to go out of whack before crashing within seconds. But it didn't crash the graphics card. After #520 it started crashing the graphics card with no visuals ingame. So I think maybe reviewing those commits would be beneficial for a number of games. Sorry if this is a bit indecisive, isolatig commits on Appveyor is annoying XD.
Prevent some divide by zeros in shaders :

x64 Speedups (I think #524 may have been commited as well):

@ScorchEmber256 I've mentioned broken TLoS:DOTD a long time ago, but only on IRC chat I think and then it was propably forgotten.Benvanik brokes it when he was trying to fix https://github.com/benvanik/xenia/issues/473 propably.
Posted a thread on the AMD forums. Hopefully an AMD dev will lead me in the right direction.
if you need to email roy he will get you in direct contact with driver devs also i suggest signing up to get on IRC channel #radeon on irc.freenode.net for radeon users and developers.
Drchat you got a forum reply from a amd dev
It would be nice if can have a simply option to switch the GL and Vulkan backend
I will post some screenshots to current comparison ogl vs. vulkan backend.
Air Conflicts: Secret Wars

Asterix at the Olympic Games

Brave

Catherine

Iron Man

Virtua Tennis 3

The darker colors in some games is likely due to swapped channels, so it could probably be considered all one issue.
How about a DX12 backend to windows 10 users?
With GL being deprecated I don't think there are any plans to work on new GPU backends. Developing Vulkan is probably the priority currently.
As I've said before - no existing contributors plan on creating a DX backend. You are completely free to do so if you want to.
Is Vulkan eventually going to replace OGL?
@Margen67 Eventually, yes
AMD people: Try 036df2ce126c1ab8d1578d627c4b3e5ea4969be0 - it might be fixed now.
@DrChat , just wonder how to switch to Vulkan backend?
@raven02 See OP.
where do we add --gpu=vulkan
still crashes
@DrChat Unfortunately it still crashing. Tested on Banjo Tooie.
Minidump - http://www112.zippyshare.com/v/Pl2bTsD8/file.html
Exe and pdb - http://www48.zippyshare.com/v/JFmAQ7SC/file.html
@krzysztof860 - Can you attach the log file as well?
@DrChat Here you go - http://www94.zippyshare.com/v/jVNNgujm/file.html
Neat - this looks like a new crash now.
thanks @DrChat
Okay - AMD is gonna be on hold til Monday.
Dragon Ball Z Budokai HD Collection:




I think this crash was posted before, but I can't find it right now.
http://i.imgur.com/06LFd9M.png
COD4 SP @ first mission - crashes in nvidia's nvoglv64.dll
*edit: Same for skyrim.
[Crash]
*Naruto: Rise of a Ninja
Unhandled execption at 0x00000000023251fc (nvoglv64.dll)
Output : https://gist.github.com/SakataGintokiYT/d43af27cfdb52dae185e247d678673ca
Log : https://gist.github.com/SakataGintokiYT/d8091e4fd51d8d8ac13b93537e566125
[Black screen ]
*Naruto - The Broken Bond
Output : https://gist.github.com/SakataGintokiYT/6ae2a70b347e63ca0c34f4042073635e
AMD people - Try it again with 75908a9865b27b2eeaa21a15e3b14c9777b00d56.
Tried 9abfc52 still crashes at the same place.
I had tried the SPIR-V validator before, it did not find any issues; it is still very much a work in progress.
I will upload the newly generated shaders to the AMD thread.
@sephiroth99 Alrighty - if you want you can take over that thread and I'll keep an eye on it.
Neat - AMD is no longer crashing as of 14a6fd838a362031195de05a37fafd0941e689a9.
@Gh0stblade Which games?
@krzysztof860
@woody2014
@Gamedev1909
Try latest build
Good job it`s not crashing But have a blank screen.
@DrChat Nevermind, no crashes. Looks like Github desktop app didn't properly pull down the latest commits.
@woody2014 Same here, just black screen.
could someone link the newest build please thanks
@DrChat - Can confirm that AMD doesn't crash anymore, but that it only shows black screen. Tested Banjo and Kazooie and Bomberman. They both play audio and accept input, just no video output.
Wonderful - Someone with experience in renderdoc, can you capture a trace and start analyzing it?
Launch Xenia with renderdoc using these flags: "--flagfile=scratch/flags.txt --vulkan_primary_queue_only=true"
When in-game, press F4 to capture a trace and close Xenia after it's finished writing it.
I can't do anything with the tracefile from here, so don't upload it.
i tried adding those flags but it doesnt open
can we open a file in the vulkan backend then trace file.
@Gamedev1909 - did you build it yourself? Otherwise you wont have the flags.txt file and it wont open. I managed to generate the trace, but renderdoc can't open the file, so I'm probably doing the wrong. I'm not really qualified to debug it anyway, but if you have any insight into why it wont open (says wrong magic header) @DrChat ?
yes i built it my self i do get a -- jit error when trying to run some games
has this black screen vulkan issue been fixed and no one said anything ?
Nope. Still need someone competent to run a trace on an AMD card.
i can't get your trace flags to work but i did get a trace for you
Trace.zip
Tested with 16.7.2 Hotfix, still the same.
Radeon R7 200
DrChat since those flags you said to use casues a crash if there any other thing i can do to gather a trace? besides what ive done insider builds are over for now
So now all Xenia does with Vulkan on AMD is Crash. GG AMD
Tested again with Minecraft.
Crashed after load the file.
-Radeon R7 200
-Driver 16.7.3 AMD Crimson Edition 28/07/2016
-Xenia build f81a99e 29/07/2016
I tried some games that were proven to work, same result.
I tried Sonic 2006, And Naruto Storm 2
AMD people: I'm working on the crashes and blackscreens - be patient.
i am about to help you with crash reports and a trace if i can
xeniaDump.zip
newest 16.7.3 drivers on windows 10 RS1 14393.5 RTM
also i am learning Vulkan to try and help in the future
@DrChat
Progress :)



can you link me that build ? and was it on amd?
@Gamedev1909
Build from appveyor
https://ci.appveyor.com/project/benvanik/xenia/build/1.0.451-master/artifacts
@SakataGintokiYT
I get some exception here (AMD):
xenia.exe!xe::gpu::vulkan::CachedRenderPass::CachedRenderPass(VkDevice_T * device, const xe::gpu::vulkan::RenderConfiguration & desired_config) Line 441 C++
solid build for opengl 4.5 but vulkan i hear sonic 06 and bam crash
well now opengl is broken and vulkan
Vulkan backend in a nutshell: https://youtu.be/68ugkg9RePc
@DrChat
look at this : [Work around semi-broken dual-source blending on AMD.] / Dolphin
https://github.com/dolphin-emu/dolphin/pull/3935/commits/e253a1673905b0b7df1fc59035b416c53b6d8d85
I think the current issue with Vulkan crash on AMD is due to this (extracted from Vulkan spec here):
Multiple attachments that alias the same memory must not be used in a single subpass
I tried to separate the 4 color attachments into 4 subpasses, and the subpass create command does not crash anymore. Now, of course the rest of the code is not made for 4 subpasses so I had other issues e.g. dependencies, but the crash is due to the single subpass I think.
Sorry for off-topic, but @DrChat someone wants to give you a R9 270X (2GB)
https://www.reddit.com/r/xenia/comments/4y25ag/help_with_donating_a_gpu_to_the_xenia_devs/
I would assume he wants a full system, ripping out a working gpu in your own personal system with one some randomer has sent you to fix 1 issue probably isn't a great idea :s
this isnt one issue this is a huge issue for everyone with amd cards so it's a good thing
@DrChat
Progress !!!
Xenia Vulkan build : [9457c63]
_Video : https://www.youtube.com/watch?v=GUzDHodfmE4_

Vulkan proves to be a giant turd for amd i hope someone adds direct x 12 soon that api is hard to mess up on any gpu
I hope DX12 is added anyway so the speed can be compared to Vulkan.
All NFS games using EAGL4 (Most Wanted, Carbon and Prostreet) crash at startup on Vulkan despite being close to playable on OpenGL
Here's the Carbon log for example
any news?
amd released new drivers that 'supports' glsl 4.5
only a year or so too late lmao
its never to late
Sent from my iPhone
On Oct 5, 2016, at 4:26 PM, Satori [email protected] wrote:
only a year or so too late lmao
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
I will update the driver and test here.
Tested: still the same results
@Gamedev1909 https://youtu.be/lL2ZwXj1tXM
@DrChat hey tried the newest build still a no go do you need anything a dump maybe?
xenia.zip
here is a dump for kicks
anyone thinks to write D3D12 back-end for Xenia?
That would have been the best idea from the start not sure why it wasnt done. Vulkan was a mistake sadly as its way to busted
Sent from my iPhone
On Jan 14, 2017, at 3:28 AM, NuclearC notifications@github.com wrote:
anyone thinks to write D3D12 back-end for Xenia?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
The Vulkan backend is a work in progress.
but fcking DirectX 11 is faster than Vulkan
EDIT: here is some benchmark http://arstechnica.com/gaming/2016/02/vulkan-benchmarks-a-boost-for-amd-and-nvidia-but-theres-work-to-be-done/
If you think so, feel free to implement a DX11 or DX12 backend yourself.
i didnt say i can do it better, but i want to understand why @benvanik removed DX11 backend from start
Because DX11 was not meeting the demands of the emulator.
btw im getting 'Access violation reading location' exception on this line when using Vulkan on AMD driver:
return disp->CreateRenderPass(device, pCreateInfo, pAllocator, pRenderPass);
Thats the line 1653 in file 'trampoline.c' function vkCreateRenderPass which is called from CachedRenderPass(...)
Here is the image:

What can i do to fix this?
@NuclearC Increasing the number of good contributors. Capable people that want to spend free time solving this issue.
I remember very well in 2015 when someone asked about the issues about AMD videocard, and the answer was something like "wait for Vulkan to be released".
After Vulkan, the answer was "AMD should fix the driver", and now they say "You are free to do it yourself".
That doesn´t mean that they are not working hard but maybe people from another emulator team could help.
@ikki84 The solution for Vulkan issues is not "make DX11/DX12 backend instead", which is what I was talking about.
For @NuclearC's issue, the stack trace clearly shows a crash in AMD's code, which is extremely hard to debug without having access to AMD hardware (at least for myself, I do not have any AMD hardware).
I'd be happy to see more contributors, but I have no interest in soliciting other projects for them. Genuine interest is key.
I do have AMD hardware and also experience the same issues.
You should send your AMD hardware to a member of the team (most likely DrChat) so that someone can actually fix it then.
I would be happy to lend you my desktop remotely to debug
Sent from my iPhone
On Jan 14, 2017, at 3:21 PM, Rick Gibbed notifications@github.com wrote:
@ikki84 The solution for Vulkan issues is not "make DX11/DX12 backend instead", which is what I was talking about.
For @NuclearC's issue, the stack trace clearly shows a crash in AMD's code, which is extremely hard to debug without having access to AMD hardware (at least for myself, I do not have any AMD hardware).
I'd be happy to see more contributors, but I have no interest in soliciting other projects for them. Genuine interest is key.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
@Gamedev1909 Okay - hop on IRC @ #xenia-dev so we can discuss doing that.
I can on monday ? If my daughter isnt born that day my email is [email protected]
Sent from my iPhone
On Jan 14, 2017, at 5:23 PM, Justin Moore notifications@github.com wrote:
@Gamedev1909 Okay - hop on IRC @ #xenia-dev so we can discuss doing that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
i would be willing to help as i have AMD, just depends if i have the time.
@Gamedev1909 Congrats, good luck to you. Whenever you're free just hop on. Same to you @neolightning
https://drive.google.com/open?id=0B4wd1D7L6SRYVlJnLS0xTWFnYkU here is the codeXL debug info the only mention i saw of shaders was in Index, CmdBuffer #, Call, Parameters, GPU Time, Result, Start Time, End Time
11, CmdBuffer3, vkCmdPushConstants, 0x00000216cfc94f90,0x00000216cfcbe9c0,VK_SHADER_STAGE_VERTEX_BIT,0,64,0x00000083366ff0d0, after that i saw nothing relating to shaders besides GCN shaders
i uploaded a session about frame 6296 it had so much more info and it shows most of the results for calls are void and only 6 worked
I have AMD too, i want to help :D xD
Hey drchat im at the hospital my wife is having contractions and my pc is booted into macos 10.12.2 so use nuc if you want
Sent from my iPhone
On Jan 15, 2017, at 1:03 AM, NuclearC notifications@github.com wrote:
I have AMD too, i want to help :D xD
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
@Gamedev1909 slightly TMI on that last note but congratulations! Have you two decided what you'll name her?
Olivia like olivia benson from law and order svu
Sent from my iPhone
On Jan 15, 2017, at 11:30 PM, Haneef Mubarak notifications@github.com wrote:
@Gamedev1909 slightly TMI on that last note but congratulations! Have you two decided what you'll name her?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Vulkan no longer crashes with latest drivers Crimson ReLive Edition 17.1.1 but shows black screen.
Yup i let drchat debug on my system
Sent from my iPhone
On Jan 27, 2017, at 6:42 PM, woody2014 notifications@github.com wrote:
Vulkan no longer crashes with latest drivers Crimson ReLive Edition 17.1.1 but shows black screen.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Are we finally gonna get a working vulkan for amd
Maybe after more work
Sent from my iPhone
On Jan 27, 2017, at 8:01 PM, woody2014 notifications@github.com wrote:
Are we finally gonna get and Vulkan working
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Again crashing in debug mode:

Maybe this makes black screen?
Tried out Deadly Premonition (Red Seeds Profile) on Xenia. I had tested this a year or two ago and the game never got past the menu, Vulkan gets ingame with graphics at full speed now which is neat! Still hilariously broken with the text jumbled with English and Russian? I think. I didn't think York could look any more creepy than he already did.
Vulkan:
https://youtu.be/hLiI6pgbXHs
OpenGL:
https://youtu.be/IfMNkyaiUDY
@DrChat --gpu=vulkan isn't needed anymore.
@Margen67 that's because Vulkan has become the default renderer for Xenia.
Exactly so the issue should be updated.
in IRC is there any reason it wont let me talk in Xenia-dev channel ? says im banned from talking but i only joined to help you out dr chat?
You only need to be identified with NickServ afaik
hey DrChat i think it's time we do more remote debugging set a day and time let's get vulkan working for amd
i cant wait for vulkan version to work with AMD hardware :D
newest build crashes amd again
@Gamedev1909 MK vs DC not crashing here, just black screen as usual.
Hit F3, can you see the profiler?
@DrChat Yes. I can see it, and hear the audio too
What games are you trying on AMD?
Can you try banjokazooie / banjotooie / supermeatboy / marbleblast / minecraft / gripshift?
@DrChat Tested supermeatboy, also shows sound, not shows any rendering on screen.
Also I had to try to load it 4 times, crashed randomly in 3 tries...
According to my friend slash sonic unleashed renders images and works a bit https://cdn.discordapp.com/attachments/223866782539186177/280858668692668426/2017-02-13_16-31-48.png
Sent from my iPhone
On Feb 13, 2017, at 11:15 PM, ikki84 notifications@github.com wrote:
@DrChat Tested supermeatboy, also shows sound, not shows any rendering on screen.
Also I had to try to load it 4 times, crashed randomly in 3 tries...—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Where does AMD crash in super meat boy? Can you give me a callstack?
So after testing minecraft and hitting f3 i see
seems it shows issues with drawing
I've spotted a point in the render cache where our API usage is invalid @ render_cache.cc#425
According to API specification (7.7.1): "Multiple attachments that alias the same memory must not be used in a single subpass." We alias attachments which aren't written to.
AMD people: As a hack, change colorAttachmentCount to 1 on line 430. In pipeline_cache.cc#1410, echo the same change.
https://www.youtube.com/watch?v=DaojxkQ1Y8Q drchat you are going to love this
Awesome - can I get some screenshots from one of the games I mentioned earlier?
@DrChat
Changed the src/xenia/gpu/vulkan/pipeline_cache.cc
"state_info.attachmentCount = 1;"
also in src/xenia/gpu/vulkan/render_cache.cc
"subpass_info.colorAttachmentCount = 1;"
now, SMB always crash for a reason that I don´t know. Here is the log.
smb.zip
Let me know if there is anything to test, i do have Marble Blast on my pc if needed for that specific game
@DrChat here is another try log.
xenia.zip
@ikki84 The logs are useless in this case. Can you provide me with a callstack of the crash?
i dont have those games but i will buy em soon can someone post that hacked build
I can send Marble Blast if you give me a few
no i need the build with those changes drchat said i rather buy games
it's good to see vulkan making progress for AMD.
@Gamedev1909 for the record marble blast was removed from xbox live years ago. the only way to get it is either from an xbox that had it before or from someone else who has it
i have it on my xbox 360 so im good
ok im using codexl to debug and capture frames from sonic unleashed
from renderdoc
xen.zip
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
0x00007ff7aa7f9fe6 - xenia.exe
0x00007ff7aa7f3281 - xenia.exe
0x00007ff7aa7dd259 - xenia.exe
0x00007ff7aa7dbcd6 - xenia.exe
0x00007ff7aa7db60c - xenia.exe
0x00007ff7aa7dbbde - xenia.exe
0x00007ff7aa7db41c - xenia.exe
0x00007ff7aa7dab6d - xenia.exe
0x00007ff7aa7ddcec - xenia.exe
0x00007ff7aa821788 - xenia.exe
0x00007ff7aa81fc7a - xenia.exe
0x00007ff7aa70513b - xenia.exe
BaseThreadInitThunk - KERNEL32.DLL
your call stack sonic unleashed
your callstack for banjo will be soon
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
0x00007ff7f7129fe6 - xenia.exe
0x00007ff7f7123281 - xenia.exe
0x00007ff7f710d259 - xenia.exe
0x00007ff7f710bcd6 - xenia.exe
0x00007ff7f710b60c - xenia.exe
0x00007ff7f710bbde - xenia.exe
0x00007ff7f710b60c - xenia.exe
0x00007ff7f710bbde - xenia.exe
0x00007ff7f710b41c - xenia.exe
0x00007ff7f710ab6d - xenia.exe
0x00007ff7f710dcec - xenia.exe
0x00007ff7f7151788 - xenia.exe
0x00007ff7f714fc7a - xenia.exe
0x00007ff7f703513b - xenia.exe
BaseThreadInitThunk - KERNEL32.DLL
here is banjo k with the mods you asked us to do
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
vk_icdNegotiateLoaderICDInterfaceVersion - amdvlk64.dll
xe::gpu::vulkan::RenderCache::BeginRenderPass - render_cache.cc, line 688
xe::gpu::vulkan::VulkanCommandProcessor::IssueDraw - vulkan_command_processor.cc, line 567
xe::gpu::CommandProcessor::ExecutePacketType3_DRAW_INDX_2 - command_processor.cc, line 1117
xe::gpu::CommandProcessor::ExecutePacketType3 - command_processor.cc, line 591
xe::gpu::CommandProcessor::ExecuteIndirectBuffer - command_processor.cc, line 416
xe::gpu::CommandProcessor::ExecutePacketType3 - command_processor.cc, line 558
xe::gpu::CommandProcessor::ExecuteIndirectBuffer - command_processor.cc, line 416
xe::gpu::CommandProcessor::ExecutePacketType3 - command_processor.cc, line 558
xe::gpu::CommandProcessor::ExecutePrimaryBuffer - command_processor.cc, line 394
xe::gpu::CommandProcessor::WorkerThreadMain - command_processor.cc, line 161
std::_Func_impl<
xe::kernel::XHostThread::Execute - xthread.cc, line 1048
xe::threading::ThreadStartRoutine - threading_win.cc, line 428
BaseThreadInitThunk - KERNEL32.DLL
hope that helps
Any news for Amd people
so drchat any other ideas we can try ?
@Gamedev1909
@DrChat
Dragon Ball Raging Blast at AMD graphic card HD 7870
https://www.youtube.com/watch?v=YGB8LDB6HIo&t=0s
Thats odd every game i tested showed nothing new
Sent from my iPhone
On Feb 18, 2017, at 3:53 AM, ☠Emulator_Team☠notifications@github.com wrote:
@Gamedev1909
@DrChat
Dragon Ball Raging Blast at AMD graphic card
https://www.youtube.com/watch?v=YGB8LDB6HIo&t=0s—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Get the RX480 if you want to use it for more than just xenia, if you just want one for xenia, pretty much any Vulkan compatible Radeon Card should work
just go with whatever feels best for your needs
at least you can have tier 3 vulkan and no longer be restricted like with nvidia missing a ton of low level api hardware features

As posted on the fundrazr page, I've bought the card and it'll be here tomorrow.
we are gonna get Xenia on AMD soon :D
soon
â„¢ :^)
AMD people: You should start seeing stuff as of 44e7c3712acd6f3d9b52af4f77fd49f628f06767.

Nice!
ok cool im going to do some debugging on color errors and stuff and send it to you here
https://ci.appveyor.com/project/benvanik/xenia/build/artifacts best to post your appveyor on main page
drchat what are the settings for render doc or codexl it crashes on me
On AMD (R9 270X) here--Not seeing too much. Just HUD and BG stuff. Seems like anything that's 3D isn't being rendered.
Everything Crashes again
All of the titles I'm loading (that manage to get in game) don't render anything. Effects are showing up, but everything else isn't showing up.
newest build all games but star ocean 4 crash
If you're going to report such issues, you need to be more specific than "all games but thing crash".
@gibbed
I know that after I updated AMD's drivers to the latest one, Xenia would crash on Vulkan. I rolled back and am now fine. I'm not sure if that's related to the crashes Gamedev is experiencing.
@Irixion Useful if you can provide the specific version of the driver and your GPU model.
@Gh0stBlade Sure.
AMD R9 270x Driver version is 21.19.137.514 (Crimson 16.6) WHQL Win 10 64
@Gh0stBlade Previous to build 44e7c37, I would get nothing, so that seems to have at least gotten the 2D elements to display.
https://www.youtube.com/watch?v=R344TIDtbss
Here's a video. Ignore the weird compression artifacts, I don't know why it captured like that.
clicks load selects iso then crash....
repeat for all games
now if i did more detail like codexl or other tools he couldnt use it anyway so not much i can do
@Gamedev1909 I would uninstall the driver and let Windows install it. AMD's drivers are buggy at best. Though you could always upload a log so we can see what's causing it.
no this driver isnt buggy and for streaming with avc this is the only one that works 16.6 is way to old has major issues with other emulators that i have
...Let Windows install the optimal driver. Newer drivers have issues. Post the log so we can figure out why it's crashing (I don't feel like updating only to roll back)
no thanks i wont install a busted driver that prevents me from work that is counter productive not saying it again
If Windows' default drivers aren't working, then you have some other issues with your system.
The latest Crimson version is 17.4.4. That's unrelated to the driver version. 21.19.137.514 is 5 months old, not to mention I have a different card. Please post the log so we can have a look at it.
Edit: And since it did work before and now all of a sudden isn't working with recent versions, then it points to a driver bug, and not a bug with Xenia. Though again, the log will tell us what's going on if you post it.
no newest crimson is 17.5.1 and it was released may 5th 2017 gl4 works as needed so until vulkan is updated or fixed i will avoid testing for now good luck guys
15.5.1 is an optional update that only has bug fixes, and isn't the recommended driver by AMD. If anyone else presents the issue, I'll update it myself seeing as @Gamedev1909 isn't uploading the log.
OpenGL backend is deprecated, and isn't being maintained. Once Vulkan gets some TLC, I'm assuming GL will be removed.
We can't help you unless you post the log.
@DrChat @gibbed So I loaded a cut scene and this happened:
Looks like some textures and part of the cut scene (flames) loading amongst the garbled mess. Here's the log for that:
For good measure this is on the 4260e381 commit. Hope this helps!
I can confirm I'm also experiencing crashes after updating to the latest AMD drivers.
vkCreateImage returns VK_ERROR_INITIALIZATION_FAILED
@Gamedev1909
@Gh0stBlade
I will mention that AMD's Recommended Driver is 17.4.4, and not 17.5.1.
K> 0000011C XThread::Execute thid 26 (handle=0000011C, 'NoSyncThread (0000011C)', native=00001928)
i> 0000011C VdSwap(BFAA4C10, 4725FA70, BFFF3008, 4725FAB0, BEEF0001, 4725FA50(BF708000), 4725FA5C(00000006), 4725FA60(00000000), 4725FA58(00000500), 4725FA54(000002D0))
i> 0000011C VdSwap(BFAB3AEC, 4725FA70, BFFF3008, 4725FAB0, BEEF0001, 4725FA50(BF708000), 4725FA5C(00000006), 4725FA60(00000000), 4725FA58(00000500), 4725FA54(000002D0))
!> 00000004 Vulkan check: vkCreateImage returned VK_ERROR_INITIALIZATION_FAILED
That being said, the latest commit, 4e6a5147 gives me this error, regardless of driver version. My current driver, and the latest driver as well.
@DrChat Is there a specific version of Vulkan that we're supposed to have?
As i said sooo many times im not switching drivers to solve a issue that shouldnt be going on with rpcs3 vulkan doesnt stop working and cause mass crashing because of a driver change and that shouldnt happen here either so i gave my logs
At the moment AMD cards are crashing because they don't support D24
formats. I'm still working on a fix that isn't a complete hack.
On Wed, May 17, 2017 at 3:46 PM, Gamedev1909 notifications@github.com
wrote:
As i said sooo many times im not switching drivers to solve a issue that
shouldnt be going on with rpcs3 vulkan doesnt stop working and cause mass
crashing because of a driver change and that shouldnt happen here either so
i gave my logs—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/benvanik/xenia/issues/578#issuecomment-302226700, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACSoQeUVsxgmDD9DOa2aUgA4vZ2hbUUqks5r61y3gaJpZM4IuZSM
.
@Gamedev1909 You shouldn't be complaining. RPCS3 has a different team. Given the frequency of the updates there, I'm going to assume they have a larger team. The problem has been identified and fingers crossed, we'll see a solution soon. Thanks to all the hard work the contributes do! <3
it's not complaining it's informing you that i wont be switching drivers for the 6TH time so far don't ya think that 6 times is a little to much to try and convince a guy to go back to slower drivers... and no they dont have a larger team they just have more users more bug reports and they have @kd-11 who is a god among men for api fixes @DrChat maybe ask him for a fix he might have solved the issues already
AMD cards don't support D24 formats? Lame. I'm sticking with team green from now on. Seeing as this issue is probably a mammoth to fix, fingers crossed. Unfortunately my experience isn't enough for me to become a contributor.
@Gamedev1909 Slower drivers? ...That's not how it works. I merely recommended that you install the same drivers that AMD recommends for 200 series cards.
Amd doesn't recommend anything and seeing how the games I play are faster on 17.5.1 that is my best option also same for my render work and 3D modelling again no thank you
Sent from my iPhone
On May 17, 2017, at 7:03 PM, Irixion notifications@github.com wrote:
AMD cards don't support D24 formats? Lame. I'm sticking with team green from now on. Seeing as this issue is probably a mammoth to fix, fingers crossed. Unfortunately my experience isn't enough for me to become a contributor.
@Gamedev1909 Slower drivers? ...That's not how it works. I merely recommended that you install the same drivers that AMD recommends for 200 series cards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
RPCS3 has a bigger team, even said it yourself. More testers, more users, more devs. Turns out that makes things progress faster.
@Gamedev1909

You were saying? Drivers don't "magically" make things "faster". They fix bugs that cause performance issues. AMD has release notes for every update. The problem with being on the "bleeding edge" is that there are always bugs left to sort out. The latest driver now is 17.5.2. That being said, if something works on one driver version, and not on another, you can assume that it is the driver causing it. AMD's drivers aren't that great anyway, and they seem to break two things for every one thing they end up fixing. The fact that their cards don't support D24 formats is the last straw for me, because clearly AMD is inferiour in a lot of areas.
Instead of arguing, you could just, you know, agree to disagree. You don't want to change your drivers? More power to you. I don't care. Being on the bleeding edge updates can cause issues sometimes. I asked you to post logs before any changes to Xenia were made. Seeing as the recent commits of Xenia try to initialize D24 on AMD cards, regardless of driver, it doesn't really matter now. Not until the developers get some sort of workaround in place, which is probably going to take a long time seeing as it isn't something anyone can put together in a few hours.
Again, many thanks to all contributes to this project. You're the real MVPs. Out of curiosity though, is it all AMD cards that don't support this format? Is it on a hardware or driver level? All AMD cards I've had are more trouble than they are worth.
Let it go already you went from forcing advice to being a sad little person nothing your doing is helping keep the whining down to a min thanks
Sent from my iPhone
On May 19, 2017, at 12:52 AM, Irixion notifications@github.com wrote:
@Gamedev1909
You were saying? Drivers don't "magically" make things "faster". They fix bugs that cause performance issues. AMD has release notes for every update. The problem with being on the "bleeding edge" is that there are always bugs left to sort out. The latest driver now is 17.5.2. That being said, if something works on one driver version, and not on another, you can assume that it is the driver causing it. AMD's drivers aren't that great anyway, and they seem to break two things for every one thing they end up fixing. The fact that their cards don't support D24 formats is the last straw for me, because clearly AMD is inferiour in a lot of areas.
Instead of arguing, you could just, you know, agree to disagree. You don't want to change your drivers? More power to you. I don't care. Being on the bleeding edge updates can cause issues sometimes. I asked you to post logs before any changes to Xenia were made. Seeing as the recent commits of Xenia try to initialize D24 on AMD cards, regardless of driver, it doesn't really matter now. Not until the developers get some sort of workaround in place, which is probably going to take a long time seeing as it isn't something anyone can put together in a few hours.
Again, many thanks to all contributes to this project. You're the real MVPs. Out of curiosity though, is it all AMD cards that don't support this format? Is it on a hardware or driver level? All AMD cards I've had are more trouble than they are worth.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
No more arguing. This issue is locked for now.
This issue is no longer necessary.
If you have issues with Vulkan, create a new issue.
If you have questions, go to the subreddit.
Most helpful comment
AMD people: You should start seeing stuff as of 44e7c3712acd6f3d9b52af4f77fd49f628f06767.