Anyone know what may be causing this river to be in a trench?

There's a vector-based river with a bad altitude paramater in the bottom of that trench. It's mostly likely set to 0 AGL.

There's a vector-based river with a bad altitude paramater in the bottom of that trench. It's mostly likely set to 0 AGL.

Where is that info kept? Can that be edited?

Hardly, which scenery is that? Looks like sort of photo-real with default autogen. I'd contact the author and point out this anomaly to him/them.

Can be fixed if you have the sdk installed.Using a program such as SBuilderX, create an exlcusion poly of attribute exclude all hydro polys that covers the offending river. Using slew mode, slew your aircraft on the river banks at ground level and read the altitide (subtract the static height of the aircraft, IIRC about 4 ft for the C172). Create a replacement river in SBuilderX. If your FSX scenery is "real world", you can use Goggle Earth as a background in SBuilderX and trace the shore as a vector line. Go all the way around, both sides. It helps to turn on the QMID level 11 grid as the offending polygon will probably stop at the edge of any QMID grid it crosses. If your terrain is default or doesn't match Google you will have to slew the aircraft in FSX and connect SBuilderX to FSX and use the aircraft position to draw your line. If you use phototerrain skip this next step: Set the property of your line to shorelines generic lake. Now use the "make poly" feature in SBuilderX. This will add a new poly based on the shoreline you created. In poly tool set the poly to hydro generic river perennial. Set the all points altitude to the alt you determined earlier (make a meter or two lower so it's slightly depressed). Again if you have phototerrain skip this: using line tool break the shoreline where you crossed it from one bank to the other so you have two lines, one for each side. Delete any extra nodes. Then select all and compile. Place the resulting cvx bgl file into addon sceneryscenery or other sceenry area that is higher priority than the addon causing this problem.The main problem you can encounter is if the river needs to slope downhill. If that's the case you can split up your new river poly into a couple of polys and set the elevation lower as you go downhill I find a change of elevation of 1 or 2 meter is about impossible to see unless you are cruising on a float plane or boat. It's also possible to make a sloped poly, but I find the "stair step" method good enough without too much work, unless you have something like "rapids" where the river falls rapidly.If your fixed poly or shoreline needs to connect to some other ones (that are OK) it will probably take a couple of tries to get them to match up. Just connect SBuilderX to FSX and slew right over the joining points at high zoom so you can accurately move the node on your poly or shoreline to match the existing. (Tip: do this with just the shoreline first before you do the "make poly" step, so you just have to do it once.)scott s..

Scott, are you sure Neil has the expertise, will and time needed for the tasks you described above? I'm scenery designer, but I'd never want to spend even one hour to fix others work in any way. If this glitch is pointed out to the author, I strongly believe, he will fix it in his source files.

Scott, are you sure Neil has the expertise, will and time needed for the tasks you described above? I'm scenery designer, but I'd never want to spend even one hour to fix others work in any way. If this glitch is pointed out to the author, I strongly believe, he will fix it in his source files.

The answer to your questions would be no. lol I have sent a message to the Megascenery Earth publisher, but I am guessing they are not fixing what seems to be a product that is a few years old. Oh well, just sucks that it's my home airport that I used to fly from in real life. I guess I'll go back to UTX and ditch the photoscenery.Anyone else have the Massachusetts Megascenery Earth that can verify they see the same thing at KFIT?

Edited March 2, 201214 yr by neil0311

I didn't even recognize the area - so that's Fitchburg, huh? I did a photo shoot there a couple of summers ago, and it's on my scenery to-do list once the New England stuff gets underway.

Scott, are you sure Neil has the expertise, will and time needed for the tasks you described above? I'm scenery designer, but I'd never want to spend even one hour to fix others work in any way. If this glitch is pointed out to the author, I strongly believe, he will fix it in his source files.

I've done a number of fixes on UT USA and UTX USA and Can. Or even the default if you install mesh. For me it's easy to just fix it myself and move on. I think I pretty much posted to the UTX bug board when I found something. The holes I guess can be lived with but on occasion I've found the 32k spike. Granted, may not be a method for everyone. Then too I'm kind of an amateur geographer so I like exploring stuff in the sim and fixing stuff is an excuse to play around in Google Earth etc.scott s..

I didn't even recognize the area - so that's Fitchburg, huh? I did a photo shoot there a couple of summers ago, and it's on my scenery to-do list once the New England stuff gets underway.

Yeah, it's where I did my primary training and flew for a few years when I lived in the area. I live in the Atlanta area now, and I didn't realize what a great place New England and the adjacent areas are to fly in real life compared with Georgia and Florida. I was really hoping the Megascenery Earth would add some realism to flying that area in the sim. Kinda bums me out. Oh well.

Edited March 3, 201214 yr by neil0311

@ ScottUnderstood, but don't you agree that if one paid for a product, one can expect it to be more or less trouble-free. It's humans that create scenery and mistakes are always possible. But than, again, everybody would expect the authors to at least correct the issues pointed out by users, if even beta testers overlooked something. And here someone that is willing to repair something like this bumps into a problem. It's payware, I don't have this scenery. And even if I'd have it, still all I can do is make the correction just for myself, otherwise I may be in breach of EULA in case I want to help fellow simmers and publish it.And just a hit about scenery builder: It's capable of making sloped polys, but a bit complicated. For creation of sloped polys I prefer FSX KML where you can edit individual points easily. For positioning I'm using Google earth tracker that displays my current FS X position in google earth and make points of polys that way, save my GE made poly as a kml file, open it in FSX_KML, edit points altitudes and compile - much easier than Scenery builder.

FSX Kml is another good solution. I guess from using SBuilder and now SBuilderX for many years it is like second nature for me.scott s..

I wasn't trying to say SbuilderX is bad, only some tasks can be performed more efficiently and precisely with other tools. I somehow hate to calculate slopes in SBX to get a sloped poly. With many points it becomes complicated.

Also found some rivers on plateaus. Is this definitely a function of the photoscenery, or could this be something else being changed by the FSGenesis mesh or UTX, to fix the innaccurate default data that is now causing issues if Megascenery is using the incorrect default data?

...or could this be something else being changed by the FSGenesis mesh or UTX

When's the last time you opened the UTX interface? I've had some strange issues after installing scenery from time to time--nothing like yours, though--and, when I do, opening the UTX interface allows it to check for conflicts and correct them. Just a thought.Rich