Forum
Important Notice for New User Registrations
To combat an increasing number of spam and bot registrations, we now manually approve all new user registrations. While this may cause a delay until your account is approved, this step is essential to ensure the quality and security of this forum.
To help us verify your registration as legitimate, please use a clear name as user name or an official email address (such as a work, university, or similar address). If you’re concerned that we may not recognize your registration as non-spam, feel free to email us at with a request to approve your username.
Support for ROSCO v2.10.3
Quote from Andhi.Kusnadi on 23. January 2026, 10:00Hi,
Would you mind to clarify if ROSCO v2.10.3 controller is supported in QBlade?
I intend to use the NREL MHK RM1 control parameters but the QBlade program seems to crash when libdiscon.dll from ROSCO v2.10.3 is used as controller DLL. I wonder if the crash is due to controller input error or due to unsupported controller DLL.
Thanks.
Hi,
Would you mind to clarify if ROSCO v2.10.3 controller is supported in QBlade?
I intend to use the NREL MHK RM1 control parameters but the QBlade program seems to crash when libdiscon.dll from ROSCO v2.10.3 is used as controller DLL. I wonder if the crash is due to controller input error or due to unsupported controller DLL.
Thanks.
Quote from David on 23. January 2026, 20:39Hi Andhi,
I just ran a quick test and can confirm that ROSCO 2.10.3 is working correctly. I was even able to run it using the 32-bit library released on GitHub, via QBlade’s built-in inter-process communication for 32bit legacy controllers.
New ROSCO releases often introduce updated or additional required parameters in the controller input file, so I would assume the issue in your case is related to missing or outdated input settings.
I would recommend enabling the controller debug output via: Menu -> Options -> Open Debug Console.
ROSCO usually provides quite verbose error messages there, which should help identify what is going wrong.Best regards,
David
Hi Andhi,
I just ran a quick test and can confirm that ROSCO 2.10.3 is working correctly. I was even able to run it using the 32-bit library released on GitHub, via QBlade’s built-in inter-process communication for 32bit legacy controllers.
New ROSCO releases often introduce updated or additional required parameters in the controller input file, so I would assume the issue in your case is related to missing or outdated input settings.
I would recommend enabling the controller debug output via: Menu -> Options -> Open Debug Console.
ROSCO usually provides quite verbose error messages there, which should help identify what is going wrong.
Best regards,
David


