Re: [Flightgear-devel] FGElev and macOS

[TheFGFSEagle <the...@gm...>]

I'm using

fgelev --expire 1 --fg-scenery="/home/user/.fgfs/TerraSync"
--fg-data="/home/user/fgdata-git"
in my FGTools scripts successfully (Ubuntu 22.04)

Am Do., 22. Juni 2023 um 14:50 Uhr schrieb Rhys Ackerman <
rhy...@gm...>:

> I haven't got a linux instance available to test, however from past
> experience it did "just work" and that is the jist I am getting from having
> spoken with a few people.
>
> On Windows, I run the following which starts fgelev allowing me to pass
> data to it. (In the FG bin dir, equivalent of MacOS dir on mac) `fgelev
> --print-solidness --expire 1000000 --fg-scenery
> "C:\Users\User\FlightGear\Downloads\TerraSync"`. After running this, fgelev
> waits for further instruction.
>
> On mac, I can run the same command adapted to au different fgscenery path,
> however fgelev exits due to not finding the .spt file, resulting in the "no
> data loaded" message (That file is not visibly present on Windows either,
> but it passes the check for that file). I have verified with my Windows
> instance that all the environment variables on there are present here,
> which they are, so I do not think it is a problem around an undefined env
> var that has no error handling.
>
> On Thu, 22 Jun 2023 at 08:54, James Turner <ja...@fl...> wrote:
>
>>
>>
>> On 21 Jun 2023, at 22:00, Rhys Ackerman <rhy...@gm...> wrote:
>>
>>
>> I have attempted to use fgelev today but had no success. Running the
>> executable gives the following output:
>>
>> ```Now checking for plug-in osgPlugins/osgdb_nvtt.dylib
>> Error reading file w180s90-360x180.spt: file not found
>> 1.30 [ALRT]:general    ./fgelev: No data loaded```
>>
>> This happens however it is run, clicking the executable, running it with
>> command line flags and data, or from calling via a python script. The issue
>> is not present on Windows, and presumably not Linux either.
>>
>> Is this user error which I tried to rule out, or is there perhaps an
>> issue of sorts with FGElev on macOS which hasn;t been picked up on before.
>> I have tested this on 2 separate macOS systems both producing the same
>> result.
>>
>>
>> I’ve never run it ‘properly’ on macOS, this does look like a path /
>> file-naming issue. Can you post the full command line you’re trying? And
>> maybe the command line that works on Linux to compare?
>>
>> Kind regards,
>> James
>> _______________________________________________
>> Flightgear-devel mailing list
>> Fli...@li...
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>