• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Beta-Test AI-Aircraft Editor

Hi Martin,

nice and fast work. Thanks.

Here is a Picture from the Window.

Did you see the same?


Surely not :eek:. Otherwise I would not have released it. This is what I see when I set my resolution down to 1024*768. In my example the AI-Editor window is extremely reduced and the fonts are no longer fitting. But you can see every control. It looks like it is shifting the border towards the middle without resizing the controls in your example. What OS are you working with?


ScreenShot043.jpg
 
Sorry :o

I screwed up the code for the model and texture handling. All default folders with the name texture and model were not correctly handled, only those with an extension (like texture.gaf or model.gub). This is fixed now.

Download AI-Aircraft-Editor 1.2.28
 
Hallo Martin,
mein OS ist Windows XP Pro mit SP2.


ooopppsss,

my OS is Windows XP with SP2. :D
 
For Jim

Martin

I am running Vista 32/SP1 in mode 1024 by 768. I will check also the dirty code since I see the same screen issue as Sandra

Jim,

have you had the chance to test the resizing? Is it scaling the form and controls or just clipping like in Sandra's screen shot?
 
Martin

I resized to a much smaller view as per the full monitor picture. Some words in the lower left are clipping but the radio buttons and added features still work



 
Suggestion

Can you also include changing the sound like you did with model and texture as you can change the sound folder when editing with Notepad or similar program?
 
This program was getting ugly as hell :)

There were so many new feature requests coming in that I just added these without much consideration of optics, aesthetics and ergonomics. So the program was deteriorating below any acceptable standard in this regards.

I have reworked many aspects of the interface last night.

  • Settings (Resize & Confirmation) have moved to the File menu
  • Quit program and Open CFG have moved to the File menu
  • [fltsim.x] deletion and renumbering is invoked with right-click popup menu on the listbox instead of button
  • the texture button forest :o is gone, all options accessible via right-click popup menu
  • multi airfile support is now better visible

Don,
thank you for insisting on right-click. This update should have taken care of most of your reported issues. What's left?

Jim,
Version 1.2.24 is very much outdated ;) You are entitled to download the current version :D

Sandra,
I have no idea while it is clipping instead of scaling on your system. Try the new version.

saiarcot895,
I will integrate changing the assigned sound.


Download AI-Aircraft-Editor 1.3.1
 
There were so many new feature requests coming in that I just added these without much consideration of optics, aesthetics and ergonomics. So the program was deteriorating below any acceptable standard in this regards.
Welcome to the world of freeware utility development. Wait until you make it generally available!

A few more comments:
  • on the main panel
    • Glad you went the right-click "route"
    • Currently, you use the combobox beside the FS9 and FSX radio buttons to quick-select the FSX\SimObjects sub-folder. It has no apparent purpose for FS9 (and still displays the FSX folder-set). Yesterday, I thought you were using it to allow manual selection of the FS9/FSX path - until you set me straight. You may wish to reconsider. FSX folder selection is easily done from the folder tree and likely will be an infrequent occurence. On the other hand, if Microsoft changes the registry location for the FS9 and FSX base folders in its next 64-bit operating system (as it did with Vista), your application will be unuseable with that operating system. Using this area for manual selection of the path to FS if your app. doesn't find it automatically would avoid that potential difficulty.
    • What is the purpose of the multi-line text box in the lower-left-hand corner which now displays the name of the .air file. Is it still needed now that you handle the .air file on the mt&a tab?
    • I urge you once again not to use the .air file to control whether or not the AI variants are displayed in the Select Aircraft window. First of all, that selection applies to all variants in the aircraft.cfg file, whether or not for AI use. If someone uses that airfile for another aircraft (not an infrequent occurence among AI developers), it could take them a long while to figure out why their new aircraft won't display in the Select Aircraft window if you have so modified it. This capability is not well-known. I know of no other utility that includes it and the setting is not otherwise apparent. While I'm sure AI Aircraft Editor will appear on most FS-users' desktops, I suspect the effects of this feature will be frequent topics in your support forum. It appears you can acomplish the same thing for both FS9 and FSX by commenting-out the "ui_" items for the individual variants. (My last words on the subject.)
    • You are using at least two font sizes in the various text boxes which, incidentally, are taller than necessary. If you standardized on the smaller font (which seems quite adequate) and re-size the text boxes, you could substantially reduce the height of your main screen (which solves half your problem with users with lo-res monitors).
  • on the Models, Textures and Airfile tab:
    • Could you display the currently assigned model, texture and .air files for the selected AI variant without requiring the user to click the "fltsim.x" label
    • Why do you need the "selected [fltsim.x] title" column? Isn't it always going to be the same as the item selected in the main listbox? If not, use of this page could get quite confusing.
    • Do you need both text boxes and combo boxes for display of model, texture and air files? A combo box normally displays the currently selected item in its text field, making the text box above it superfluous.
    • The title for the .air file section is "currently assigned flight model". While this is not incorrect, you refer to it as "Airfile" on the tab header. To avoid confusion, why not use "Airfile" (or whatever) in both places.
    • The three buttons in the lower righthand corner of this tab become enabled even if there is only a single option available - and, hence, nothing to change.

    Offered the vein of being helpful.

    Don
 
I urge you once again not to use the .air file to control whether or not the AI variants are displayed in the Select Aircraft window. First of all, that selection applies to all variants in the aircraft.cfg file, whether or not for AI use. If someone uses that airfile for another aircraft (not an infrequent occurence among AI developers), it could take them a long while to figure out why their new aircraft won't display in the Select Aircraft window if you have so modified it. This capability is not well-known. I know of no other utility that includes it and the setting is not otherwise apparent. While I'm sure AI Aircraft Editor will appear on most FS-users' desktops, I suspect the effects of this feature will be frequent topics in your support forum. It appears you can acomplish the same thing for both FS9 and FSX by commenting-out the "ui_" items for the individual variants. (My last words on the subject.)

Don

I beg to differ. The .air is the standard way of stopping a FS9 AI Plane from showing in the select aircraft menu. This is still used by most freeware FP programs that add approved Models to there uploads and individuals that upload models on a single basis.

Open any model plane that is package with WOAI and we must reset the 105 flag in the .air file to see the plane in the list menu. This is mandatory to do when setting up a airport with ADE since we have to select the plane in order to place parking spots properly.

AI_Aircraft editor is not setting the precedence but must work with what has already been done with 1000's of AI Planes released since FS9.

Removing the UI's removes the name of aircraft from the selection list but the UI is also the tags used by all modlers to place their design name such as Arrdvark, AIG, TFS, etc. and logo's.

If you think no other utiity has this feature for setting the 105 flag which you stated then start looking at AITM or many of the other FP/aircraft utilities available for FS9.

(My last words on the subject.)

If this is your last words on the subject then please link me to your first words.

If I am missing the pro's and con's to what the .air file is for I would like to see what else you had to say.
 
Last edited:
[*]Currently, you use the combobox beside the FS9 and FSX radio buttons to quick-select the FSX\SimObjects sub-folder. It has no apparent purpose for FS9 (and still displays the FSX folder-set). Yesterday, I thought you were using it to allow manual selection of the FS9/FSX path - until you set me straight. You may wish to reconsider. FSX folder selection is easily done from the folder tree and likely will be an infrequent occurence. On the other hand, if Microsoft changes the registry location for the FS9 and FSX base folders in its next 64-bit operating system (as it did with Vista), your application will be unuseable with that operating system. Using this area for manual selection of the path to FS if your app. doesn't find it automatically would avoid that potential difficulty.

I think that for the time being we won't see any new FS version any time soon. Some words about the logic for this part of the program.

Using the drive and folder combo you can select every locally available folder. So this guarantees that AI-Editor is always usable, even if for any reason it can't find neither FS9 nor FSX.

The two radio buttons and the combo box are to be seen as shortcuts to specific folders. Clicking on FS9 will bring you to "..\<FS9-Dir>\aircraft" folder while clicking on FSX leads to "..\FSX-Dir>\SimObjects".

During program load I check if FS9 is installed. If found, the FS9 radio button is enabled. Then I check for FSX. If found, the FSX radio button is enabled and I check if I find the fsx.cfg and can read the SimObjectPaths entries. If yes, I populate the combo box. This is helpful for users who use additional fsx aircraft folder outside the SimObjects\* path. They can quickly navigate to those.

If FSX is not found, the FSX radio button is disabled, and if I can't find and verify SimObjectPaths entries the combo box is disabled as well.

[*]What is the purpose of the multi-line text box in the lower-left-hand corner which now displays the name of the .air file. Is it still needed now that you handle the .air file on the mt&a tab?

Here you see all airfiles assigned in the currently loaded aircraft.cfg. And here you can change the type between AI/Heli/Normal. While you select different [fltsim.x] sections you can see what airfile is assigned to it because the selection in the list box will change.

This is not the place where you can change the assignment of airfile in the [fltsim.x] section (sim='airfile'). This is done on the respective tab where you can also change texture, model and (in future) sound.

[*]I urge you once again not to use the .air file to control whether or not the AI variants are displayed in the Select Aircraft window. First of all, that selection applies to all variants in the aircraft.cfg file, whether or not for AI use. If someone uses that airfile for another aircraft (not an infrequent occurence among AI developers), it could take them a long while to figure out why their new aircraft won't display in the Select Aircraft window if you have so modified it. This capability is not well-known. I know of no other utility that includes it and the setting is not otherwise apparent. While I'm sure AI Aircraft Editor will appear on most FS-users' desktops, I suspect the effects of this feature will be frequent topics in your support forum. It appears you can acomplish the same thing for both FS9 and FSX by commenting-out the "ui_" items for the individual variants. (My last words on the subject.)

I developed that feature after a well known and widely used utility AI BBQ (click to see on AVSIm). If AI and non-AI variants are dealt within the same aircraft.cfg file, in AI-Editor you would have to make the change for all airfiles referred to. The issue I have always found discussed on several boards and also have seen myself was that AI aircraft were visible, not the other way round. But I make sure that this is thoroughly explained in the documentation.

You are using at least two font sizes in the various text boxes which, incidentally, are taller than necessary. If you standardized on the smaller font (which seems quite adequate) and re-size the text boxes, you could substantially reduce the height of your main screen (which solves half your problem with users with lo-res monitors).

The size is set identical in all controls. On my screen only the new one on the lower left side (with the airfiles) looks bold and although it drives me mad I have not yet found out the reason.:o But I will !
On my screen (1600*1200) the fonts are good readable, but I would not want to have them any smaller. Can you give me an example from your screen at what control the font seems to be smaller and where it seems to be larger, please.

  • Could you display the currently assigned model, texture and .air files for the selected AI variant without requiring the user to click the "fltsim.x" label
  • Why do you need the "selected [fltsim.x] title" column? Isn't it always going to be the same as the item selected in the main listbox? If not, use of this page could get quite confusing.
  • The title for the .air file section is "currently assigned flight model". While this is not incorrect, you refer to it as "Airfile" on the tab header. To avoid confusion, why not use "Airfile" (or whatever) in both places.
  • The three buttons in the lower righthand corner of this tab become enabled even if there is only a single option available - and, hence, nothing to change.

It was late in the night.... :rolleyes: I Think I know what you mean and have it re-designed. Better this way?

[*]Do you need both text boxes and combo boxes for display of model, texture and air files? A combo box normally displays the currently selected item in its text field, making the text box above it superfluous.

No, from a programmers perspective this is not needed. I do it this way because I have often received the feedback that this seems to be easier to understand on first look.
 
If this is your last words on the subject then please link me to your first words.

If I am missing the pro's and con's to what the .air file is for I would like to see what else you had to say.


Jim,

Don and I had a long post exchange on AI-Editor before our discussion went to the open forum. He was only indicating that this would be the last time he was trying to convince me :)
 
Jim, glad to see you haven't lost your way with words. You make it vary hard for me to leave those as "my last words on the subject". So, I'll be brief.

Removing the UI's removes the name of aircraft from the selection list but the UI is also the tags used by all modlers to place their design name such as Arrdvark, AIG, TFS, etc. and logo's.
I didn't suggest removal, but rather, commenting them out for that very reason.

Personally, I was previously unaware of this "standard" method (which, by itself, doesn't mean a whole lot). Virtually every AI aircraft I've encountered displays in my FS9 Select Aircraft window - most from major FS9 AI creators. And. it doesn't appear that Lee felt it necessary to include that capability in AFCAD 2.21. (I don't use AITM.)

At the risk of repeating myself, I fear this method will result in confusion that will substantially (and unnecessarily) increase the level of support required for AI Aircraft Editor. But then, I'm not going to have to render that support. My intent was to make Martin aware of a potential difficulty and to offer what appears to be a viable alternative - even though you don't seem to favor it. It's his program and he'll have to decide how to handle this issue.

Martin privately invited me to review and comment. If he wishes to release our e-mail conversations from yesterday, I have no objection. I'm simply trying to help - and I'll let Martin be the judge on that.

Don
 
I think that for the time being we won't see any new FS version any time soon
I was not referring to a new version of FS but, rather, to the Vista replacement OS now in beta and due for release in less than a year.

During program load I check if FS9 is installed. If found, the FS9 radio button is enabled. Then I check for FSX. If found, the FSX radio button is enabled and I check if I find the fsx.cfg and can read the SimObjectPaths entries. If yes, I populate the combo box.
If the registry items are not where you expect in the new OS, how will these radiobuttons get enabled. That being said, I agree your program will not be inoperative because, as you say, you can always select the folders from the directory tree.

Can you give me an example from your screen at what control the font seems to be smaller and where it seems to be larger, please.
The font in the text boxes in the first line under "current wing_span ..." is larger than that used on the left-hand side of the tab and in the line below. I haven't checked every box.

I look forward to the next version.

Don
 
I was not referring to a new version of FS but, rather, to the Vista replacement OS now in beta and due for release in less than a year.

If the registry items are not where you expect in the new OS, how will these radiobuttons get enabled. That being said, I agree your program will not be inoperative because, as you say, you can always select the folders from the directory tree.

I see what you mean, Don. But if this is the case, I will release a "Hotfix" (KB0815) :D

The font in the text boxes in the first line under "current wing_span ..." is larger than that used on the left-hand side of the tab and in the line below. I haven't checked every box.

You mean the label then? These are indeed smaller, but on my resolution too small for comfortable usage where you have to read and write.
 
You mean the label then?
No. I've sent you a screenshot via e-mail. (The forum limits the size of jpgs to an impracticably low resolution for this particular purpose.)

Don
 
Jim,

Don and I had a long post exchange on AI-Editor before our discussion went to the open forum. He was only indicating that this would be the last time he was trying to convince me :)

As I said AI-Aircraft is not setting a precedence on what will be done but has to work with what has been done for 6 years. Every aircraft editor that came along and worth the time to use sets the .air 105.

One of the only editors that did not set the flag was yRoute. Spacejock got a lot of mail asking for the .air 105 record be added so the main stream of AI users know what has to be done in order to get the model listing in the FS9 aircraft menu.

Models do not have the same datum point. You can take 2 identical B737-400's from 2 different modlers and they load differently into the parking spot. George would like to see the 2 A380 AI's available sit in the 40.1M parking spot the same but they do not. Setting up the "T" offsets on the ramp for one model does not even agree when the other A380 model if used. The same applies to Arrdvark models compared to EVAI, AIG or TFS. Some models place the nose wheel up on the pushback tug when FS places them in the parking spot. Set the exits for one modlers B767 and then load another modlers B767 using the same exit points. Watch what happens to Jetway and baggage loader placement.

Anyone setting up a large airport for parking must have access to the .air and make the model selectable in order to set up parking correctly. Once a airport is finished then we set the 105 record back to the no show in the FS9 airplane list.

Modlers like CDAI, AIG, FSP, CDJ, Arrdvark do not allow the FP people like WOAI, etc. to tamper with UI's since they use these in FS9 for their own identification.

The same applies to FSX. There are no FSX AI Planes that are freeware. All AI Planes being developed today are FS9 models and we import to FSX. If we want the FS9 model to list in the FSX aircraft menu we have to alias a panel in a added panel folder. Again the UI's are specific to the name of the model designer or group of designers.

Why is it everything is compared to AFCAD and what it will or will not do. AFCAD is a incomplete utility. There are many codes in AFCAD that were never finished since AFCAD stopped at beta version 2.21. The aircraft editor in AFCAD was originally for setting the model radius to correspond to the PAI standard parking radius scheme and not for setting the .air 105 record.

Lee work with AFCAD and Tom work with AITM/TTools. We at PAI tested and used both utilites together and each did not overlap the other since Lee and Tom kept a dialog going in the PAI AFCAD forum.

Most all the major AI plane suppliers set the .air to non-flyable. If AI-Aircraft cannot enhance /go forward with the existing aircraft editors that have been out there for 6 years then why use AI-Aircraft. If Martin removes code that 6 year old utilites still have and need then what incentive is there to use AI-Aircraft over the various versions of AITM or ACA.

AI-Aircraft has not even tap into the aircraftTypes.csv fields yet that other FS9 aicraft utilities work with and as Martin moves forward AI_Aircraft can become the utility for the future.

 
Back
Top