Concrete Tile Set

Concrete Tile Set Low-poly 3D model

Verification details of the FBX file
Files
Binary FBX
Scene
No unsupported objects
Geometry
No N-gonsNo faceted geometryManifold geometry
Textures and Materials
PBR texturesNo embed texturesSquare texturesPower of 2 texture sizesAssigned materials
UVs
No UV overlapsUV unwrapped model
Naming
Allowed characters
Description

  • Concrete Tile Set consist of midpoly models for vertex paint, and low poly models with LOD's in .max, .ma, .tbscene and .fbx formats and textures in 2k.
  • This models can be used for games, virtual reality, advertising, render scenes, design, etc. Concrete Tile Set sizes varies from 1 by 1 meter single mesh, to 4 by 4 meters plane.
  • This archive consists of:
      27 separate meshes:

    • tile set plane - 9 different size meshes
    • tile set corner narrow - 4 texture variation meshes
    • tile set corner wide - 4 texture variation meshes
    • tile set slab square base - 10 texture variation
    • 4 stexture set (4 materials) all in 2048*2048 pixels:
    • ground_mud - 7 textures
    • slab stairs concrete new - 7 textures
    • slab stairs concrete mid - 7 textures
    • slab stairs concrete old - 8 textures

  • You can change the distance between the slabs and the curb and place them at different heights relative to each other. Also you can use lowpoly meshes planes if needed. All meshes has LOD's and uv for bake lightmaps. This set ready for using in Unreal Engine.
  • This archive has only basic materials for 3ds max 2017, and Maya 2020, FBX version 2020.1.1

  • Concrete Tile Set meshes statistics:
    • tile_set_slab_square_base
    • lod0 - tris: 142, edges: 157, verts 73.
    • lod1 - tris: 80, edges: 92, verts 42.
    • lod2 - tris: 12, edges: 12, verts 8.
    • lod3 - tris: 2, edges: 4, verts 4.

      tile_set_corner_narrow
    • lod0 - tris: 158, edges: 184, verts 81.
    • lod1 - tris: 92 , edges: 119, verts 48.
    • lod2 - tris: 28, edges: 38, verts 16.
    • lod3 - tris: 4, edges: 9, verts 6.

      tile set corner wide
    • lod0 - tris: 180, edges: 206, verts 92.
    • lod1 - tris: 100, edges: 115, verts 52.
    • lod2 - tris: 32, edges: 39, verts 18.
    • lod3 - tris: 7, edges: 15, verts 9.

      tile_set_4x4_plane(and all lower size variations propotionally)
    • lod0 - tris: 512, edges: 544, verts 289.
    • lod1 - tris: 128, edges: 144, verts 81.
    • lod2 - tris: 32, edges: 38, verts 25.
    • lod3 - tris: 2, edges: 4, verts 4.

    B
    bobblunderton 2021-12-07 04:39:18 UTC
    These objects are quite nice, actually. If you use individual objects to create the scene, without homogenizing the objects into much larger chunks before run-time, you can sometimes cause more work for the render backend when using four levels of detail opposed to two or three. This is due to the fact that render calls on identical objects/pieces that are displaying the same LOD phase will batch, there-for creating little to no extra render overhead VS there only being one piece of XYZ object on the scene even if you have 1000 of them. If it goes to display different detail levels, this is a new set of draw calls here (worse if you have disconnected areas of the UV grid, and also other maps such as normal maps will also have to be drawn as with anything else). Draw calls are the enemy. If you can do so with some objects without pop-in, use less detail levels as it'll also make the VRAM weight just a tad smaller. Draw call reduction in DX12 or Vulkan rendered scenes is not as serious a need as in DX11 and older, due to multi-threaded rendering-backend being possible. DX11 and below is an absolute bear to get performing well by comparison, and often gets choked with draw calls leaving one core of the CPU jammed at 100% while the GPU and remaining CPU cores/threads not being fully utilized. I would still keep this version for sale, however. If someone is using a modern rendering engine, I don't foresee a huge issue with draw calls due to these objects, but I still thought I'd mention it none-the-less.
    MAX-HorizonS
    MAX-HorizonS 2022-03-29 08:24:24 UTC
    Еhanks for leaving a good and detailed review, very detailed information, such details and limits on the use of such 3d models have always been interesting. I'm glad it was useful, and I will be glad to any constructive criticism to improve the quality of the models. If there are suggestions on how to improve such sets, I will be glad to hear any advice.
    U
    umaxontoclaxon 2021-06-22 07:51:04 UTC
    Cool set! Nice looking textures, light weighted models! Easy to use in UE4! I love variations and aged versions!
    MAX-HorizonS
    MAX-HorizonS 2021-06-22 08:00:25 UTC
    I am glad that you liked this set and that it came in handy!
    Item rating
    1 0
    U
    umaxontoclaxon 2021-06-22 07:50:26 UTC
    Recommended
    Cool set! Nice looking textures, light weighted models! Easy to use in UE4! I love variations and aged versions!
    Concrete Tile Set
    $8.00
     
    Royalty Free License 
    Concrete Tile Set
    $8.00
     
    Royalty Free License 
    Response 50% in 3.6h
    3D Modeling
    Low-poly Modeling
    UV mapping
    Texturing
    3D Scanning
    PBR modeling
    View all Designers Models

    3D Model formats

    Format limitations
    • Autodesk FBX (.fbx) (2 files)1.49 MBVersion: 2020.1.1
    • Autodesk 3ds Max (.max) (2 files)3.27 MB
    • Autodesk Maya (.ma, .mb) (2 files)2.74 MB
    • Marmoset Toolbag (.tbscene, .tbmat)441 KB

    3D Model details

    • Publish date2021-06-21
    • Model ID#2994382
    • Animated
    • Rigged
    • VR / AR / Low-poly
    • PBR
    • Geometry Polygon mesh
    • Polygons 544
    • Vertices 289
    • Textures
    • Materials
    • UV Mapping
    • Unwrapped UVs Overlapping
    • Plugins used
    • Ready for 3D Printing
    Help
    Chat