I could reproduce sitting with the MD-81 on the Runway 25L

This will fix a warning that is currently printed when the Docker image is built:

https://docs.docker.com/reference/build-checks/json-args-recommended/

Follow-up for: !61 (comment 3177900263)

Florent Rougon (b05d3344) at 21 Mar 19:55

Florent Rougon (b05d3344) at 21 Mar 19:54

Florent Rougon (4cb20e1e) at 21 Mar 19:54

Florent Rougon (f37fa2eb) at 21 Mar 19:54

Thanks, but AFAICT this would make the uv.lock file outdated. My understanding is that it would need to be updated as well.

Besides, this adds an empty dev-dependencies, however this key is deprecated and will be removed.

Fixes #8 - Updates docutils from 0.21.2 to >=0.22

Yep, agreed.

Latest revision of this comment is from 3/22/26 at 04:30 UTC

running out of bits?? What if the enum representing Debug Classification were instead used as a template parameter to a template singleton class, instanced globally?

The log call could be something like:

inline SG_LOG2<SG_AI>::log ( <log-level>, <text> )  SG_AI being and example of a debug "class".  

The first statement in the log would only need to compare the static log level for the debug class with the log level from the call. If the level in the call is higher than the static value for the given class, output is needed. That test can be done with a single if statement that fully determines whether there will be output or not.

Each Debug Class instance would have its own log level, set during initialization from the default level or from the command line, either individually or for all classes.

If output for a given class is to be suppressed, just set the class static log level to a large number.

One could even change the defaults at compile time via CMAKE variables in the user's development environment, but use the standard default during CI.

Would a change like this work for what Keith suggested in the original description of the issue?

and supposed went next not release 2024.1

if i done merge wrong my apologies new at gitlab system used to github and file is updated ambient file that goes in lighting folder

i updated radiance curve in the file to be smoother

i just those files should got uploaded to the fgdata repo i apologize i just recently just started using gitlab im use to github

the ambient and specular files came from lightning folder radiance curve were sharp so smooth them out and i forgot rename them when i uploaded them back to original which i can do so you have code compare

#3207 was my old request.

If there's more to discuss beyond the scope of this merge request about future development in the area of logging, where should that discussion happen? An epic, an issue, or a new or existing thread on flightgear-devel?

Unless there's work already planned or underway. I'd vote for a thread on flightgear devel or a new epic, to hash out an agreed direction and strategy then move to specifics in one or more issues. Once things are settled.

-Pat

No, this is just an area in which I am rather ignorant.

Uh, yes? (Maybe I miss the meaning...)

So, this is “cross-architecture virtualization”, if I dare say so?