Whoops, looks like I ran into a bug or something in Metal specific to the video card I'm using: http://stackoverflow.com/questions/31925440/metal-texture-mapping-on-mac-os-with-swift …
-
-
Replying to @robinkunde
@robinkunde You should ask@warrenm if he's familiar with this.
1 reply 0 retweets 0 likes -
Replying to @RedQueenCoder
@RedQueenCoder@robinkunde Textures flipped vertically (Tri) Incorrect tex coords Incomplete mipmap levels (Cube) No depth state/texture1 reply 0 retweets 2 likes -
Replying to @warrenm
@warrenm@RedQueenCoder@robinkunde I’m that which had no problem. We should maintain a place to find out if our problems are consistent.1 reply 0 retweets 1 like -
Replying to @jessyMeow
@jessymeow@warrenm@redqueencoder@robinkunde I would love to help with that.3 replies 0 retweets 1 like -
Replying to @gpu3d
@mhorga_
@jessyMeow@warrenm@RedQueenCoder Check it out at https://github.com/robinkunde/MetalTextureMapping …2 replies 0 retweets 0 likes -
Replying to @robinkunde
@robinkunde Looks like an NV-specific compiler bug possibly related to packed struct member offsets. Workaround: https://gist.github.com/warrenm/63e467d387890f517f65 …3 replies 0 retweets 1 like
@mhorga_ I’ve seen packed type-related issues before, so once I narrowed it down to that I played around with ways to reinterpret the buffer
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.