Quote from: DJ Omnimaga on May 03, 2015, 06:16:14 AMWell, I've been more or less active on omnimaga lately, but I kind of forgot about this site. I'll try to be more active here too.
Ohai 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?
And this isn't really for anything I've already worked on (I'm mainly just trying stuff out, looking at what stuff I can get together), but I might pick up one of those projects when I can get enough things working.
Quote from: TheMachine02 on May 03, 2015, 09:19:43 AMUsing GPosition seems to work, thanks.
gVBOVertex(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.