subscribe to codewalrus
Started by TheMachine02, January 19, 2015, 05:10:01 pm
0 Members and 1 Guest are viewing this topic.
Quote from: DJ Omnimaga on May 03, 2015, 06:16:14 amOhai ben_g, long time no see . Hopefully @TheMachine02 can help you there. Or maybe @matrefeytontias could help a bit if he looked into gLib before.By the way is this for the 3D thing you used to work on several years ago?
Quote from: TheMachine02 on May 03, 2015, 09:19:43 amgVBOVertex(id) does only put the full-3d coordinate in the new gPositionX,Y,Z structure, and doesn't give screen position.The gVBOPoint(id) does give the screen position (wich are now 1 byte) and the clipCode in hl.The new gVBOGetData allow retrieve evrything in one pass though. the syntax is gVBGetData(destination_adress, size, offset, id), so I guess you most likely want to call it like that : gVBGetData(°GscreenX, 8, 0, id)The screen coordinate will be in °GScreen, and the vertex coordinate in °GPosition. This is basically the "bottleneck" I talked about. VBO are pretty badly implemented, and need a pretty much whole refactoring. gLib spent to much time in those vertex data manipulation So yeah, this is the current syntax, but that will most likely change.
CodeWalr.us 2.0 © 2019, DJ Omnimaga & Juju
Page created in 0.028 seconds with 37 queries.