• Content count

  • Joined

  • Last visited

Community Reputation

3266 Excellent

About Capoeirista

  • Rank

Personal Information

  • Interests
  1. Nobody Wants A Cybergod?

    I doubt that anyone on this forum doesn't understand the significance of the idea but that's all it is at the moment, an idea. All we have is your word that Rube is an actual 'thing'. People tend not to care about other peoples ideas; everyone has ideas. If you want help building it though this is the place; is an exceptional helpful community. Demonstrate what it is Rube can do, show us why we should care.
  2. OpenGL [Solved] OpenGl Shader Output

    Oh damn, thanks for that! I assumed that OpenGL would map the 'out' variable from the vertex shader to the 'in' variable of the fragment shader - assuming the types matched; had no idea the actual variable names had to be the same. Thank you, this was driving me a bit insane!
  3. OpenGL [Solved] OpenGl Shader Output

    I had a quick look at the fragment shader using NSight, and while the vertex shader looks like it has valid input parameters, I couldn't see anything relating to color in the fragment shader. I've attached a couple of screen-caps from NSight.
  4. Hey folks, Seeing some odd behaviour with a very simple OpenGL shader I'm trying to get working. Here's the vertex shader: #version 400 //////////////////// // Input Variables //////////////////// in vec3 inputPosition; in vec3 inputColor; //////////////////// // Output Variables //////////////////// out vec3 outputColor; //////////////////// // Uniform Variables //////////////////// uniform mat4 worldMatrix; uniform mat4 viewMatrix; uniform mat4 projectionMatrix; //////////////////// // Vertex Shader //////////////////// void main( void ) { // calculate the position of the vertex using world/view/projection matrices gl_Position = worldMatrix * vec4( inputPosition, 1.0f ); gl_Position = viewMatrix * gl_Position; gl_Position = projectionMatrix * gl_Position; // store the input colour for the fragment shader outputColor = vec3( 1.0f, 1.0f, 1.0f );//inputColor; } And this is the fragment shader: #version 400 //////////////////// // Input Variables //////////////////// in vec3 inputColor; //////////////////// // Output Variables //////////////////// out vec4 outputColor; //////////////////// // Fragment Shader //////////////////// void main( void ) { outputColor = vec4( inputColor, 1.0f );//vec4( 1.0f, 1.0f, 1.0f, 1.0f); } If I try and use the 'inputColor' in the fragment shader everything is just rendered black... however if I explicitly set the colour (in the commented out code) everything renders correctly... so there's a breakdown in communication between my vertex and fragment shaders. Is there anything obvious I'm missing in the shader code? I'm not seeing any compilation warnings from the C++ code side of things, and all of the world/view/projection matrices are being passed in correctly. Thanks!
  5. Audio Integration into games?

    Audiokinetic have some great, free Wwise tutorials available online (you only have to pay if you want the certificate), you can check them out here. It's definitely worth running through them - as a sound designer the more you know about Wwise the better. You won't have to touch any code, but you'll need to understand how audio works in games.
  6. Interior Volume Detection

    Haven't figured out exactly how recast works yet, but it can output voxels for walkable surfaces it detects. The code is reasonably well documented too. I was half thinking I could grab it's interior edge detection algorithm to walk around the interiors of the geometry I'm looking at... then just extend the resulting mesh to the desired height. It's an impressive piece of tech; very quick generation and handles things like stairs without any trouble.
  7. Interior Volume Detection

    Hey JoeJ, Thanks for the awesome response The purpose of this is to automate the placement of sound occlusion volumes in the world, so a completely robust solution isn't necessary. I'm just trying to cut down the manual, repetitive work that sound designers have to do in our level editor. Performance isn't really an issue since this is all going to be done in an offline process, and while the voxel solution is working well so far it is by no means complete... just trying to cover all of my bases here I haven't tried Simplygon, but I have been looking at Recast - an open source navmesh generation system. It seems to do a really good job mapping out mesh interiors.
  8. Interior Volume Detection

    Sounds like you want something like a low poly occlusion mesh? Simplygon can generate this, but i have not tried yet: Your algorithm may work depending on your needs and inputs. Other ideas: * Voxelization + flood filling * BSP tree for exact solution Hey JoeJ I've been having a play with a couple of the ideas you suggested, and while the voxel flood fill seems to work quite well (although expensive) I'm not sure how to go about evaluating space with a BSP tree. I've been able to build a BSP tree of course, but I don't see how to extract the spatial information from it since it only really storing the relationship between individual polygons... if that makes sense I've read that you can represent the empty space using something called a solid-leaf BSP tree, but can't find any descriptions of the algorithm, just that it exists. Cheers!
  9. Interior Volume Detection

    Hey JoelJ Yeah a low-poly occlusion mesh is exactly what I'm after; a bounding volume that can trigger audio events when a player enters an indoor area. I'll have a look at simplygon, see if I can get something up and running. Voxelization is an awesome idea, and should be relatively easy to implement, thanks for that. I'll have to look in to BSP trees as well. Thanks!
  10. Hey folks, So I've got a reasonably interesting problem to solve and just wanted to reach out and see if I'm on the right track for a solution. Given a piece of geometry - typically the exterior of a building - I need to be able to generate a shape that represents it's interior volume. My geometric algorithm knowledge is a little lacking, but an approach I'm considering is: stitch a plane on to the 'floor' of the building geometry (to catch ray casts) work out where the center of the building is perform a bunch of raycasts from the center point to hit all of the interior bounds  stitch the resulting racast intersection vertices together (removing unnecessary ones) in to the desired volume Is this a reasonable approach to the problem? I should probably note that I'm likely going to have to handle both convex and concave pieces of geometry. Any suggestions would be greatly appreciated, thanks!
  11. Ah you probably still need the following include directory: c:\Program Files (x86)\Windows Kits\8.1\Include\um\ Since that's where Windows.h, you really just want to make sure that you're including and linking against the June 2010 SDK and not the Windows Kit SDK for DirectX.
  12. Yeah spot on. I had similar issues setting up a DX project recently. By default your VS project properties probably have the following include and lib directories: c:\Program Files (x86)\Windows Kits\[some version]\Include\ c:\Program Files (x86)\Windows Kits\[some version]\lib\winv6.3\x64 Or something similar, I think there are around three Include directories and a couple of lib directories. This is where the current version of DirectX is kept and your project is probably linking against these instead of the June 2010 SDK. To prevent this from happening, under your project's Include & Lib directories you can uncheck the 'Inherit from parent or project defaults' checkbox. Note that you'll probably still need to explicitly include $(VC_IncludePath), and have $(VC_LibraryPath_x64) for your libs... it's the Windows SDK stuff you want to avoid. Hope that helps!
  13. Can anyone recommend some good books on graphics with c++?

    The RasterTek tutorials are fantastic for getting a handle on rendering. They haven't been updated for a year or so, but they'll give you a solid foundation to build on. Once you've built that foundation then the ShaderX & GPU Gems series of books can really help you understand some more advanced rendering techniques.
  14. [FIXED] XAudio2 in Managed C++

    Aaaaand it's because my C++ DLL was linking to the 'Windows Kits' v8.1 and I'm running Windows 7, so don't have access to XAUDIO2_8.DLL. Re-linking my project to the June 2010 DirectSDK & dsound.lib fixed things up.
  15. [FIXED] XAudio2 in Managed C++

    Just used 'Dependency Walker' to inspect the managed DLL I'm building... and it looks like my system is somehow missing XAUDIO2_8.DLL. No idea why I'd be missing the DLL, but at least it's somewhere to start looking :)