2.0 MSE California  and Nevada sceneries don't fit well on lake Tahoe :

 

Am I alone with this lake split in two parts ?

Kind of knew this would happen and similar situation on Arizona and Utah border with lake powell area. Things this that are fixable with updates and bluesky can cover it up

Goose Lake on California/Oregon border needs also a patch from MSE :

Gonna be eye sores with the product sometimes as the photos were taken during different times of the day or different part of the year. Think post processing featheredge coloring would help we did this painting quarter panels on cars to hide paint lines smooth out small color differances.

 

Overall, like mega earth states as can use vfr charts online and see realty on the ground after 1500 agl think looks great. Blemishs and all in long term it makes easier to create real scenery. Does not end just the photoscenery installed some of us will build landmarks, spawn powerlines, realign airports.

There are a lot of anomalies like this.  I found them at the Maryland/Virginia borders.  Have you tried moving Nevada above California, Oregon above California in the Scenery Library?

 

Best regards,

Jim

Yes, Jim. I have reversed the order in the scenery library and got the same bad result on both lakes.

Just wanted to check to be sure.  I had anomalies on the Virginia/Maryland Potomac River borders and moving Virginia on top of Maryland helped some but did not fix the anomalies (a mess around the Woodrow Wilson Bridge!).

 

Best regards,

Jim

Happily I can say I am not seeing it.  But then again I am mixing MSEv1 California with MSEv2 Nevada.  This is what I get... 

 

A few shots from the same angles as the original poster, then a few looking back at South Lake Tahoe.  Then I just had to throw in a few a dusk.  No way am I giving that up for v2 and "lakelines"!

 

This is in Prepar3D.

 

Clutch

 

Unacceptable imo. It doesn't matter if it's a huge area of photoscenery. Little niggles and bugs should be found and fixed. It doesn't seem like they did any testing. Just took simsavvy and broke it up into individual packages. They probably could have launched them all at once but spreading it out week by week generates more sales and creates demand

"Unacceptable imo"

 

+1

I hope they fix this...

 

Thanks for the updates. The Lake Tahoe issue is known. Thanks for pointing out the other one.

This thread has been forwarded to the appropriate persons working on the MSE project.

Here is another anomaly along the Oregon-California border.  This one near the border at the Pacific coastline, between Brookings, Oregon, and Pelican Beach, California.  The first is a screen shot from FSX / MSE2 with both MSE2 Oregon and California installed.  The general anomaly is inside the light blue oval.  You can see the distinct border between the two sceneries inside the yellow oval.  The second image below is from Google Earth for the same area.   Some of the state line borders are even more pronounced.  In particular I notice a significant color difference when flying east from Indiana into Ohio.  Some of these variances I can accept, but those such as Lake Tahoe, Goose Lake, and this coast line anomaly should I believe be addressed.

 

 

This all just begs a question from me.  How do Ultimate Terrain X and MegaScenery Extreme 2 work together?  I did some searches tonight here on Avism, and then some general Google searches and only came up with a few discussion from the early MegaScenery days.  Like 3 to 5 years ago.  I have a generous compliment of MSE2 states that connect via the routes I frequent from coast to coast, and all of my city sceneries are positioned above MSE2 states.  My UTX is positioned below all of my MSE2 sceneries.  If I stick to flying in my MSE2 states then do I need to leave UTX selected in my scenery library?  What are the implications?

 

I expect that UTX has no effect on the MSE2 state to state transitions like those seen above or like this transition from Nebraska to Kansas.

 

So no news on Lake Tahoe yet????