Hi @Mohammed,
I saw your post about the double lane change reference application error in MATLAB 2025b. This looks like it could be a compatibility issue with the newest release. The "Not enough input arguments" error in the Vehicle XY Plotter block suggests that the vdynXYplot function is being called without all the required parameters during model initialization.Here are a few things you can try to resolve this:
First, instead of using the command line function, try opening the model directly. Open MATLAB and type DLCReferenceApplication in the command window, which should open the Simulink model. Then try running it from the Simulink interface using the Run button rather than the vdynblksDblLaneChangeStart command.
If that doesn't work, there might be an initialization issue with the workspace variables. Before running the model, try manually initializing the required parameters. You can look inside the model's PreLoadFcn callback to see what variables need to be set up. Go to Model Settings > Model Properties > Callbacks > PreLoadFcn to check what should be initialized.
Another possibility is that the Visualization subsystem isn't getting the proper input signals during initialization. Try opening the DLCReferenceApplication model, then navigate to the Visualization subsystem. Double-click on the Vehicle XY Plotter block and check the Internal Vehicle XY Plotter subsystem. The error is happening at line 5, which is likely where it's trying to access input data that hasn't been initialized yet.
Since you're on 2025b, which is a very recent release, there's a chance this could be a bug that was introduced in this version. The Vehicle Dynamics Blockset examples are usually very stable, so having this error in a pre-built example is unusual. You might want to check if there's a patch or update available for your MATLAB installation. In MATLAB, go to Home > Add-Ons > Check for Updates.
If none of these work, I'd recommend reaching out to MathWorks Technical Support directly since this is a pre-built example that should work out of the box. You can contact them through the Help menu or at Mathworks Support .
Since you've already tried a complete reinstall, they'll want to know that, and they may have a specific fix for 2025b. As a temporary workaround, if you have access to an earlier MATLAB version like 2024b or 2024a, you could try running the example there to see if it's specifically a 2025b issue.
Hope this helps!
