Some scenery help please

[lilduckfoot]

Hi Guys,

Need to query the brain trust here. Long story short...new fast PC, fresh dual installs of FS9 and GW3. All are working fine except....

I've insalled the Donationware FDg Corsair pack and the F-4U scenery that comes with it. The scenery displays as it should in FS9 but it's in a huge crater in GW3. I've installed FSG 36m mesh in both installs and believe they are positioned (prioritized) correctly in the scenery config files.

Can anyone point me ti a fix for the GW3 problem?

See the screen shots below. - Oh Well, don't seem to be able to post images.

Thanks,

lilduckfoot

PS, and thanks, WR, for the screen shot instructions.

[windrunner]

I can't help with your scenery ( do you have some added mesh around that may confliclt with somethng?), but to insert an image just copy the "http" adress inside the following code (but erase the "+" first) or click on the 4th icon on the second row of icons (the one between the globe and the email one)

[+img]insert adress here[/img]

[lilduckfoot]

Thanks WR. I'll post a couple of screens tonight.

BTW the only mesh I haven't disabled in GW3 is the FSG 76 meter. But I have it all activated in my FS( install and the scenery shows up perfectly.

LDF

[Dave3cu]

lilduckfoot,

Re. posting images-mainescenery.proboards.com/index.cgi?board=stick&action=display&thread=3341

The airport elevation issue is common when adding terrain mesh, and is not specific to GW3. Fixed elevations (airports. lakes and rivers) do not automatically adjust to the new elevations, their elevations must be 'corrected'. While payware mesh provides these 'corrected elevations (for default scenery), freeware generally does not.

From your description it sounds like the mesh installs in FS9 and GW3 are not in sync. Some things to check:

-FS9.cfg and FSGW3.cfg-check the following entry;

[TERRAIN]
.
TERRAIN_MAX_VERTEX_LEVEL=20 // 20 for 38m mesh
....................

-Check that you're not missing the appropriate <mesh>.bgl file in one of the installs. ( If you're using the FSG freeware mesh you can use a single install, point both sim scenery libraries to the same install. This will keep them in sync and make adding new mesh files easier. Not sure if this would be possible with the payware version).

-Scenery Priority-the sim will always use the highest resolution mesh available regardless of it's priority....with one exception. If you have 2 or more meshes with the same resolution (covering the same area) the sim will use the one farthest DOWN in the scenery priority list. If the F-4U scenery has it's own mesh you should place it below the FSG mesh in the scenery priority list.

Let us know what you find....

Dave

[lilduckfoot]

Hi Dave and thanks for the tips.

I have the free FSG mesh in one location with both installs pointing to the same files.

Here's where I get a little thickheaded, the "high and low" priority in the scenery library lsitings vs. the cfg list. I've read and reread "the Order of Things" and the way I understand that is the mesh should be at a lower number (file/layer) in the scenery cfg file than the addon scenery. So, in my FSGW3 scenery cfg I have the mesh at a very low number order and the F-4u scenery at the highest number, that is "number".

I've also renumbered all the scenery file/layer sequences in the scenery cfg to match based on the way I understand the "Order of Things"(and I've backed up everything 2 and 3 times over and stored them outside the sim).

I don't have a clue as to how the cfg order (numbers) corrlates to the addon scenery library list in game and the priority numbering system there. It seems to me they are totally oppsite, which, BTW, is the way it is in my install.

I will verify TERRAIN_MAX_VERTEX_LEVEL=20 // 20 for 38m mesh
tonight. I don't think it would be a missing bgl since I'm using the same mesh files for both installs and the FS9 install is working as it should.

Thanks again, Dave. I'll post results tonight and pics if necessary.

LDF

[lilduckfoot]

Well, Dave, the TMVL = 20 was set, so no joy there.

I've now removed all FSG mesh and have on other 3rd party mesh or terrain installed in GW3. Unfortunately that seems to have made difference either. I've un- and re- installed the F-4U scenery but Vella La Vela is still in a crater.

I really don't want to go through a reinstall of GW3 becasue everything else runs and looks great, and my tiny little mind can get a grip on what else it could be, so I'll just live with it the way it is.

Thanks again, Dave, for your interest and tips.

Steve

[Dave3cu]

Steve,

What's the geographic location of the F-4U scenery? (Is it Vella LaVella in the Solomons).

Dave

[Tom Constantine]

Steve-
Have you installed the Classic Goose or Golden Hawaii in FSGW? or any CFS2 scenery for the Solomans?

[lilduckfoot]

Hi Tom,

No Pacific scenery other than Midway Carriers, MAAM CVL 13, CVL27, and F-4U Vella La Vela on Munda in then Solomons.

However, I am using a common addon scenery folder for both my FS9 and GW3 installs, but do not have any addon Hawaii scenery.

I have all of the freeware carriers and flatten files loaded. Contemporary activated in FS9, WW2 and before activated in GW3.

I've checked and double checked scenery prioritys in their respective config files and can't see any issues.

Vella La Vela seems to be the only pacific area affected. The shore lines have the squared off "Saw-Tooth" look and the airfield is in a crater.

All the other pacific loactions I start in appear to be normal with natural shore lines and airfields and cities placed normally without any elevation conflicts.

Steve

[Dave3cu]

Steve,

The missing shorelines are another clue. It, along with the elevation issue, suggests that some addon which renders modified terrain has caused the problem. (the GW3 install does not mess with these files)

The default terrain files for Munda area:
Shorelines-...\Scenery\Ocen\scenery\ HL989340.bgl and HP989340.bgl
Terrain Mesh-..\Scenery\World\scenery\ demsol19.bgl

Two other possibilities I would investigate-

1-another addon is conflicting or following it's removal/uninstall did not return your gw3 install to it's previous state.

2-(and my favorite) The F-4U scenery installed new and/or modified files in your fs9 install that haven't made their way into your gw3 install.

Dave

[lilduckfoot]

Hey Dave,

Thanks very much for the tips. I'll check dates on those files you suggest against the stock files to see if anythings is amiss there.

As mentioned above, the only installs made that loosely coincide with the F-4U scenery problem is that of the free FSG mesh, USA 38m and 76m activated in both FS9 and GW3 from a common terrain folder outside both FS folders, and Ultimate Terrain USA/Canada/Alaska installed in the same common terrain folder and activated in the FS9 install only.

With regard to your "favorite" suspect, what files should I look for and where?

I've uninstalled and reinstalled the F-4U scenery a couple of times by 1st unchecking then deleteing it from the GW3 scenery library, and then deleting the folders/files from the GW3 folder. Currently the F-4U scenery is installed in the GW3 addon scenery folder with its own scenery and texture subfolders and is sitting at the top of the library priority list and verified the same in the scenery.cfg.

Thanks again, ya'll, for your comments and suggestions. They are very much appreciated.

Steve

[Dave3cu]

Steve,

Neither the FSG USA mesh(s) nor UT USA/... should have any effect on the F-4U scenery.

"....what files should I look for and where?" That depends on the methods the author used. Often new or modified files related to terrain are written to appropriate default folders in order to establish proper priority without requiring user input.

I downloaded 'FDGv2_f4u1_fs9_install.exe' from Donationware. Is this the package you're referring to? Although I can't complete the install (did not purchase) the installer setup might give some clues.

Did you 'install' the scenery to gw3 by pointing the installer at gw3?.....or by copying the scenery's folders from fs9?

Dave

[lilduckfoot]

Dave, yes that is the correct package. I unzipped / installed to a temporary folder and manually copied the files into the Addon Scenery folder inside GW3.

However, the scenery was working properly at one time in both installs, then came the problem with GW3 only. As of last night it still worked in the FS9.

[lilduckfoot]

UPDATE...

I gave up! I did a complete un and re-install of GW3. The new GW3 install was a piece of cake. Reinstalling some of my "key" addons turned out to be a real pain in the backside.

But it appears that it's over the hump and it's been smooth sailing for the last few flights.

I appreciate the interest and all the suggestions and tips from you guys, which I used in my feeble attempt to trouble shoot my problem.

Cheers,
Duckie