The answer is RTFM, sorry but in the manual there is an example in chapter 5.5.
For all who have the same problem, here is a small codesnippet that works for me now:
PLACEPOINTSALONGLINE|FTYPE="LINE" and fclass="motorway"|SINGLE|149;150|10;10|0|String;OBJECT|LIGHT|HDG...
I used PLACEPOINTSALONGLINE for a long time and created the AGN out of the old now depreciated command CREATEAGNLIBOBJ.
With the new CREATEAGNLIBOBJECT command it however expects a polygon instead of a line.
So the lightpoles placed with PLACEPOINTSALONGLINE are not exported
thanks, this is really helpful for all who want to make a platform. I found my problem which was that I forgot to press initialize.
It works great now.
Thanks my friend for your great input to the comunity here
I am currently trying to add an object with a concrete surface to my scenery. So I made a copy of the visible object and tried to attach a platform with the FSX Attachpoint Tool to it.
I get the following error message when trying to attach:
The reason seems to be clear, the tool simply...
no you do not have to change anything in the toolset for now. My tests were ALL ok so it works fine. When I some issues in the future, I will let you know.
I made my comments concerning the altitude because you said, you couldn´t see the scenery objects when testing automatic bgl...
I started with a simple car which works perfect.
Also a windsock with bone animations compiled perfect for fsx.
The last test with automatic bgl function with a simple object also compiled fine and the object is visible in the scenery
So all tests worked perfect, great job Kris...
I still have Blender 2.72 in use but get a similar message when using skinned mesh animations which still have IK Constraints in it.
In my case I select all bones in pose mode, then bake Pose-Animation-Bake Action with parameter Visual Keying set on.
Afterwards you can delete the IK...
It is the default modeldef.xml which is coming with P3D V3.3
I am experimenting with bone animation and was not successfull with Blender2FSX toolset. So I wanted to try the Blender2P3D version.
Simply doing Ambient animations. But the error mentioned above is also shown without any animation.
thanks for the fast reply. It is exactly in:
HKEY_LOCAL_MACHINE, 'SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v3 SDK.
and it is a 64bit Win10 machine.
This is the registry folder shown in the second screen.
when trying to export an object I get an error, that the script doesn´t find the modeldef.xml
I am still using Blender 2.72b
The latest SDK is properly installed, the registry entry seems to be ok, but it expects the modeldef.xml in F:\Lockheed Martin....
Do you have any idea whats going...
Just a guess:
Wrong texture mapping: Is it possible, that your texture is flipped vertically? When you convert your texture to DDS you have to flip it. If you do that via imagetool in the SDK the flipping is done for you automatically
MIRI sign: Perhaps you forgot to assign a material? This is...