AOS 4.x Warp3D problem in W3D_DrawArray

The second Warp3D bug from me (not exactly from me, but from Mr_Capehill?, who did Quake3 port to aos4) are in the W3D_DrawArray function. The problem with Vertex count values (i hope Mr.Capehill will explain it better later). The smaller workring vertex count value are 9 (only). 2, or 3, or 5 just does not works. 10 works. 11 too. 12 not. And so on. 333 works. 300 not.

I upload Here his example. Which by default have values 333 for vertex count, and it works fine. But, if you will change it on 300 for example, it just does not works (grey window). Its hardly to understand why it like this, and where is logic, so, we assume that its a bug, and any vertex value should works.

@All

Anyone can try to download that example, and try to run it from shell. By default it have 333 (works), but you can try to put as first argument to programm any other value from 1 and more, just to see that with some values it works, with others are not, and there is not logic why it like this.

@kas1e

Thanks bro, but it's possible that my code has a bug. IIRC I don't divide by three the triangle count. Have to check. And sorry about the hassle :)

EDIT: or maybe the other way around, I did an unnecessary division.

@Capehill

On latest IOQuake we have also many problems about audio distortion, almost on Sam/Sam Flex machines ...

hello,

if launched on the SAM with text.exe or text.exe 1 or 2 or 3,...., there are lots of fail -9 on the shell.

@Capehill

Quote:

Could you check whether this is the case or not before someone starts trying to track down a phantom bug?

Hans

@Hans

Yes, it's my fault. Count parameter set wrong. Sorry. Bug is here:

IWarp3D->W3D_DrawArray( context, W3D_PRIMITIVE_TRIANGLES, 0, VERTICES/3 );

@Capehill

Ah, okay. Any luck tracking down which rendering calls are causing quake3 lockups?

Hans

@Capehill
So, with good parameter set all is ok for now ?

@kas1e

I guess so. I didn't do very deep testing though. It also makes now sense why 333 worked (111 vertices, can be divided by 3) and 300 not (100 vertices, can't be divided by three)

@Hans

Not yet :(

@Capehill

So, the bug is still here ? I.e. 300/3 = 100 verts are not works (but must) ?

@kas1e

Quote:

Change:

IWarp3D->W3D_DrawArray( context, W3D_PRIMITIVE_TRIANGLES, 0, VERTICES/3 );

to:

IWarp3D->W3D_DrawArray( context, W3D_PRIMITIVE_TRIANGLES, 0, VERTICES );

If you look at the autodocs, W3D_DrawArray()'s final parameter is the number of vertices, not the number of primitives being rendered. The number of vertices should be a multiple of the number required per primitive, or it won't draw a thing.

Hans