Search Issue Tracker
Active
Votes
0
Found in [Package]
4.0.0-pre.1
Issue ID
1298809
Regression
No
[Fbx Exporter] FbxProperty.Set() does not take 'string' argument
Reproduction steps:
1. Open attached project "FbxExport.zip"
2. In Project window, open Assets/Test.cs
3. In script editor, observe lines 13 and 17
Expected result: No errors, FbxPropertyString.Create() creates type of FbxPropertyString, FbxProperty.Set() can use a 'string' parameter
Actual result: Error, FbxPropertyString.Create() creates type of FbxProperty, FbxProperty.Set() can't use a 'string' parameter
Reproducible with: 3.2.1-preview.2 (2018.4.30f1), 4.0.0-pre.1 (2019.4.18f1, 2020.2.2f1, 2021.1.0b2)
Notes:
1. Issue also reproduces with other parameter types, such as 'bool'.
2. As a workaround, it's possible to add a custom script to the package's base class 'FbxProperty':
public FbxPropertyString Set(string pValue)
{
FbxPropertyString ret = new FbxPropertyString(NativeMethods.FbxPropertyString_Set(swigCPtr, pValue), false);
if (NativeMethods.SWIGPendingException.Pending) throw NativeMethods.SWIGPendingException.Retrieve();
return ret;
}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment