Sign in to follow this  
Dirk98

Problem at KSJC FSX by Imagine Sim

Recommended Posts

Guys, I bought KSJC some time ago and found this airport hardly playable because of the following problems:

 

fsx2012-08-2802-26-15-71.jpg

 

Also, when I start my flight at KSJC the scenery seems ok, except for the above, but if I fly from somewhere else into KSJC this is what I get:

 

fsx2012-08-3001-10-39-32.jpg

 

fsx2012-08-3001-10-41-80.jpg

 

fsx2012-08-3001-11-35-23.jpg

 

fsx2012-08-3001-14-43-19.jpg

 

If I change my view and look from above the textures look ok:

 

fsx2012-08-3001-14-34-20.jpg

 

As I mentioned, when I start my flight at KSJC the textures are ok:

 

fsx2012-09-0820-19-18-08.jpg

 

I don't know if it can be related but I checked the airport elevation with AFX and ADE, the stock APX15180.bgl shows 18.9 meters and afcad_ksjc.bgl by Imagine sim shows 17.68 meters.

 

I had this problem without underlying MegaScenery Earth block CA-009 first, than I installed it under KSJC and found the same anomalities.

 

Thanks,

Dirk.

 

Also, for what it matters, my Scenery settings are as follows:

Mesh complexity: 91

Mesh resolution: 10m

Texture resolution: 1m

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Have you made sure that it is at the top of the library?

 

Also, have you downloaded the latest updates from ImagineSim?

 

It should fix the bumping on the first screenshot. Let's see if it fixes the bleed through textures of the underlying scenery.

 

Thanks, Ben!

 

Dirk.

Share this post


Link to post
Share on other sites

I have several ImagineSim Airports and I can tell you that 2 of them work correctly. KATL (I have version 1) and KCVG. If you do a search on the site you will see how they have repeatedly produced "broken" scenery.

 

Not a fan...been waiting over 2 years for fixes to the ones I have. Won't spend another dime with them until they fix what they have. Too bad really because they have many airports that I want to fly at and would buy.

Share this post


Link to post
Share on other sites

Unfortunately the latest update does not cure the elevation / underlying textures problem. I'm waiting for the next communication from ImaineSim in a few days.

 

Cheers,

Dirk.

Share this post


Link to post
Share on other sites

I used the pro version of ADE to raise the elevation of the entire field 1m and that fixed it for me.

Share this post


Link to post
Share on other sites

Scott, I have the pro version too. I open Tools and pick Change Airport Altitude in the menu. The default shows 17.68m. Please share how many meters (or feet) you put in there. Also, what did you do next? Did you just compile the Airport bgl? If it were the default airport I'd drop KSJC_ADEX_IP in Scenery\World\Scenery folder, but what to do for an add-on airport? Is there anything else needed to change or add?

 

Thanks,

Dirk.

Share this post


Link to post
Share on other sites

By any chance, are you using My Traffic?

 

No, I do not.

 

Dirk.

 

what is your mesh resolution set at ??

 

Mesh is set to 5m, can it be a problem?

 

Thanks,

Dirk.

Share this post


Link to post
Share on other sites

Some scenery needs a high mesh resolution set but you setting is fine. Too low can cause issues where the scenery needs it to be set higher. I dont know what to tell you to do and I hater to tell you this but dont expect ANY help from the ImagineSim team..... :(

Share this post


Link to post
Share on other sites

I'm having the same problem with Fly-Tampa Boston scenery. The altitude was set to 0 ft. It should be at 20. I will give this a try.

Share this post


Link to post
Share on other sites

I'm having the same problem with Fly-Tampa Boston scenery. The altitude was set to 0 ft. It should be at 20. I will give this a try

 

Leave Boston alone. It was set where it was for a reason. Read the Manual and it tells you why.

Share this post


Link to post
Share on other sites

Imaginesim just released updates for KSLC, KCLT, and KIAD that appear to have fixed these sorts of problems in FSX. Updates are on their website.

Share this post


Link to post
Share on other sites

Imaginesim just released updates for KSLC, KCLT, and KIAD that appear to have fixed these sorts of problems in FSX. Updates are on their website.

 

Dont have SLC or IAD, but I just installed the KCLT update. Glad I made a copy of my original CLT scenery and texture folder cause the "update" gives you the HORRIBLE looking landing and approach lights at night time. After the install I did a quick slew around at night facing the runways and they look like a horrible mess of overly birght lights. So bad that the runway looks like a solid sheet of light, not at all realistic. Runways are a lot harder to spot at night time and look nothing like that in real life. I didn't have any issues with the original KCLT so I will be going back to my last version. Plus they didn't even include the newest runway.

 

These guys really need to do something about the runway and approach lights. They did the same thing with the KATL update before they made the new version and I had to revert back to the older one. Makes you wonder what they were thinking when they design those lights if they think that it looks good or realistic. Maybe they should do an intro flight at their local airport at night to see how runway and approach lights really look like then revisit what they did. Doubt it though.

Share this post


Link to post
Share on other sites

Imaginesim just released updates for KSLC, KCLT, and KIAD

Thanks for the HU, Bob. About time. ^_^

Share this post


Link to post
Share on other sites

Dont have SLC or IAD, but I just installed the KCLT update. Glad I made a copy of my original CLT scenery and texture folder cause the "update" gives you the HORRIBLE looking landing and approach lights at night time. After the install I did a quick slew around at night facing the runways and they look like a horrible mess of overly birght lights. So bad that the runway looks like a solid sheet of light, not at all realistic. Runways are a lot harder to spot at night time and look nothing like that in real life. I didn't have any issues with the original KCLT so I will be going back to my last version. Plus they didn't even include the newest runway.

 

These guys really need to do something about the runway and approach lights. They did the same thing with the KATL update before they made the new version and I had to revert back to the older one. Makes you wonder what they were thinking when they design those lights if they think that it looks good or realistic. Maybe they should do an intro flight at their local airport at night to see how runway and approach lights really look like then revisit what they did. Doubt it though.

Gotta love ImagineSim..... NOT !!!!!

Share this post


Link to post
Share on other sites

I own all the latest versions of the ImaginSim sceneries for FSX and I can honestly say, the latest updates to KSJC and KCLT are now two of the worst performing airports I own. They now tank at around 8 FPS. I normally enjoy ImagineSim (for the most part) but I cannot understand why multiple copies of old AFCADs would be includ in the update-zip files without any installaton instructions. I too will be dumping the SP1 patches and turning back to the original 2008 installations.

Share this post


Link to post
Share on other sites

Your comments don't make me wanna try the updates. :Worried: I mean, I've already manually fixed some of my IS airports. KSLC. Wrong elevation, ILS detail and I think another item. At other places, I had to use that trick with the 'flipped' runway as the PAPI lights otherwise ate my framerate for whatever reason.

 

While the later IS stuff is ok for me, even good at times, those older things are troublesome. :mellow:

Share this post


Link to post
Share on other sites

Good catch!

KSLJC. Wrong elevation, ILS detail and I think another item.

The funny thing is that the freeware KSLC works just fine and the payware KSJC was in need of fixes. :Rolling Eyes:

Share this post


Link to post
Share on other sites

I just wanted to add a positive result. I've installed all the service packs Bob mentioned. Means for KIAD, KCLT and KSJC and they all work out. Well, except for the missing DME at KSJC which I've manually added.

 

Now what is missing is a list of detailed fixes. But there is a readme.htm in every zip file which mentions the rough ones. What's truly missing are some instructions. Now I had all previous updates installed, so the simple copy and paste action worked out. Don't ask me if that's the way to go of if you can skip the former updates in general. I guess. Would make sense.

 

I've loaded the airports at both, night and day. Just to check the lights and their fps impact. With the previous version, one received single digit fps at night and only a manual tweak helped. Now, it seems like it's working out of the box.

 

There may be a hurdle when it comes to the zip contents. For whatever reason, there is a AF2_KCLT_without_parked_aircraft.bgl and a AF2_KCLT_with_parked_aircraft.bgl in the zip. With both files ending at bgl, this could be one too much. I've disabled one. Same for KSJC.

 

So maybe the fps problems of some of you folks arise with those double files being active. Just guessing. I'm using FSX Acceleration on Win764 and all three airports performed nicely. By this, I'm happy to finally have some fixes for those older purchases of mine, replacing my rough edits.

Share this post


Link to post
Share on other sites

Thanks for the tip on the missing DME.

 

FWIW, both of those AFCADs (_with_parked_aircraft and _without_parked_aircraft) included in the update are "null" BGL files that contain no airport data--they appear to have been put there to overwrite both of the old AFCADs so that the new ADE file included in the update will not conflict with either of the old AFCAD files. And make sure you don't have a custom AFCAD lurking about also active, because double AFCADs *will* cause trouble.

Share this post


Link to post
Share on other sites

I think both AFX files should be removed, SG_AFX_KSJC_with and without, because KSJC_ADEX_ADE... is the afcad file

 

How did you add the missing DME?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this