Search Issue Tracker
Fixed in 3.0.2
Votes
4
Found in [Package]
3.0.1
Issue ID
1188556
Regression
No
[Linux] Adding terrain tools package makes an endless loop of importing
To reproduce:
1) Create a new project
2) Select "Window -> Package Manager" in the top bar
3) Reveal preview packages
4) Install Terrain Tools package
5) Try interacting with Unity after it's installed
Result: Nothing can be done as an endless importing loop between "Fbm" and "FBM" folders
Deleting one of the folders through file explorer fixes the issue.
Reproduced in 2019.3.0a9, 2019.3.0b6, 2020.1.0a1, 2020.1.0a7
Not reproduced in 2019.2.8f1, 2019.3.0a8
Not reproduced in Windows 10
Comments (3)
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
lukesanantonio
Jul 27, 2020 23:03
Reproduced in 2019.4.1f1. Please fix this is a major showstopper and hopefully an easy fix!
Indyk
May 23, 2020 23:35
Reproduced in both .3.8 and .3.14
JorMed
Apr 02, 2020 17:52
Reproduced in every editor from 2019.3.1f1 upto 2019.3.7f1. Major bug witch prevents using Unity on linux. My guess it's very simple bugfix just some of filepaths uses capitalized FBM folder, in linux Fbm and FBM are different folders, in windows it is the same.