We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Porting of code from V3D Code Examples to project’s “name.js” file

Home Forums Programming Porting of code from V3D Code Examples to project’s “name.js” file

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #62148
    Johnson
    Customer

    Hi Soft8Soft!

    Can anyone here please show me how to get these two from Verge3D Code Examples into the runcode section of my project’s .js file or into my project?

    https://github.com/Soft8Soft/verge3d-code-examples/blob/master/webgl_postprocessing.html (mainly focused on RGBShiftShader)

    https://cdn.soft8soft.com/demo/examples/index.html?q=post#webgl_postprocessing_dof2

    I’m trying to reverse engineer these from advice in past topics, but can’t seem to get it to work!

    #62158

    Hi,

    Pay attention to the browser console, it might tell you what is missing in your implementation.

    BTW, we might need to write some tutorial on that matter, I’m going to discuss this with the team.

    Soft8Soft Tech Chief
    X | FB | LinkedIn

    #62160
    kdv
    Participant

    (mainly focused on RGBShiftShader)

    That’s all. Just 4 lines of code needed in this case…
    https://v3d.net/i2l

    Puzzles and JS coding. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

    #63166
    Johnson
    Customer

    (mainly focused on RGBShiftShader)

    That’s all. Just 4 lines of code needed in this case…
    https://v3d.net/i2l

    Thank you so much kdv! I really appreciate that– this made my day!!! :yahoo:

    Alexander, that would be amazing– as I have been trying to bring different post-processing effect to my V3D projects, and more documentation would be a lifesaver for beginning/intermediate developers like me!!! Thank you!!!! :-)

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.