Aerodynamic Objects Forum

Is it possible to import an X-Plane aircraft file, and will the physics of the plane be similar to those in X-Plane? Of course, I understand that I would need to develop a parser, etc., but I’m specifically interested in the physics and controls.

I created an airfoil in Blender, exported it as an FBX file and when I imported it Unity recognizes it as a mesh. I can't seem to use this mesh in the geometry game object and have the aerodynamics work. It seems that the aerodynamics only work with Unity primitive meshes. I have a work around where I use a cube game mesh for the geometry to create a wing as described in one of the first tutorials. Then I added a game object into the geometry with my blender mesh and scaled it so that it's larger than the cube mesh. There are two drawbacks to this approach. First is the fact that it's not using the airfoil surface to compute the lift and drag forces (so I'm lying!). Second is that I can't add a control surface. Is it possible to use different meshes than the few that I've seen including sphere, cube, cylinder, capsule?

Some bugs and performance issues I noticed while playing around with the new version of AO. 1. Player builds are failing due to references to UnityEditor in non-editor scripts. Assets\AO\Scripts\Flow\FluidVolume.cs(446,13): error CS0234: The type or namespace name 'EditorApplication' does not exist in the namespace 'UnityEditor' (are you missing an assembly reference?) Assets\AO\Scripts\Flow\FluidVolume.cs(32,30): warning CS0109: The member 'FluidVolume.collider' does not hide an accessible member. The new keyword is not required. Assets\AO\Scripts\Flow\VortexNode.cs(32,21): error CS0234: The type or namespace name 'EditorApplication' does not exist in the namespace 'UnityEditor' (are you missing an assembly reference?) Assets\AO\Scripts\Flow\VortexNode.cs(48,62): error CS0103: The name 'HandleUtility' does not exist in the current context Assets\AO\Scripts\Flow\UniformFlow.cs(97,40): error CS0103: The name 'HandleUtility' does not exist in the current context Assets\AO\Scripts\Flow\UniformFlow.cs(99,13): error CS0103: The name 'Handles' does not exist in the current context Assets\AO\Scripts\Flow\UniformFlow.cs(100,13): error CS0103: The name 'Handles' does not exist in the current context Assets\AO\Scripts\Flow\AreaSource.cs(108,13): error CS0103: The name 'Handles' does not exist in the current context Assets\AO\Scripts\Flow\AreaSource.cs(113,21): error CS0103: The name 'Handles' does not exist in the current context Assets\AO\Scripts\Flow\AreaSource.cs(117,21): error CS0103: The name 'Handles' does not exist in the current context These can be fixed by adding #if UNITY_EDITOR blocks around the references to UnityEditor things. 2. The localFluidVolumes.RemoveAll call in FlowAffected.cs is allocating a lot of memory every frame. This can be fixed by using a for loop instead. for (int i = localFluidVolumes.Count -1; i >= 0; i--) { FluidVolume item = localFluidVolumes[i]; if (item == null || FlowInteractionManager.IsInteractionIgnored(interactionID, item.interactionID)) { localFluidVolumes.RemoveAt(i); } } 3. When using LiftingBodyWake, it is constantly Instantiating and Destroying GameObjects every frame. It would be much more efficient to use ObjectPooling for this or use data structures outside of GameObjects entirely.