392
edits
(added mfranz's visualisation script) |
|||
Line 232: | Line 232: | ||
*'''power:''' in kW | *'''power:''' in kW | ||
*'''max-force:''' in N | *'''max-force:''' in N | ||
=== Visualisation === | |||
To make the programmed aircraft visable it is possible to load and compare it with the 3D model within [[Blender]]. The applaud for this ''very'' usefull script goes to M. Franz, thank you very much! | |||
The script is available in FlightGear's [[CVS]] tree (source/utils/Modeller/yasim_import.py) or downloadble [http://cvs.flightgear.org/viewvc/source/utils/Modeller/yasim_import.py?view=co here]. | |||
The howto, taken from inside the script: | |||
yasim_import.py loads and visualizes a YASim FDM geometry | |||
========================================================= | |||
It is recommended to load the model superimposed over a greyed out and immutable copy of the aircraft model: | |||
(0) put this script into ~/.blender/scripts/ | |||
(1) load or import aircraft model (menu -> "File" -> "Import" -> "AC3D (.ac) ...") | |||
(2) create new *empty* scene (menu -> arrow button left of "SCE:scene1" combobox -> "ADD NEW" -> "empty") | |||
(3) rename scene to yasim (not required) | |||
(4) link to scene1 (F10 -> "Output" tab -> arrow button left of text entry "No Set Scene" -> "scene1") | |||
(5) now load the YASim config file (menu -> "File" -> "Import" -> "YASim (.xml) ...") | |||
This is good enough for simple checks. But if you are working on the YASim configuration, then you need a | |||
quick and convenient way to reload the file. In that case continue after (4): | |||
(5) switch the button area at the bottom of the blender screen to "Scripts Window" mode (green python snake icon) | |||
(6) load the YASim config file (menu -> "Scripts" -> "Import" -> "YASim (.xml) ...") | |||
(7) make the "Scripts Window" area as small as possible by dragging the area separator down | |||
(8) optionally split the "3D View" area and switch the right part to the "Outliner" | |||
(9) press the "Reload YASim" button in the script area to reload the file | |||
If the 3D model is displaced with respect to the FDM model, then the <offsets> values from the | |||
model animation XML file should be added as comment to the YASim config file, as a line all by | |||
itself, with no spaces surrounding the equal signs. Spaces elsewhere are allowed. For example: | |||
<offsets> | |||
<x-m>3.45</x-m> | |||
<z-m>-0.4</z-m> | |||
<pitch-deg>5</pitch-deg> | |||
</offsets> | |||
becomes: | |||
<!-- offsets: x=3.45 z=-0.4 p=5 --> | |||
Possible variables are: | |||
x ... <x-m> | |||
y ... <y-m> | |||
z ... <z-m> | |||
h ... <heading-deg> | |||
p ... <pitch-deg> | |||
r ... <roll-deg> | |||
Of course, absolute FDM coordinates can then no longer directly be read from Blender's 3D view. | |||
The cursor coordinates display in the script area, however, shows the coordinates in YASim space. | |||
Note that object names don't contain XML indices but element numbers. YASim_hstab#2 is the third | |||
hstab in the whole file, not necessarily in its parent XML group. A floating point part in the | |||
object name (e.g. YASim_hstab#2.004) only means that the geometry has been reloaded that often. | |||
It's an unavoidable consequence of how Blender deals with meshes. | |||
Elements are displayed as follows: | |||
cockpit -> monkey head | |||
fuselage -> blue "tube" (with only 12 sides for less clutter); center at "a" | |||
vstab -> red with yellow flaps | |||
wing/mstab/hstab -> green with yellow flaps/spoilers/slats (always 20 cm deep); | |||
symmetric surfaces are only displayed on the left side | |||
thrusters (jet/propeller/thruster) -> dashed line from center to actionpt; | |||
arrow from actionpt along thrust vector (always 1 m long); | |||
propeller circle | |||
rotor -> radius and rel_len_blade_start circle, direction arrow, | |||
normal and forward vector, one blade at phi0 | |||
gear -> contact point and compression vector (no arrow head) | |||
tank -> cube (10 cm side length) | |||
weight -> inverted cone | |||
ballast -> cylinder | |||
hitch -> circle (10 cm diameter) | |||
hook -> dashed line for up angle, T-line for down angle | |||
launchbar -> dashed line for up angles, T-line for down angles | |||
A note about step (0) for M$ users: the mentioned path is inside the folder where Blender lives, something like <code>C:\Program Files\Blender Foundation\Blender\.blender\scripts</code>. | |||
{{FDM}} | {{FDM}} |
edits