BAe-146 200 Jumbolino

[N3266G]

Great. i'll look to see if i can get his attention on the subject.

[FL2070]

maybe this catches @FL2070 eye? He is kinda our sound engineer

It caught both of my eyes.

Back to work... =3

[N3266G]

maybe this catches @FL2070 eye? He is kinda our sound engineer

It caught both of my eyes.

Back to work... =3

So how soon do you think that you could get those done.

[FL2070]

Well, I'm currently on vacation with a computer that doesn't have FG on it or any of my sounds that I've almost completed. Once I get back, I'll make a few finishing touches and the pack should be released within two weeks. There's also another project that I'm working on, a total sound pack for IL-2 Sturmovik 1946, which has slightly delayed progress in the past and will continue to do so for the next month until that's finished.

Whew, so much to do. Expect the sounds for the Jumbolino in around 10 days, maybe two weeks if I run into XML troubles.

[N3266G]

@FL2070 have a nice vacation, hope to see you back with us soon.

[Octal450]

Well, the aircraft does not showup in my FGrun! Any ideas? I got it from FGMEMBERS

[IAHM-COL]

yes. The launcher is faulty. We know that.
It only loads via command line

Code: Select all

--aircraft=BAe-146-200


[Octal450]

Oh. Well, would you mind telling me how to do that in Windows?

[legoboyvdlp]

Uh, cmd.
Start, Run, CMD.EXE

[IAHM-COL]

well... I don't have windows so I am troubled to guide you well.

But
When you get a terminal open
http://smallbusiness.chron.com/open-ter ... 56627.html

Try typing

Code: Select all

fgfs --aircraft=BAe-146-200

It may or may not work. You may need to also add important flags, such as the location of your FG_ROOT or additional aircraft directories

Code: Select all

fgfs --aircraft=BAe-146-200 --aircraft-dir=<path> --fg-root=<path>

Finally here is the longest list of options I know of
http://wiki.flightgear.org/Command_line ... al_Options