check_model() shows nothing on some PCs about performance HOT 7 OPEN

See the code of this vignette for plotting single panels: https://github.com/easystats/performance/blob/main/vignettes/check_model.Rmd

from performance.

You can try check_model(..., panel = FALSE), which should return single plots. I haven't faced this issue with VSCode yet, so I'm not sure if it's a particular issue with this combination of RStudio, Windows and increased scaling?

from performance.

Can you share some screenshots of what they are seeing and also share their hardware information (especially graphics card and display driver)?

from performance.

Could you also ask them to try to "make the image panel bigger". I remember having a similar issue on laptops with small screens, and making a bigger plot panel worked. Not sure if that's the same issue butt it's worth a try

from performance.

You may read this long thread: #536

Have you updated to the latest package versions? In that case, check_model() should return an informative warning/error message:

I think that msg covers most/all possible solutions to your problem.

from performance.

We are having the same problem on a couple of students' PCs. check_model(m) runs with no errors or warnings, but only produces a blank canvas. We've got one student on Debian and one on Windows 10. Windows 10 was a standard 13" screen running the recommended 150% Scaling. We managed to fix it with a combination of changing Scaling (in Windows) and Zoom in RStudio, so the size is the underlying issue here as well.

However, this renders the rest of RStudio unbearably small and doesn't seem to be a good long term solution. Could a solution be to run the plots sequentially with a warning when the plot window is too small for the patchwork version?

Everyone is running freshly updated R, RStudio, performance, see and patchwork.

from performance.

This works great for me (on Mac), thanks! I can report back tomorrow. I think there's definitely an element of the combination, but I'm really not sure why it can get away with not even producing the informative error message although producing a blank plot.

The ...panel = FALSE solution is acting a bit odd to me, though it might not be an issue:

• If I call check_model(..., panel = FALSE) on its own, no plots are produced, contrary to panel = TRUE. I'd expect it to output the plots.
• But if I call check_model(..., panel = FALSE) |> plot() that produces all the plots. Great!
• However, if I only want to then call one of the plots, I'd imagine I could run model_checks <- check_model(..., panel = FALSE) then plot(model_checks[1]), but that produces the error Error in xy.coords(x, y, xlabel, ylabel, log) : 'x' is a list, but does not have components 'x' and 'y'. That's quite unexpected behaviour to me.

from performance.