Slashdot Mirror

← Back to Stories (view on slashdot.org)

Over 160 Tutorial Videos Created For Unreal Dev Kit

Posted by Soulskill on from the how-it's-done dept.

As a follow-up to Epic Games' release of a free version of the Unreal Engine last month, the company has now posted over 160 video tutorials which demonstrate the various uses of the Unreal Development Kit. Roughly 20 hours of footage were created by technical education company 3D Buzz, with topics ranging from user interface to game physics to cinematics.

8 of 48 comments (clear)

  1. Videos by sopssa · · Score: 5, Informative

    And here are the videos:

    User Interface
    Simple Level
    Lighting
    Geometry Mode
    Kismet
    Materials
    Terrain
    Fractured Static Meshes
    Sounds
    Particles
    Fluid Surfaces
    Physics
    Crowds
    Cinematics
    UI Scenes
    Top-down Game Types

    They seem to be quite nicely done too. So not only giving a free version of Unreal Engine, they're helping the users too. And these are interesting even if you wouldn't use the Unreal Engine.

    1. Re:Videos by nitroyogi · · Score: 5, Informative

      You missed 'Skeletal Mesh Pipeline' videos.
      Here they are -
      Skeletal Meshes: Intro
      Skeletal Meshes: Skeletal Meshes Import/Export
      Skeletal Meshes: Mirror Tables
      Skeletal Meshes: Sockets
      Skeletal Meshes: Physics Assets

      kthxbye

  2. Re:GNU/Linux support? by L4t3r4lu5 · · Score: 3, Informative

    No.

    Minimum Requirements:
    - Windows XP SP2 or Windows Vista
    - 2.0+ GHz processor
    - 2 GB system RAM
    - SM3-compatible video card
    - 3 GB Free hard drive space

    --
    Finally had enough. Come see us over at https://soylentnews.org/
  3. Re:Terrain generator? Aerodynamics? by ZeroExistenZ · · Score: 3, Interesting

    I remember reading a 90s published book "3D game design" which walks through (in 2000 pages) the creation of an 3D FPS shooter.

    The terrain generator described inthere, is just a grid with random height vertices, smoothed with interpolation and stored in a grayscale bitmap to represent the "height variation". The parser of this bitmap hence could also be fed by a simple image in which you drew your landscape's height variation and overlay a texturemap.

    For this you just need to be able to draw vertices and creative use of randomized numbers.

    But for todays high-res gamedesign, I think there are more involving techniques needed...

    --
    I think we can keep recursing like this until someone returns 1
  4. Terrain generator? Use fractal landscapes! by thijsh · · Score: 3, Interesting

    Random generated is soooo 90's... in this century they use fractals (which is just a simple formula with some more random added in it). ;-)
    But seriously read more about fractal landscapes here: http://en.wikipedia.org/wiki/Fractal_landscape

    1. Re:Terrain generator? Use fractal landscapes! by ZeroExistenZ · · Score: 2, Funny

      Oh no, it takes another 4-5 hours to finish work :)

      If you want me to, I can forward my ED-spam to you. "forward (to IndustrialComplex)" is just one button away from "mark as spam".

      --
      I think we can keep recursing like this until someone returns 1
    2. Re:Terrain generator? Use fractal landscapes! by 2short · · Score: 2, Interesting


      Ahh, the random midpoint displacement algorithm. Thanks for pointing out that neat thing they do this century. Mind you, it's genuinely cool stuff, and you shouldn't be less excited about it just because other people were excited about it previously. But that "soooo 90's" is pretty damn funny, since what you're describing is probably the same thing the OP is talking about, and it is actually... soooo 80's.

      At least, I wrote a little program to play with it in 1991 after reading about it in a book published in the late 80s.

  5. Epic by Steauengeglase · · Score: 4, Insightful

    I've got to give Epic credit, they've taken a lot of criticisms about developing for Unreal to heart and went miles beyond what anyone could have expected.