I’m using Windows 10, GLMakie 0.3.0.
Other features of the new update such as colour cycling and DataInspector are working fine (and very welcome - thanks!).
Tony
I think the additional axis keyword in the heatmap call might mess this up, because the GLMakie backend doesn’t know what to do with it. You already have an axis, so you can’t pass an additional axis keyword. Pass the aspect to the Axis directly instead.
My example is over-complicated because I copied the code fron the Makie announcement thread and also wanted to show that Colorbar still works. Just using
I just checked and I can’t reproduce it.
Can you show the versions of Makie + GLMakie?
What could have happened is, that the new shader introduced one of those super annoying driver specific bugs…
Can you show the output of display(heatmap(rand(5, 5))) ?
In case it’s relevant, PlotlyJS seemed to be holding back the update so I had to remove it (something about WebIO versions, I think) before I could get the latest version of GLMakie.
I’ve tried deleting my .julia folder and re-instantiating but that didn’t help.
I can reproduce the empty plot and I also have a Dell XPS175 with an NVIDIA card. And that’s probably the same reason why 3D scatter plots do not work too. As I mentioned in another thread this plots an empty axes
Sorry to deviate a little but I’ll have to go soon and wanted to leave this other remark.
This surface plot works fine (aside from me still having to figure out the tight memory layout for the matrices). It shows the Canary islands and coast of Africa from an unknown viewpoint, but that doesn’t matter here. What matters is that once displayed my GPU stays a 100% use and fan goes crazy even if I don’t touch the figure. That, I think, is a very killing feature, specially when run from laptops.
using GLMakie, GMT
f = Figure(resolution = (1200, 800), fontsize = 14)
ax = Axis3(f[fldmod1(1, 2)...], aspect = (1,1,0.1))
G = gmtread("mauritania.grd");
surface!(G.y, G.x, G.z)
Hi @joa-quim. I had that problem with plots with lots of data and the solution given to me was to reduce the rate at which the plot is redrawn by something like
Thanks @tt1234567 it does make a difference but not that much. Experimenting with this case showed that I need a framerate~=10 to have a smooth refresh, but with that the gpu usage is in the 70-80%