Open AlexanderPoone opened 3 years ago
I also discovered that if the source has a highly overlapped UV map, the chances are that many parts of the mesh cannot be rendered correctly.
@SoftFeta Thank you for the information. We are aware of this issue and are working on a solution.
@rvargasESRI
Thanks for the response. By the way, there is a normalTexture
attribute in the materialDefinitions materialDefinitions i3S specification. Does it imply that ArcGIS Online supports normal mapping? Thanks.
@
@SoftFeta Thank you for the information. We are aware of this issue and are working on a solution.
Hi! I have met the same problem. Does this problem solved in new version?
Hi! I tried to merge 200 osgb files into a single SLPK. I have tried two methods but they ended up having the same effect. The osgbs are not in a pyramid hierarchy. Although the entire scene is rendered at first, most parts near the boundary disappeared within a split second.
osgconv
utility from openscenegraph.org to merge all 200 osgbs into a single osgb, then convert it to SLPK using the Create Integrated Mesh Scene Layer Package tool in Pro. No errors are raised using both tools.Options I have tried: setting
OSG_OPTIMIZER
environment variable toCOMBINE_ADJACENT_LODS
MERGE_GEOMETRY
MERGE_GEODES
SPATIALIZE_GROUPS
TESSELLATE_GEOMETRY
INDEX_MESH
or a combination of these, but to no avail. SettingOSG_COMPUTE_NEAR_FAR_MODE
toDO_NOT_COMPUTE_NEAR_FAR
, yet this does not work either.You may also exclude the possibility of the model having incorrect normals, because removing the normals results in the same glitch.
Input Dataset
in the Create Integrated Mesh Scene Layer Package tool in Pro. No errors are raised. The visual glitch is identical to that of the previous method.I am using Pro 2.7.3 and OpenSceneGraph 3.6.4 / 3.6.5.