Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
3.5.1f1
Issue ID
451795
Regression
No
Sometimes when importing .lxo file it fails saying I need Modo 501.
Sometimes when importing .lxo file it fails saying I need Modo 501.
Note: I have Modo 501 installed and the Mesh was built in this Modo version.
Error in console:
Modo couldn't convert the .lxo file to fbx file.
You need at least modo 501 to import .lxo files directly.
Modo log file (Temp/ModoLogFile.txt) contents:
-- modo Event Log -- Mon Mar 19 14:50:49 2012
System -------- Time -------------------- Type -- Message -------------------------------------
Log System Mon Mar 19 14:50:48 2012 Info Log system started
Scripts Mon Mar 19 14:50:49 2012 Info C:/Program Files (x86)/Unity/Editor/Data/Tools/ModoToUnity.py
Mon Mar 19 14:50:49 2012 Info Exception "command failed: Scene load was unsuccessful.
C:/Users/Christopher/Desktop/Modo/Flat/Assets/Models/TV stand.lxo (80000000)" on line: 47
Repro Steps:
1. Launch Unity 3.5.1
2. Create new project and Import attached asset
3. Observe error in console
Desired outcome: The files to be converted without any problems
Actual outcome: The importing fails claiming I should use Modo 501 at least but I do have modo 501 installed.
Please view attached screenshot.
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