Lil_Lloyd

Members
  • Content count

    93
  • Joined

  • Last visited

Community Reputation

287 Neutral

About Lil_Lloyd

  • Rank
    Member
  1. Eek! I have another issue now, and it shows my ignorance with pointers to pointers. I search through a linked list like so: //use two pointers to gague where the new ptr should go MallocStruct** ptr1 = NULL; MallocStruct** ptr2 = &freeListHeader; //case3 other wise needs to be inserted into a list somewhere... while(newFree > *ptr2){ ptr1 = ptr2; ptr2 = &((*ptr2)->next); //if next is NULL we need to go to case 4 - inserting at the end if(*ptr2 == NULL) break; }    Then, if I need to insert my new block, I insert it like so: // end of the list if(ptr2 == NULL){ (*ptr1)->next = newFree; newFree->prev = (*ptr1); }else if(ptr1 == NULL){ //beginning of the list (*ptr2)->prev = newFree; newFree->next = (*ptr2); (*ptr2) = newFree; }else{ //middle of the list (*ptr1)->next = newFree; newFree->next = (*ptr2); (*ptr2)->prev = newFree; newFree->prev = (*ptr1); }  The problem is the middle of the list insertion. I'm under the false assumption that (*ptr1)->next = newFree; merely changes the address that (*ptr1)->next points to, however it changes the value of *ptr2 too! How am I supposed to insert a node into a list like this?
  2. Making a sliding puzzle

    What you need to do is have many quads (tiles or squares in the puzzle) and have the main image as a texture. Then for the coordinates of the quads you also need texture coordinates between 0.0 and 1.0. As an example if I had four squares the texture coordinates of the top left square would be (0.0,0.0)---------(0.25,0.0) | | | | | | (0.0,0.25)--------(0.25,0.25) As the square moves around its screen coordinates will change but its texture coordinates will remain constant. I also made a sliding puzzle some time ago, you can see it under my projects here: http://www.lloydcrawley.com/projects/ at the bottom of the screen There is a github repo link there too if you want to look at the source code. Good luck!
  3. ...my line of code in the free function isn't accessing the value I expect! I have the free blocks of memory kept in a doubly linked list and used blocks also carry size information but aren't kept in the linked list.  const int MAX_BYTES = 16 * 1024 * 1024; static MallocStruct* freeListHeader; static unsigned char DataBuffer[MAX_BYTES]; struct MallocStruct{ MallocStruct* next; MallocStruct* prev; unsigned char* buffer; size_t size; }; void  InitMalloc(){     freeListHeader = (MallocStruct*)DataBuffer;     freeListHeader->next   = NULL;     freeListHeader->prev   = NULL;     freeListHeader->size   = MAX_BYTES - sizeof(MallocStruct);     freeListHeader->buffer = (unsigned char*)(freeListHeader + sizeof(MallocStruct)); }   void* MyMalloc(int size){ MallocStruct** ptr = &freeListHeader; //round up size if(size % 4 != 0){ size = (float)size/4 + 1; size *= 4; } while(size + sizeof(MallocStruct) > (*ptr)->size){ ptr = &(*ptr)->next; if(*ptr == NULL) return NULL; } int newSize = (*ptr)->size - (size + sizeof(MallocStruct)); MallocStruct* next = (*ptr)->next; MallocStruct* prev = (*ptr)->prev; //now change the pointer in the list, and get a pointer to this current location (*ptr)->next = NULL; (*ptr)->prev = NULL; (*ptr)->size = size; (*ptr)->buffer = (unsigned char*)((*ptr) + sizeof(MallocStruct)); unsigned char* data = (*ptr)->buffer; //update the freelist pointer unsigned char* ptr3 = (*ptr)->buffer + (*ptr)->size; *ptr = (MallocStruct*)ptr3; (*ptr)->buffer = (unsigned char*)((*ptr) + sizeof(MallocStruct)); (*ptr)->size = newSize; (*ptr)->next = next; (*ptr)->prev = prev; if((*ptr)->next != NULL) (*ptr)->next->prev = *ptr; if((*ptr)->prev != NULL) (*ptr)->prev->next = *ptr; return data; } void MyFree(void* data){ //create a free node, uncoalesced MallocStruct* newFree = (MallocStruct*)((unsigned char*)data - sizeof(MallocStruct)); int size = newFree->size + sizeof(MallocStruct); //now insert it into the linked list MallocStruct** ptr = &freeListHeader; //case 1 - no prev for freeListHeader and address below if((*ptr)->prev == NULL && newFree < *ptr){ (*ptr)->prev = newFree; newFree->next = *ptr; newFree->size = size; *ptr = newFree; return; } //case 2 - no next for the freeListHeader and address higher if((*ptr)->next == NULL && newFree > *ptr){ (*ptr)->next = newFree; newFree->prev = *ptr; newFree->size = size; return; } //case3 other wise needs to be inserted into a list somewhere... while(newFree > (*ptr)->next){ //if next is NULL we need to go to case 4 - inserting at the end if((*ptr)->next == NULL) break; ptr = &((*ptr)->next); } //case 4 - end of the list if((*ptr)->next == NULL){ (*ptr)->next = newFree; newFree->prev = (*ptr); newFree->size = size; return; } //back to case 3 - list insertion newFree->next = (*ptr)->next; (*ptr)->next->prev = newFree; (*ptr)->next = newFree; newFree->prev = *ptr; newFree->size = size; } More specifically the lines   MallocStruct* newFree = (MallocStruct*)((unsigned char*)data - sizeof(MallocStruct)); int size = newFree->size + sizeof(MallocStruct);   aren't extracting the size value I expect, newFree->size is being read as '0' so the size is being recorded as 16, the size of a MallocStruct only. I don't understand why at all!   Someone please explain my hopefully silly and trivial mistake.
  4.   You know I said this didn't work? Well, before I started normalising the planes properly it didn't. I tried it again last night and it worked PERFECTLY. However, it was only after agonising hours of experimentation that I decided to try this again. Including making a debug view from above with the bounding rectangles shown on screen. Taught me a few things though! Thanks. :)
  5. Well I can't remember clearly but last summer I tried using Xinput with GLFW and thought it was a pain, and found GLFW by itself easier to manage as long as I didn't want to use the shoulder triggers
  6.   When I wrote the article (last summer) I was unaware that the left and right triggers thing was related to the drivers used by the o/s whilst apparently xInput uses some different drivers to most to read the input from the pad.    However you can install a driver from here that helps:  http://www.jonnys-place.com/index.php?topic=10495.0   The negative being every user of your game will need the driver. Unless I become a driver programmer and use such arcane wizardry instead of GLFW.
  7. RENDERING A FRUSTUM   So I found some code on rendering a frustum in old school style fixed pipeline GL   void Frustum::DrawFrustum(){ mat4x4 temp = m_projMatrix * m_modView; mat4x4 inv = temp._inverse(); vec4 fr[8]= { // near vec4(-1, -1, -1, 1), vec4( 1, -1, -1, 1), vec4( 1, 1, -1, 1), vec4(-1, 1, -1, 1), // far vec4(-1, -1, 1, 1), vec4( 1, -1, 1, 1), vec4( 1, 1, 1, 1), vec4(-1, 1, 1, 1) }; // Transform all vertices: // multiply vertex array (fr) by matrix. result is transformed vertex array (tfr) for(int i = 0; i < 8; i++) fr[i] = inv * fr[i]; for (int i=0; i<8; i++) { fr[i].x /= fr[i].w; fr[i].y /= fr[i].w; fr[i].z /= fr[i].w; fr[i].w = 1.0f; } glColor3f(1.0f,0.0f,0.0f); glBegin(GL_LINES); glVertex4fv(&(fr[0][0])); glVertex4fv(&(fr[1][0])); glVertex4fv(&(fr[1][0])); glVertex4fv(&(fr[2][0])); glVertex4fv(&(fr[2][0])); glVertex4fv(&(fr[3][0])); glVertex4fv(&(fr[3][0])); glVertex4fv(&(fr[0][0])); glVertex4fv(&(fr[4][0])); glVertex4fv(&(fr[5][0])); glVertex4fv(&(fr[5][0])); glVertex4fv(&(fr[6][0])); glVertex4fv(&(fr[6][0])); glVertex4fv(&(fr[7][0])); glVertex4fv(&(fr[7][0])); glVertex4fv(&(fr[4][0])); glVertex4fv(&(fr[0][0])); glVertex4fv(&(fr[4][0])); glVertex4fv(&(fr[1][0])); glVertex4fv(&(fr[5][0])); glVertex4fv(&(fr[2][0])); glVertex4fv(&(fr[6][0])); glVertex4fv(&(fr[3][0])); glVertex4fv(&(fr[7][0])); glEnd(); }   It seems solid to me, and I have a new 'debug' mode where I detach the camera from the frustum and can control it from above in an orthographic view. However, I'm getting behaviour that is odd. There is no frustum being rendered but only odd lines of varying length depending on camera rotation and sometimes the line doesn't even render unless the camera is in a certain location. Bizarre.    Here's a video link/demo   http://www.youtube.com/watch?v=_Jw1luubvz0&feature=youtu.be
  8.   Well, vectors/points are things described by an x,y and z value so sometimes they can be easily confused at times unless you keep in mind except that vectors describe direction and magnitude and points, well, describe points in space! In 4d points and vectors the difference is the w component, points have a value of one and vectors have a value of zero, when you subtract a point from a point to get a vector the w component goes to zero as required.   As for testing points against planes as opposed to testing 'vectors' is that you do in fact test points such as corners of a cube etc. With that said, yes normalizing a point is indeed odd. 
  9. ALSO - this may be a noobish question, but when I test a point against a frustum plane, do I have to normalise the point? Or leave it as it is? Additionally I have been using points defined in WORLD SPACE. This is correct yes?
  10. OK I just noticed something big, but fixing still hasn't solved the problem   void Frustum::NormalizePlane(int index){ float normFactor = m_planes[index][0] * m_planes[index][0] + m_planes[index][1] * m_planes[index][1] + m_planes[index][2] * m_planes[index][2]; m_planes[index] /= normFactor; }     Should have been   void Frustum::NormalizePlane(int index){ float normFactor = m_planes[index][0] * m_planes[index][0] + m_planes[index][1] * m_planes[index][1] + m_planes[index][2] * m_planes[index][2]; normFactor = glm::sqrt(normFactor); m_planes[index] /= normFactor; }   I was forgetting to squareroot the length! However I'm still getting weird errors... :(
  11. Nope that didn't work, but thanks anyway!
  12. Thanks, I'll try that. This project is causing me a lot of trouble over simple things I understood the theory behind, but actually implementing it is so deceptively frustrating.
  13. I have a quadtree terrain, but nearby quads are being culled. Like so:   http://www.youtube.com/watch?v=b8ztYDkO_28&feature=youtu.be   I was thinking maybe its my frustum extraction code? This is in OpenGL by the way in case matrix layout has any bearing on the problem and I am using the glm mat4x4 and vec4 types to represent my projection matrices and frustum planes    void Frustum::Extract(const vec3& eye,const mat4x4& camMatrix) { m_pos = eye; m_modView = camMatrix; m_projMatrix = GraphicsApp::GetInstance()->GetProjection(); mat4x4 MVPMatrix = m_projMatrix * m_modView; for(int plane = 0; plane < 3; plane ++){ int index = plane * 2; m_planes[index] = MVPMatrix[3] - MVPMatrix[plane]; NormalizePlane(index); } for(int plane = 0; plane < 3; plane ++){ int index = plane * 2 + 1; m_planes[index] = MVPMatrix[3] + MVPMatrix[plane]; NormalizePlane(index); } } void Frustum::NormalizePlane(int index){ float normFactor = m_planes[index][0] * m_planes[index][0] + m_planes[index][1] * m_planes[index][1] + m_planes[index][2] * m_planes[index][2]; m_planes[index] /= normFactor; }    
  14. INSANE quadtree bugs/artefacts

    I fixed the big issues using a different approach found on the rastertek site, but thankyou for replying. However, now I have bizarre frustum culling issues where nearby quads are being culled. I'll post a separate thread for that.