PhoenixRC - Quick way to setup one model to fly like another.
04-16-2007 | 04:07 PM
#1
Thread Starter
Junior Member
Joined: Mar 2007
Posts: 4
Likes: 0
Received 0 Likes
on
0 Posts
From: Sacramento, CA
PhoenixRC - Quick way to setup one model to fly like another.
Here’s a little tip I posted on RunRyder:
Example – I want the Scale helicopter “dauphin” to fly like the Performance helicopter “raptor50_3D”
1 – Launch PhoenixRC > Simulation > Select Aircraft > Helicopters > Performance > raptor50_3D > Click “Finish”
2 – Select Simulation > Edit Aircraft > In the bottom right drop down box, select Duplicate Current > Change “unnamed” to “rename”.
3 – Close PhoenixRC > Go to C:\Program Files\PhoenixRC\variants\helicopters > rename “raptor50_3D_rename.fly” to
“dauphin_Raptor503D.fly”
4 - Launch PhoenixRC > Simulation > Select Aircraft > Helicopters > Helicopters > dauphin > Raptor503D > Finished
Now the scale helicopter Dauphin will fly like the Raptor50_3D.
Tips
The first part of the “.fly” file must be exactly the same as the model you are adding a custom configuration to. In the example above this would be the “dauphin_.fly” part. The second part of the “.fly”, everything after the “_” could be anything, but do not use spaces or an underscore.
Enjoy
Tom[8D]
Example – I want the Scale helicopter “dauphin” to fly like the Performance helicopter “raptor50_3D”
1 – Launch PhoenixRC > Simulation > Select Aircraft > Helicopters > Performance > raptor50_3D > Click “Finish”
2 – Select Simulation > Edit Aircraft > In the bottom right drop down box, select Duplicate Current > Change “unnamed” to “rename”.
3 – Close PhoenixRC > Go to C:\Program Files\PhoenixRC\variants\helicopters > rename “raptor50_3D_rename.fly” to
“dauphin_Raptor503D.fly”
4 - Launch PhoenixRC > Simulation > Select Aircraft > Helicopters > Helicopters > dauphin > Raptor503D > Finished
Now the scale helicopter Dauphin will fly like the Raptor50_3D.
Tips
The first part of the “.fly” file must be exactly the same as the model you are adding a custom configuration to. In the example above this would be the “dauphin_.fly” part. The second part of the “.fly”, everything after the “_” could be anything, but do not use spaces or an underscore.
Enjoy
Tom[8D]
