Re: [Flightgear-devel] about the carrier used in scenario
jean pellotier wrote we did a scenario that use the carrier type to make an arresting cable with a flols working, at LFRJ airport (Landivisiau, France), but if we check the turn to wind button the cable and the flols are moving, considered like a normal carrier. Is there a way to make it fix relative to the ground, or the only way is to never use turn to wind? i join the scenario file (LFRJ_wires_demo.xml) Concerning the flols, last two red lights (the lowests) taking part of the wave off are not in the right place, compared to the flols model, as you can see here: http://wiki.flightgear.org/images/thumb/9/9d/Carrier5.jpg/800px- Carrier5.jpg here's a patch to synch them, that seems to be an inversion between y and z axis,here's the result: http://fr.flightgear.tuxfamily.org/lib/exe/fetch.php?cache=cachew=900h=6 70media=school:move:porte-avion:flols:waveoff-nimitz.jpg have a nice landing on Nimitz Thanks for the input on the flols. I'm not sure what the issue is with putting it ashore. Does it move in some way? Checking the turn into wind will make it turn into wind, so the best way of avoiding this bug is not to check turn into wind :-). I'll fix the error in the Wave Off Lights soonest - thanks for the patch. Vivian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] about the carrier used in scenario
I wrote jean pellotier wrote we did a scenario that use the carrier type to make an arresting cable with a flols working, at LFRJ airport (Landivisiau, France), but if we check the turn to wind button the cable and the flols are moving, considered like a normal carrier. Is there a way to make it fix relative to the ground, or the only way is to never use turn to wind? i join the scenario file (LFRJ_wires_demo.xml) Concerning the flols, last two red lights (the lowests) taking part of the wave off are not in the right place, compared to the flols model, as you can see here: http://wiki.flightgear.org/images/thumb/9/9d/Carrier5.jpg/800px- Carrier5.jpg here's a patch to synch them, that seems to be an inversion between y and z axis,here's the result: http://fr.flightgear.tuxfamily.org/lib/exe/fetch.php?cache=cachew=900h=6 70media=school:move:porte-avion:flols:waveoff-nimitz.jpg have a nice landing on Nimitz Thanks for the input on the flols. I'm not sure what the issue is with putting it ashore. Does it move in some way? Checking the turn into wind will make it turn into wind, so the best way of avoiding this bug is not to check turn into wind :-). I'll fix the error in the Wave Off Lights soonest - thanks for the patch. The Wave Off Lights 71 and 72 are in the correct position as measured in AC3D. The patch is therefore an incorrect solution to the problem which you are seeing. The cause of the problem is not obvious, but I can reproduce it here. I'll look into it some more to try to come up with a proper solution. Vivian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] about the carrier used in scenario
I wrote jean pellotier wrote we did a scenario that use the carrier type to make an arresting cable with a flols working, at LFRJ airport (Landivisiau, France), but if we check the turn to wind button the cable and the flols are moving, considered like a normal carrier. Is there a way to make it fix relative to the ground, or the only way is to never use turn to wind? i join the scenario file (LFRJ_wires_demo.xml) Concerning the flols, last two red lights (the lowests) taking part of the wave off are not in the right place, compared to the flols model, as you can see here: http://wiki.flightgear.org/images/thumb/9/9d/Carrier5.jpg/800px- Carrier5.jpg here's a patch to synch them, that seems to be an inversion between y and z axis,here's the result: http://fr.flightgear.tuxfamily.org/lib/exe/fetch.php?cache=cachew=900h=6 70media=school:move:porte-avion:flols:waveoff-nimitz.jpg have a nice landing on Nimitz Thanks for the input on the flols. I'm not sure what the issue is with putting it ashore. Does it move in some way? Checking the turn into wind will make it turn into wind, so the best way of avoiding this bug is not to check turn into wind :-). I'll fix the error in the Wave Off Lights soonest - thanks for the patch. The Wave Off Lights 71 and 72 are in the correct position as measured in AC3D. The patch is therefore an incorrect solution to the problem which you are seeing. The cause of the problem is not obvious, but I can reproduce it here. I'll look into it some more to try to come up with a proper solution. OK - Wave Off Lights 71, 72 were in the wrong position, as were 61, 62, which confused me. Fixed now in cvs - please check that the problem is solved for you. Vivian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] about the carrier used in scenario
Vivian Meazza a écrit : OK - Wave Off Lights 71, 72 were in the wrong position, as were 61, 62, which confused me. Fixed now in cvs - please check that the problem is solved for you. now 71 and 72 are in the right place, but 61 and 62 are in the same place as 51 and 52, so there's missing two lights ... setting 51 and 52 this way did the job: model nameWave-Off-51/name pathModels/Geometry/Nimitz/Models/wave-off.xml/path offsets x-m0.1/x-m y-m0.77/y-m z-m-0.39/z-m /offsets /model model nameWave-Off-52/name pathModels/Geometry/Nimitz/Models/wave-off.xml/path offsets x-m0.1/x-m y-m-0.77/y-m z-m-0.39/z-m /offsets /model have a nice day :) jano - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] about the carrier used in scenario
jean pellotier wrote Vivian Meazza a écrit : OK - Wave Off Lights 71, 72 were in the wrong position, as were 61, 62, which confused me. Fixed now in cvs - please check that the problem is solved for you. now 71 and 72 are in the right place, but 61 and 62 are in the same place as 51 and 52, so there's missing two lights ... setting 51 and 52 this way did the job: model nameWave-Off-51/name pathModels/Geometry/Nimitz/Models/wave-off.xml/path offsets x-m0.1/x-m y-m0.77/y-m z-m-0.39/z-m /offsets /model model nameWave-Off-52/name pathModels/Geometry/Nimitz/Models/wave-off.xml/path offsets x-m0.1/x-m y-m-0.77/y-m z-m-0.39/z-m /offsets /model have a nice day :) So they are - fixed in cvs (I hope) - try again Vivian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] about the carrier used in scenario
Vivian Meazza a écrit : So they are - fixed in cvs (I hope) - try again that's ok for me, thanks. jano - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] about the carrier used in scenario
jean pellotier wrote Vivian Meazza a écrit : So they are - fixed in cvs (I hope) - try again that's ok for me, thanks. Glad that we've fixed that - it must have been that way for several years. But what is the real issue with the demo? I couldn't get it to work here - doesn't it need the model as well? I imagine that you would really like a new AI Object which is a subset of the AICarrier, rather than your current hack? Vivian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] about the carrier used in scenario
Vivian Meazza a écrit : Glad that we've fixed that - it must have been that way for several years. But what is the real issue with the demo? I couldn't get it to work here - doesn't it need the model as well? oh sorry, i didn't gave you all needed to do it working, here's what's missing: first the scenary used (7M)needed to have cable in the suitable hight: http://janodesbois.free.fr/doc/meeting-08-2008.tar.gz it contains terrain with little differents with scenery 1.0, so i recommend to uncompress it where you want and to give his path with something like that: --fg-scenery=path/to/meeting-08-2008:path/to/data/scenery and here's all the 3D models needed for the 4 airports and lot of planes low-poly, included the scenario (37M) : http://janodesbois.free.fr/doc/data.tar.gz or only the files needed for the scenario: http://janodesbois.free.fr/doc/scenario-LFRJ.tar.gz then just start at LFRJ with the LFRJ_wires_demo.xml enabled! for french users: http://fr.flightgear.tuxfamily.org/doku.php?id=meeting:representations:03-08-2008 I imagine that you would really like a new AI Object which is a subset of the AICarrier, rather than your current hack? yes that would be cool, the most important would be that all the coordonnes shouldn't need to be relative, but given as the ufo's output. for me a flols who can work alone, and the same for the cable would be perfect, but i'm not specialist! and one more thing about using the carrier for ground arresting cable, it is impossible to give a roll in the scenario file, because the first seconds the boat fdm make it flat jano, trying to catch a wire navigating through the ground - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] about the carrier used in scenario
hi all we did a scenario that use the carrier type to make an arresting cable with a flols working, at LFRJ airport (Landivisiau, France), but if we check the turn to wind button the cable and the flols are moving, considered like a normal carrier. Is there a way to make it fix relative to the ground, or the only way is to never use turn to wind? i join the scenario file (LFRJ_wires_demo.xml) Concerning the flols, last two red lights (the lowests) taking part of the wave off are not in the right place, compared to the flols model, as you can see here: http://wiki.flightgear.org/images/thumb/9/9d/Carrier5.jpg/800px-Carrier5.jpg here's a patch to synch them, that seems to be an inversion between y and z axis,here's the result: http://fr.flightgear.tuxfamily.org/lib/exe/fetch.php?cache=cachew=900h=670media=school:move:porte-avion:flols:waveoff-nimitz.jpg have a nice landing on Nimitz jano ?xml version=1.0? PropertyList scenario description Arrestor Cables for training of landing in a aircraft carrier. park-1 is a parking position for Heavy Military Aicraft park-2 is a parking position for Military Jet !-- park-3 is for a civilian aircraft /-- /description entry typecarrier/type nameLFRJ-bak26-1/name modelAI/Airports/LFRJ/BAK26+flols.xml/model TACAN-channel-ID098Y/TACAN-channel-ID wireline/wire latitude48.53306323/latitude longitude-4.137254038/longitude altitude335.4462275/altitude heading253.32/heading flols-pos x-offset-m25/x-offset-m y-offset-m-30/y-offset-m z-offset-m1.8/z-offset-m -- /flols-pos max-lat0/max-lat min-lat0/min-lat max-long0/max-long min-long0/min-long /entry entry typecarrier/type nameLFRJ-bak08-1/name modelAI/Airports/LFRJ/BAK08+flols.xml/model TACAN-channel-ID098Y/TACAN-channel-ID wireline/wire latitude48.52714689/latitude longitude-4.166412234/longitude altitude334.8964534/altitude heading73.32/heading flols-pos x-offset-m25/x-offset-m y-offset-m-30/y-offset-m z-offset-m1.5/z-offset-m /flols-pos parking-pos namepark-1/name heading-offset-deg10/heading-offset-deg x-offset-m365/x-offset-m y-offset-m610/y-offset-m z-offset-m-2/z-offset-m /parking-pos !-- Military Jets /-- parking-pos namepark-2/name heading-offset-deg190/heading-offset-deg x-offset-m252/x-offset-m y-offset-m600/y-offset-m z-offset-m0/z-offset-m /parking-pos !-- Civilian Aircrafts /-- !-- parking-pos namepark-3/name heading-offset-deg0/heading-offset-deg x-offset-m200/x-offset-m y-offset-m-600/y-offset-m z-offset-m0/z-offset-m /parking-pos /-- max-lat0/max-lat min-lat0/min-lat max-long0/max-long min-long0/min-long /entry /scenario /PropertyList !-- latitude-deg type=double48.53306323/latitude-deg longitude-deg type=double-4.137254038/longitude-deg elevation-ft type=double335.4462275/elevation-ft --Index: Models/Geometry/Nimitz/Models/flols.xml === RCS file: /var/cvs/FlightGear-0.9/data/Models/Geometry/Nimitz/Models/flols.xml,v retrieving revision 1.6 diff -u -r1.6 flols.xml --- Models/Geometry/Nimitz/Models/flols.xml 21 Apr 2008 08:23:20 - 1.6 +++ Models/Geometry/Nimitz/Models/flols.xml 29 Jul 2008 18:33:25 - @@ -289,8 +289,8 @@ pathModels/Geometry/Nimitz/Models/wave-off.xml/path offsets x-m0.1/x-m - y-m0.77/y-m - z-m-1.18/z-m + y-m1.18/y-m + z-m-0.77/z-m /offsets /model model @@ -298,8 +298,8 @@ pathModels/Geometry/Nimitz/Models/wave-off.xml/path offsets x-m0.1/x-m - y-m-0.77/y-m - z-m-1.18/z-m + y-m-1.18/y-m + z-m-0.77/z-m /offsets /model animation - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
