Tutorial: Hyperspace Effect
BlendMaster writes:
Hey Everyone! In this tutorial we will go over how to create a simple hyperspace scene inside of Blender. The overall scene is very simple, and to achieve the final look of hyperspace, we will be utilizing a really cool node in the compositor. The end result looks perfect for any space animation including a jump through hyperspace.
I hope you guys enjoy this tutorial and learn something new! ;)
The result:
The tutorial:
This is a pretty bad tutorial with a bad result.
The animation has glitches in it (lines blinking and fuzzing) and the quality of the render is below good.
Please dont feature things like this, its not even an interesting technique.
Personally, I find your comment a bit raw.
And even if the result and/or the tutorial is has not at the quality you expect for blendernation, there could have things to grab here and there for some peoples.
Anyway, as soon as this is shared for free and “BlendMaster” obviously spent time to do it, such a comment seems to me unfair.
Maybe you also disagree with some approaches, your constructive feedback could help the author or those who’ll read the comments to learn something new and interesting…
“And even if the result and/or the tutorial is has not at the quality you expect for blendernation, there could have things to grab here and there for some peoples.”
Someone could stream doing literally anything in Blender and there could be something in there “to grab here and there for some people”. Thats not an argument.
Fact is, this is a bad tutorial for the thing it is trying to create. It introduces people to wrong approaches and bad practice.
I’m even convinced the creator doesn’t know WHY he has these glitches (even though he tried to convince me he did the glitches on purpose to make it “more realistic” in the YT comments)
I do however.
The glitches occur as objects resolve in the render and create singular pixels that are then uniformly smudged by the directional blur node, appearing as lines out of nowhere.
Since he used nodes to add contrast to the pixel output, the pixels appear and disappear near the resolution boundary of the camera, which then creates glitchy disappearing lines that flicker until they get close enough to the camera to resolve into enough pixels to stay indefinitely.
The correct (and easier) way to generate this effect is to use cycles Motion Blur in the render settings, crank it way up to 2 and animate your camera, without all this compositor directional blur and gaussian nonsense, then flavor to your liking with glare and distort/dispersion node.
Result in under 2 minutes of setup: http://sendvid.com/sq2dp13e
This tutorial is shitty, it uses the wrong tools and introduces several techniques that are flat out wrong and a bad practice.
Like trying to get rid of aliasing artifacts with gaussian blur.
Dear god, what the actual fuck.
Sorry this is harsh but that’s the reality of it.
I understand that there are multiple ways to go around creating a hyperspace effect in Blender. I agree that you provided one way that is simple and works just as well.
However, your idea of why the glitches appear in my result are incorrect. The glitches actually appear because of the low amount of samples that I used to render out the animation. I used one sample. As a result, there were a lot of glitches since noise interfered with how the directional blur node reacted with the resulting image. An easy fix for this problem is to simply render the animation with a larger amount of samples, perhaps 100. The glitches had nothing to do with the fact that I added contrast in the compositor.
I also tried out your method, and if you were to render out the animation your way using one sample, it would look even worse than the result of my tutorial. I want you to understand that it is not my technique that created the lower quality animation, but the settings with which I rendered them. So don’t go around telling people that they don’t know what they are doing and that their technique is bad if you yourself do not even know what is wrong.
“However, your idea of why the glitches appear in my result are incorrect. The glitches actually appear because of the low amount of samples that I used to render out the animation. I used one sample. As a result, there were a lot of glitches since noise interfered with how the directional blur node reacted with the resulting image. An easy fix for this problem is to simply render the animation with a larger amount of samples, perhaps 100. The glitches had nothing to do with the fact that I added contrast in the compositor.”
No it fucking doesnt:
http://sendvid.com/q2j0pn2o
The amount of samples isnt going to change the resolution boundary of the camera or improve the post effect of directional blur.
“So don’t go around telling people that they don’t know what they are doing and that their technique is bad if you yourself do not even know what is wrong.”
Pot. Kettle. Black.
I’m just trying to help.
Here is the result when you render it at 100 samples following my method.
http://sendvid.com/jcn7jbr3
I only add a slight contrast after the directional blur node. If you add contrast before the directional blur, I agree that it will contain glitches. But if you follow the tutorial and render it out at 100 samples, it will appear like the result that I shared above. Below is the result following your method, but with 1 sample.
http://sendvid.com/kkpm2mr6
This proves that the samples do in fact make a difference.