It finally behaves!

I have change all the sea colors to 0.9, otherwise, the sky looks a little bit greeny.

It also works if I replace the following line of code:

vec4(0.,getSeaColor(p,n,light,dir,dist)),

in vec4 color = mix( vec4(SkyBg(dir),0.), vec4(0.,getSeaColor(p,n,light,dir,dist)), pow(smoothstep(0.0,-0.05,dir.y),0.3) );

with

needs to be vec4(getSeaColor(p,n,light,dir,dist),0.).

It's ok. All the demos work fine for me. The problem appears after I apply effect in the C2.

Wow!!! You are a wizard! It works.

The only problem is with the blue gradient that appears and bounces on the screen.

I have already seen the original shader, it displays normally, maybe even perfectly, it's a very beautiful shader. So it's a question of what causes the trouble. I'm not familiar with WebGL, maybe the problem happens after the effect displays incorrectly in the viewport? I have noticed that the reflection is ultra- green instead of white.

It displays normally.

Well, it is most likely part of the effect. Seas are generally blue to green, so a seascape effect would probably do that.

It is not, I have tried all the params and get the same result.

3 years ago Gigatron published a very interesting SeaScape effect. It didn't work on my PC properly - the water had a unnatural greenish-blue color. I thought the reason was an old Nvidea graphics card.

Later I tried to launch the effect with the Radeon rx 560 videocard, but got the same problem:

I'd like to know why the effect displays incorrectly, is it still a videocard problem or something else?

Gigatron, zenox98 The disappearing issue was a mistaken of mine, i think, sorry....but that color problem remains, even with this parameters.....I can resolve this adding a blend luminosity fx and changing BG color, but is not an appropriate solution...The Demo you posted with the slider bars is perfect... but i haven't found the capx inside the rar file... (although i think it doesn't resolve )

I have the same problem with color

Any ideas?

Lucky Orange Knowledge Base Toggle Navigation

Working with Canvas Elements

Our dynamic recordings use browser Mutation Events to figure out when html content changes. This allows us to record highly dynamic pages with high accuracy. However, canvas elements do not support Mutation Events.

We do have a workaround.

Notifying Lucky Orange When Canvas Has Updated

If you want to capture changes inside of a canvas element, you'll need to alert Lucky Orange that the canvas element has indeed changed. You do this by calling the LO.update_canvas_element() method and passing in the element to it. The function accepts an actual canvas element OR a query selector. So, if you had a canvas element on your page with an id of my_canvas you could call it like this:

LO.update_canvas("#my_canvas");

Alternatively, if you had many canvas elements that all just updated you could also do this:

LO.update_canvas("canvas");

Calling the LO.update_canvas() method will get the image data from the canvas and send that to our servers. If you have a lot of canvas elements or very large canvas elements and are frequently calling this method, it can use a lot of bandwidth.

Please ensure you test this out in a staging environment to see the performance impact before pushing to production.

Still need help? Contact Us Last updated on November 18, 2016

Search

Toggle Search

CATEGORIES

Quick Tips

Dashboard

Live Visitors

Recordings

Conversion Funnels

Chat

Heatmaps

Polls

Form Analytics

Integrations

White Labeling

© Lucky Orange LLC 2019. Powered by Help Scout

Offline. Please leave a message