I think "Flying toaster" was working on an F-14 for FG, I saw a topic on that a while ago, but it's not here anymore. Anyway, I was wondering how that was going. It would be really cool to have an F-14 for Flightgear!

Yes I am still working on it I have just added a refuelling probe and boarding ladder.http://sfp1.site.voila.fr/images/refuelprobe.png Can any tomcat lover tell me if I got the probe off its normal position or not of the good size ? Thanks for the input ;)

it looks stunning but the probe should be just a tad more to the left

Very nice model! That looks amazing. If you're still wondering about the probe, http://www.anft.net/f-14/f14-detail-refprob.htm has a couple diagrams and pictures regarding the probe.

Alas this model is not likely to be released due to licencing issues (check FG developers mailing list for the whole story).

>Alas this model is not likely to be released due to licencing>issues (check FG developers mailing list for the whole>story).whatever licensing issues there may be: you only have to release your work under a GPL compatible license IF you intend it to become a part of the official (base package) distribution, while this is indeed highly desirable for the majority of contributions, there's really no reason why you shouldn't be able to come up with a custom license and provide access to it separately - after all, it's your own work.In fact, there have previously been several such cases, you may want to check out the MB-339 PAN project (http://hcilab.uniud.it/pan/) for another example of a FlightGear aircraft that cannot become a part of the FlightGear base package due to licensing issues, nevertheless there are many people who like to use it anyway-for users this only means to download and extract the archive separately, instead of getting it by default with FlightGear.

Another way around the "GPL or nothing issue" would be to set up an Aircraft repository in the flightgear section of AVSIM file library or to create a portal for "free-license" add-on material on flightgear. As a host of licenses exist that may fit the need for a specific author who wants to release his (her) creations for free (no charge) or even for possible hacking around, but not according to the terms of flightgear base package (GPL). Don't get me wrong, GPL is a good license but sometimes authors may want to set restrictions (non-profit only for instance) and then GPL is ... restrictive

>Another way around the "GPL or nothing issue" would be to>set up an Aircraft repository in the flightgear section of>AVSIM file library or to create a portal for "free-license">add-on material on flightgear.yes, as far as I remember, something like this has in fact been previously suggested, several times actually. A specific pathway for non-GPL'ed contributions.However, I think the last time this suggestion failed because it would have involved setting up a corresponding database for the flightgear.org server, which -for whatever reasons- wasn't a viable option back then(?), even though someone actually suggested to take care of the frontend programming and maintenance.Originally, there were even some regular FlightGear contributors who intended to set up a separate repository site for FlightGear related resources (aircraft, scenery, 3D models etc) over at sourceforge, mainly in order to reduce bandwidth consumption for the main flightgear server.I am however not sure why this (given that a sourceforge project is easily created and set up) or even just the idea to set up a corresponding category here at avsim was never pursued.>As a host of licenses exist that may fit the need for a>specific author who wants to release his (her) creations for>free (no charge) or even for possible hacking around, but not>according to the terms of flightgear base package (GPL).Yes, a central repository for such work would probably still be a good idea. On the other hand, it's of course in the best interest of the project as a whole to encourage preferably GPL'ed contributions.>Don't get me wrong, GPL is a good license but sometimes>authors may want to set restrictions (non-profit only for>instance) and then GPL is ... restrictiveYes, I see.On the other hand, you could argue that whatever GPL project you may be using, grants you also all of such rights-and thus any of your contributions to such a project, should preferably also provide the same freedoms to other users in order to ensure the progress of the project.I mean, let's face it: the absolute majority of rights you would possibly want to reserve for yourself is unlikely to become a factor for FlightGear (its users) anytime soon: FlightGear in general simply isn't really that popular that any contributor would really have to fear contributions being exploited in any serious way, after all any released/distributed derivative products of your work would have to be accompanied with the corresponding sources, thus benefitting the overall project as a whole.

Hello together,I'm no regular on this forum but I stumbled across this thread. Now I'd offer you a comment in order to prevent false allegations.>yes, as far as I remember, something like this has in fact>been previously suggested, several times actually. A specific>pathway for non-GPL'ed contributions.>>However, I think the last time this suggestion failed because>it would have involved setting up a corresponding database for>the flightgear.org server, which -for whatever reasons- wasn't>a viable option back then [...]There's been a discussion on the FlightGear-devel mailing list some time back - I guess you might be referring to this. Someone proposed the idea of having such an aircraft collection an I actually offered my support for creating and maintaining the respective database.In the end nobody stepped onto the plate and actually _did_ something in this direction. While I'd be happy to _support_ such an idea, I'm not the guy who feels responsible for implementing other people's wishes. If someone _does_ start such a project, I'll be there for supporting it with the required infrastructure but don't expect me to do all the work.>Originally, there were even some regular FlightGear>contributors who intended to set up a separate repository site>for FlightGear related resources (aircraft, scenery, 3D models>etc) over at sourceforge, mainly in order to reduce bandwidth>consumption for the main flightgear server.Such databases already exist, one for 3D-models, one for Scenery Landcover data - the latter now in cooperation with the OSGeo project (and it took me innumerable hours to get that far).Bandwidth or computing ressources are not an issue, the issue is that someone actually has to do the related work, designing the internal layout of a database-driven website, considering security-related issues and actually _code_ a working frontend.Cheers, Martin.

>Hello together,>I'm no regular on this forum but I stumbled across this>thread. Now I'd offer you a comment in order to prevent false>allegations.I'm sure that if you do re-read the thread, you may find that there were actually no "false allegations" at all:>There's been a discussion on the FlightGear-devel mailing list>some time back - I guess you might be referring to this.As you didn't post any pointers to the thread that you are now referring to, I will probably have to resort to guessing, too?Well, I don't think, that's going to be very helpful or constructive ultimately:>While I'd be happy to _support_>such an idea, I'm not the guy who feels responsible for>implementing other people's wishes. If someone _does_ start>such a projectI'm really not sure why you are obviously feeling the need to be that defensive, I don't think anybody in this thread made any allegations whatsoever, neither did anybody specifically mention any people for not following up on offers such as the one you mentioned above. So, if you actually felt attacked by anything in my previous posting, I truly apologize, while admitting that I clearly wouldn't understand why you should feel that way!?>Bandwidth or computing ressources are not an issue, the issue>is that someone actually has to do the related work, designing>the internal layout of a database-driven website, considering>security-related issues and actually _code_ a working>frontend.While I do really appreciate your input, I am coming to the conclusion that the two of us must be referring to different discussions and that your input may thus be based on false assumptions: I was specifically referring to the -repeated- suggestion to set up a corresponding database-driven repository over at flightgear.org, which back then was rejected due to the mySQL requirement for flightgear.org. In fact, if I remember correctly several offers to set up mySQL based contributions over at flightgear.org were REPEATEDLY rejected for the very same reason.I hope this clarifies the situation.

Hello!I am working on a FlightGear model which will feature folding wings similiar to how the F-14 wings sweep back. I am wondering, does your flightGear model have this feature (can you control the sweep of the wings) and if so, do you also have ailerons on those wings that rotate off from the sweeping wings?Because this is a problem in that PLIB doesn't appear to support hierarchy of any kind to make the wing/aileron juncture correct and parented, so how did you achieve this on your working model in FLightGear? I have to create a variable wing UAV for a project, and I am wondering how to make the wings foldable with the ailerons and all attached to them and rotateable.Your model looks like the real thing! Very awesome. If you can be of any help in the FlightGear importing process I would very much appreciate it!- Mark

>Because this is a problem in that PLIB doesn't appear to>support hierarchy of any kind to make the wing/aileron>juncture correct and parented, so how did you achieve this on>your working model in FLightGear? I have to create a variable>wing UAV for a project, and I am wondering how to make the>wings foldable with the ailerons and all attached to them and>rotateable.You can encapsulate one animation (or multiple ones) inside another. For example:child ... ...parent child ... ...The animations for the landing gears of the A300 make extensive use of this method. You should download it and use it as a guide.