Plotting does not work on Win 11

[rsriniva]

runmat> plot(sin(0:0.1:2*pi))
Error: Execution failed: No matching overload for plot with 1 args: expected 2 args, got 1

Win 11 / Powershell 7.5.2/ runmat 0.0.1 downloaded from GH release

[rsriniva]

SO basic x,y plot example from documentation worked, but the window failed to close, even though the runmat REPL says window closed

[luisdamed]

This happened to me as well on Win 10

runmat> plot(sin(0:0.1:2*pi))
Error: Execution failed: No matching overload for plot with 1 args: expected 2 args, got 1

plot(Y) is a special case of the default Matlab syntax: plot(X,Y), which does work correctly.
It opens the GUI window with the correct plot.
However it doesn't close correctly as mentioned by @rsriniva, until runmat quit is issued.

Command Prompt Session

Microsoft Windows [Version 10.0.19045.6216]
(c) Microsoft Corporation. All rights reserved.

C:\Users\luisd>runmat
[2025-08-19T11:16:24Z INFO  runmat] RunMat v0.0.1 starting
[2025-08-19T11:16:24Z INFO  runmat] Configuring GC with preset: "default"
[2025-08-19T11:16:24Z INFO  runmat] Initializing GUI plotting system
[2025-08-19T11:16:24Z INFO  runmat] Native window system initialized successfully
[2025-08-19T11:16:24Z INFO  runmat_plot::gui::thread_manager] Global GUI thread manager initialized successfully
[2025-08-19T11:16:24Z INFO  runmat_plot::gui::thread_manager] GUI thread started successfully
[2025-08-19T11:16:24Z INFO  runmat] GUI thread manager initialized successfully
[2025-08-19T11:16:24Z INFO  runmat] GUI system health check: Success: GUI thread healthy
[2025-08-19T11:16:24Z INFO  runmat] Starting RunMat REPL
[2025-08-19T11:16:24Z INFO  runmat] JIT compiler: enabled
[2025-08-19T11:16:24Z INFO  runmat_turbine] Initializing Turbine JIT engine
[2025-08-19T11:16:24Z INFO  runmat_turbine] Target triple: x86_64-pc-windows-msvc
[2025-08-19T11:16:24Z INFO  runmat_turbine] Turbine JIT engine initialized successfully for x86_64-pc-windows-msvc
[2025-08-19T11:16:24Z INFO  runmat_repl] JIT compiler initialized successfully
[2025-08-19T11:16:24Z INFO  runmat] RunMat REPL ready
RunMat v0.0.1 by Dystr (https://dystr.com)
Fast, free, modern MATLAB runtime with JIT compilation and GC

JIT compiler: enabled (Cranelift optimization level: Speed)
Garbage collector: "default"
No snapshot loaded - standard library will be compiled on demand
Type 'help' for help, 'exit' to quit, '.info' for system information

runmat> plot(linspace(0,2*pi,2*pi/0.1+1), sin(0:0.1:2*pi))
[2025-08-19T11:16:51Z INFO  wgpu_hal::vulkan::instance] Debug utils not enabled: debug_utils_user_data not passed to Instance::from_raw
[2025-08-19T11:16:51Z WARN  wgpu_hal::vulkan::adapter] Disabling robustBufferAccess2 and robustImageAccess2: IntegratedGpu Intel Driver is outdated. Found with version 0x19483F, less than the known good version 0x194843 (31.0.101.2115)
[2025-08-19T11:16:51Z INFO  wgpu_core::instance] Adapter Vulkan AdapterInfo { name: "NVIDIA GeForce GTX 960M", vendor: 4318, device: 5019, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "572.16", backend: Vulkan }
[2025-08-19T11:16:51Z WARN  egui_wgpu::renderer] Detected a linear (sRGBA aware) framebuffer Bgra8UnormSrgb. egui prefers Rgba8Unorm or Bgra8Unorm
[2025-08-19T11:16:51Z INFO  naga::back::spv::writer] Skip function Some("position_from_screen")
CAMERA: Set orthographic bounds: left=-2, right=4, bottom=-2, top=4
VERTEX: Struct size = 48, stride = 48
ans = 'Plot window closed successfully'
runmat> quit
[2025-08-19T11:18:19Z INFO  runmat] RunMat REPL exiting

Environment:

• Windows 10 Version 10.0.19045.6216 Command Prompt
• RunMat v0.0.1

[nallana]

@rsriniva @luisdamed -- the plotting system needs a bit more work. Currently the bulk of the logic is in place, but there are some areas that are not yet finished. Additionally, some of the built in functions do not have all their variants of argument inputs finished up.

I've documented that all here now:

https://runmat.org/docs/roadmap

The release getting RunMat to full language grammar and semantic coverage was released yesterday (getting this to all checkmarks).

The next 2-3 releases over the next 2-3 weeks will include canonical implementations of the minimal builtins (e.g. the variants of the plot function you're describing @luisdamed), the remaining todos in the plotting library finished, and the package manager / extensibility framework [in no particular order -- suggestions on what of the three would be the most and then least useful would be helpful].

Overall aiming to get all three done in the coming weeks as we skate to a v1.0 release.