Post

Replies

Boosts

Views

Activity

Comment on Metal Developer Tools on Windows Companion File issue
Sure thing I will try this out and get back to you. I've also tried to do it by embedding sources instead of extracting into a companion file but Xcode ends up showing "No source" in a window where you'd expect the source. I inspected the shader properties in the debugger and it showed the filepath as if it was on windows still. I suspect, it's trying to locate the original source file and failing to do so. I ran the exact same commands through xcrun and everything worked like a charm.
Topic: Graphics & Games SubTopic: General Tags:
Feb ’22
Comment on Metal Developer Tools on Windows Companion File issue
Just to clarify, compiling from %temp% drive fixes the original error but we're back to "No Source" in xcode debugger
Topic: Graphics & Games SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’22
Comment on Metal Developer Tools on Windows Companion File issue
Created a new ticket in feedback assistant FB9959429
Topic: Graphics & Games SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’22
Comment on Metal Developer Tools on Windows Companion File issue
So I tried to generate the dsym companion file in the same disk as %TEMP% but this is the warning that I get: warning: 'test.metallib' architecture air64_v21 does not support a companion MetalLib; copying verbatim Note the same commads work fine using xcrun
Topic: Graphics & Games SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’22
Comment on Metal Developer Tools on Windows Companion File issue
Yes I'm on latest Xcode release. I'll do a feedback assistant and update here asap
Topic: Graphics & Games SubTopic: General Tags:
Replies
Boosts
Views
Activity
Mar ’22
Comment on Metal Developer Tools on Windows Companion File issue
Sure thing I will try this out and get back to you. I've also tried to do it by embedding sources instead of extracting into a companion file but Xcode ends up showing "No source" in a window where you'd expect the source. I inspected the shader properties in the debugger and it showed the filepath as if it was on windows still. I suspect, it's trying to locate the original source file and failing to do so. I ran the exact same commands through xcrun and everything worked like a charm.
Topic: Graphics & Games SubTopic: General Tags:
Replies
Boosts
Views
Activity
Feb ’22