WOW. I was entertained just watching that. I can't wait to get it running on my flightgear!
Oscar wrote:These are the things I'd love to see:
- Only the jetway you're clicking on should move (you're working on that one I think)
Oscar wrote:- The animations should be way slower, as nickyivyca said
simbabeat wrote:Still think its way to fast. I don't think I am sure. We are going for realism here right? It goes at a snail pace whenever I've seen 'em move.
Geesh, tough crowd!
Currently the animation lasts a total of 21 seconds. Any suggestions for the timing?
nickyivyca wrote:It really depends on the total distance needed to be traveled. Changing from 737 to CRJ will take over 2 minutes, but just from A320 to 757 will probably be less. Not sure if that kind of distance based time is available on your system, though...
if(jetwayPos > jetwayShouldBe){ jetwayPos = jetwayPos - 0.1; }
if(jetwayPos < jetwayShouldBe){ jetwayPos = jetwayPos + 0.1; } // This is not even close to Nasal, but I hope you understand?
nickyivyca wrote:So, on the wiki article, it says that "some center of axis coordinates need to be changed." What are these?
nickyivyca wrote:By the way, I might take a look at the script that's in the alpha release and see if I can devise something that will change the length of time required based on the amount of distance needed to be covered.
settimer(func
{
scenery.airport.jetway.door[1].toggle();
}, getprop("aircraft/jetway-pos/z-rot") * X);
nickyivyca wrote:So, when positioning it, do I need to do anything differently? I don't know if you mean that the xml for the model animates it differently, or positioning is different as well.
nickyivyca wrote:Doing the thing in Blender described on the wiki where you move the jetway around to find out what the values that go in the set file are.
Users browsing this forum: No registered users and 7 guests