{"id":18549,"date":"2026-04-23T09:11:34","date_gmt":"2026-04-23T13:11:34","guid":{"rendered":"https:\/\/blogs.mathworks.com\/simulink\/?p=18549"},"modified":"2026-04-23T09:11:34","modified_gmt":"2026-04-23T13:11:34","slug":"whats-new-in-r2026a","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2026\/04\/23\/whats-new-in-r2026a\/","title":{"rendered":"What’s New in R2026a?"},"content":{"rendered":"
\"\"<\/img><\/a><\/div>
MATLAB R2026a is available, let's see what's new in the Simulink world.<\/span><\/div>

New Context Menu<\/span><\/h2>
This one cannot be missed! We decided to modernize our right-click menu.<\/span><\/div>
Here is what it looks like when you right-click on a Constant block:<\/span><\/div>
\"\"<\/img><\/div>
I have been using this new menu for many months now and it works well for me. It takes a little bit of getting used to, but overall, I think this is a good evolution.<\/span><\/div>
See the <\/span>release notes<\/span><\/a> for more details.<\/span><\/div>

Move In\/Move Out<\/span><\/h2>
This one will save me so many clicks!<\/span><\/div>
Select blocks connected to a Subsystem and move them in, in one click. <\/span><\/div>
\"\"<\/img><\/div>
Select blocks connected to an Inport or Outport inside a subsystem and move them out, in one click.<\/span><\/div>
\"\"<\/img><\/div>

Time Tolerance to input Data<\/span><\/h2>
Throughout the years, one blog post that I had to refer to more often than I would like is this one: <\/span>Using Discrete Data as an input to your Simulink model \u00bb Guy on Simulink - MATLAB & Simulink<\/span><\/a>.<\/span><\/div>
To summarize: If you specify time points for input signals that are slightly different from the time steps that Simulink takes, you will end up with skipped or duplicated points.<\/span><\/div>
This new feature finally solves this issue. Let's revisit the example from this old post with and without the feature activated.<\/span><\/div>
ts = 0.001;<\/span><\/span><\/div><\/div>
t = (0:ts:10)';<\/span><\/span><\/div><\/div>
u = (1:length(t))';<\/span><\/span><\/div><\/div>
mdl = <\/span>'testInputTol'<\/span>;<\/span><\/span><\/div><\/div>
in = repmat(Simulink.SimulationInput(mdl),2,1);<\/span><\/span><\/div><\/div>
in(1) = in(1).setModelParameter(<\/span>'InputTimeTolerance'<\/span>,<\/span>'off'<\/span>);<\/span><\/span><\/div><\/div>
in(2) = in(2).setModelParameter(<\/span>'InputTimeTolerance'<\/span>,<\/span>'on'<\/span>);<\/span><\/span><\/div><\/div>
out = sim(in,<\/span>'ShowProgress'<\/span>,<\/span>'off'<\/span>);<\/span><\/span><\/div><\/div>
figure;<\/span><\/span><\/div><\/div>
subplot(2,1,1);<\/span><\/span><\/div><\/div>
stem(abs(u-out(1).logsout.get(<\/span>'u'<\/span>).Values.Data));<\/span><\/span><\/div><\/div>
title(<\/span>\"Without Time Tolerance\"<\/span>);<\/span><\/span><\/div><\/div>
subplot(2,1,2);<\/span><\/span><\/div><\/div>
stem(abs(u-out(2).logsout.get(<\/span>'u'<\/span>).Values.Data));<\/span><\/span><\/div><\/div>
title(<\/span>\"With Time Tolerance\"<\/span>);<\/span><\/span><\/div>
<\/div>
<\/div>
<\/div>
<\/div>
<\/div><\/div><\/div><\/div><\/div>
Minor related addition: <\/span>external input signal can now contain Inf and NaN<\/span><\/a>.<\/span><\/div>

Rapid Accelerator is Rapider<\/span><\/h2>
I hope you know that Simulink has a Rapid Accelerator mode. The way it works is it compiles the model into an executable, and that executable usually runs faster than the interpreted model.<\/span><\/div>
One problem is that launching this executable takes 1-2 seconds. For very short simulations, this can be significant. If you need to run a million of those, it's 1-2 million seconds lost. In R2026a, this initial launch time has been significantly decreased, speeding up short simulations.<\/span><\/div>
Here is an example:<\/span><\/div>
mdl = <\/span>'vdp'<\/span>;<\/span><\/span><\/div><\/div>
Simulink.BlockDiagram.buildRapidAcceleratorTarget(mdl);<\/span><\/span><\/div>
### Searching for referenced models in model 'vdp'.\r\n### Total of 1 models to build.<\/div><\/div><\/div><\/div>
kv = 1:0.1:1.9;<\/span><\/span><\/div><\/div>
in = repmat(Simulink.SimulationInput(mdl),length(kv),1);<\/span><\/span><\/div><\/div>
for <\/span>i = 1:length(kv)<\/span><\/span><\/div><\/div>
    in(i) = in(i).setVariable(<\/span>'k'<\/span>,kv(i));<\/span><\/span><\/div><\/div>
    in(i) = in(i).setModelParameter(<\/span>'SimulationMode'<\/span>,<\/span>'Rapid'<\/span>);<\/span><\/span><\/div><\/div>
    in(i) = in(i).setModelParameter(<\/span>'RapidAcceleratorUpToDateCheck'<\/span>,<\/span>'off'<\/span>);<\/span><\/span><\/div><\/div>
end<\/span><\/span><\/div><\/div>
out = sim(in,<\/span>'ShowProgress'<\/span>,<\/span>'off'<\/span>,<\/span>'UseFastRestart'<\/span>,<\/span>'on'<\/span>);<\/span><\/span><\/div><\/div>
t = arrayfun(@(i) out(i).SimulationMetadata.TimingInfo.TotalElapsedWallTime,1:length(kv));<\/span><\/span><\/div><\/div>
mean(t(2:end))<\/span><\/span><\/div>
ans = <\/span>0.3968<\/div><\/div><\/div><\/div><\/div><\/div>
In older releases, the same code gives me an average execution time of 2.3 seconds.<\/span><\/div>
On a somewhat related topic, in R2026a, it also becomes possible to <\/span>simulate models with algebraic loops in Rapid Accelerator mode<\/span><\/a>.<\/span><\/div>

Initialization Timing in Simulink Profiler<\/span><\/h2>
The<\/span> <\/span>Simulink Profiler<\/span><\/a> <\/span>now provides information about how compilation time is distributed among compilation phases and among referenced model.<\/span><\/div>
It's an enhanced version of the <\/span>CompileStats<\/span> captured by <\/span>sldiagnostics<\/span><\/a>. If you call technical support about problems with initialization performance, this is the first thing we will ask you to look at.<\/span><\/div>
\"\"<\/img><\/div>

Self-Paced Training<\/span><\/h2>
A new set of self-paced training to get you started with many basic aspects of Simulink:<\/span><\/div>