01-05-2018
12:27 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
01-05-2018
12:27 PM
If you are talking about the update I guess I had to load 2018.2 before I load 2018.2.1
But neither of the updates fixed my issue..