Sign in to follow this  
DallyLama

OpenGL Drawing the inside of a cube

Recommended Posts

Hello All, I'm kinda a beginner in openGL and I'm trying to draw the inside of a room using openGLES, what I've done so far was that... I create a cube [-1,1]x[-1,1]x[-1,1] and since on my platform I don't have support for most of the openGL API i created my own projection Matrix. Using only my projection Matrix (built like every other openGL matrices) assuming the camera is in the origin and glViewport i rendered the cube, but it looks horrible I only see one wall and it is all flattened, it doesn't have that nice 3D feel to it. I did switch the normals so it will look on the inside but I feel like im doing something fundamentally wrong... Any tips, ideas tutorial or links pointing to the right direction will be gladly Appreciated. Thx all.

Share this post


Link to post
Share on other sites
how are you rdrawing the cube? reversing the direction you pass the vertices in (or indices if your doing it that way) will change the faces to point inwards instead of outwards. Otherwise you can change full face to back
glCullFace(GL_BACK); (I think thats it, you could disable culling enritly too).

I would advise againstmessing with the culling though.

Share this post


Link to post
Share on other sites
Quote:
Do you mean you see the walls, just not the corners/edges? If so, did you enable lighting?


Yes that is exactly what I mean. I do my lightning inside the fragment shader, I don't use any of the GLstates or predefined attributes, I pass it all manually!

Quote:
how are you rdrawing the cube? reversing the direction you pass the vertices in (or indices if your doing it that way) will change the faces to point inwards instead of outwards.


As I said before I do my own attributes calculation's that means normal's too,
And no cullMode is enabled at least I hope so. does openGL does defualt culling?

Quote:
If your cube looked flattened then it could be either of the following.

(1) The vertices are defined properly.
(2) The projection matrix is not defined properly.


here is the definition of my projection matrix and the definition of the cube:


//the cube:
#define VAL 1.0
#define M_VAL -VAL

glBindTexture(GL_TEXTURE_2D, texture[0]);
float cube_position[]= {
M_VAL, M_VAL, VAL , VAL , M_VAL, VAL , M_VAL, VAL , VAL ,
VAL , M_VAL, VAL , VAL , VAL , VAL , M_VAL, VAL , VAL ,

M_VAL, VAL , VAL , VAL , VAL , VAL , M_VAL, VAL , M_VAL,
VAL , VAL , VAL , VAL , VAL , M_VAL, M_VAL, VAL , M_VAL,

M_VAL, VAL , M_VAL, VAL , VAL , M_VAL, M_VAL, M_VAL, M_VAL,
VAL , VAL , M_VAL, VAL , M_VAL, M_VAL, M_VAL, M_VAL, M_VAL,

M_VAL, M_VAL, M_VAL, VAL , M_VAL, M_VAL, M_VAL, M_VAL, VAL ,
VAL , M_VAL, M_VAL, VAL , M_VAL, VAL , M_VAL, M_VAL, VAL ,

VAL , M_VAL, VAL , VAL , M_VAL, M_VAL, VAL , VAL , VAL ,
VAL , M_VAL,M_VAL, VAL , VAL , M_VAL, VAL , VAL , VAL ,

M_VAL, M_VAL, M_VAL, M_VAL, M_VAL, VAL , M_VAL, VAL ,M_VAL,
M_VAL, M_VAL, VAL , M_VAL, VAL , VAL , M_VAL, VAL , M_VAL };

float cube_normal[]= {
0, 0, 1.0f, 0, 0, 1.0f, 0, 0, 1.0f,
0, 0, 1.0f, 0, 0, 1.0f, 0, 0, 1.0f,

0, 1.0f, 0, 0, 1.0f, 0, 0, 1.0f, 0,
0, 1.0f, 0, 0, 1.0f, 0, 0, 1.0f, 0,

0, 0, -1.0f, 0, 0, -1.0f, 0, 0, -1.0f,
0, 0, -1.0f, 0, 0, -1.0f, 0, 0, -1.0f,

0, -1.0f, 0, 0, -1.0f, 0, 0, -1.0f, 0,
0, -1.0f, 0, 0, -1.0f, 0, 0, -1.0f, 0,

1.0f, 0, 0, 1.0f, 0, 0, 1.0f, 0, 0,
1.0f, 0, 0, 1.0f, 0, 0, 1.0f, 0, 0,

-1.0f, 0, 0, -1.0f, 0, 0, -1.0f, 0, 0,
-1.0f, 0, 0, -1.0f, 0, 0, -1.0f, 0, 0,
};

float cube_uvs[] = {
M_ONE, M_ONE, ONE , M_ONE, M_ONE, ONE,
ONE , M_ONE, ONE , ONE, M_ONE, ONE,

M_ONE, M_ONE, ONE , M_ONE, M_ONE, ONE,
ONE , M_ONE, ONE , ONE, M_ONE, ONE,

M_ONE, M_ONE, ONE , M_ONE, M_ONE, ONE,
ONE , M_ONE, ONE , ONE, M_ONE, ONE,

M_ONE, M_ONE, ONE , M_ONE, M_ONE, ONE,
ONE , M_ONE, ONE , ONE, M_ONE, ONE,

M_ONE, M_ONE, ONE , M_ONE, M_ONE, ONE,
ONE , M_ONE, ONE , ONE, M_ONE, ONE,

M_ONE, M_ONE, ONE , M_ONE, M_ONE, ONE,
ONE , M_ONE, ONE , ONE, M_ONE, ONE,

};

// the projection matrix

void gl2_projection(float* mat, float n, float r, float t, float f)
{
gl2_identity(mat);
mat[0] = n/r;
mat[5] = n/t;
mat[10] = -(f+n)/(f-n);
mat[11] = -(2*f*n)/(f-n);
mat[14] = -1;
mat[15] = 0;

}

//drawing function

//defining the transformations
gl2_identity(projection_matrix);
gl2_identity(modelview_matrix);
gl2_projection(projection_matrix, 0.1, 2.0, 2.0 , 5.0);
gl2_rotate(modelview_matrix,mAngle,1.0f,1.0f,1.0f);
MulMatrix(projection_matrix,modelview_matrix,mvp_matrix);
glViewport(0,0,480,800);

// passing all the necessary attributes to the sahders...

//drawing

int mFirstIndex = 0;
int mStripCount = 12;

for(int i = 0; i < mStripCount; i++)
{
glDrawArrays(GL_TRIANGLE_STRIP, mFirstIndex, 3);
mFirstIndex += 3;
}



And to all of you great thanks


Share this post


Link to post
Share on other sites
I see you're rotating the camera to see the edges/corners, don't you?

Could you post your shader code?


One thing wrt. your normals:

Your first wall is placed at positive z (VAL) and its normals also point in positive z direction (0,0,1). The opposite wall is located at negative z (M_VAL) and its normals all point to negative z (0,0,-1).

This means your normals are pointing outwards and a normal lighting calculation would just apply ambient light to the vertices if the camera is located inside the cube.


P.S.: per default backface culling is turned on, but since you see the walls, that should not be your problem.

Share this post


Link to post
Share on other sites
Quote:
I see you're rotating the camera to see the edges/corners, don't you?


No this is dead code mAngle is set to 0.

Quote:
Could you post your shader code?


I will post them up later today not near my computer.

Quote:
Your first wall is placed at positive z (VAL) and its normals also point in positive z direction (0,0,1). The opposite wall is located at negative z (M_VAL) and its normals all point to negative z (0,0,-1).


I reverse the normal in the fragment shader... again later today I'll post my shders.

Share this post


Link to post
Share on other sites
shader code attached im trying to make deferred shading so ill just attach the lighting pass fragment shader...


#define MAX_LIGHTS 20


#define COSSPOTCUTOFF 0.988 // cos(pi/12)

uniform vec3 lightDirection[MAX_LIGHTS];
//uniform vec3 spotDirection[MAX_LIGHTS];
uniform vec3 lightColor[MAX_LIGHTS];

uniform int maxLights;

uniform sampler2D Env,normalTex,posTex;

varying vec2 vTexCoord;

const vec4 red = vec4(1.0, 0.0, 0.0 ,1.0);
const vec4 blue = vec4(0.0, 0.0, 1.0 ,1.0);
const vec4 green = vec4(0.0, 1.0, 0.0 ,1.0);

void main(void)
{
vec3 v_eyePosition = vec3(0.0,0.0,-25.0);

// sampling the pre made textures
//vec3 normal = texture2D( normalTex, vTexCoord ).xyz;
vec4 t = texture2D( normalTex, vTexCoord );
t =( t*2.0)-vec4(1.0,1.0,1.0,1.0); // transforming back to the normal range

vec3 normal = t.xyz;

vec4 pos = texture2D( posTex, vTexCoord );
pos = (pos*2.0) - vec4(1.0,1.0,1.0,1.0);
vec4 texColor = texture2D( Env, vTexCoord )*1.5;

vec4 diffuse;
vec4 color = vec4(0.1, 0.1, 0.1, 1.0); //this is the ambient term
vec4 specular;
normal = normalize(normal);
vec3 eyeVector = normalize((pos*10.0).xyz - v_eyePosition);
float p = 0.0;
vec4 dif;
for (int i = 0; i < maxLights; i++)
{
//i =;
vec3 lightDir = (pos*10.0).xyz - (lightDirection[i]*20.0);
float NdotL = -dot(normalize(-lightDirection[i]),normal);
//p = NdotL;
if (NdotL > 0.0)
{
float spotEffect = dot(normalize(-lightDirection[i]), normalize(lightDir));
if (spotEffect > COSSPOTCUTOFF)
{

//attanuation factors
spotEffect = pow(spotEffect, 80.0);
float att = spotEffect / (0.02 * length(lightDir));
p = att;


vec3 ref = reflect(normalize(lightDir), normal);

diffuse = NdotL*vec4(lightColor[i],1.0); //diffuse term

float RdotE = max(dot(-normalize(ref), eyeVector),0.0);
specular = pow(RdotE, 35.0)*vec4(lightColor[i],1.0); //specular term
color += att * (diffuse + specular);
dif = color;
}
}
}
gl_FragColor = texColor*color;
}




just to explain the array lightDirection is actually the positions of the spotlights, and all the spot direction are the direction between the position and the origin

Share this post


Link to post
Share on other sites
I didn't thoroughly read your code, but there are some questions:

1. Since your positions/normals should be in eye-space, why do you set another eye position (should be (0,0,0) in eye-space)?

2. Are your light positions/directions given in eye-space to?

3. I assume you use orthographic projection and your frusum spans 8 units in each direction, why do you multiply your fragment positions with 10 (so their z-value could be -10 or 10)? Your maximum depth of 1 (the value in the texture) would correspond to eye-space z = 4 and not 10.

4. Did you try with a directional light first in order to reduce complexity?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Announcements

  • Forum Statistics

    • Total Topics
      628342
    • Total Posts
      2982176
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now