| 26 Apr 2023 |
 jasperrlz | They don't work on web either | 14:43:01 |
| 29 Apr 2023 |
|  imlostlmao joined the room. | 11:09:42 |
| 2 May 2023 |
 kvark | Where do people go chat about gameplay programming, tools, physics, etc (unrelated to Rust)? I’ve always been in contact with graphics devs, but I’m curious where the other groups live. | 02:54:40 |
| jasperrlz | there's a few communities I've been in for tools. Physics, I have no clue about | 03:12:19 |
| kvark | jasperrlz: could you hook me up to them? | 03:27:49 |
| 7 May 2023 |
|  @g-tenko-r:matrix.freyachat.eu joined the room. | 15:11:39 |
|  @ralph:fx45.in joined the room. | 19:31:20 |
| 12 May 2023 |
|  @volsunghel:matrix.org left the room. | 10:50:44 |
| 14 May 2023 |
|  Fernando Raviola joined the room. | 06:25:27 |
|  @heavyrain266:mozilla.org changed their profile picture. | 20:27:23 |
| kvark | Anybody tried Optick profiler? I enabled it through profiling, added start_capture/stop_capture, it spew a giant files (for the first segment). Opening this file seems to hang Optick. | 22:35:20 |
| 18 May 2023 |
| @g-tenko-r:matrix.freyachat.eu left the room. | 04:24:14 |
| 19 May 2023 |
| @heavyrain266:mozilla.org changed their profile picture. | 14:18:49 |
| @heavyrain266:mozilla.org changed their profile picture. | 14:18:57 |
| 20 May 2023 |
| @ralph:fx45.in left the room. | 22:06:34 |
| 24 May 2023 |
| @heavyrain266:mozilla.org changed their profile picture. | 15:58:13 |
| 26 May 2023 |
|  nul1 joined the room. | 14:03:42 |
| 1 Jun 2023 |
|  niggerius joined the room. | 21:53:27 |
| 3 Jun 2023 |
| kvark | Is RenderDoc crate working for people?
I'm trying it on windows, RD 1.27, and it's not capturing | 19:21:10 |
| kvark | hmm ,was able to get it by checking "Auto Start", even though it shouldn't be applicable | 19:24:44 |
 cwfitzgerald | Just captured using wgpu's integration yesterday off wgpu trunk | 19:25:17 |
| cwfitzgerald | Are you capturing the submit? | 19:25:41 |
| kvark | yeah. Seems rather wonky... but works, phew | 19:29:58 |
| kvark | debugging on AMD Windows Vulkan is really the most painful thing I've experienced
AMD apparently abandoned the graphics debugging tools? It only has RT debugging and profiling.
There is no way to see textures and stuff :/ | 19:30:43 |
| kvark | they used to have AMD CodeXL, PerfStudio, which were ok. But now it's just a wild west.
And to add insult to injury, RenderDoc refuses to work with any RT apps
So now I have to isolate non-RT code into a separate executable/code path, just so I can capture it and see... | 19:31:38 |
| cwfitzgerald | You're supposed to use renderdoc, they have integrations with renderdoc - the problem ofc is rdoc doesn't support RT | 19:31:43 |
| kvark | AMD is really dropping the ball here. If they are relying on RenderDoc, they've got to convince Baldur to work on RT. | 19:32:14 |
| cwfitzgerald | Another strike against vulkan | 19:32:34 |
| cwfitzgerald | It's a larger problem that vulkan doesn't actually consult the debuggers before they Implement features, whereas something like pix is maintained by the dx12 team so they're very aware of what they can and can't Implement in it easily | 19:36:39 |
| kvark | oh boy, I have to add thread::sleep at the end of the app for RD to actually grab that capture. This is bad | 19:37:08 |
