Re: [Flightgear-devel] Issues with current next

[Wayne B. <kil...@co...>]

> For Wayne: linking to a forum post about a range of issues is pretty hard to follow, it would be better to send people here to describe their issues in detail (as separate threads)

I was going to suggest to the forum participants to either file a bug report or bring it here if they couldn’t resolve their issues. Once I realized I had a related issue I decided to bring it here. I was really only concerned with my issues of a recent build. The other information on that post only convinced me it was not exclusive to me. Referring to a forum post with available information and a link to a visual aid was my intention, not to flood developers with a cacophony of issues.

Both of my issues were adequately resolved, I verified it was David’s scenery. I do think the terrasync warning may be responsible for the subsequent white message box which might be something someone needs to know about or look into. I checked the logs and the only outstanding information in the log was about the thresholds.

Thanks for the help.

Wayne

From: James Turner
Sent: Tuesday, June 20, 2023 5:24 AM
To: FG Developers List
Subject: Re: [Flightgear-devel] Issues with current next

Hi, trying to follow up on this:

For Wayne: linking to a forum post about a range of issues is pretty hard to follow, it would be better to send people here to describe their issues in detail (as separate threads)


On 19 Jun 2023, at 22:42, Scott Giese <sc...@gm...> wrote:

Known issue: David's US/Canada scenery is throwing errors due to helipad/thresholds.  This is being reported in the TerraSync dialog (which is misleading).  Try disabling this scenery and see if the error dialog goes away.
I’ve already pushed a fix for that, it was reported on the bug tracker by Huntley. We now skip over invalid threshold data. (And the current code does not support threshold.xml for Helipads, would need to be added)
White box for the Error Detail Dialog... I've not seen that occur.  Wild guess is that it may be associated with the PUI updates???  The log file/terminal window could be a workaround to see the error message.  If you are able to capture the error, please share the details.
I don’t think it would relate to the error details, indeed : there is the error notification *popup* which is current disabled (as far as I know) : it uses Canvas so could appear as a white box in the top-right if fails to load, but the error *details* is just a regular PUI dialog like any other, so not sure how that could appear as white.

A bug ticket for this one would be my preferred way of understanding what’s going on, captyuring some screenshots, steps to reproduce, etc.

Kind regards,
James