Re: [Flightgear-devel] Fair practice autorisations
Hi, In my precedent mail I have forgot to say that Ernest Teutcher, Alexis Laille, Christian Thiriot and Clément de l'Hamaide (it's me) are the members of the PAF team. We can consider the current DC-3 is here because the PAF team had created 80% of the DC-3. And E.Baranger had created 20% of DC-3. In this way we can say : there are not one author but there are many authors. Since there are many authors it's a fair practice to ask to other authors an autorisation. Honestly, E.Baranger is just the author of some parts 3D models and some parts of XML file but his works represente only 20% of the DC-3 and we can consider that E.Baranger is a small contributor of the DC-3, and he isn't the main author, he is author of some parts that's all. For history, E.Baranger was a member of PAF team but he have been banned because he insulted some member of the PAF team and he refused to send our JSBSim FDM on GIT. Finally he was the only contributor of PAF team having commit rights and he makes an abu of his rights. In this way he censured our work by refusing to accept our JSBSim FDM. Now I focused an other faults of E.Baranger : he censures the work from other authors. Censure is it a good quality to become a committer ? It's surprising ! Thanks you for your attention. I know the current time all developper works on the next release. Maybe it's not the best moment to speak about this. If you prefer to continue this discussion after the release I can absolutely understand this. @Syd : thanks you for you intervention I understand your message. Since my work is under GPL I'm not complaining. Just I would like to focus on the fair practice which need to apply from committers before commit the work of other authors. (Mostly if the committer isn't in good way with these other authors) Cheers, Clément -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fair practice autorisations
On Sun, 2012-02-12 at 10:45 +0100, Clement de l'Hamaide wrote: Hi, In my precedent mail I have forgot to say that Ernest Teutcher, Alexis Laille, Christian Thiriot and Clément de l'Hamaide (it's me) are the members of the PAF team. We can consider the current DC-3 is here because the PAF team had created 80% of the DC-3. And E.Baranger had created 20% of DC-3. In this way we can say : there are not one author but there are many authors. Since there are many authors it's a fair practice to ask to other authors an autorisation. Honestly, E.Baranger is just the author of some parts 3D models and some parts of XML file but his works represente only 20% of the DC-3 and we can consider that E.Baranger is a small contributor of the DC-3, and he isn't the main author, he is author of some parts that's all. Actually Emanuel is the main author and you've just updated his work. I have to step up here since there is just too much misunderstanding going on. You guys took a GPL'd model and modified it. Since it started out as a GPL model it will always be a GPL model no matter how much you change. Even if nothing of the original model is left, you agreed to be bound by the GPL the moment you started working on it. So Emanuel has every right to dismiss any modifications on *his* model and to update git accordingly. That said, it's sad to see the situation end up like this. I always found it quite pleasing to work with others that updated my model byt frankly I would get mad when at one point they would claim ownership like you do. That's uncalled for. It's a joint effort and every member should bet credits (even if his/her work is not included anymore). Now sit back, take a few deep breaths and accept the facts. -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fair practice autorisations
Am 12.02.12 11:00, schrieb Erik Hofman: On Sun, 2012-02-12 at 10:45 +0100, Clement de l'Hamaide wrote: Hi, In my precedent mail I have forgot to say that Ernest Teutcher, Alexis Laille, Christian Thiriot and Clément de l'Hamaide (it's me) are the members of the PAF team. We can consider the current DC-3 is here because the PAF team had created 80% of the DC-3. And E.Baranger had created 20% of DC-3. In this way we can say : there are not one author but there are many authors. Since there are many authors it's a fair practice to ask to other authors an autorisation. Honestly, E.Baranger is just the author of some parts 3D models and some parts of XML file but his works represente only 20% of the DC-3 and we can consider that E.Baranger is a small contributor of the DC-3, and he isn't the main author, he is author of some parts that's all. Actually Emanuel is the main author and you've just updated his work. I have to step up here since there is just too much misunderstanding going on. You guys took a GPL'd model and modified it. Since it started out as a GPL model it will always be a GPL model no matter how much you change. Even if nothing of the original model is left, you agreed to be bound by the GPL the moment you started working on it. So Emanuel has every right to dismiss any modifications on *his* model and to update git accordingly. That said, it's sad to see the situation end up like this. I always found it quite pleasing to work with others that updated my model byt frankly I would get mad when at one point they would claim ownership like you do. That's uncalled for. It's a joint effort and every member should bet credits (even if his/her work is not included anymore). Now sit back, take a few deep breaths and accept the facts. Oh sorry, the idea of hangars in fgdata/aircrafts came back here, but just for some seconds. Forgive me for this comment. Cheers, Yves -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Shader debugging
I've spent four hours yesterday to trace down the cause for fog inconsistencies which I observed in custom terrain. One of them was the fact that the top fog level was sometimes displaced by some offset from terrain chunk to terrain chunk in the new CORINE Italy scenery and the other is the fog pattern over the ocean. The first issue goes like this: I've been operating under the impression that for the purpose of rendering scenery, vec4 ep = gl_ModelViewMatrixInverse * vec4(0.0,0.0,0.0,1.0); alt = ep.z; gives the correct altitude of the eye above MSL and terrain_alt = gl_Vertex.z; gives the altitude of the vertex and that comparing these altitudes against external uniforms (like the ground haze level or the snow level) gives correct results (the last assumption is coded in landmass.vert/frag for snow) - which usually does a good enough job. It turns out however this isn't correct in general - in the custom scenery, the altitudes computed that way were not above MSL but displaced scenery chunk by scenery chunk with a constant offset, so the same alt=500 condition in the shader meant 700 m MSL for one chunk of scenery but 850 m for an adjacent chunk, resulting in a discontinuity in fog (and snow) rendering across terrain seams. I don't know if this is a flaw in the custom scenery building process (I haven't seen the problem in default scenery yet) or not, in any case the terrain itself renders correctly, so the offset is known to ftransform(); but for the purpose of shader coding, it means we cannot assume to have know the proper MSL altitude scale inside the shader. The correct solution is to pass eye altitude (eye_alt) as a uniform, then the offset is given by offset = (ep.z - eye_alt); and the the true MSL altitude of the vertex is true_alt = gl_Vertex.z + offset; and this indeed deals with the discontinuities just fine. For testing purposes, I've implemented the eye altitude property to be passed as uniform from Nasal, but it should be done properly, hence: Do we have the eye altitude in meters in the tree in a property that is readable (= is continuously updated) by the shader, or alternatively, can we get it, i.e. the equivalent of var viewpos = geo.viewer_position(); var alt =viewpos.alt(); I believe all snow renderers should take that into account as well. The second problem is the 'checkerboard' appearance of fog rendering over ocean. To the limit of my ability to test, the cause is incorrect interpolation of distances and angles due to very large vertex spacing (I've asked the shader to plot step functions in angle and distance to see how the interpolation goes, and it had the expected outcome). Basically, when you approach a huge square directly from the side so that the closest distance is 1 unit and you see the two corners under 45 deg, then the distance to the corners is actually 1.414 units, and naturally the interpolator thinks that the distance is 1.414 units everywhere on the line even when actually it gets much closer - this is why fog seems to 'cling' to the middle of the line, because there the distance is overestimated. The default shader doesn't fog with true distance but with z-distance in eye space, which in the above situation pretends that the distance to the vertices is just 1 unit as well, which makes for homogeneous fogging along the line. But this leads to massive artefacts for larger FOV - at 90 deg FOV, the error in fogging at the edge of the screen already is 50%, at 120 deg the edges are done completely wrong. Moreover, the scheme doesn't work together with the two component calculations required by the terrain haze shader. To me, the only viable solution appears to be more vertices for ocean tiles, I don't think there are computational tricks which wouldn't be at least as bad under certain conditions - comparing with vertex density of normal terrain, even a factor 100 should be doable without problems. I vaguely remember that Vivian and Emilian had tried this and were negative, but I haven't really seen the outcome. I believe the results over terrain show conclusively that at some vertex density the problem goes away, and given that I can understand and explain all aspects of the problem I see, I think my analysis is correct. Cheers, * Thorsten -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fair practice autorisations
Le 12/02/2012 11:00, Erik Hofman a écrit : That said, it's sad to see the situation end up like this. I always found it quite pleasing to work with others that updated my model byt frankly I would get mad when at one point they would claim ownership like you do. I second Erik on that one. I also find this story very sad as people, at least some, forget the main purpose of contributing in a project like FG, that is doing something great, working together, and finally offering this work to the community. Now we see people, counting little parts of a team work, adding one percent ownership on a side, another one percent on the other side, showing weird feelings competing on pieces of fame. After all, this DC3, as nice it can be, is only a collection of well arranged but short-living bits. There is no point showing anger or any conflict for such a tiny matter. That's just a loss of time. At least if some ownership details ought to be corrected, this could be done without involving the whole devel list. Alexis aka xiii -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Final 2.6.0 Release Preparations
On Sat, Feb 11, 2012 at 10:16 AM, ThorstenB wrote: Every free, open source project is really driven by active community _participation_, not so much by (passive) user's _requests_. In general, it's not even a matter of economic incentives, though this may be the case with FG. But you can see it with Linux kernel development: loads of companies and individuals involved, all pushing the project forward - each with their own private fun or economic interests. What really matters to an OS project is the community effort and the option for everyone to get involved. Even if this results in the mentioned group hug :) - I think that'd be the really important point to stress, when hinting a comparison with MS Plight (oops, typo ;-) ). I've changed the text to the following: Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute. Full text below. -Stuart The FlightGear development team is happy to announce the v2.6.0 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Major improvements from v2.4.0 include reduced AI aircraft load times, easier graphics tuning, more sophisticated AI aircraft and improved usability. Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in Universities and for interactive exhibits in museums. FlightGear features more than 400 aircraft, a worldwide scenery database, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute. Download FlightGear V2.6.0 for free from http://www.flightgear.org. FlightGear - Fly Free! -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fair practice autorisations
Hi all, You are right, we are here to improve FG. In our next release we will include a file with the list off all our last improvment. After this release I stop to improve the DC-3 C47 To close this discussion : DC-3 C47 released by helijah : http://www.youtube.com/watch?v=cNp6ub7hQak DC-3 C47 released by PAF team : http://www.youtube.com/watch?v=0RKb1pXDXPs Thanks you very much at all for your attention and your point of view Cheers, Clément -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fair practice autorisations
Clement de l'Hamaide wrote: To close this discussion : DC-3 C47 released by helijah : DC-3 C47 released by PAF team : No, I'm certainly _not_ going to look at the videos, because I consider this sort of competition in an OpenSource project as plain stupid. Why didn't the various authors of the DC-3 simply collaborate on one single aircraft in our common GIT repo ? No, this smells like people are trying to defend their inability of participating in collaborative development - really sad. Cheers, Martin. P.S.: You'll find out it's a common symptom in Scenery development as well - but this doesn't make it any better. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sanitizing materials.xml
On Friday 10 February 2012 23:05:45 Stuart Buchanan wrote: Hi All, - The forest effect doesn't currently use the default fog effect (include_fog.[vert|frag] etc.).. For consistency with the rest of the terrain, and the tree effect, I think it should. Is there any particular reason why it doesn't? -Stuart -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Hi, just an oversight on my part. I'll fix it ASAP. Emilian, -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] The Douglas Dc 3 in GIT
Hi Martin, Gijs, Syd, Curt, and all other, When the team of the PAF has decided to prohibit access to their work to me, they also requested the opportunity to put it on ILM. When I finally got access to their improvements, through a person who has nothing to do with them but that dispatched the wiki link that I did not know, so I logically integrated all their work to my airplane. Thus it has always worked. I always took the time to report the authors of the additions in my site because it seems normal for me. If the team of the PAF not appreciate the principle of respect of the original authors of the open source, they go to make aircraft for FS X or X Plane. In addition, it can make money I'm tired of seeing all these kids puerile want to use the work of others, to obtain recognition as authors. And back on the 5 or 6 files with licensing issues in my airplanes is ridiculous. As usual, Clement did not consider before speaking. Because most have been fixed. Since I started I've always done anything that try to bring something to FG and to please the greatest number. I'm not trying to please me personally. But this, it seems that the PAF can not understand. It's a shame. The team is talented, but seems guided by a kid with goals unrelated to FG and Open Source. I remain attentive to all and to serve the greatest number. Regards Emmanuel -- BARANGER Emmanuel http://helijah.free.fr -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Release 2.6.0: Chimney smoke / windturbine wrong wind direction
Hello, just found a severe bug in fgdata (testet with 2.6.0_rc2-4.1 and fgdata_next). Unbelievable . the smoke of the chimneys face INTO the wind! Same with the windturbines. They show out of the wind. Windsocks are ok. And I wonder that I'm so fast in the final approach :-) Best regards D-NXKT -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The Douglas Dc 3 in GIT
When the team of the PAF has decided to prohibit access to their work to me, they also requested the opportunity to put it on ILM. They only banned you from the PAF-Forum. Simply because you offended some users there just for having a different opinion than you. That can be read by everyone in the forum, without beeing registered. And everyone can download their work, without beeing registered. I have seen that you nearly always act like that, even on the official forum and here on the mailing-list. Lacking social skills I would say. When I finally got access to their improvements, through a person who has nothing to do with them but that dispatched the wiki link that I did not know, so I logically integrated all their work to my airplane. Thus it has always worked. To YOUR aircraft? THEIR work? You started the work on the aircraft, but it was the team who finally finished it. So to make it clear: it's not alone your work, and not alone their work. It is a work of ALL INVOLVED! And they published the link in the official forum- you can't have missed that. I always took the time to report the authors of the additions in my site because it seems normal for me. If the team of the PAF not appreciate the principle of respect of the original authors of the open source, they go to make aircraft for FS X or X Plane. In addition, it can make money Muaahahaha - ROFL! 1.) Who is the original author? You? Again: You just started a work; the real work- making it flyable and usuable- was done by this group. Without them it would have been another crappy aircraft made by you as the other more than hundred (!) ones by you. They are the original authors as well, like beside you! I would even say, that have made the main work! So there are multiple original authors- that's something you have to learn. And you have to respect them as well. You didn't learn from the AlouetteII-conflict last year, right? 2.) YOU want tell us about the principle respect of original authors? I can still find the already mentioned copyright violations in your aircraft! But see below. I'm tired of seeing all these kids puerile want to use the work of others, to obtain recognition as authors. I have searched through the forums and mailing-list, and it still seems to me that you did not really understand OpenSource. And back on the 5 or 6 files with licensing issues in my airplanes is ridiculous. As usual, Clement did not consider before speaking. Because most have been fixed. 5 or 6? I can remember more - still too much. And much too much for someone who accuses others here for disrespecting OpenSource. Since I started I've always done anything that try to bring something to FG and to please the greatest number. I'm not trying to please me personally. But this, it seems that the PAF can not understand. Sorry, I have to doubt your words, I'm not trying to please me personally. is looking too suspicious to me! And they do the same what you want to make us believe you do: trying to bring something to FG; and please to greatest number. And it seems to me that they do with great success- as many more users are tired of the many half finished, unusuable aircraft made by you. It's a shame. The team is talented, but seems guided by a kid with goals unrelated to FG and Open Source. I don't see that, can you prove it? I wonder how many discussions like that will follow- there seems to be a coherence between your acting and understanding of teamwork and OpenSource and such discussions- OSG-Particles, Bell UH1, AlouetteII, Velocity-XL, and now the DC-3 Why I don't see such discussions on Gijs, Martins, Syds and others work? Why? Pierre Mueller Switzerland-- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The Douglas Dc 3 in GIT
All, I'm sure that there's right and wrong on both sides of this discussion, and I'm aware that some have some difficulty with the English language but could we please continue it in a more decorous manner, and take the personal abuse elsewhere. The Devel list has a long tradition of avoiding personalizing discussion, and I for one wiish it to remain so. Vivian -Original Message- From: Pierre Mueller [mailto:pierre.muel...@ymail.com] Sent: 12 February 2012 17:53 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] The Douglas Dc 3 in GIT When the team of the PAF has decided to prohibit access to their work to me, they also requested the opportunity to put it on ILM. They only banned you from the PAF-Forum. Simply because you offended some users there just for having a different opinion than you. That can be read by everyone in the forum, without beeing registered. And everyone can download their work, without beeing registered. I have seen that you nearly always act like that, even on the official forum and here on the mailing-list. Lacking social skills I would say. When I finally got access to their improvements, through a person who has nothing to do with them but that dispatched the wiki link that I did not know, so I logically integrated all their work to my airplane. Thus it has always worked. To YOUR aircraft? THEIR work? You started the work on the aircraft, but it was the team who finally finished it. So to make it clear: it's not alone your work, and not alone their work. It is a work of ALL INVOLVED! And they published the link in the official forum- you can't have missed that. I always took the time to report the authors of the additions in my site because it seems normal for me. If the team of the PAF not appreciate the principle of respect of the original authors of the open source, they go to make aircraft for FS X or X Plane. In addition, it can make money Muaahahaha - ROFL! 1.) Who is the original author? You? Again: You just started a work; the real work- making it flyable and usuable- was done by this group. Without them it would have been another crappy aircraft made by you as the other more than hundred (!) ones by you. They are the original authors as well, like beside you! I would even say, that have made the main work! So there are multiple original authors- that's something you have to learn. And you have to respect them as well. You didn't learn from the AlouetteII-conflict last year, right? 2.) YOU want tell us about the principle respect of original authors? I can still find the already mentioned copyright violations in your aircraft! But see below. I'm tired of seeing all these kids puerile want to use the work of others, to obtain recognition as authors. I have searched through the forums and mailing-list, and it still seems to me that you did not really understand OpenSource. And back on the 5 or 6 files with licensing issues in my airplanes is ridiculous. As usual, Clement did not consider before speaking. Because most have been fixed. 5 or 6? I can remember more - still too much. And much too much for someone who accuses others here for disrespecting OpenSource. Since I started I've always done anything that try to bring something to FG and to please the greatest number. I'm not trying to please me personally. But this, it seems that the PAF can not understand. Sorry, I have to doubt your words, I'm not trying to please me personally. is looking too suspicious to me! And they do the same what you want to make us believe you do: trying to bring something to FG; and please to greatest number. And it seems to me that they do with great success- as many more users are tired of the many half finished, unusuable aircraft made by you. It's a shame. The team is talented, but seems guided by a kid with goals unrelated to FG and Open Source. I don't see that, can you prove it? I wonder how many discussions like that will follow- there seems to be a coherence between your acting and understanding of teamwork and OpenSource and such discussions- OSG-Particles, Bell UH1, AlouetteII, Velocity-XL, and now the DC-3 Why I don't see such discussions on Gijs, Martins, Syds and others work? Why? Pierre Mueller Switzerland -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The Douglas Dc 3 in GIT
On Sun, Feb 12, 2012 at 7:31 PM, Vivian Meazza wrote: I'm sure that there's right and wrong on both sides of this discussion, and I'm aware that some have some difficulty with the English language but could we please continue it in a more decorous manner, and take the personal abuse elsewhere. +1 Where elsewhere is not the FlightGear Forums! -Stuart -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Projection system question
Hi everyone, I've been speaking with some of the folks on the FG forum about a problem I'm having, and I was recommended to contact this group for some possible help. I'm trying to build a sim using Paul Bourke's projection method. Simply put, you can achieve an immersive, 180+ degree field-of-view using a single projector, a hemispherical mirror, and any geometry screen your wish (it could be a dome, a cylinder, or walls and a ceiling). You can get more details in his papers: http://paulbourke.net/papers/jmm/jmm.pdf http://paulbourke.net/papers/cgat09b/ Paul was kind enough to share his code libraries with me that make this work. The problem, however, is that the code is written in C and uses the features of OpenGL, not OSG. Here they are: domelib.h: http://codepad.org/i2EaRFsz domelib.c: http://codepad.org/42EVHWo4 I'm not a programmer, so I have no idea if upgrading the code to use C++ and OSG is difficult or not. I'm also not trying to replicate his process exactly. His method uses four different views to get a 180-degree field of view in all directions. When flying, horizontal field of view is much more important than vertical. I'd like to get a 210-degree horizontal field of view and about a 118-degree vertical (that's a 16:9 image). This isn't just for home use, by the way. I plan on using this setup at a flight school here and seeing how well it works as a training aid. Here's an experimental camera group I've developed to get the look I want (I'm not sure if it's useful for this discussion or not): http://codepad.org/zGfzR79D Any help or advice the community can give me will be greatly appreciated! Also, if I can help in some way, please let me know. As I said, I'm not a programmer, but I am a flight instructor and part-time aviation faculty. So if I can help with things like training, human factors, or simulator fidelity, I'll help as much as I can. Finally, I know you folks are busy with the new build. If this is a bad time, I can ask again after the release date. Thanks in advance! Roy -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The Douglas Dc 3 in GIT
On Sun, 12 Feb 2012, Vivian Meazza wrote: The Devel list has a long tradition of avoiding personalizing discussion, and I for one wiish it to remain so. Seconded. Take your pissing matches elsewhere. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! Buying desktop hardware and installing a server OS doesn't make a server-class system any more than sitting in a puddle makes you a duck. [Cipher in a.s.r] -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Scenery web and scene models
I just checked this out.. git://gitorious.org/fg/sceneryweb.git So I am at a standstill as some parts are missing.. Notably header.php is missing and other stuff for db connection. and obviously data.. Which is understandable.. we dont want everyone to have access to a not db and the server is apache and probably configured in a custom way.. as is usual... So how to move forwards... For all of us to play moving forwards, we need a db or a clone or some public access etc...ideal worls.. but Regardless of the server side.. and all its complications with code + access...and then downloading a huge DB... and all we want is.to develop the site... So Can I suggest we patch up the server simple and quick to do simple task of returning data in json format.. To get started what would be idea would be a list of types/ also a list of models and a list of authors... Making this data available via json is basically a db query or whatever and spit out... the data... eg with adodb.. $models = $db-getAll(select * from models order by model) headers(Content-type: json) echo json_encode($models); If there is a RO access to this machine on a db level then am keen.. and create server api includes paging.. etc//... However atmo its an unknown thing happening in some dark room with some parts available.. as a smarty contributtor/commiter I still like php and is cool.. although nowadays is more python for pure apps.. So to make it clever .. we'd need to create a FGphp class system so its easy for everyone... and php it good at this.. so where do we go from here to impoving the sceneryweb.. maybe I can knock one up here in pyqt.. and get data from online... is all i want.. is we need to make sceneryweb/api/* interface.. read only to start with.. and with nginx could be in seperate spaces.. just some thoughts so we can all have fun... Noted the rss is machine readable and json feed etc etc.. its web init ?? pedro -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The Douglas Dc 3 in GIT
This is exaclty the kind of BS i was hoping we wouldnt see ! -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
