Military AI Works • All of my MAIW Traffic is gone and Also Traffic 360 to
Page 1 of 1

All of my MAIW Traffic is gone and Also Traffic 360 to

Posted: 30 May 2018, 20:02
by jpf813
Hello All,

A strange thing just happened today and I cant figure it out and wanted to get your suggestions and advice.

First, I was loading Tyndall AFB up to fly last night and none of the traffic came up on the ramp which I thought was odd. Maybe it was just that one package. Then I started checking all of my MAIW packages and no traffic at all, the files are still there and in the correct folder.

Then I noticed that none of my traffic 360 traffic was coming up, you cant even do the view aircraft tab which is standard with traffic 360. No traffic at any airports period.

I am really confused on this one, I don't think I did anything to change this setting, or is FSX just acting up?

The only major recent things I have installed were orbx products.

Finally, all my scenery for all of my MAIW packages and other payware scenery loads just fine.

Thanks,

Jon

Re: All of my MAIW Traffic is gone and Also Traffic 360 to

Posted: 30 May 2018, 20:35
by jpf813
Ok, so update on this. The Last MAIW package I installed was NAS Lemoore. Well, I just loaded it and all the the traffic was there and now the Traffic 360 is showing up to. So I figured I would try another base. I tried travis afb, no air force traffic at all and just two hornets from lemoore were on the ramp..

Any ideas? has this lemoore package shut down all of my other MAIW traffic?

Thanks,

Jon

Re: All of my MAIW Traffic is gone and Also Traffic 360 to

Posted: 30 May 2018, 21:14
by jpf813
Ok, final update, I noticed I had one fs9 lemoore file that I guess wasn't converted, I took it out and now the traffic on all bases seems to be working fine.

Odd that it would affect traffic 360 and all of the maiw files

Re: All of my MAIW Traffic is gone and Also Traffic 360 to

Posted: 30 May 2018, 21:51
by Firebird
Well I am glad that you managed to work it out yourself.

It is a well known phenomenon. It is simply because FS9 traffic files are different standard to FSX, and later, ones. So the two can't be mixed. In simple terms in FS9 the Week starts on Sunday and in FSX and later the week starts on Monday, so you can't mix them up.

The files have a header which tells the system if they are FSX or not. If it finds an FS9 file it will ignore any FSX format file.

Now you could ask why not just use FS9 format files then? In theory you could but a lot of the default airfields in FS9 had their ICAO id altered in FSX so you would need to convert the plans to the new ICAO id as well.
If you did that then it can all get a bit tricky so it is best to keep them completely separate and use the find FS9 traffic file function of AIFP and then use the tool to convert them to to fix your issue.

The reason that Traffic 360 files are affected as well is that they are in FSX standard so get ignored as well.