Search Issue Tracker
By Design
Votes
0
Found in
2019.2.0a1
2019.3.0a3
Issue ID
1155222
Regression
Yes
[Preset Manager] Preset of .skp file don't have the same properties as SketchUpImporter
Preset of .skp file doesn't have the same properties as SketchUpImporter.
Steps to repro:
1. Create a new project.
2. Import attached .skp file. (Langevin.skp)
3. Create preset of the file.
Actual Result:
Longitude, latitude and north correction values are different.
Expected Result:
Preset has same properties as SketchUpImporter.
Environment:
Windows and Mac
Occurring with:
2019.3.0a3, 2019.2.0b3, 2019.2.0a1
Working fine:
2019.1.0f2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note (2019.3.X):
Those three values are read only and coming from the .skp file itself. Since a preset as no target per say, we have no value to display in a preset inspector. Therefore, those values are cleaned on preset creation.