jsvcycling

Members
  • Content count

    66
  • Joined

  • Last visited

Community Reputation

1222 Excellent

About jsvcycling

  • Rank
    Crossbones+

Personal Information

  1. Nvidia GI Hardware Support

       Actually, they are using Voxel Global Illumination (VXGI) which seems to be very similar to Sparse Voxel Octree Global Illumination (SVOGI) which was first published by Cyril Crassin of NVIDIA in 2011.   From the NVIDIA page on the technology behind VXGI:   VXGI is not a Direct3D 12 specific feature, in fact, SVOGI it was first implemented in OpenGL 4.x and Direct3D 11. Though the technology has (mostly) been available for years, NVIDIA's Maxwell graphics architecture is the first of its kind to have "built-in" support for the technology.
  2. I'm actually working with UE4 on my current project and I've had a great experience with it so far. With that said, I don't think it'll fit you well with you based on your OP.   UE4 is built more as an all-inclusive framework that you game is built on top of rather than a library that is built into your game. So for you it'll seem just like Unity where they require you to use their style of framework; this is the exact same approach UE4 takes. Also, although UE4 has the source available to subscribers, it is by no means minimalistic as all the core components of the engine are rather tightly knit together. Lastly, if you found Unity's GUI system painful, then you will find UE4's Slate system even more painful. The only way to get a "good" UI system into UE4 is essentially what would need to be done with Unity which is purchase a 3rd-party GUI framework (Scaleform and Coherent UI are the two big ones for UE4 thus far).   I'm not saying UE4 is a bad engine (heck I use it myself), but I'm just saying that it's not going to fit your needs/wants.
  3.   In order to contribute to UT, you'll need to stay on with a subscription or you will lose access to the UT GitHub repository.
  4. Switching between languages/API

    I regularly switch between several languages and APIs. For the languages I use the most (C, C++, C#, Java, JavaScript, PHP, Python, and Haskell) I have a quick reference sheet that has some of the common techniques and styles that are specific or noteworthy to that language. For APIs, I also have references for some of my more commonly used methods or classes in some of my regularly used APIs. I also have at least 1 book for each language or API (if there is a book for it) nearby so I can pull it out and use it if my quick reference sheet doesn't provide enough detail.   I also like to comment my code regularly, especially when using 3rd-party libraries.   Plus there's always the internet and I have a bookmarks folder for all the reference pages for just about every API I use regularly.
  5. What programming skills for Unreal 4

      The shaders seem to be written in HLSL using the internal Material Editor. The HLSL is compressed so you cannot access it from the file system (you must use the Show HLSL option in the Material Editor). The HLSL is converted to GLSL when packaging for the OpenGL rendering target (or when running on OS X). This is the same way it was done in UE3/UDK.
  6. Sadly, I'm discontinuing my Direct3D 11 series until further notice. Between work and school, I just can't seem to find the time to work on it. :(