circular-studios / dash Goto Github PK

• Merge Texture into material module.
• Merge all shaders together.
• Merge Lights into a single module.

We have some basic camera support, but we need something a lot more robust.

Create a project on LinkedIn and add the group members to it.

So the previous way we did this with 192 was to scan for variables in the shaders, and then query their positions. A potential rework of this system would be to have a meta data file of some sort that includes variable names (making it less of a pain to do arrays) and the positions of variables, so we could set them ourselves. Thoughts or alternative ideas are welcome.

Please comment here once you update your Github profiles.

We should be able to bind inputs to string keys, Unity style.

This will make the root folder much cleaner.

We need to design and implement a shader pipeline for efficiently drawing objects.
Things To Do:

• Set up textures for deferred rendering
• Shut down textures for deferred rendering
• Determine object render framework
• Implement Shader compiling
• Implement object loading

We need to be able to click on things. This means we need to do a raytrace (or something similar) and return the first object on the screen.

Where ever the objects move, the camera always follows it.

• Remove draw from components.
• Evaluate what needs to be a component.
• Implement how GameObject handles specific components

Commits:

• 54c0e0d
• 2e06802

These should probably be in degrees.

Quaternion.fromEulerAngles( 0, 0, 0 ) results in a quaternion representing a 180 degree rotation about the Y axis.

Create a Unity-like Prefab system.

The math structures need to be properly implemented for rendering to work properly.

Tyler and I were discussing the location of our shader code, and while the current system works fine for now the size, complexity and number of shaders will most likely increase as we continue to add features.

We were thinking of a system where shaders can be paired in a file, i.ie. geometryVS and geometryFS and all the shader files could be included in their own package.

Another concern is the ShaderUniform enum which will most likely become massive, but we were unable to think of a good solution right now.

Our previous license is probably still good, but I would have the engine team all agree on something before copying it.

Currently you can only check isKeyDown every frame. There should be a bool parameter specifying a check for one-time or every frame.

Splitting this from Directional/Ambient since those are more likely to occur on time.

Implement a graphics and window adapter for use with Linux platforms.

Create a system to create and manage materials (as collections of different types of textures).

Window resizing/resolution changing should maybe be something we consider eventually

MacBook Pro (Early 2011), Windows 8: black screen
MacBook Air:, Windows 8.1: Texture doesn't display properly

Variables such as fov, near, and far do not belong in adapter and should be in camera.

Assimp is an object file importer that could replace the current model loading system.

Also, it's already been ported to D.

Implement a graphics and window adapter for use with OSX.

Get that readme all fancied-up before GDC. This will also help as we begin interacting with the D community.

Potential Additions:

• Our Vision / Goals
• Important Wiki Links
• Links to our other repos (Speed, Sample Game)
• Engine Logo

Commits:

• 7b8923a: Added link to demo game.

Is reloading a yaml file feasible? It would be great if we could reload and reset all the prefabs without having to close the engine.

The next step beyond this would be diff reloading (only reload what changed), but I'm not about to ask for that.

Implement the encode and decode for normal maps in the geometry and lighting fragment shaders.

Design how the render pipeline will work, and how the shaders will be implemented.

Move binding function to the shader class from material

We need to make it so that the game developer can change the name of the window. This is probably not something we want to put in Config.yml, but more likely a property on the DGame class.

Scaling through Yaml isn't functional. Doesn't work on initial load or on reload.

I imagine syntax like myObject.Position.x = 20. The console could be done in-game via Awesomium if that's what we pick for the UI, or it could be a command-line window seperate from the game.

Prereq: threading

It's causing more issues than it's worth.

I noticed a few remaining mentions of Dvelop here. Pretty minor fix.

There should be some method for the game script to set/control the cameras. Camera class works fine, but the render pipeline doesn't know anything about the camera.

We keep forgetting to actually do this.