Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 04 07:30
    hjpfyf opened #31
  • Aug 21 15:59
    Befzz opened #30
  • Jul 23 02:55
    Systemcluster opened #29
  • Jun 04 08:13
    xoyojank commented #27
  • May 31 06:41
    godlikepanos commented #26
  • May 31 05:37
    Ternvein commented #26
  • Apr 23 17:52
    Sparking2 opened #28
  • Apr 10 09:27
    marcovidaurre opened #27
  • Apr 04 13:20

    stef-levesque on lsp

    :alembic: Experimental support … (compare)

  • Apr 04 12:42
    stef-levesque commented #23
  • Apr 01 04:57
    ikrima commented #23
  • Mar 30 12:32
    stef-levesque commented #23
  • Mar 30 12:31
    stef-levesque commented #23
  • Mar 29 05:55
    ikrima commented #23
  • Mar 06 20:51
    godlikepanos opened #26
  • Feb 01 23:01
    mjbvz commented #24
  • Jan 14 06:49
    greggman commented #21
  • Nov 22 2018 18:08
    stef-levesque commented #25
  • Nov 22 2018 15:33
    Max1412 commented #25
  • Nov 22 2018 15:33
    Max1412 commented #25
-HP
@bokuco_osu_twitter
Hey, i got a problem with my GLSL syntax highliter
it seems like it doesnt recognize .fsh files
stef-levesque
@stef-levesque
There is a bit of a conflict between HLSL and GLSL files
I use the following convention :
.glsl, .frag, .vert, .fp, .vp, .geom files : GLSL syntax
.fx, .hlsl, .vsh, .psh files : HLSL syntax
Although, you can add this to your vscode settings.json to manually associate files with syntaxes:
"files.associations": {"*.fsh":"glsl"}
You can even specify it per project
SSBMTonberry
@SSBMTonberry
Hello
Got a bit of a problem displaying images via shader toy for vscode
void main()
{
vec2 uv = (gl_FragCoord.xy / iResolution.xy);
uv.y += .05 sin(iGlobalTime + uv.x 10.);
uv.x += .05 sin(iGlobalTime + uv.y 10.);
vec4 color = texture2D(iChannel0, uv);
color = color * color;
gl_FragColor = color;
}
stef-levesque
@stef-levesque
Sorry, you have the wrong room :smile:
Looks like a nice extension, though
SSBMTonberry
@SSBMTonberry
Oh, damn
They don't have a room like this :(
Sorry for the disturbance, this extension is wonderawesome :D
stef-levesque
@stef-levesque
You probably can log a issue on his GitHub project
Noah Santschi-Cooney
@Strum355
hey, hope you see this message sometime soon. i was asking if i would be able to work on a seperate fork of your plugin for a specific community. we have a lot of non-standard things in our shaders + shader parsing, hence i thought it would be a better idea to keep it seperate :) full attribution would naturally be given to you for the underlying base
stef-levesque
@stef-levesque
Hey, what kind of non-standard thing do you have? Is it GLSL or HLSL related ?
Noah Santschi-Cooney
@Strum355
glsl, we have a lot of stuff that is parsed in various comments, drawbuffer formats, drawbuffers used as well as CPU-side constants being set via the shaders, as well as #includes
stef-levesque
@stef-levesque
I don't do any syntax parsing on GLSL. It is planned, but haven't start working on it.
If you want to have a look at it, I don't mind you creating a fork. If it's open-source, I might have a look.
Noah Santschi-Cooney
@Strum355
most of the stuff i feel isnt used outside of our community, hence i felt like it wouldnt have a specific place in your general plugin
we have 7 drawbuffers to work with, and up to 10~ composite passes, and we define which drawbuffer to render into at each pass in a comment per file, and i was wanting to add warning functionality etc, stuff that isnt used elsewhere at all to my knowledge
things like that ^^
itll be open-source for sure
Matthew Nichols
@Polkm
Anyone here?
stef-levesque
@stef-levesque
Yes
Noah Santschi-Cooney
@Strum355
o/