01-06-2019 11:58 AM
I installed Vivado 2018.3 and noticed that the "Zoom Fit" function seems broken in the block design editor. I'm using Ubuntu Linux 18.04. When I click it (or if I just simply open the block design) it defaults to zoomed *way* out. I have to zoom in a bunch to find my design. It also zooms way out if I click "Regenerate Layout".
It's happening on both a brand-new design as well as an existing design I upgraded from 2017.3 to 2018.3. I've attached an example screenshot of how it looks when I initially open the block design (or after I click "Zoom Fit").
01-06-2019 09:26 PM
I checked for one test design which is migrated from Vivado 2017.4 to Vivado 2018.3 and the block design got open with proer zoomed in.
Can you please share your test design to reproduce the issue at my end.
01-06-2019 09:57 PM
Thanks for checking it out. Any design does it. Here is a set of steps for creating a simple design demonstrating the issue:
Again, in case it matters, I'm running Ubuntu 18.04. Specifically I'm running Ubuntu MATE 18.04. This problem does not happen in Vivado 2017.3. I've attached a screen recording of the problem in action (it's a webm video playable using Chrome or VLC Media Player).
01-06-2019 10:07 PM
I already responded to your message once, and it appears that maybe my response was blocked or something? The post went through, and now it seems to have disappeared. Anyway, in that response I posted a video showing the problem. Hopefully the forum moderator can fix my blocked response so you can see the video. The gist of my message was that it doesn't matter; just create a new project, create a block design, and add an IP block. It will appear zoomed way out by default, and the "zoom fit" button also won't zoom in. I'm using Ubuntu MATE 18.04, and this problem doesn't happen with 2017.3.
01-07-2019 10:43 PM - edited 01-07-2019 10:45 PM
I tried to reproduce the issue following the steps shared from your end, but it didn't reproduced at my end.
When i added the IP it appeared in normal size, please thake reference from snapshot:
01-08-2019 06:58 AM
Hmm, weird. I wonder why it's only happening to me. What's weird about it is that 2017.3 doesn't have the problem...only 2018.3. I guess I can try some different distros in a VM to try to narrow the problem down further. That will take me a while to do. It looks like you're running Red Hat. Maybe the problem is limited to Ubuntu or something.
01-08-2019 10:30 PM
I made a bunch of virtual machines, and I am unable to reproduce the problem I reported in any of my VMs. That includes Ubuntu 16.04, Ubuntu 18.04, Ubuntu MATE 16.04, and Ubuntu MATE 18.04. So this must be something specific to my computer. I'm not sure what's going on with my particular computer, but it doesn't seem to be a general problem because everything works fine in a virtual machine running the exact same version of Ubuntu.
01-13-2019 09:36 AM - edited 01-13-2019 09:41 AM
I wanted to add one last piece of information. This problem also does not occur in 2018.2. So something about the combination of 2018.3 and my computer seems to be broken for zooming. I've reinstalled 2018.3 multiple times just in case it was a corrupted install or something. Something has changed in 2018.3 that breaks the zoom functionality on my computer.
Edit: I suspect this is probably related to how 2018.3 claims to now have native high-resolution monitor support.
01-22-2019 06:59 PM
Just updating on this issue, Xilinx is aware of it and there is already an internal Change Request (CR-1016551) for investigating and fixing this issue.
At the moment, unfortunately there is no patch or workaround yet, other than manually zooming in.
We'll update as we have more info on this case.
01-22-2019 07:13 PM
Thanks for the update, Andre. I appreciate it! And thank you wickmann for confirming that you saw the issue too...at least now I know I'm not going crazy! :-)
02-02-2019 05:23 AM
First of all, I would like to mention that I have encountered the same problem. And I'm moving the situation even further, and I'm telling you that there are problems with Chipscope (CS) wave windows. Zoom and CS problems started after Vivado 2017.3 (with Vivado 2018.1). I first thought these were problems with Vivado, but I realized that the problems were caused by the VMware agent. Because I have never encountered any of the problems mentioned in physical machines. When the connection is opened using the VMware viewagent on Ubuntu Mate 16.04 and Ubuntu Mate 18.04 virtual machines (using Horizon Client), zoom and CS problems start. For my part, I couldn't find a permanent solution to the problem, but I found a way to overcome it. After the boot of the VM, you connect it with the Horizon Client. You then log out (not re-boot or shutdown) and re-connect to the VM with Horizon Client. So the VMware agent is re-started. You will no longer see the above mentioned errors unless you change the number or resolution of the monitors. You must repeat this logout-reconnect cycle after each re-boot or shutdown.
02-13-2019 11:33 AM
I'm facing the same issue. It's so frustrating because the "zoom out" happens even when I make a connection between two ports.
I'm running CentOS 7, if this helps to solve the issue.
02-15-2019 08:09 PM
Today, I installed vivado version 2018.3 and it's hapened to me too. I coould fix it by a ubuntu display setting. I change the "scale for menu and title bars" to 1
02-16-2019 03:11 AM
The work around that you mentioned works for CentOS 7 and gnome 3. Thank you for the solution, now it is possible to work with Vivado 2018.3.
You have to execute Gnome Tweak and then in the left hand side menu select Fonts, and set Window Title to 1 and Scaling Factor to 1 as well. Check the image or this post https://unix.stackexchange.com/questions/257163/reduce-title-bar-height-in-gnome-3-gtk-3
02-27-2019 09:59 AM
This is fixed in 2019.1.
For 2018.3, Please use /usr/bin/gnome-tweak-tool to change the "Scaling factor" as shown above to 1.0.
07-19-2019 04:07 AM
So happy you found a solution for Ubuntu machines. This has fixed all 5 of my 15 training laptops that where exhibiting the issue! However the issue only appeared on the Older Elite books, not the newer machines? All running 16.04lts and the same 2018.3 installation...