https://linen.dev logo
Join Discord
Powered by
# lime
  • t
    aight I got it now, also why does the picture here depict the camera as if it has some positive y value while its just (0, 0, -3) which should look like as if its laid down on the origin or something

    https://cdn.discordapp.com/attachments/769686258049351722/1105926391230382181/image.png▾

  • h
    No idea but in his code the camera is elevated a bit to give a more interesting view
  • a
    you can only use it with AlSource, I've got some samples I should upload to github
  • t
    alr just wanted to make sure, and sorry another question to this, so he doesn't explain the normalization part, so does normalizing the vector essentially mean to set its length to 1? (like in the picture) and secondly, why even do that?

    https://cdn.discordapp.com/attachments/769686258049351722/1105927955567358132/image.png▾

  • r
    elaborate
  • r
    i mean i know how its supposed to work
  • r
    the problem is that source3[i/f] take ints/floats as their last argument, while in the document the last argument is always the adress towards the actual ALFilter (in those cases at least)
  • r
    which makes sense considering there they're stored in integers
  • r
    but it simply doesnt work for haxe
  • r
    and has been overseen completely (since in haxe you have actual ALEffect and ALFilter objects instead of ID's)
  • r
    uiFilter[0], in this code, is an Int

    https://cdn.discordapp.com/attachments/769686258049351722/1105928952792485938/137e0b4d05dd69e0bba0c38574999493.png▾

  • r
    works just fine
  • r
    but as i said since theyre stored as actual objects on the haxe port they do not work with the Int parameter
  • r
    which there is simply no way around for
  • r
    considering the ALEffect/Filter objects have no field representing an integer id or anything alike that could possibly be used for that argument
  • r

    https://cdn.discordapp.com/attachments/769686258049351722/1105929409002741930/ca0836174c2461c1ab1ce54872773343.png▾

  • r
    however, with sourcei you can send direct filters
  • r
    since sourcei takes a dynamic type argument
  • t
    > The main reason we use normal vectors is to represent a direction; for example, if you are modeling a light source that is an infinite distance away, you can't give precise coordinates for it. But you can indicate where to find it from a particular point by using a normal vector. I found that, but I'll pretend I understand. I probably need to watch a linear algebra course before proceeding
  • r

    https://cdn.discordapp.com/attachments/769686258049351722/1105929929482309795/f951918e0a13b8c448458490e8433d64.png▾

    https://cdn.discordapp.com/attachments/769686258049351722/1105929929738166323/b68d142d877a4c0bb5eddb4a9933b620.png▾

  • r
    why doesnt source3i ??? no idea!!
  • a
    give me a moment to digest all this, it all worked fine last time I tried
  • a
    but it's possible you're trying something else
  • r
    its all good im just giving you context on what i already know
  • a
    I've definitely had filters and reverbs going
  • r
    well yes effects arent a biggie
  • r
    and as i said, direct filters should work just fine
  • r
    however filters attached to aux slots do not work
  • a
    hmm
  • r
    to be fair this isnt that big of a problem
1...113114115...138Latest