But the blurries issues is a bigger thing, somehow I think there is now a bigger demand on the PC to look for and find the correct textures to display.

 

 

 

Good point I hope thats the not the case

 

 

My thinking is that the latest move to unified, while it sounded great, means that we are totally locked into Orbx, "Captain of the World".

 

I've always felt that many of FSX's troubles are/were brought about because there are too many developers doing their own thing and no 'governing body' overseeing standards. So many different LCs, meshes, etc. etc. It's not surprising that some of these products fail to play nicely with each other. This, in my mind, leads to people poking around doing internal examinations in an effort to 'sort things out' (forgive my over use of inverted commas)

 

When Orbx comes along with a solution to Orbx's need to keep swapping regions the doo doo was bound to hit the fan. For my part I only have Orbx stuff and yes I know Pilot's mesh and Vector aren't truly Orbx, but you get my drift.

I have had no problems with migration and therefore no need to fiddle. When I install new scenery I run Vector AEC, job done.

 

Now if Microsoft had insisted that any add-ons complied with a standard or protocol, probably  a lot of angst could have been prevented....Or not.

 

Oi missus! Freshen my drink.

I've always felt that many of FSX's troubles are/were brought about because there are too many developers doing their own thing and no 'governing body' overseeing standards. So many different LCs, meshes, etc. etc. It's not surprising that some of these products fail to play nicely with each other. This, in my mind, leads to people poking around doing internal examinations in an effort to 'sort things out' (forgive my over use of inverted commas)

 

When Orbx comes along with a solution to Orbx's need to keep swapping regions the doo doo was bound to hit the fan. For my part I only have Orbx stuff and yes I know Pilot's mesh and Vector aren't truly Orbx, but you get my drift.

I have had no problems with migration and therefore no need to fiddle. When I install new scenery I run Vector AEC, job done.

 

Now if Microsoft had insisted that any add-ons complied with a standard or protocol, probably  a lot of angst could have been prevented....Or not.

 

Oi missus! Freshen my drink.

 

I tend to agree.  This does not explain why in my case, which is mostly Orbx. Global everything, Regions everything, dozens of airports. AND UTX Canada, USA, Europe properly located.

 

Simaddons, Canadian airports about 10.

Ozx all their stuff, which are airports.

Norway freeware.

REX 4, plus Soft Clouds

FS Addons compatible Tongass, Vic Plus, Van Plus

FS Genesis Mesh, NextMap

 

Nothing in this list should be incompatible. Forget weather, take away Mesh, what you have left are freeware airports, UTX might be an issue, but really shouldn't be as its Vector stuff with a few custom textures.

 

I know how they all interlink, how they are all working together.

 

But finally, I had no blurries before the migration, could fly my jets at 400knt with no issue, then migration, now issues of blurry textures over say 200 knts.  I can alleviate most blurries by locking down the frames to 25-30 from unlimited, so I can still get an amazing experience....however, it doesn't explain what happened.

I  had to re install all of ORBX and roll back to an old version of the library and now have perfect non migrated world again. What I really dislike is how JV turned up yesterday to mock a poster but no mention of a fix