USA TOUR Event | SAT FEB 21ST 17:00 - 24:00 UTC

[IAHM-COL]

http://www.thejabberwocky.net/downloads/

It does not exist yet

[MountainFlyerN22]

OK.

[LesterBoffo]

@ALL

By that I mean, it is not that amiable to just instruct Lesbof to do this or that as an Instruction or a command.

With this rejoinder... It is also wise to recall what one has said to me over Mumble in the past. As I have a long memory for jackasses.

[CA1012_Falcon5]

@ALL

By that I mean, it is not that amiable to just instruct Lesbof to do this or that as an Instruction or a command.

With this rejoinder... It is also wise to recall what one has said to me over Mumble in the past. As I have a long memory for jackasses.

Lester I did not mean to be pushy, and please do not hold a grudge about what happened on mumble, i was dumb and arrogant, and i aslo frogot what i said to you that made you mad at me. Forgive and forget. Am I right everyone?

[islandmonkey]

In fact, I'm switching planes over to the Avro Vulcan.

[KB7]

OK.

Shouldn't be much longer before I package it up for Jwocky to put out - end of the weekend at the outside I'll be ready and then it'll take time for him to post it. Thanks to Jwocky, Falcon, and cain I managed to get the particle suppression suppressed - ended up using condition for Groundspeed less than 5 kts. That way when I'm parked the rear half of the airplane isn't swathed in a not-too-realistic cloud of smoke. (Well, the smoke cloud might be real for a jet this old, but oh well.)

I am also learning the lesson that when one actually starts improving a design one's wishlist expands rapidly. I discover new things daily I'd like to do with this, but having to stop in time for the tour.

[IAHM-COL]

How do you download from SVN?

Hi N22
Now the Confirmed Aircraft list in linked to a Git mirror for FG Aircrafts I've created [*]: https://github.com/FGMEMBERS
For those willing to fetch via git, or use the "DOWNLOAD ZIP" button lower right.
Best
IHCOL

[*] PS: I ve created a git for every aircraft currently in FGDATA git repository, given noticing that these will be eliminated, and in a near future will be accessible thru SVN instead. I am trying to Lobby for a better alternative, and we will see where we are heading.

[MountainFlyerN22]

Thanks.
I wish you the best of luck with that lobbying.

[LesterBoffo]

Not to choke up this thread with off-topic chatter but, is there a discussion thread for the Git/SVN portal that IAHM-COL started?

Since I'm a bit of a neophyte concerning updates vis-a-vis GIT and SVN, can this new portal be used to 'push' (I think that's the correct term?..) changes in aircraft you have in the download repository?

[IAHM-COL]

Hi Lester
The question is really good indeed

Yes, that is one of the ideas of the GIT repos I am starting.

It will be feasible for any developer to go ahead and 'push' changes to any particular aircraft. In other words, any aircraft becomes an independent development progress. There are several avenues to do this that I am going to overlay below. But first let me tell you a history of two tales:


Tell #1: SVN. Forget about it. To push into SVN you need to be given Access to the WHOLE AIRCRAFTs SVN the dev cores created. Not very smart thing to do is to give anyone access to such SVN, so that method really maintains the mainstream development under a protection (a siege, I call) and its only modifiable by the "ELITE" ones.

Tell #2. GIT, the one IHCOL is trying to lobby for, and create the per-aircraft system. Here the idea is that you can get (called clone in git world) any aircraft individually. Then modify it for development purposes. (in principle, simply make that aircraft better). The "github" method is that you create what's call "a fork". Meaning your own personal Idaho for that plane. Do anythign you wish. And when you are happy, you push to your own fork. Since it is YOURS no-one needs to filter what you do. Since it yours, you will not compromise "mainstream". Then when you feel like your fork should become available community wide, you create what is call as a pull request. That is you are suggesting that the "mainstream" plane should take your improvements, that is pull from you. One this is done, effectively the mainstream plane takes your changes (ie improvements!).

The mainstream planes belong to the members of the FGMEMBERS group. Which are the ones that can accept your pull request. In principal, I could even gain you access to the "FGMEMBERS" allowing you to be able to accept your pull yourself.

So in general, having gitted individual planes has among other advantages, democratize the development of the planes to all our community, as opposed to a very centralized method that is being currently implemented (aka SVN)

[IAHM-COL]

is there a discussion thread for the Git/SVN portal that IAHM-COL started?

Not so much of a thread, but you can take a look at my lobbying efforts here:
viewtopic.php?f=28&t=25314

[CA1012_Falcon5]

Just out of curiosity, dose anyone have a download link for the Vickers VC10?

[Jabberwocky]

Okay, I'm building the plane list for my website now and ran into problems

1.) F-36 and G-MNKY want to fly Concorde ... is that the one from the FlightGear main site? I can't link if I don't know.

2.) Falcon ... Nene or what? And I need still a file for your modifed Nene if you fly her to put it up as download unless you want to use the dropbox with a cryptic number

3.) IAHM-COL: Do we create a zip for convenience download or shall I link to your Git?

4.) Islandmonkey, that is the Vulcan from FGUK? Did you check the range?

5.) Lester: I read Comets, 1946 design and SeaHawk ... I have no idea what's going on

6.) KB7 when you are done, send me a zip and I make it downloadable

7.) N-22 if this is the BAe from KB7 ... I have no file yet, but will put up a download as soon as I have

8.) SkyBoat ... I try my best to get this Garmin up and running as well

So if yomeone could tell me what's up?

[IAHM-COL]

• E.F.A Typhoon - USA TOUR Ready (IH-COL): GIT | ZIP Snapshot | Jabberwocky's Link | WIKI
  
• BAC-Concorde (F-36, G-MNKY): Download | WIKI | GIT
  
• Vickers Nene Viking (N-22): Dropbox Download
  
• BAE-125 (KB7): Download | GIT | [url]Jabberwocky Link for customized version[/url]
  
• Jwocky customized DH106 DeHavilland Comet 4 (JWOCKY): Download | This link is required due to changes in path names with original DH-106
  
• Hawker Sea Hawk (Lesbof): Download | GIT | WIKI
  
• Undecided Aircraft; (Skyboat, Falcon)
  
  

This is ok except G-MKNY changed. I have the same question you do with him.
I believe. Lesbof is going seahawk. thats last I've heard.

For the EF-Typhoon, just link to the download button in the git

[Jabberwocky]

Okay, will do, that gives us till end of Monday already a better list. F-36 just told me, his Concorde is the one from the main site, so that is cleared as well.
And on an unrelated subject, I was asked how to do all this git stuff and had no idea. so we need to bring some people together in order for you to give them some info.