AI Aircraft Editor.NET Initial Release

[Stingray15]

Had it installed long ago

Seems problem is gone now. At least I was able to start it

[Firebird]

Martin,
Is there something that P3D users need to/should do if they move to a new version?

[gsnde]

No, Steve. AIAE.Net does not recognize P3Dv4 yet, but that only affects the recognition of the simobjects folders.

A real problem that I did not counted in is that if AIAE crashes on start immediately, the auto update will never bring the new version with fixes to the client.

[gsnde]

New version is online

[petebramley]

Hi Martin

Just carried out a virus scan (Avira free) and got this come up:

D:\Utilities\AI-Aircraft Editor\Assimp32.dll (SHA-256: 00247972a1dc7fc35e6011e8870e7c98315d3fd20ea48b8637381779cd701ac1)
[DETECTION] Contains suspicious code HEUR/APC (Cloud)

For now I have added it to my ignore list but do I need to worry ??

Regards

[Firebird]

That module is also used in MCX so my guess would be that that would also be flagged if you had that installed.

[gsnde]

Actually it is on board as part of the Model Viewer. You can be sure that Arno's modules are absolutely safe.

[petebramley]

I pretty much assumed that it was ok. just wanted to let you know in case others had problems

[phantomfreak]

Has anyone had any problems updating the editor? I get an error that the setup file is corrupt after I download the update. Also, I use Avast as my antivirus and it has blocked a few times as a potential threat.

[Firebird]

I confess that I haven't had issues with the update, it may be that you will need to uninstall and reinstall the app but I will let Martin say whether that is necessary or not.
I do know that Martin did have problems with some AV software blocking it but I thought that he had got that sorted out. I will have to defer to him again on the latest situation with that.

[pslinger]

I'm receiving some errors and I'm not quite sure what to do about them. I've read the PDF that came with AI Aircraft editor and I'm I'm unsure where to turn next. The AC Folder and AC Status: OK, however in the dialog box just above I am receiving the following messages in red text:
Error - Model file ... .mdl>>can't be read
Error - Model file ... .mdl>>not identified
FS9 is selected from the Sim dropdown menu and the aircraft were identified as FS9 aircraft when downloaded. I am only seeing the error with certain aircraft and not sure about next steps. Thanks

Paul

[Firebird]

Lest start with simple diags.
Choose one folder that has the problem. Tell us which one it is, then tell us how many model folder you have in that folder.

Now the second part, check in each of the model folders and tell us if they have only one mdl file and a model.cfg file in side or not. If not, then please list how many and what the mdls are called and which model has the problem.

Finally, if there are no model folders with anything other than one mdl inside what you need to do is check the model.cfg in each model folder.

What you should have inside the cfg file is something like this :-
[models]
normal=JYAI_EC145_Police

The file name after the normal= needs to match the mdl file inside the model folder. The normal parm DOES NOT need the .mdl on the end.

Now those are the basic checks. Let us know what you have found.

If you don't find something that you can solve then we will start checking other things. Once we have one folder done the cahnces are that you will be able to rectify the others.

[pslinger]

Hi Steve,
Everything you mentioned appears to be OK. The following are answers to your specific questions:

A folder with the problem:
JYAI A-10 Thunderbolt II Great Lakes ANG

How many model folders in the A-10 folder:
There are four model folders:
model.C_clean
model.C_combat
model.C_drill
model.C_ferry

Each model folder has:
One .mdl file with a name that corresponds to the folder name; Clean, Combat, Drill, and Ferry
One model.cfg file in each model folder

Each model.cfg has the following information:
Clean
[models]
normal=JYAI_A-10C_CLEAN

Combat
[models]
normal=JYAI_A-10C_COMBAT

Drill
[models]
normal=JYAI_A-10C_DRILL

Ferry
[models]
normal=JYAI_A-10C_FERRY

I hope the information is what you are looking for. Thanks for the help.

Paul

[Firebird]

OK I have copied the original folder from JYs package into my system and loaded up AIAE.
It shows no errors at all so if you have not made any alterations to your folder then I must conclude that the problem is not with the folder but with something on your system.

You should have the latest version of AIAE which is 3.1.10.0 so which version of OS are you running and are all your .Net versions up to date?
If you are running Win 10 the version number and build might help.

Also in AIAE if you hit File > Log-files a listing should pop up. If you could view and save that, zip it up and attach it here I could have a look and of course it will save Martin some time as well.

[pslinger]

Here are the answers to your questions:

Version of AIAE V.3.1.10.0

Operating System Windows 7 Home Premium version 6.1 (Build 7601: Service Pack 1)

.NET Framework:
1.1 version 1.1.4322
4.7version 4.7.02053

.NET Framework was just updated on 10/10/2017 (KB4043766)

Attached is the AIAE Log-file

Hope this helps.

Paul

[Firebird]

Continuing to diagnose.

What I have noticed is that the earliest time you had this problem was with your Airbus_A300-200 in April, although I can't identify which model it is to check against my system.

At first I thought the error was only produced by models by JY but this was quickly dismissed as I see that the last error is against a couple of B-52s.

My gut feeling here is that you may have stumbled upon a problem in Martin's program, but as I don't have it in my log file I am either very lucky or you could have a corruption in one of the modules.

Could I ask you to uninstall and re-install AIAE again and retry the folder and send me the logfile again please. This should rule out a corruption.

[pslinger]

I tried the uninstall and re- install of AIAE and the same error(s) re-appeared. I then re-installed JYAI A-10 Thunderbolt II Great Lakes ANG and the .mdl error disappeared; log-file attached

[Firebird]

OK I can see that that problem has gone away. I admit that I wouldn't have thought that you would have so many install issues though.

OK now the folders for the DM aircraft, as I saw that the 357th had the error earlier. If they do then try re-installing those one at a time and re-checking to see if the issue goes away there as well.

In fact lets try an additional step to see if you have an index problem.
If you have a problem with one of the folders then move it to another disk/drive/device.
Then copy it back and see if it has the same issue.
IF it does, then re-install from the original DM pack again and re-check.

The reason I am wondering about this is it is possible that you have a minor file index problem on your C drive. If you do it is nothing to worry about, we can fix that.

[pslinger]

Here is what I tried. I downloaded DM package and installed and checked the aircraft with AIAE after each install and the .mdl error still appeared. I back-up FS9 on an external drive and installed the DM aircraft from the external drive and the error remained. I don't know if this help or confuses the issue. Even though there is an .mdl error with the DM aircraft, they still appear at DM. However, even though I don't have an .mdl error with with Great Lakes A10, they don't appear at any of the based in the package. This would seem to suggest some type of issue with my computer.

[Firebird]

OK you seem to have two issues here.
Lets deal with your Great Lakes problem briefly. If you did not have this mdl check issue then you would automatically assume that the problem is one of the normal aircraft-not-appearing issues. That problem does not appear to have any relationship to your original issue and leave that to one side.

Now back to your main issue.
I thought that moving a problem folder might cured an index issue, as you effectively copy and delete the original folder and the index should be updated.
However, if that has not worked the next thing to do is to a chkdsk.

If you have never done one before you need to open up the Command Prompt with administrative privileges by hitting Windows+X and selecting “Command Prompt (Admin)" - just in case you didn't know how to do this.
Then the command you need to enter is :-
chkdsk /r c:

Now the C: disk is where you have FS9 installed so that is what you need to check. The 'r' switch checks and fixes index errors and also checks for bad sectors.
As your system runs from the C: drive nothing will happen. It will schedule it to run at next start up, so reboot and see if you get any errors and fixes.
Then try and check those folders again.