If we want to disable some features

[cmpbllsjc]

Martin,

I just installed and included all options as the first test. I know that generally you say that if you want to turn off some options to re-run the installed and uncheck what you dont want. Rather than doing that can we just change the .bgls of the features we dont want to .bak and leave it at that.

If so, can you list what .bgls correspond to the ones that have the check boxes in the installer? I think I can figure out some of them just buy their names, but a list would be nice if you would to be sure I rename the correct one if I decide to turn something off.

Thanks

POST EDIT: If we do need to re-run the installer to turn off a feature like volumetric grass or something else, do we first need to deleted the contents of the scenery and texture folder, or just rerun the installer and uncheck those features.

[martin[flytampa]]

Just re-running installer is fine. It deletes the files that are optional.
I assume you are asking this for the FSX version:

_grasses.bgl (looks great but around 1.5 million polys not rendered all at once of course)

_terminal_veh.bgl (apron vehicles and objects)

_tram_anim.bgl

_cars_anim.bgl

cvxTAMPA_TRAFFIC.bgl (Generic FSX road traffic)

_fountains.bgl (water fountains)

_flags.BGL (skinned animated flags)

_water.BGL (airside water reflections)

grd_edgelights**.bgl (taxiway 3d units, but don't delete the grd_edgelights_halo**.bgl)

For changing the Tunnel from 3D to Flat I suggest the installer method.

[cmpbllsjc]

Thanks Martin and yes I was talking about the FSX version, I should have mentioned that.

That was exactly the info I was looking for and wasn't sure if the installer would either remove or rename a previously installed feature.

BTW, out of all your FSX products I own, which is everything except for the Grenadines and Kai Tak, I think this maybe your finest work to date and I can see why it would take you a year to do it.

[cmpbllsjc]

I forgot to mention that on my initial install I included all options and loaded up the PMDG 747 and flew a couple approaches with air traffic turned off to get a base line measurement and got good FPS, around 25 to 28 steady, until I was on the ground then the it dropped into the low 20's high teens, assumably due to the volumetric grass. Still though low FPS on the ground isn't a big deal while taxing since FPS on approach are what really important to me. Not to mention I was using the most FPS hungry plane I own.

Well done!!!

[cmpbllsjc]

Sorry one other thing. One the subject of the grass, is that the same thing as the grass bgl in Buffalo and Boston as well? I don't remember the installers in those two products giving the option to turn them off and if they are that many polys I may try disabling them for both of those sceneries.

[martin[flytampa]]

Boston I don't think had this type of grass. Buffalo has a similar method but not nearly as dense as Tampa. It is not worth deleting in those 2 sceneries.

At Tampa on the other hand, it should only be enabled if you have recent hardware (like I7 and NV4xx card). Anything older then 2 years or a laptop won't cope with the grass.

[wenham]

OK, thanks for the heads up!

[cmpbllsjc]

Boston I don't think had this type of grass. Buffalo has a similar method but not nearly as dense as Tampa. It is not worth deleting in those 2 sceneries.

At Tampa on the other hand, it should only be enabled if you have recent hardware (like I7 and NV4xx card). Anything older then 2 years or a laptop won't cope with the grass.

Ok thanks. Your right, I ran the Boston installer again and it had no options to turn anything off, but the Buffalo installer did.

As far as the hardware requirement, with all options checked and the conditions I listed above, I got those performance figures with an oveclocked E8400 at 3.85 ghz, 2gb RAM at 1066mhz, and a GTS 260 OC 1gb card, so the grass isn't that bad, even on my slightly older rig. When I switched to the LDS757 I got about 5 more FPS across the board which still gave me in between 28 to 33 FPS on approach and around 23 to 25 on the ground. Maybe if I wasnt overclocked it would make more difference, but not bad with the rig I have now.

Thanks for the help.

[martin[flytampa]]

2gb RAM is very little for FSX with Photoscenery and high-res texture Addons. You are probably seeing the "blurries" which I don't miss at all

[cmpbllsjc]

You are probably seeing the "blurries" which I don't miss at all

Not at all, believe it or not. I would have done another upgrade months ago if that was the case. Hang on for a minute and I will give you a few snaps as proof

[cmpbllsjc]

You are probably seeing the "blurries" which I don't miss at all

Not at all, believe it or not. I would have done another upgrade months ago if that was the case. Hang on for a minute and I will give you a few snaps as proof

Here's a few randoms with a few from the new KTPA. Anything that does look a little blured is probably a result of having just installed KTPA, KBOS, and KBUF within the past few weeks and not defragging. In fact my HD is probably really in need of a defrag after installing a bunch on NL2000 stuff. But all in all for the most part I never have any blurry problems, unless of course I am doing 600 Kts at 1000' agl, but even then the scenery keeps up pretty well on my "antique" system.

Anyways, once again, job well done on TPA, I love it

1.jpg (1.16 MiB) Viewed 13601 times

2.jpg (1.29 MiB) Viewed 13601 times

3.jpg (1004.71 KiB) Viewed 13601 times

4.jpg (639.91 KiB) Viewed 13601 times

5.jpg (655.61 KiB) Viewed 13601 times

6.jpg (897.09 KiB) Viewed 13601 times

7.jpg (907.99 KiB) Viewed 13601 times

8.jpg (1.04 MiB) Viewed 13601 times

[DJJose]

I must agree that this creation is their finest work. I'm blown away by all the detail and excellent performance.

I'm extremely thankful.

[big_al]

As usual another masterpiece. Everything you guys do is great! Looking forward to the next one

[martin[flytampa]]

Very impressive crisp shots cmpbllsjc