René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Bug in GLSL code for examples/Topics/Shaders/Nebula ","articleBody":"### Issue description\r\nWhen you run this example, opaque black regions occasionally appear in the visualization. This appears to be caused by the surface3 function returning values larger than 1.0 due to the way it sums various different frequencies of noise. When the value is larger than 1.0 the calculated color can end up negative which results in the opaque black sections.\r\n\r\n### URL(s) of affected page(s)\r\n\r\n\r\n\r\n### Proposed fix\r\n\r\n    float surface3 ( vec3 coord, float frequency ) {\r\n\t\r\n\tfloat n = 0.0;\t\r\n\t\t\r\n\tn += (0.5     + 0.00625) * abs( cnoise4( coord * frequency ) );\r\n\tn += (0.25    + 0.00625) * abs( cnoise4( coord * frequency * 2.0 ) );\r\n\tn += (0.125   + 0.00625) * abs( cnoise4( coord * frequency * 4.0 ) );\r\n\tn += (0.0625  + 0.00625) * abs( cnoise4( coord * frequency * 8.0 ) );\r\n\tn += (0.03125 + 0.00625) * abs( cnoise4( coord * frequency * 16.0 ) );\r\n\t\r\n\treturn n;\r\n    }\r\n\r\nThis suggested new version of surface3 ensures that the return value is never greater than 1 by weighting the noise frequencies more appropriately. I have reduced the main weighting of each frequency by half and added back a small extra bit to ensure the total of all the weights is 1, while maintaining approximately the same intended distribution.\r\n\r\nThe result is a little more nebula heavy than the original so more tweaking might be needed by those with a better eye for graphic design than me.\r\n","author":{"url":"https://github.com/pjfordham","@type":"Person","name":"pjfordham"},"datePublished":"2023-05-02T00:19:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/20/processing-examples/issues/20"}