47
edits
Howto:Work with AC3D files in Blender: Difference between revisions
Jump to navigation
Jump to search
Howto:Work with AC3D files in Blender (view source)
Revision as of 10:14, 10 December 2021
, 10 December 2021→Notes: - added scripts location in cases when blender is distributed as a snap image.
Fahim Dalvi (talk | contribs) m (Added latest blender version (2.9) to explicitly show support of importer) |
(→Notes: - added scripts location in cases when blender is distributed as a snap image.) |
||
| Line 32: | Line 32: | ||
* To see textured surfaces as they will be shown in FlightGear, go into the material texture and set the blend type to ''Multiply'' instead of the default ''Mix'' (the importer will also do this automatically). An example plane that will look very different if this is not done is the FGAddon aircraft {{fgaddon source|path=Aircraft/ASK13|commit=1363|text=ASK-13}}, notice the wingtips. | * To see textured surfaces as they will be shown in FlightGear, go into the material texture and set the blend type to ''Multiply'' instead of the default ''Mix'' (the importer will also do this automatically). An example plane that will look very different if this is not done is the FGAddon aircraft {{fgaddon source|path=Aircraft/ASK13|commit=1363|text=ASK-13}}, notice the wingtips. | ||
* The final model might display color mismatches (Texture color vs Material color) when viewed in Flightgear. Hand editing the [[AC files: Basic changes to textures and colors#Materials|materials]] section of the exported AC3D file might fix this. | * The final model might display color mismatches (Texture color vs Material color) when viewed in Flightgear. Hand editing the [[AC files: Basic changes to textures and colors#Materials|materials]] section of the exported AC3D file might fix this. | ||
* If you wonder where to put the scripts you could open blender's user preferences ({{Key press|Ctrl|Alt|U}}, or ''File > User Preferences'') tick for example Import/Export and extent the information concerning an existing script. Usually this throws the path. For for example Ubuntu 14.04LTS/Blender 2.79b it is: <code>/usr/share/blender/scripts/addons/</code>. | * If you wonder where to put the scripts you could open blender's user preferences ({{Key press|Ctrl|Alt|U}}, or ''File > User Preferences'') tick for example Import/Export and extent the information concerning an existing script. Usually this throws the path. For for example Ubuntu 14.04LTS/Blender 2.79b it is: <code>/usr/share/blender/scripts/addons/</code>. In recent Ubuntu versions blender is distributed as a snap image. In such cases blender addon scripts are placed in: <code>$HOME/.config/blender/X.YY/scripts/addons/</code> (where X.YY is blender version, for example 2.82). | ||
* Be aware that Blender only has greyscale for emission and ambient colors. If you want to export/import a color for those, import/export options gives you capability to choose to use Blenders mirror color for that. | * Be aware that Blender only has greyscale for emission and ambient colors. If you want to export/import a color for those, import/export options gives you capability to choose to use Blenders mirror color for that. | ||
* The importer will not fail if it does not locate a texture, instead it will issue warnings. Pull down the top bar to see if there was any, they will be orange lines. | * The importer will not fail if it does not locate a texture, instead it will issue warnings. Pull down the top bar to see if there was any, they will be orange lines. | ||