The error pops up in



For Q3BSP Code check Here (i havn't touched the rendersurfaceshader procedure).

I use to have this problem with the skyboxes (Sphere ones) on some Quake 3 maps, but i "fixed" that by drawing it "manualy" insted of using the array method.

Screenshots below.

Note: the error only appears in parts of the map, other parts cause no errors.

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

It would be verry useful if you would locate the error by adding showMessageDlg commands to your code. When you get the exception dialog, go back to the last message dialog and locate the error.

It will b the glDrawArrays , which doesn't help. Something gets set to an invalid thing. Last time i looked for info on the error i found nothing useful.

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

I don't think your problem is the glDrawArrays. It's more likeley in glVertexPointer, as your stride parameter seems to be wrong. Many people make the mistake and set this to the size of their vertex structure, which is wrong. The stride parameter contains the offset between two vertices. So if you have something like this :


Then the stride parameter must be set to zero, cause all vertices are tightly packed in that array (i.e. there is nothing between two vertices). An error in glVertexPointer also would explain your Access Violation.

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

I'm using a 32 Byte packed Vertex record and I've set stride to 32. It seems that stride=0 is a special case.

I never actualy made that procedure so i don't know how the glVertexPointer works.





EDIT:

setting the stride to 0 creates a screwed up world.

EDIT2:

I turned shaders off and it doens't create the error, so it seem that something happening in the shader routines arn't liked by the array method (going by the skybox which was screwing up with the array method in some maps, actualy works perfectly drawing it "manualy"....)

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

Your engine looks fine! The style of the level has something of the old Heretic game (by Raven soft). The only thing I miss is water (chanels an such things).

But...this is OT.

_________________
Blog: kevin-fleischer.de und fbaingermany.com

Someone plz correct me when I'm wrong (it's late ) :

First, you should use a "packed record" instead of only a record, so you can be sure that Delphi won't change something on your record's alignement :


After that, you need to calculate your stride. I guess your vectors are made of single, so you calculate your stride like this :


So that means, that between two vertices (TBSPVertex.Position) is a stride of 44-12 -> 32 Bytes, i.e. 32 Bytes after the first position of a vertex, the next position follows in your array :



So I hope (and also think ) that this should work.

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

Actualy Helios uses Q3MapView as a base (well its files, so the level rendering was already made, tho seems to have some bugs....). The map is Q3DM2 (Quake 3).

anway, Back on topic. Its definatly not the glvertexpointer, the rendersurface (used by textures with no q3 shader(not to b confused with opengl/direct x shaders)) has the same line in it and it works perfectly.

Also changing the stride to 32 makes it look similer to with it set to 0.(only seems to work when its, its own size).

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

The following are procedures that modify the vertex position, texture position, etc depending on the shader for the texture.







I think the problem is in one of these since:

1. Its something relating to a shader
2. they modify the data depending on the shaders

And incase anyone wonders what a q3 shader looks like here is one:

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu