LandonJerre

Members
  • Content count

    27
  • Joined

  • Last visited

Community Reputation

1002 Excellent

About LandonJerre

  • Rank
    Member

Personal Information

  • Interests
    Programming

Social

  • Github
    LandonJerre
  1. Tone Mapping

    RGBA16_FLOAT format for HDR should be more than enough. You should probably be running your post processing on non-multisampled textures. You should resolve or even downsample your g-buffers before post processing for faster access in the shaders. The output render targets should definetly be non multisampled for post processing. Small addition: if you use physically based sky/sun stuff, you could easily end up with values in your scene, that are bigger than what a half can store. In that case you either need to do some preexposition at the end of the lighting/sky passes (the frostbite pbr course notes mention how they do this), or use 32bit RTs. (I do the latter at the moment, preexposing would be the preferable way to solve this, but I haven't yet had the patience to rewire my frame graph to support it.)
  2. Exponential VSM problem

    It is an expected behaviour, with VSM (and any other related techniques) you have to render both the occluders and the receivers into the shadow map. If you think about it, when you blur the VSM without the receivers in it (or even if you just sample that map with proper texture filtering), you blur between the occluder depths, and the maximum z value, meaning that the blurred values will strongly tend towards the max z. Tending towards max z also means that the blurred values will be "behind" the receiver pretty quickly, and that messes up the whole thing. (This explanation is exactly mathematically precise, but hopefully it's enough to illustrate the problem.)
  3. Diffuse lighting for water shader

    I could be wrong, but from the images you linked it looks like you're using a single color for the entire sky. Before hacking the water lighting calculations, I would try to replace it with something more "interesting", like a proper texture of a clear sky. It should help at least somewhat, because if you use a homogenous sky, the direction of the reflection vector won't really matter, you will fetch the same color regardless. With a proper sky texture that won't be the case, because different parts of the sky are colored different kinds of blue.
  4. AFAIK the PS4 Pro has some special hardware extensions to make checkerboarding easier, but the R6 Siege version doesn't depend on any special capabilities. http://www.gdcvault.com/play/1022990/Rendering-Rainbow-Six-Siege The slides say that the resolve pass adds about 1.4ms, but the whole stuff still saves around 8-10ms, which is kind of awesome. (Ever since I first saw the slides describing how they do this, I'm toying with the idea of implementing it in my hobby renderer, but the resolve shaders flow graph, and the fact that they admit their implementation was done by trial and error, scares the hell out of me.)
  5. setInterval

    The truth is somewhere inbetween the two. :) setInterval afaik doesn't care about how long the passed callback runs, and it won't fire exactly on given delays either. With the given example, the browser will queue up the passed callback for execution every 150ms, but it will only execute when the execution "thread" doesn't have anything else important to run. (This is why the age old setTimeout with zero delay hack works, a 0 as a delay in this case doesn't mean it will execute immediately, it just means that it will run as soon as possible when nothing else is running.) Sidenote: it is perfectly possible to do the second option you described with recursive setTimeouts, e.g: (function func(){     setTimeout(function(){         //code         func();     }, delay); })();
  6. Me too use RenderDoc (https://renderdoc.org/) for graphics debugging, it does everything you described and much more. Debugging really large shaders can bit a bit of a pain, but other than that I haven't had any significant problems with it.
  7. Try changing the line "i /= base" to something like "i = math.floor(i / base)". ( https://en.wikipedia.org/wiki/Halton_sequence if you look at the pseudocode, it has the floor operation too. )
  8. Soft Particles Vanishing in the Distance

    If your depth buffer isn't linear, then the depth distance between things at a unit distance from eachother in the world, will become shorter as you get further away from the camera. ( https://developer.nvidia.com/content/depth-precision-visualized the article isn't particularily about this, but the figures illustrate well what happens here. ) So effectively your particles get "closer" to other stuff, that would trigger the softening the furter away from the camera they are. The fastest fix in this case would be linearizing the two depths before you compare them.
  9. Resolution scale, good thing ?

    They create the render target on the fly if not one is available for the asked size using a render target pool ? Is it ok to downscale/upscale using the hardware filtering ? With dynamic scaling you have a minimum and a maximum resolution multiplier, so it's easier to just create a rendertarget that fits the size of the maximum scale, and then render with the viewport set to the actual scale used at the moment. I used this (https://software.intel.com/en-us/articles/dynamic-resolution-rendering-article) article as a reference to implement this kind of stuff in my framework, it discusses filtering options too.
  10. Resolution scale, good thing ?

    Well, from an end user perspective it's either never used, or it's a lifesaver. For example without a resolution scaling option, I would've had a hard time playing Mass Effect: Andromeda, to reach a framerate between 30-60FPS I needed to put everything to low and set the scale to x0.8. (My i7 920 + GTX670 rig isn't the beast it used to be :) ) If you think about it, back in the old days we set lower resolutions to get some extra needed perf, resolution scaling achieves about the same effect, but provides more fine control over the rendering resolution, and does this while still outputing a backbuffer in the native resolution of the screen. (Not to mention that no matter what the set scale value is, you can still render your ui at the native resolution, so it doesn't become a blurry unreadable mess.)
  11. Is there a inline assembler overhead?

    MSVC only lets you to use inline asm for x86, it isn't supported for ARM or x64 targets at all. (https://msdn.microsoft.com/en-us/library/4ks26t93.aspx) So even if you find a case, where you absolutely need to use inline asm, MSVC probably won't really cooperate with you.
  12. Website development

    This. "The notion of best practices in frontend world has a half life of about 3 months." said Steven Sanderson (he created knockout.js years ago) once in a presentation (https://youtu.be/I1USsIW8aWE?t=43m34s), and he was a, generous about the timeframe b, only talking about frontend. Going full stack is the way where madness lies. (I'm a "full stack" .net dev by trade, and often there are times when the regular 8 hour workday just isn't enough to keep on top of all the new and shiny frontend and backend stuff. )
  13. What kind of game developer are you?

    Well, if only strictly console stuff counts, then Destiny on the PS4. Being from Eastern Europe, someone owning a console was astonisingly rare in my childhood, because it was harder to pirate stuff for them, and back in the 90's we neither had a grasp on the concept of copyright, nor the money to actually pay for stuff. If PC counts too, then the original Half-Life wins.
  14. Coding-Style Poll

    If I find the policy to be sane, then I don't have a problem with it. For example: I prefer Allman style, and use it where it is possible, but at work we write Java and Javascript code with the Java variant of K&R style, and I don't really have a problem with it. On the other hand if the policy would be to use Whitesmiths style, or something I find equally unreadable, I probably would have found another job already.    Variable name prefixes basicly make the code unreadable for me. I usually don't read code properly like text, I just run through it, so for variable names usually I only look at the first 3-4 characters, and the length. (I heavily lean on autocompletion during actual coding for this exact reason, I usually don't know the full names of variables, just how they start.) Because of this, if the first characters are consistently the same throughout multiple variable names, I'm forced to read the code like proper text, which is irritating to me, and much slower too. Class name prefixes while irritating, I can live with them, but they make harder to find stuff for me (again I usually remember the beginning of the class names, and if all classes start with a C, that doesn't make my life easier). I'm fine with anything else that doesn't involve prefixes.
  15. You're probably missing the d3d debug layer, take a look at this topic on how to install it: http://www.gamedev.net/topic/678115-device-creation-fails-win-10-c/