On the Verge by Petr "HurracioDurrski" Švenda

    Quote from SpronyvanJohnson

    Is that patch work for the vaulted ceilings or did you import it as a model?


    its patches, i always did everything right in the radiant.


    i recently started learning blender, and importing game assets to unreal engine and mostly had problems with unwrapping, baking, lightmaps etc. and what experienced people model for 30-60 minutes im making whole day . i dont have really much time to learn this for quake 3.

    i had some design that will be better or need model making but i probably pass it and try to do everything in radiant. hope i finish the map in time and somehow optimized.

    Make sure you stay around 40k tris, then it won't matter how many patches you use.


    Or well, don't use too many =) But the imit is pretty high I think, I never had any issues with using plenty of them.

    I did a test with ~90k tris and my fps dropped from constant 90 to 82, if I turn arround very fast. And I dont have a monster pc.

    Just make sure to increase the hunkmegs, or q3 crashes while loading.


    Nice gothic architecture

    thanks guys, by the way isnt hunkmegs set higher in console? other people would need to increase it too and that doesnt much ok i think.


    I have old computer, but its builded good so it runs new AAA games, and laptop that has very bad gfx and cant even run quake live on 125fps with picmip settings or Rune (UT99 engine i think), so i will test on it too.


    iam also using lot of that stonewall and rust texture combination in my gothic maps but it isnt exactly polycount friendly

    Quote from HurracioDurrski

    OK noob question, where can i get polycount for my map after rendering a cant find it anywhere


    /r_showtris, this draws the level as polygons being rendered by Q3. /r_speeds, this shows a readout of the number of polygons being rendered. /r_lockpvs, this culls areas of the map outside the leaf node that you occupy at the time of enabling.

    Ok, like this:


    NNN/NNN TRIS


    First numbers are triangles in a single pass (like with basic textures as base_wall/concrete_dark), this is your raw triangle count.


    Second numbers are triangles i several passes (when you have textures with several stages to them, like ctf/killblockctf_b, which has 4 additional stages inside the shader, because it's rotating and shit)


    You should know that everything you see on the screen adds to these numbers, not just the level, you can directly deduct ~800-1000 tris, if you display your weapon, hud and the r_speeds numbers themselves that are something around ~400 tris. A letter/number is 2 triangles so.

    You should know that patches adds a lot of (dynamic cause of LOD) triangles, even if this can be modified through console commands in game, you really should treat your tri-count as if everyone were running on max settings and no special console commands or whatever.

    Quote from Hipshot

    You should know that patches adds a lot of (dynamic cause of LOD) triangles, even if this can be modified through console commands in game, you really should treat your tri-count as if everyone were running on max settings and no special console commands or whatever.


    control points for stairs alone are on grid, i can convert them to brushes, but texture aligment would be probably hell idk.


    also, there should be same stairs on right side, but destroyed and i need some destroyed pillars too, and when i rotate these brushes and then moved it they all deform and unalign.

    so its another patches or i think ill just go learning how to make models for quake in blender where i can reduce polycount by quite big number i think (baked from highpoly to lowpoly).

    Your main concern will probably be sparklies.


    Quote

    For brushes, a convex polygon is defined for the area of each visible brush-face that touches one or more Convex Leaf Nodes. Brush-faces with surfaceParm nodraw are ignored. Extra vertices on are created on the edges of each polygon where other polygon vertices meet the edge and create a T-junction. The extra vertices 'fix' the T-junction by turning it into a point where three polygon edges meet. If a vertex lies on an edge that cannot be split, there will be a tiny crack in the hull of the map (along the edge that cannot be split). These tiny cracks are known as "sparklies", because of the way they look when a bright surface is drawn behind the crack and 'sparkles' through it. Finally, each polygon is divided into triangles and stored as an OpenGL primitive called a Triangle-Strip, or as a Triangle-Fan in some cases.Patch Surfaces are treated as a collection of points during the BSP compile, and are turned into Triangle-Strips when the map is loaded. For this reason, T-junctions involving Patch-surfaces cannot be fixed automatically.

    map reset it would be too much detail in one view, so i started working on new layout



    original idea was ruins of some evil temple / cathedral floating parts in space.


    something like this:



    cant decide now if i should keep normal layout or break it

    i will probably start experimenting with it when i finish this center room so i have the proportions right.

    i have some technical questions:


    do vertexes on patches split brushes ?


    can you overlap patches with brushes and sink patches into another patches ?


    also is there any way to make detail brushes have different outline color in 2D view ? like func_group is blue

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login