search

FGMEMBERS / Jumbolino

FG Aircraft | Jumbolino by JWocky
GNU General Public License v2.0
0 stars 1 forks source link

Aircraft Does Not Appear in the FG Launcher (Mac OS) #2

Open ericksonstudio opened 7 years ago

ericksonstudio commented 7 years ago

The aircraft does not appear in the FG launcher, even when filtering by any name variation ("BAe-146", "Jumbolino", "BAe", etc.) or completeness/rating.

Tested configuration:

IAHM-COL commented 7 years ago

yes. the Launcher is the failure The aircraft works well and can be launched with the command line.

On Tue, Dec 6, 2016 at 3:29 PM, erickson studio notifications@github.com wrote:

The aircraft does not appear in the FG launcher, even when filtering by any name variation ("BAe-146", "Jumbolino", "BAe", etc.) or completeness/rating.

Tested configuration:

  • macOS 10.12.1 "Sierra"
  • FlightGear version 2016.3.1

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/FGMEMBERS/Jumbolino/issues/2, or mute the thread https://github.com/notifications/unsubscribe-auth/AJfcGybe8HPeTny_nQb2teyA4AY6eZwHks5rFe_PgaJpZM4LGBAr .

RenanMsV commented 4 years ago

This gotta be something with JPack, perhaps the file encoding. If you remove the include from this line https://github.com/FGMEMBERS/Jumbolino/blob/611c98ddc5a2e71e41363c3f6a263dad39188aba/BAe-146-200-set.xml#L16 it will appear in the launcher.

JWocky commented 4 years ago

Yeah, it also will lose it's AP and some other functions

wlbragg commented 4 years ago

Yes. the Launcher is the failure The aircraft works well and can be launched with the command line.

I have seen this happen before, at lest a few times, it is not the launchers failure. It is most certainly something in Interface.xml that is causing issues. Typically these are hard to find. I usually start by commenting out all code in Interface.xml and slowly adding it back in until I find the problem.