missing scene.obj for tutorial_vk sample

[oscarbg]

Hi,
compiling tutorial_vk needs scene.obj file.. dx same..
can include simple obj..
thanks..

[himanshugoel2797]

I just used the sponza.obj from here https://github.com/jimmiebergmann/Sponza

[ilyas-gazizov]

We will probably add a simple scene a bit later. Sponza is a good one for experiments as mentioned above.

[oscarbg]

Ok, thanks for help..
@igpooh I don't want to open another issue but once you select a default ".obj" for the samples to run would be nice to add to README.md some expected performance numbers on Mrays/s on various AMD hardware.. for example on a Vega 56 I was getting from a simple "cube.obj" ( seeing the console output) something like 450Mrays/s and on Titan V >1000Mrays/s if I remember correctly..
other issue I could open (altough lame one) is that one sample backend seems missing printing to console the Mrays/s.. I believe VK prints Mrays/s but DX12 backend not..
I know RadeonRays is for devs but anyway for "curious" users would be nice to have this performance numbers on various GPUs and compare performance differences of DX12 and Vulkan backends..
sorry for long response..
will be closing later once scene is added if you don't mind..

thanks..

[norsetto]

Still have to check the code, but is this what one should get with the sponza scene?

[himanshugoel2797]

Yep. That's exactly what I get. The colors are the UV along the triangle.

…

On Sat, May 16, 2020, 9:31 AM norsetto ***@***.***> wrote: Still have to check the code, but is this what one should get with the sponza scene? [image: vk_geom] <https://user-images.githubusercontent.com/3383359/82121000-2fb69f80-978a-11ea-9a63-c7f3cab39e12.jpg> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#208 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7OP7MUFBCQSYGOFEPLIADRR2ITFANCNFSM4NAC3TYA> .

[ilyas-gazizov]

Ok, thanks for help..
@igpooh I don't want to open another issue but once you select a default ".obj" for the samples to run would be nice to add to README.md some expected performance numbers on Mrays/s on various AMD hardware.. for example on a Vega 56 I was getting from a simple "cube.obj" ( seeing the console output) something like 450Mrays/s and on Titan V >1000Mrays/s if I remember correctly..
other issue I could open (altough lame one) is that one sample backend seems missing printing to console the Mrays/s.. I believe VK prints Mrays/s but DX12 backend not..
I know RadeonRays is for devs but anyway for "curious" users would be nice to have this performance numbers on various GPUs and compare performance differences of DX12 and Vulkan backends..
sorry for long response..
will be closing later once scene is added if you don't mind..

thanks..

Yes, sure, I will add the performance results printing for DX12 in the upcoming version. Some performance numbers will be included too.

[oscarbg]

@igpooh thanks..