1- The FExportMaterialProxy didn't give the proper static parameters for the materials instance. It always used those from the parent/master material.
2- The mesh description extracted from the static mesh component was sometimes invalid. This occurred when the mesh had an empty section as it first section. This resulted in a mesh with all its polygons being part of the first section when rendered for the proxy mesh.
Also renamed a variable in the create proxy mesh function since its previous name didn't make sense with what it is.
#jira UE-90322
#rb Sebastien.Lussier
[CL 12234869 by Julien StJean in 4.25 branch]
#rnx
#rb none
#ROBOMERGE-SOURCE: CL 10869240 via CL 10869516 via CL 10869902
#ROBOMERGE-BOT: (v613-10869866)
[CL 10870584 by ryan durand in Main branch]
Fixed mesh pivot point offset not being applied in this specific case
#rb patrick.enfedaque
#ROBOMERGE-SOURCE: CL 10056720 via CL 10057694 via CL 10057717 via CL 10057792
#ROBOMERGE-BOT: (v566-10053404)
[CL 10057904 by sebastien lussier in Main branch]
HLOD useLODAImposter seems to not copy over all UV channels
Mesh merging code was assuming the UV2 & UV3 channels were free to use to store position & scale of imposter instances.
This behavior seems to have been hacked in the engine for an internal project & is not needed anymore since it's now possible to use instanced static meshes with LODActors
Still kept old behavior around (CVar) in case someone would really need it
#rb patrick.enfedaque
[CL 9868123 by Sebastien Lussier in Main branch]
Attempted to resolve merge conflict for CL 9844036 Robomerge, it caused compilation errors
#rb Jake.Romigh
#fyi sebastien.lussier
[CL 9845666 by Laz Matech in Main branch]
#jira UE-82185
HLOD useLODAImposter seems to not copy over all UV channels
Mesh merging code was assuming the UV2 & UV3 channels were free to use to store position & scale of imposter instances.
This behavior seems to have been hacked in the engine for an internal project & is not needed anymore since it's now possible to use instanced static meshes with LODActors
Still kept old behavior around (CVar) in case someone would really need it
#patrick.enfedaque
[FYI] bryce.lumpkin
#ROBOMERGE-OWNER: laz.matech
#ROBOMERGE-AUTHOR: sebastien.lussier
#ROBOMERGE-SOURCE: CL 9843087 via CL 9843965 via CL 9844036
#ROBOMERGE-BOT: (v548-9842178)
[CL 9845167 by laz matech in Main branch]
#jira UE-79140
jeanfrancois.dube
#ROBOMERGE-SOURCE: CL 8210627 via CL 8211744
#ROBOMERGE-BOT: (v401-8057353)
[CL 8211754 by sebastien lussier in Main branch]
Added new accessors for getting individual SourceModels, or the entire array.
#rb none
#jira none
#ROBOMERGE-SOURCE: CL 7668562 in //UE4/Release-4.23/...
#ROBOMERGE-BOT: RELEASE (Release-4.23 -> Main) (v372-7473910)
[CL 7668565 by richard talbotwatkin in Main branch]
* Now extracted from sub levels and brought in the main map to be rendered as instanced static meshes.
* Impostors meshes created during proxy creation.
#rb jeanfrancois.dube, jurre.debaare
#ROBOMERGE-SOURCE: CL 6675359 via CL 6675861
#ROBOMERGE-BOT: (vundefined-6665479)
[CL 6675880 by sebastien lussier in Main branch]
#fix No need to reverse the section indices when a static mesh has a mirrored transform as TransformRawMeshVertexData() is now calling ReverseAllPolygonFacing() in this specific case
#jira UE-56953
#rb none
#lockdown cristina.riveron
#ROBOMERGE-SOURCE: CL 6252335 in //UE4/Release-4.22/...
#ROBOMERGE-BOT: RELEASE (Release-4.22 -> Main)
[CL 6317322 by sebastien lussier in Main branch]
There was a second crash after this one where the code did not call RegisterMeshAttribute on a newly created FMeshDescription.
#jira UE-71929
#rb none
#ROBOMERGE-SOURCE: CL 5504837 via CL 5504994 via CL 5517943
[CL 5535766 by alexis matte in Main branch]
