ubc-aamodt-group / vulkan-sim

Vulkan-Sim is a GPU architecture simulator for Vulkan ray tracing based on GPGPU-Sim and Mesa.
Other
50 stars 11 forks source link

Error while running other traces #9

Closed pratyush48 closed 1 year ago

pratyush48 commented 1 year ago
  1. While running other traces:

Raytracing

vulkan_samples

I am getting these errors. Kindly let me know how I can solve these errors.

  1. After dumping the traces(https://github.com/ubc-aamodt-group/RayTracingInVulkan) takes a very long time to run and at the end gives a segmentation fault stating the root node is unable to access an address. Is there any way I can run the traces in batch mode or limited to an area so that the time to run traces decrease significantly?
mohammadrezasaed commented 1 year ago
  1. For RayTracingInVulkan can you remove the --fullscreen argument and try again? For Vulkan-Samples just looking at the error there seems to be a font missing. Can you install the font and try again?
  2. Are you using the traces we provided? If you are dumping them yourself can you fix the error above and try again? You can render your images on a lower resolution when dumping the trace for faster execution. You can edit the resolution after dumping in the 0.callparams file.
pratyush48 commented 1 year ago

The traces you provided work. I changed the resolution after dumping and the time it took to render was significantly less. Can you suggest to me which font I need to download in order to run Vulkansamples? For RayTracingVulkan when I removed the --fullscreen argument it still gave the same error, is there anything else I am missing?

mohammadrezasaed commented 1 year ago

In the image you provided I can see there's an error with not finding a font in the assets/fonts folder. Also note that you should execute Vulkan-Samples from the parent Vulkan-Samples folder and not the folder that contains the binary file. ./build/linux/app/bin/Debug/x86_64/vulkan_samples sample raytracing_extended

For RayTracingInVulkan I can see an error with not finding the compute queue. Are you using our version of RayTracingInVulkan? We removed the compute queue from the original version since it wasn't being used.