Re: Input Devices window crashing on the 'next' branch?

If you're trying to work on terrain rendering, next is the place to be. Stable can run WS3 (I haven't tried it, so don't take my word for it), but next is the future, and from the sound of it, what you're doing will intersect with a lot more than just the terrain rendering. As far as next stability goes, it's made leaps and bounds in recent times, but is still not stable as far as the word goes. If you don't have much use of the dialogs, or know how to bypass them, you can integrate your work with next fairly easily. There will be a few simulator conveniences that will not be available to you, but those may or may not be minor depending on what exactly you're doing. As far as the HDR renderer goes, however, and as far as I know, that should be mostly stable enough that you can work with it without running into too many oddities or pitfalls.

TLDR: next should be fine. Might be slightly more difficult right now, but it's easier than porting from stable when everything's said and done.
________________________________
From: Gerard Krol <[email protected]>
Sent: Wednesday, June 3, 2026 12:44 PM
To: [email protected] <[email protected]>
Subject: Re: [Flightgear-devel] Input Devices window crashing on the 'next' branch?


Thanks for the info.

Looking through the work items, there seems to be quite a bit of ongoing work around the rendering changes.

I'm curious about the overall state of the 'next' branch. How stable would you consider it at the moment? Should I pause working on the experimental streaming (DSM) terrain for now? I'm at the point where I'd want to continue the experiment with integrating it a bit more (some UI, combine with the existing terrain rendering engines). Doing this work on stable would probably make it very difficult to merge it into 'next' later.

Regards,

Gerard

On 03-06-2026 21:03, Alex Barrett wrote:
https://gitlab.com/flightgear/flightgear/-/work_items/3459#note_3398123191

On Wed, 3 Jun 2026 at 19:32, James Hogan via Flightgear-devel <[email protected]<mailto:[email protected]>> wrote:


On 3 June 2026 19:11:15 BST, Israel Emmanuel <[email protected]<mailto:[email protected]>> wrote:
>Because of rendering changes on next, several of the dialog boxes are very, very broken. I haven't seen this issue with the Input Devices menu (at least not on the screen, might be in the console logs), but that dialog has not worked for me lately either. If you'd like to take a crack at making it work in next (people have been doing this for other dialogs as well), I'm sure that would be appreciated, otherwise there isn't much you can do.

Its probably worth reporting any such broken cases as work items on gitlab so they can be tracked. I had noticed this one too, but hadn't got around to doing so.

Cheers
JamesH


_______________________________________________
Flightgear-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/flightgear-devel




_______________________________________________
Flightgear-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel