Results 1 to 10 of 42

Thread: pascal and learning 3d

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    turned out that I was dereferencing a pointer in a wrong way
    with static array it was just:
    glBufferData(GL_ARRAY_BUFFER,x,buffer,GL_STATIC_DR AW);
    and with dynamic should be:
    glBufferData(GL_ARRAY_BUFFER,x,@buffer^[0],GL_STATIC_DRAW);

    where 'buffer' is a pointer for that array type.

    ps: it liiveees!!
    Last edited by laggyluk; 01-12-2012 at 11:42 PM.

  2. #2
    PGDCE Developer Carver413's Avatar
    Join Date
    Jun 2010
    Location
    Spokane,WA,Usa
    Posts
    206
    there is no way the compiler would change the layout for dynamic vs static that would break the compatibilty of the two. my guess is that you are miscalculating the size some where and the data isn't making it to the final destination. Edit:guess Iwas too slow, so you got it, looks good.
    Last edited by Carver413; 02-12-2012 at 12:20 AM.

  3. #3
    Not sure if it's solved but I want to make a comment about record alignment. In the engine I wrote and used in the 2nd. PGD Challenge I didn't use records to store data that is used with OpenGL; I use vectors (ARRAY) instead. For example, to store xyz points I used something like:
    Code:
    CONST
      COOR_X = 0;
      COOR_Y = 1;
      COOR_Z = 2;
    TYPE
      Vector3D = ARRAY [0..2] OF glFloat;
    To access to each axis I use the CONST (i.e. Point[COOR_X], etc). This way I can use the "v" functions without alignment problems.
    No signature provided yet.

  4. #4
    yeah it works alright now

  5. #5
    I have a bunch of classes now, should I worry about writing destructors for them or memory will be freed autimatically when app terminates?

  6. #6
    PGDCE Developer Carver413's Avatar
    Join Date
    Jun 2010
    Location
    Spokane,WA,Usa
    Posts
    206
    when it comes to classes whatever you create you must destroy. you should get heap trace up and running if you don't already. check the output file often to check mem leaks as you go along. also make sure to free up any opengl stuff in your destructors.

  7. #7
    ok, thanks. list of leaks is so long that it doesn't fit on the screen

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •