In the next update:

 

1. An updated data base MTX_V60.myt , the current copy has some internal problems so that the autoscheduling does not work as expected.
2. Extra traffic in Heathrow.
3. 2000 United A320 type name corrected.
4. NFFN treated like a Chinese airport, this leads to some unwanted aircraft in New Zealand and Australia.
5. Updated installation instructions in distribution.
6. Communicator background screen corrected.
7. Changes to the editor to compile more schedules (less empty gates enforced @100% traffic density).
8. Changes to the editor to put "preferred flights" autogenerated with looser criteria to higher density settings (starting with 70% only).
9. MyTraffic Interactive to support the newest paints.

Anyone else getting the aiplayer.dll error ?

Rod,

 

I have all my 3rd party airports much higher up than you. I have no entries between Addon Scenery and Propeller Objects other than MyTraffic.

 

 

Ray, where are your stock Areas:

Reno

Istambul

Longleat

Berlin

Edwards_AFB

located

in relation to Addon Scenery?

 

By default I had these inbetween Propeller Objects and Addon Scenery Areas (FSX-SE stand alone).

 

Thanks,

Dirk.

Dirk,

 

All my stock areas are much lower down in Scenery Library (i.e. they have a lower number). As I mentioned in an earlier message prior to installing MTX6 I had no entries between Addon Scenery and Propeller Objects.

 

Rather than move all those stick entries just move Addon Scenery up so it's next to Propeller Objects.

 

Burkhard's instructions make it clear that's where the MTX entry should go.

Is it worth to upgrade from my 2013 performance wise? I have mt2013 by aerosoft and I'm fairly happy. I don't care about newest schedules but need busy airports and good performance. I run jet Ai only on 22% all other traffic off.

The schedules might have been updated but they aren't very realistic compared to real world. I'd stay with what you have and increase the Ai slider.

Well in EDDL area (my current hub) I have so many Ai aircrafts anyway that it's enough. I just thought that Mt 6 models are somehow better for frames

 

Thanks

I didn't notice any difference in fps with v6 but Traffic Optimizer will definitely give you a boost. It seems to work best with FSX:MS and can be found here. Be aware the author seems to have left the forums so support is from other users.

So would My Traffic 6 be a good program for model matching on VATSIM? I hate not having the proper models show up.

I didn't notice any difference in fps with v6 but Traffic Optimizer will definitely give you a boost. 

 

Thank you Sir! I will definetly try it :-) 

Dirk,

 

All my stock areas are much lower down in Scenery Library (i.e. they have a lower number). As I mentioned in an earlier message prior to installing MTX6 I had no entries between Addon Scenery and Propeller Objects.

 

Rather than move all those stick entries just move Addon Scenery up so it's next to Propeller Objects.

 

Burkhard's instructions make it clear that's where the MTX entry should go.

 

Ron, I've had no problems with MTX6 so far. My question was about how come we ended up with different enumration of the stock areas in the stock scenery.cfg? What seems to be the problem so to say?

 

Thanks,

Dirk.

Ray, where are your stock Areas:

Reno

Istambul

Longleat

Berlin

Edwards_AFB

located

in relation to Addon Scenery?

 

By default I had these inbetween Propeller Objects and Addon Scenery Areas (FSX-SE stand alone).

 

Thanks,

Dirk.

 

Dirk,

 

I was relying on my memory yesterday. Having now looked at my scenery.cfg I have the following entries:-

 

[Area.114]

Title=Propeller Objects

Layer=114

Active=TRUE

Required=TRUE

Local=Scenery\Props

Texture_ID=

 

[Area.115]

Title=MyTraffic

Active=TRUE

Layer=115

Required=FALSE

Local=C:\MyTraffic Professional\MyTraffic

 

[Area.116]

Title=Addon Scenery

Layer=116

Active=TRUE

Required=FALSE

Local=Addon Scenery

Texture_ID=

 

Areas higher than 116 are all additions by me.

 

I can't find any reference to those places you listed in the default scenery.cfg. If those are 3rd party addons they should be above Addon Scenery (116). Not where you have placed them.

 

 

Ron, I've had no problems with MTX6 so far. My question was about how come we ended up with different enumration of the stock areas in the stock scenery.cfg? What seems to be the problem so to say?

 

Who's Ron? My name is Ray. :wink:  I would suggest those entries are there on your system because that's where you positioned them. By default, new entries will be positioned at the top of scenery.cfg. i.e. they will have the highest Area number.

 

If you look at the original scenery.cfg in the FSX root folder you'll see the last entry is 115. Addon Scenery. All user-added scenery will be placed above that.

 

I can't find any reference to those places you listed in the default scenery.cfg. If those are 3rd party addons they should be above Addon Scenery (116). Not where you have placed them.

 

Ray, these are not 3rd party, they are stock and have always been there in all FSX iterations in scenery.cfg, at least in my case:

 

Reno

Istambul

Longleat

Berlin

Edwards_AFB

 

Dirk.

Dirk,

 

They're not there in my version. I had an early one, not Acceleration. Perhaps they were added in that.

 

Incidentally, it's Istanbul.

 Those are part of Acceleration. Either way, they don't impact how MyT operates.