Eric and Curt,What kind of framerates are you getting with KDEN....I can only manage 12-15 fps?Mike

I use a framerate limiter at 30. With default aircraft it runs at 30, and with the PMDG J41 it's at 19. I do have airport vehicles off, and that may be contributing to my fps performance.

I know this thread is a few days old but I thought I would share my experience. I purchased this scenery via Flight1 just in case things didn't go so well. To start off, I have quite a few IS airports and am used to the bitmapping issue, which I did for KDEN. This only took me about 5 - 10 minutes so it wasn't too big a deal. Next, the in sim test. 30+ FPS with the iFly 737 in VC, all good there. Then came the night test. The good news about this part of the test, the buildings weren't dark or shimmering between dark and light (happens with my KMCI scenery). However, as posted above, the runway and approach lights were extremely bright. So bright, you would literally blind yourself while landing.I decided to email support and surprisingly, I got a response. The first response was check your bloom settings and graphics settings. I replied stating that I don't use light bloom or the enb series. It must not be my graphics settings as this is the only addon airport that I own with this issue. Well, I just got another response and it was "We're sorry, we don't know what is causing the issue then".So, thankfully with the Flight1 refund policy, I will be returning my product (first I've ever done). It's a shame that they either refuse to believe they have an issue, or really like the bright lights and think it's normal. Oh well, maybe another developer will come out with KDEN. As for me, I'm done purchasing from IS until they realize that they have an issue with this and other airports they have created.

However, as posted above, the runway and approach lights were extremely bright. So bright, you would literally blind yourself while landing.I decided to email support and surprisingly, I got a response. The first response was check your bloom settings and graphics settings. I replied stating that I don't use light bloom or the enb series. It must not be my graphics settings as this is the only addon airport that I own with this issue. Well, I just got another response and it was "We're sorry, we don't know what is causing the issue then".So, thankfully with the Flight1 refund policy, I will be returning my product (first I've ever done). It's a shame that they either refuse to believe they have an issue, or really like the bright lights and think it's normal. Oh well, maybe another developer will come out with KDEN. As for me, I'm done purchasing from IS until they realize that they have an issue with this and other airports they have created.

Well to them the approach lights are "normal" because that is how they designed it, so to them it seems ok or looks right, which is why they say they can't see any problem.I agree though, I am done with them and glad that I only went as far as the demo of KDEN and didn't have to go thru the refund process, but at least they offer it thru Flight1 just in case.On the subject of those approach lights, they did the same thing to KATL which is why I have never run their latest update of that airport. I am still running their first FSX version with one or two small updates installed, but not the last major update that causes the blinding approach lights. I have also noticed that Tropical Sim has gone to this style of super bright lights as well. About a year ago I got their SBGR Sao Paulo scenery and was so disappointed with the super bright approach lights, as well as the taxiway and runway lights. At least I now know that going forward I will probably start skipping anymore Imaginesim or Tropical Sim releases and just try to stick to my stand-by developes like FSDT and FlyTampa who's products are never a let down.

I don't understand why Flight1 would consider adding such an inferior product/company to their excellent line of products.Normally, a full refund policy, is offered on products that more than likely will not be returned. This doesn't make sense to me. Flight1 is going to be spending valuable time processing refunds, when IS has consistently demonstrated that their sceneries are just not that good.They have a demo. Download it. Try it. Then remove it.

While I have purchased a number of their products (including KDEN), I hope the ImagineSim style of operations go by the wayside. I honestly don't know why I, or anyone, purchases from a company that has no forum and doesn't care what their customers think. Their products could be better if they just listened to what people are saying. If they just had a forum where they responded to concerns, a good deal of these negative comments would disappear from places like AVSIM.I know a lot of people think that every scenery add on needs to be at the level of FSDT or FT. I don't and have purchased IS stuff because they create airports that I want. I'd rather have IS scenery than no scenery at all. Nonetheless, when people have real issues with their scenery, it seems like the guys at IS have extremely thick skulls and refuse to acknowledge problems even exist until their name is publicly dragged through the mud. I think it is actually pretty sad.

While I have purchased a number of their products (including KDEN), I hope the ImagineSim style of operations go by the wayside. I honestly don't know why I, or anyone, purchases from a company that has no forum and doesn't care what their customers think. Their products could be better if they just listened to what people are saying. If they just had a forum where they responded to concerns, a good deal of these negative comments would disappear from places like AVSIM.

I agree 100%. I assume they dont have a forum because they dont want to feel like they are pressed into responding to customer complaints/questions/requests. Going wiht email support is probably a lot easier for them because they can pick and choose what they want to reply to as well as not having a bunch on customer complaint issues posted on a forum for the world to see.Just another reason I prefer to do business with scenery developers like FSDT, FlyTampa, and ORBX, not just because their products are better looking, but because they dont give the appearance of hinding from customers. I dont even know how many emails I have sent to Imaginesim in the past with support related questions that never got answered and after a while I just stopped emailing and for that matter buying as well.

I know a lot of people think that every scenery add on needs to be at the level of FSDT or FT. I don't and have purchased IS stuff because they create airports that I want. I'd rather have IS scenery than no scenery at all. Nonetheless, when people have real issues with their scenery, it seems like the guys at IS have extremely thick skulls and refuse to acknowledge problems even exist until their name is publicly dragged through the mud. I think it is actually pretty sad.

I'm the same way. Granted it would be great if all developers had scenery that looked and performaned like FSDT and FT, sometimes I will settle for an Imaginesim or a BluePrint offering just because they are the only ones that make a particular airport I am interested in and having their version will be better than running the default. Your right though about the guys at IS having thick skulls. I still remember the problem years ago with KDTW that had pink looking apron/taxiway textures and the guys over there took forever to acknowledge the complaints and fix it. The same happened a while after that when TJSJ had waves going over the runway and they claimed it was fine. They eventually patched both the KDTW and TJSJ issues but only after many complaints and at that it still took them a while to do it.

However strange it may be, I'm pleased to read I'm not the only body who thinks IS support could be better. I'm doing a review of their WSSS scenery, and I have stumbled into autogen, mesh and coastline issues. The photo scenery to the south is covered with autogen while the screenshots show this shouldn't be the case, and probably because I have FSGenesis mesh installed, some of the default scenery "peaks" through the photo scenery because it's a higher elevation. Finally, I see rolling waves inside the photo scenery, and at other places, there is default terrain where the photo scenery supposedly has a coastline. I have asked them about it, but the eventual conclusion was "we have no idea why this" and that was the end of it. It would have been so easy to eliminate the autogen and mesh problems. Simply stick in an exclude rectangle. Problem is, that triggered all kinds of issues because I am too inexperienced to know what exactly it is I'm doing. Such a pity.I might buy their KDEN at some point, not sure when though.

And we should not forget to play fair at some vital parts: You can download a demo there and you can later buy the full version with a 30 day money back guarantee (when going via F1). These two things alone set up a very fair policy in my eyes. You can always improve the after sales support side, but since the financial aspects before are handled that well, one is complaining on an already high level and should be aware of this.I wouldn't call me a fan of their stuff and I also wouldn't strongly recommend them in the first place, but except for the maybe too high price on e. g. KDEN (when bought as single release, without the bundle sales) I have nothing to really complain about.Running a nice, but not perfect KDEN here now.The support related notes are of course valid, don't get that wrong.

And we should not forget to play fair at some vital parts: You can download a demo there and you can later buy the full version with a 30 day money back guarantee. These two things alone set up a very fair policy in my eyes. You can always improve the after sales support side, but since the financial aspects before are handled that well, one is complaining on an already high level and should be aware of this.I wouldn't call me a fan of their stuff and I also would blindly recommend them, but except for the maybe too high price on e. g. KDEN (when bought as single release, without the bundle sales) I have nothing to really complain about.Running a nice, but not perfect KDEN here now.

100% agree. This is why I purchased KDEN, because there's nothing to lose. I tried it to give it a chance, and honestly, if it weren't for the runway lights, I would keep it. If they finally fix those lights in the future, I'll purchase it again. Everything else about the scenery is fine for me. For me, scenery doesn't have to be FSDT quality, better than default is what I'm looking for. I also own almost every Blueprint scenery, and I love them. Cartoony or not, it's way better than the default airports they cover.

The support related notes are of course valid, don't get that wrong.

Right. That's where they falter the most in my eyes. If they had a forum (and monitored it), this thread probably wouldn't exist. In their attempt to control the public conversation about their shortcomings, they have actually lost control of the conversation. It is a lesson that similarly situated developers can learn from.

And we should not forget to play fair at some vital parts: You can download a demo there and you can later buy the full version with a 30 day money back guarantee (when going via F1). These two things alone set up a very fair policy in my eyes. You can always improve the after sales support side, but since the financial aspects before are handled that well, one is complaining on an already high level and should be aware of this.I wouldn't call me a fan of their stuff and I also wouldn't strongly recommend them in the first place, but except for the maybe too high price on e. g. KDEN (when bought as single release, without the bundle sales) I have nothing to really complain about.Running a nice, but not perfect KDEN here now.The support related notes are of course valid, don't get that wrong.

True. I own their KLGA, KATL and KIAD for some time now. While I'm not that happy with KLGA, the other two or just fine and I like flying into them, no complaints here.

I have read several times about this bitmapping issue with Imaginesim airports...is there a tutorial on how to fix this?Also I have noticed that when I reinstalled my 3d lights it made the runway approach light bloom issue alot better.Mike

Hello Mike,Saw your PM. The bitmap issue is something you will have to do manually. At first, it's a pain, but you'll get quick at it as you go.First, you must have the FSX SDK. Go to /Program Files/Microsoft Flight Simulator X SDK and find a program call imagetool.Open imagetool and select File, Open. Navigate to the KDEN texture folder (FSX Folder/Imagine Sim/KDEN/Texture.Next, open about 10 - 15 bmps, remember where you stopped at. Don't try to open too many as it will not work.Next, on every image, select in imagetool (I think the menu option is Image) then select create mipmaps. It will do it's thing quickly. Then, save the image and close it.You need to do this for every bmp in the texture folder to get rid of the shimmering.What 3D lights are you talking about, REX or A2A?

Shockwave A2A 3D lightsThanks alot for the help