Hello there. Just want to ask how many polygons in one model can FPSC R handle? I exported model with 12k polygons and it crashed. Then i divided this model(building) in two and add it 2 times in editor and everything ran well. So where is problem? Thx

Hi
In the folder Doc, you can find the instructions. .....C:\Program Files (x86)\The Game Creators\FPS Creator Reloaded\Docs
Recommend to create objects with 500 polygons and characters with 6000.
If you look in the store you will also find objects with poly 6000-7000.
I think that's the maximum number of poly fpscr that supports it.
Forgive my English

Thx for quick response . Well I tried model with 8600 polygons and it also runs well .

i have found that 19k is the max that will load after that you will get a 3d error message in your case the verts may be more than reloaded can handle.

Reached 35 000 polygons easily, pretty sure I can push for even more maybe double that, as polygons isn't an issue it's the amount of vertices the model has, in fact if you delete hidden faces and merge the edges you can get a way with even more as a vert is counted on every intersecting edge.

35 000 wow always had mine crash at 19k but as you said its more the verts

Yip working on high detail models, so going to be epic...!! No more 4 x 4 block rooms

Nice wizard!

The engine uses a 16 bit index buffer system, so if you are using face data (indice data) then you are limited to 65535 entries, which breaks down to about 21K polygons. If you model was vertex data only however, that uses a 32 bit buffer and you can go as high as 600K polygon mesh, but I would recommend keeping your meshes to around 1000-3000 for ideal draw call performance on current/past generation cards.

Ahh makes sense i was wondering why anything over 19-20k would run a 3D mem error for me.

Will that limit ever increase?

Yes and no that is the format limits, not engine, per say. However the way I got around is tricky, but you can make use of NURBS surfaces.Besides you don't need really need to go higher than that unless you import a complete level, but that is not only impractical, but no one does that, as pretty much most engines support creating primitives with in the engine.



Ambient occlusion mapping is going to throw a fit when has to render that, most likely end up crashing, even thought a section of what I am creating weighs in at 35 000K polygons I still have to employ polygon reduction and slice it to a more manageable 150 x 150 units, which equals to a more respectable 10k polygons.



Also pretty sure the ambient occlusion lee is working doesn't have per pixel light mapping, in other words it doesn't smooth objects, is such a case less is better. Ambient occlusion only calculates the inner most angles of a model, which why lee has to batch render models, as the static as in effect he is trying to render the static object as a single model and not individual objects, that is my understanding at least.

The pre-bake ambient occlusion is per-texel which means every coordinate on the lightmap texture that belongs to a polygon gets calculated for ambient occlusion and source lighting. You 'COULD' export a single 35K mesh as vertex only export and it would load in, but you'll be sending a huge draw call to the engine in one go and it will not be able to use camera frustum culling, object occlusion or more than one texture set. The reason I recommend 1000-3000 polygons per mesh is that graphics cards like to handle draw calls in bite sized chunks rather than one huge list of triangles (at least that was the case when the cards I am supporting where around). If your 35K model uses multi-materials, the engine should split up the mesh for you behind the scenes however. Best thing is to send me the model by email with all it's textures and I will confirm if it's supported by the engine I have here (internal build).

I will send you some models Lee. Thx all for your comments.