• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

This is baffling

WarHorse47

SOH-CM-2024
Over the weekend I decided to get a few P-51 Mustangs over to my FSX install, so I picked up the Warbirdsim Flight Leader X and spent a good part of yesterday adding repaints and flying around.

Towards the end of the day I decided to add some missing lines to each entry to associate the planes with Warbirdsim and added the following lines for each entry:
ui_typerole="Single Engine Prop"
ui_createdby="Warbirdsim"

Today I discovered that this works with only one entry, and all the other entries are still listed as 'Unknown' for some unknown reason. Why would it work for one entry and not the others?? :salute:

Weird. Just plain weird.
 
I've done this exact same thing, and had the same problem. Unfortunately it was user error! I had mistyped and in error copied this entry to all other repaint entries. You'll probably have to closely look at each entry and spot the error.
 
There are 53 entries [fltsim.52]

The changes only affect [fltsim.31], meaning it is the only aircraft that appears under a "Single Engine Prop" or "Warbirdsim".

The additions I made to each aircraft were copied from another, working aircraft.cfg. The only thing modified was for 'ui_createdby='.

I'm still trying to figure out why 1 out of 53 works, but the other 52 do not. If there is a typo, I haven't found it. Sigh. :sleep:
 
You ain't gonna believe this.... but I figured it out. You might want to sit down for this one.

As I mentioned earlier, I purchased the Flight Leader X from Warbirdsim and added a lot of repaints. Well, what I found out is that the entry for [fltsim.31] had a different ui_manufacturer= entry.

Every one of the entries including the default textures had a ui_manufacturer= North American. The only one that showed up properly had ui_manufacturer= North American Aviation (all without quotes, BTW).

As it just so happens my install of the Warbirdsim P-51D also has ui_manufacturer= North American Aviation, so this might have been a factor as well.

Anyways, all I had to do was to make every manufacturer entry as 'North American Aviation' and now all the aircraft are listed under Warbirdsim. :isadizzy:

All I know is that the Mustangs now show under the right creator and role, finally.

Sheesh. I think I need an adult beverage. :guinness: or two.. :guinness::guinness:
 
BTW, just a tip that might save some time and typing in the future...

If you have entries that will apply to every one of the variations, you can simply place that information in the [General] section once, and it will apply to all of 'em!

For example:
[General]
atc_type=Cessna
atc_model=C525
ui_manufacturer=Cessna
ui_type="Citationjet CJ1+"
ui_typerole="Corporate Jet"
ui_createdby="Eaglesoft Development Group"
description="Eaglesoft Cessna Citation CJ1+"

editable=1
performance=Max Cruise Speed\t 3891 knots TAS @ 35,000 ft\nService Ceiling\t41,000 ft
Category=airplane

The four ui_ entries and the description are common to all of the variations, so I placed them in the [General] section. This way, the only entry that is unique to each variant is - not too surprisingly - the ui_variation one...

[fltsim.6]
title=Eaglesoft Citation CJ1+ N900ES
ui_variation="N900ES"
et cetera...
 
Excellent info, Bill ! :icon_eek:


Many thanks for sharing yet another esoteric insight arising from your years of experience as an FS-Insider ! :cool:

GaryGB
 
Thanks, Bill. Good stuff.

The challenges (and learning curve) are coming from adding textures and porting over some aircraft from FS9.

I'm learning that when textures are added to FSX aircraft, not all the readme.txt entries are consistent which in turn caused the issue I first posted.

Same goes for some port-over aircraft from FS9 as the FS9 aircraft.cfg goes by different rules.
 
Back
Top