Closed Nolram12345 closed 4 months ago
Not sure how your file was created, but if you look at the hexcode, you'll see non-ascii chars in the first few bytes., using xxd chromatic_aberration.txt
, we see
00000000: efbb bf2f 2f2d 2d2d 2d2d 2d2d 2d2d 2d2d ...//-----------
00000010: 2d2d 2d2d 2d2d 2d2d 2d2d 2d2d 2d2d 2d2d ----------------
Also there is windows style carriage return 0d0a
00000050: 2d2d 2d0d 0a2f 2f20 4368 726f 6d61 7469 ---..// Chromati
These are not what matc
expects as input.
This file was created by creating a new file in Clion, the IDE recommended for Filament development. No idea how that got there. What formatting does matc expect as input?
With testing, it looks like matc can handle CRLF
(windows new line) fine. So it's probably just those errant bytes at the beginning that was the problem. I don't know if there's a strict definition of the input for matc
, but as long as you can fix those bytes, you're good I think.
Describe the bug When attempting to compile a material that #includes the attached fragment shader file, the compile fails on a non-existent character (Ç).
To Reproduce Steps to reproduce the behavior (not tested yet):
Expected behavior The shader should compile correctly (or at least error on an actual error) and not fail on this non-existent symbol.
Logs
Additional context Tried this on Windows 10 22H2, using Clion as an IDE, on a fresh clone of the Filament repository. This issue may be user error - I'm only just attempting to get my bearings in working with Filament's internals by implementing a simple post-processing effect.
I had to attach the .fs file renamed to a .txt due to GitHub limitations.
chromatic_aberration.txt