General Category > General Discussion

All fsdreamteam airports became corrupt after updating KORD V2

(1/3) > >>

jb747:
Hi,

After I completed the update to KORD to V2 I found that all of my fsdreamteam airports (KORD,KJFK, KDFW, PNNL, and KLAX now appear to have corrupt bgl's.  I ran the check for duplicates and nothing shows up but I have, for example, the trees from KORD showing up on the taxiways at KLAX, etc..  Only the fsdreamteam sceneries were impacted.  KSFO is fine.

I assumed that since KORD V2 was the latest and greatest I could just delete the old and install the new (deleting the Couatl and add-on manager per instructions, etc).  Do I have to uninstall all of them and reinstall in a specific order? I know that when KLAX was introduced it had to be installed last but assumed that since KORD V2 was newer I was okay.

A little confused about this.

Cheers

virtuali:
That KORD update could have "corrupted" other sceneries, up to the point of having trees showing on the other scenery, it's plain and simply *impossible*

You must have installed something else that did this, and the fact it happened when you installed KORD, it was just a coincidence.

You can reinstall sceneries in any order you like, but if you don't have all the latest installer, you might want to download and install the Stand-Alone Addon Manager AFTER all the sceneries.

jb747:
LOL.  I expected that response regarding the trees.  Never the less, I have made absolutely no changes to my computer between having everything work and the corruption issue.  I just turned it on and loaded FSX.

So, I'll go ahead and uninstall and re-install everything which is not a big deal.  I'm glad to know that there is not an issue with re-installing things.  I always download the latest versions before I do that anyway.

Ciao,

jb747:
Okay,  Uninstalled the old.  Made sure no antivirus was running... downloaded everything new... and re-installed.  Everything shows up in the menu just fine but the artifacts are still there with all of the fsdreamteam sceneries.  Same deal... KSFO is fine.

Uninstalled FSX and all add-ons, then re-installed everything.. same result.

Removed all of the fsdreamteam sceneries and installed just one of them (KLAX) and tested.  It's corrupt.

Any other thoughts?

Ciao

virtuali:

--- Quote from: jb747 on January 20, 2012, 10:07:56 pm ---Everything shows up in the menu just fine
--- End quote ---

This means everything's fine with the installation, and should simply stop worrying about antivirus and any other install problem.


--- Quote ---but the artifacts are still there with all of the fsdreamteam sceneries.  Same deal... KSFO is fine.
--- End quote ---

I don't quite understand what do you mean with "artifacts", they surely can't be a problem of the sceneries, if they were, we would have heard many reports by now.

As I've said already, it's NOT POSSIBLE that installing a scenery would make problems with *trees* to ANOTHER FSDT scenery.

The only possible explanation for this, is that you installed SOMETHING ELSE, like a 3rd party vegetation "enhancement" package, which has meddled with the default tree textures, which is affecting all the FSDT sceneries that use them, either as Autogen or as scenery objects.

Fact you think it's happened after installing the KORD update, was just a coincidence, or simply because you checked the affected sceneries only after installing KORD, but the problem already happened when you installed the other thing.

OR, even if you haven't installed anything of the sort, it might simply be an issue of the default tree textures being corrupted for any reason (entirely unrelated to the KORD installer) on your hard disk, so any scenery calling some default textures will show problems.

The only thing 100% sure, it wasn't *caused* by the KORD update, because in case we refer to default textures (when the scenery use Autogen, this is absolutely normal) we never, ever, modify or touch the default files so, it must have been something else.

You might not see the other problem in other sceneries (KSFO, for example) because the different Land Class in that area might just call *different* default tree textures, which are not corrupted on your system.

Navigation

[0] Message Index

[#] Next page