Reposted/reformatted from previously unlisted thread, as this is a remaining valid issue affecting HTML/JS weather listener/weather preset data use.
Version: 1.4.16.0
Frequency:Consistently
Severity:High
Context:Any flight, any aircraft, using custom/Preset weather
Bug description: Wind speeds in wind layers are limited to 150kts (77m/s) for custom preset weather via UI max/clamp values. When a user or add-on attempts to use 150kt or higher, the wind speed unexpectedly drops to zero instead of being clamped as intended.
Repro steps: Attempt to set wind speed > 150 knots (77m/s) for any wind layer in Preset/Custom weather via coherentGT debugger or custom javascript code. Observe depicted wind speed becomes 0.
Expected behavior: If there is a hard limit, the limit should be enforced but not corrupted/zeroed when reached (it should cap at 150kts in this case).
Yes, still happening, in the latest official anyway. I haven’t tried the betas this round yet. Here is an example of the code that shows the issue:
// MSFS2024 Build 1.4.20.0
// Language/units setting en-us/U.S. System
// This works, all wind layers become 150 knots
const overrideWindSpeedKts = 150.0;
for (let i = 0; i < as_wx_Preset.tWindLayers.length; i++) {
as_wx_Preset.tWindLayers[i].dvSpeed.value = overrideWindSpeedKts;
}
this.as_wx_Listener.updateTempWeatherPreset(as_wx_Preset);
// This fails, all wind layers become 0 knots
const overrideWindSpeedKts = 151.0;
for (let i = 0; i < as_wx_Preset.tWindLayers.length; i++) {
as_wx_Preset.tWindLayers[i].dvSpeed.value = overrideWindSpeedKts;
}
this.as_wx_Listener.updateTempWeatherPreset(as_wx_Preset);
Setting above 150 no longer causes wind speed to become zero, but sadly the limit of 150 knots is still imposed in the ui, preventing realistic scenarios above such speeds.
This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.
If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.
