The only workaround to that is ignoring any additional reference to an asset already shown but that isn't a good solution either because it worsens the readability of the dump (as exporting references recursively does in either case). More problems would arise when the same asset is referenced twice or when an endless recursion occurs. The dump doesn't resolve the references because it would easily cause issues reimporting because it would either have to discard the changes to referenced assets or change assets that the user didn't select. With both the absolute ID of the targeted asset and the m_PathID, you can find the referenced asset in the list (using "View->Go to asset" if necessary). The reference is valid if m_PathID is not 0, in which case the m_PathID value is equal to the path ID as shown in the asset list. assets file with the same absolute ID as the dumped asset. If the m_FileID value is 0, the PPtr refers to the same. The number left to this file name in the upper list is the absolute file ID. assets file where the number is m_FileID-1. To find the "absolute" file ID of a PPtr (as shown in UABE's list) with a m_FileID value bigger than 0, use "View->Dependencies", select the absolute file ID of the dumped asset in the upper list and look up the name of the targeted. assets file where the dumped asset is located. If you need the dump of an asset "inside" a PPtr, you can use the m_FileID and the m_PathID fields. The View Data dialog allows directly showing other assets referenced through PPtrs. This is very important! Maybe then, I can Supplement it ( extract animations, terrain, structures, prefab and scene). I beg you, fix this if you will not be difficult.Īnd one more request - is it possible your utility, in the language of C#?! Save file and no reference to the texture. Export Dump does not work correctly! Sohrae NOT the complete data. No ability to copy (or save to file), the contents of the View Data (Asset Data). Try it, to extract the data I needed (terrain & animation)
0 kommentar(er)
