There is a base address used by all attribute buffers at GPUREG_ATTRIBBUFFERS_LOC. When you configure each of the individual attribute buffers the data is specified as an offset from the shared base using GPUREG_ATTRIBBUFFERSi_OFFSET.
Thank you so much for all of this, this is really helping out! As for VERTEX_OFFSET being left to 0, it appears, in the case of portal3ds, that GPUREG_ATTRIBBUFFERSi_OFFSET is set the first vertex of whatever there is to draw everytime there's something to draw, thus defeating the purpose of the VERTEX_OFFSET register, I suppose.
. The whole point of this for me is to learn this kind of thing, so if you have any thoughts regarding what I said here, feel free to share them, as talking about this kind of stuff really makes it easier to understand and learn! (Again, thanks a lot for your help, and sorry for my potentially broken english!)GPUREG_ATTRIBBUFFERSi_OFFSET points to a buffer with vertex data. GPUREG_INDEXBUFFER_CONFIG is used to generate primitives based on the order in the index buffer. the index buffer format only allows bytes or shorts for the index values. in theory GPUREG_VERTEX_OFFSET could be used to start further along in the buffer. I suspect it is something along the lines of glDrawElements vs glDrawElementsBaseVertex, but I am not really sure.Thank you so much for all of this, this is really helping out! As for VERTEX_OFFSET being left to 0, it appears, in the case of portal3ds, that GPUREG_ATTRIBBUFFERSi_OFFSET is set the first vertex of whatever there is to draw everytime there's something to draw, thus defeating the purpose of the VERTEX_OFFSET register, I suppose.
That's what I got from the source regarding what you said, althought I'm probably wrong
While I didn't quite get the last part with the OpenGL correlation you made, I meant by "defeating the purpose" that while using the VERTEX_OFFSET register was possible, it would only cause the models to not be drawn fully. The only proper use of it I can think of would be to draw each model without adjusting GPUREG_ATTRIBBUFFERSi_OFFSET every time, and instead use the VERTEX_OFFSET register to separate the models from one another, however that does not seem feasible to me because of the way things are layed out in memory (the structs would prevent being able to keep the synchronisation between GPUREG_ATTRIBBUFFERSi_OFFSET and the vertex attributes from one model to the next, but then again maybe I'm not visualizing things right here. Would that be correct?) Also the VERTEX_OFFSET register is also left at 0 when using drawarray calls.
.If that did not make sense then I recommend that you ignore the vertex offset register and leave it at 0.While I didn't quite get the last part with the OpenGL correlation you made, I meant by "defeating the purpose" that while using the VERTEX_OFFSET register was possible, it would only cause the models to not be drawn fully. The only proper use of it I can think of would be to draw each model without adjusting GPUREG_ATTRIBBUFFERSi_OFFSET every time, and instead use the VERTEX_OFFSET register to separate the models from one another, however that does not seem feasible to me because of the way things are layed out in memory (the structs would prevent being able to keep the synchronisation between GPUREG_ATTRIBBUFFERSi_OFFSET and the vertex attributes from one model to the next, but then again maybe I'm not visualizing things right here. Would that be correct?) Also the VERTEX_OFFSET register is also left at 0 when using drawarray calls.
Thanks again, and by the way please tell me if I'm getting annoying with this
@
RedColoredStars:
@
RedColoredStars:
@
RedColoredStars:
@
RedColoredStars:
@
RedColoredStars:
@
SylverReZ:
@
SylverReZ:
] 