Re: [SPAM] Re: 2024.1.6 rc2

Not necessarily. There is a FG_BUILD_TYPE, which is separate from the CMake
build type that can be set and controls if Sentry starts up in Release or
Debug mode, along with some other things. It is controlled in your build
command with `-DFG_BUILD_TYPE`. If that is not specified, it defaults to
"Dev". the possible options are "Release", "Dev", and "Nightly"

I have just ran 2 tests, one building FG on Windows without specifying
this, and I get the same debug messages as you. I then rebuilt, but
specifying the build type as "Release" and I cannot see the same messages
at all. And the fgfs.log starts with "Build Type Release" rather than
"Build Type Dev"

Hopefully setting this will fix your issue. I will update the wiki later on
with this as it is not present there.

On Sat, 13 Jun 2026 at 19:23, Josh Davidson <[email protected]>
wrote:

> Hi Rhys,
> Thanks for the explanation. Yes I do not know why, as it is built as
> RelWithDebInfo or Release.
>
> Shouldn't it check these build types?
>
> --
> Josh Davidson
> ------------------------------
> *From:* Rhys Ackerman <[email protected]>
> *Sent:* Saturday, 13 June 2026 12:32:11
> *To:* FlightGear developers discussions <
> [email protected]>
> *Subject:* Re: [Flightgear-devel] [SPAM] Re: 2024.1.6 rc2
>
> TLDR: More stuff is logged using a new method. Running the Sentry SDK in
> Debug mode shows this happening live in your console, but because not as
> much was logged before and was done so in a different way, you just never
> saw it.
>
>
> I have checked on Sentry with your UUID that you sent me, and indeed, it
> seems that yours has been running as a Dev build for quite some time.
>
> 2024.1.6 brought some changes to what is logged and how. Unfortunately,
> there was a *slight* oversight which is resulting in everything you see
> in your fgfs.log, plus more, being logged, and you are seeing that happen
> live because Sentry is in Debug mode and therefore repeating what it is
> logging essentially. For a bit of context for those interested, in the last
> 14 days we have received 679 million logs. 75% of these are categorised as
> debug, which for the most part are just noise such as `Took 0ms to update
> layer WXR` or `setting listener #611 in
> C:/Users/*****/FlightGear/Downloads/fgdata_2024_1/Nasal/canvas/tooltip.nas:109`,
> but still count towards our quota. And these numbers have been reached with
> only approximately 50% of users who have Sentry enabled and are using
> 2024.1.6 (or nightlies), which is the first version to use the new logging
> system.
>
> There will have to be some sort of change with 2024.1.7 as we are
> struggling to handle the amount of logging right now, but exactly how much
> we will log or discard is yet to be worked out. There's some very valuable
> stuff coming to us from both a development/debug point of view, and also
> analytical, and once we iron out the teething troubles, I will be looking
> into ways we can present some of this data to users in an easy to read way.
>
> If you enable debug level logging in FG, you will actually see those same
> lines logged in your fgfs.log by FG. But by default they are not shown as
> they are too low of a priority message to show with the default logging
> level of Info.
>
> Hopefully that helps clear it up a little for you
>
>
>
> On Sat, 13 Jun 2026, 15:33 Josh Davidson, <[email protected]>
> wrote:
>
> Why was this never a problem before now though?
>
> It looks like for some reason it was always building as a dev build but I
> never got sentry spamming the log
>
> --
> Josh Davidson
> ------------------------------
>
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>

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