Search Issue Tracker
4.5 version pdb2mdb.exe missing few dlls
There is missing few dll`s in "(Your Unity)\Editor\Data\MonoBleedingEdge\lib\mono" that is required by pdb2mdb.exe. It used to work ... Read more
Test Runner UI shows that Async / Await tests were successful when these...
The Assertion failure gets logged into the Unity console when the Test fails but the Test Runner UI shows a green tick and doesn't w... Read more
Backspace doesn't works in WebView android plugin
Steps to repro: 1. Build and run project provided by user 2. After start app will immediately invoke WebView plugin and open google ... Read more
[Image] Image with Source Image set to 'None' uses the same texture as o...
Steps to reproduce: 1. Create a new project and import the attached package 2. Open 'ImageSourceNoneBug' scene (Assets/StaticAssets... Read more
When opening MonoDevelop, 2 instances of one script are opened
To reproduce: 1. Open attached project. It contains two scripts 2. Open both of these scripts in monodevelop 3. Try to open either o... Read more
Error message - Asset import did not unload metadata path. This will lea...
Reproduction steps: 1) Add a model to a project, or open the attached project 2) Click the model (Rio) in the project window 3) Cli... Read more
RenderTextures do not include Canvas (UI) elements
How to reproduce: 1. Open the attached project 2. Open and play Main scene 3. Notice that where was white screen, screenshot appeare... Read more
Enabling gyroscope on Samsung Note 3 adds big cpu overhead
With gyroscope disabled, the CPU overhead is 4-7 ms. With gyroscope enabled the CPU overhead jumps to 20-30 ms with occasional spike... Read more
Slow, system-crippling startup of D3D11 players with DisplayPort monitors
1) Locate a machine with an NVIDIA graphics card where the monitor is connected via a DisplayPort connection. 2) Build a Windows Sta... Read more
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Labels to enable or disable Columns for Reflection Probes Clipping Planes do not match actual Column Labels
- Crash upon undo/redo operations performed repeatedly and errors are thrown
- Columns are mislabeled in the Reflection Probes section of Light Explorer
- Resolution is labeled as Near Clip in Cubemap Capture Settings
- Error "type is not a enum value" logged when ordering Reflection Probes by Resolution in Light Explorer