It's my first try with an attitude indicator and I'm clueless.
I've looked at a few other threads about these indicators, but didn't find whatever it is I need to learn.
I have the bank indicator keyed with rotation keys. No problem with it.
I cannot figure out what needs to be done with the...
I have a window that displays various performance readings. This is where I see that the gauge is reading the low value.
It uses this: Vertical Speed\t%((A:VERTICAL SPEED, ft/min))%!d! to show the vertical speed.
My gauge has this code:
I shouldn't reply to any posts when it's so early in the morning. :tapedshut
I just reread your OP where you said
That is what your problem is.
You have to select either the Specular or PBR mode.
Which one you should select will depend on which version of P3D your object is for. Check the...
I suggest that you have a look at the Material parameters section of the Wiki page here. There is also lots of other good information on the page.
I wonder if the first paragraph won't solve your problem.
Did you select a Material Mode?
Arno and Doug,
I just figured out what the problem was.
The first time using this version of MCX, the file Save As dialog had FS2004 MDL aircraft object as the default Save as type.
I didn't notice that then, because for some time all the MCX updates have used what my previous settings were...
That is the case here.
That seems likely.
That is probably why I get away with exporting it.
Yes, it is too complex and will be simplified before/ if I am ever finished. :oops:
I have exported some objects where I get several of these warnings and I haven't seen any problems with the objects in FSX.
That was why I wondered what the warning meant.
Anyway, it probably wouldn't be a bad idea for me to reduce the part complexity.
I don't know if your last reply (#32) means that you found the answer to the question you asked in your reply #31:
If not, it is one of the options in the ComboBox at the top of the material editor:
I'm guessing that this may have something to do with object complexity and the new Assimp library.
I get this error when I try to import the below attached Collada file:
I can import other less complex objects with no problem.
Also, the attached file imports with no problems using...
Thanks for your time Arno,
But, I don't see any difference with the 4/26 release.
Here are two more images that should show the problem more clearly:
Here is the SU 8 .dae file:
FWIW, this object was made in SU 2017, then textured in Blender 2.82a and exported from it as a .DAE file.
Edit: never mind the Blender info, the same thing happens with the .dae straight from SU.