I love FSDT and Flightbeam add on airports, but the one common denominator of both is that darn "Add On Manager". I don't like the way it fiddles with your FSX .cfg file whether you ask it to or not.

 

 

This is one of the worst airports I have bought.

 

It's not possible to buy something from us and not being satisfied, because as everybody knows, everything we sell is sold in Trial version. The Trial version doesn't ever expire, you can launch FSX, test with different settings, start it again, with no limitations.

 

Looking at our forum, I can see TWO posts from you, this one:

 

http://www.fsdreamteam.com/forum/index.php?topic=8242.0

 

Which clearly show you had problems with textures at KLAX, that also nobody else reported, and you haven't said if you finally fixed them, but of course everybody knows that KLAX does NOT look like that...

 

And one related to CYVR:

 

http://www.fsdreamteam.com/forum/index.php?topic=8905.0

 

Here, you are saying "all I get anywhere in the aiprort are graphical flashes and anomolies", but when you reported it in the proper place, you ONLY reported a place where two scenery tiles meets which is NOT something that is really specify to CYVR. ALL our sceneries are made exactly like that, and there might be places where this can be more or less obvious.

 

You haven't reported anything else so, are these the "graphical anomalies" that appears everywhere ( they don't, they only appear when tiles meet), and since this happens just the same with any FSDT scenery, and you have at least one FSDT scenery (KLAX) which is identical in this regard, either you have something else, which you should report, or it's not really the case you don't see this "anywhere else", because you surely have it at KLAX, and any other FSDT scenery, since they are all made that way.

 

Note that, this problem is more visible if you LOWER your settings so, by running "conservative" settings and low res textures, you are only making it more visible.

I love FSDT and Flightbeam add on airports, but the one common denominator of both is that darn "Add On Manager". I don't like the way it fiddles with your FSX .cfg file whether you ask it to or not.

 

This has been explained countless of times!!! The Addon Manager will NOT change FSX settings in the FSX.CFG without your intervention.

 

Those settings you see there, are the same setting you ALREADY HAD in your FSX.CFG, the Addon Manager is only reading them. In order for an FSX setting in the FSX.CFG to be changed, you must press the "Save to FSX" button, nothing will change until you do that.

 

Even if you didn't had any tweak in the FSX.CFG, it doesn't mean FSX doesn't have a default value that is used for that tweak when there's no entry for it in the FSX.CFG so, maybe, you are being mislead thinking the Addon Manager makes changes on its own, just because it "added" a tweak that didn't existed before. But unless you changed its value, the "added" tweak wasn't really "added", it was simply set to the default value that FSX would have used anyway if no tweak was there to begin with.

 

And, in any case, this happens only if you press the "Save to FSX" button.

 

The only tweak that is set without pressing the Save to FSX button, is the texture resolution slider, but here the Addon Manager is doing you a service: it's the ONLY utility out there that applies the setting in real time without having to restart FSX. The FSX.CFG is changed so the value will be saved for the next session too, but the change is immediate, because the Addon Manager changes the value in memory directly.

 

There are OTHER absurd utilities out there which makes all kind of foul things to your FSX.CFG: there's one I saw installed on an user system, which writes on the the FSX.CFG EVERY SECOND, to force the texture resolution, because the parameter is normally reset if you touch the FSX slider in the settings so, since they didn't know how to do it properly (like the Addon Manager does), they relied to this barbaric method of constantly rewriting the FSX.CFG!!! 

 

And you are worried about the Addon Manager...

 

There is another thread about the Addon Manager and/or Couatl modules. Everything that could be said about it has been said, and it was clearly proven how the Addon Manager is needed and useful for the sceneries, no need to start it again here.

This has been explained countless of times!!! The Addon Manager will NOT change FSX settings in the FSX.CFG without your intervention.

 

Those settings you see there, are the same setting you ALREADY HAD in your FSX.CFG, the Addon Manager is only reading them. In order for an FSX setting in the FSX.CFG to be changed, you must press the "Save to FSX" button, nothing will change until you do that.

 

Even if you didn't had any tweak in the FSX.CFG, it doesn't mean FSX doesn't have a default value that is used for that tweak when there's no entry for it in the FSX.CFG so, maybe, you are being mislead thinking the Addon Manager makes changes on its own, just because it "added" a tweak that didn't existed before. But unless you changed its value, the "added" tweak wasn't really "added", it was simply set to the default value that FSX would have used anyway if no tweak was there to begin with.

 

And, in any case, this happens only if you press the "Save to FSX" button.

 

The only tweak that is set without pressing the Save to FSX button, is the texture resolution slider, but here the Addon Manager is doing you a service: it's the ONLY utility out there that applies the setting in real time without having to restart FSX. The FSX.CFG is changed so the value will be saved for the next session too, but the change is immediate, because the Addon Manager changes the value in memory directly.

 

There are OTHER absurd utilities out there which makes all kind of foul things to your FSX.CFG: there's one I saw installed on an user system, which writes on the the FSX.CFG EVERY SECOND, to force the texture resolution, because the parameter is normally reset if you touch the FSX slider in the settings so, since they didn't know how to do it properly (like the Addon Manager does), they relied to this barbaric method of constantly rewriting the FSX.CFG!!! 

 

And you are worried about the Addon Manager...

 

There is another thread about the Addon Manager and/or Couatl modules. Everything that could be said about it has been said, and it was clearly proven how the Addon Manager is needed and useful for the sceneries, no need to start it again here.

Excuse me, but I have just spent two days reinstalling W7 and then FSX and all of my sceneries. I put my desired tweaks into my FSX .cfg, one of them being Bufferpools=0 Every time I go back to my cfg after placing my a/c at KDFW or KPHX, I go into the Add On manager and it shows BP=1 and a pool size, after exiting FSX I went back into my config and there were two lines added under my BP=0 entry, one was : BufferPools=1 and the other was a pool size.

 

If this is not supposed to happen, then please tell me what I am doing wrong and not being an expert like you, please tell me in layman's terms, how to use your add on manager so that my FSX config is "completely" as I edited it. This would make me a happy man

 

Regards,

 

 

how to use your add on manager so that my FSX config is "completely" as I edited it. This would make me a happy man

 

In laymans terms, simply don't use the Addon Manager. My FSX.cfg is always how I've left it.

It's not possible to buy something from us and not being satisfied, because as everybody knows, everything we sell is sold in Trial version. The Trial version doesn't ever expire, you can launch FSX, test with different settings, start it again, with no limitations.

 

Looking at our forum, I can see TWO posts from you, this one:

 

http://www.fsdreamteam.com/forum/index.php?topic=8242.0

 

Which clearly show you had problems with textures at KLAX, that also nobody else reported, and you haven't said if you finally fixed them, but of course everybody knows that KLAX does NOT look like that...

 

And one related to CYVR:

 

http://www.fsdreamteam.com/forum/index.php?topic=8905.0

 

Here, you are saying "all I get anywhere in the aiprort are graphical flashes and anomolies", but when you reported it in the proper place, you ONLY reported a place where two scenery tiles meets which is NOT something that is really specify to CYVR. ALL our sceneries are made exactly like that, and there might be places where this can be more or less obvious.

 

You haven't reported anything else so, are these the "graphical anomalies" that appears everywhere ( they don't, they only appear when tiles meet), and since this happens just the same with any FSDT scenery, and you have at least one FSDT scenery (KLAX) which is identical in this regard, either you have something else, which you should report, or it's not really the case you don't see this "anywhere else", because you surely have it at KLAX, and any other FSDT scenery, since they are all made that way.

 

Note that, this problem is more visible if you LOWER your settings so, by running "conservative" settings and low res textures, you are only making it more visible.

 

Hi Umberto,

 

Please don't mistake my problems with some product bashing post, that I not my intention. Yes, you are correct, I did have the opportunity of a demo, which I took advantage of and therefore I accept any responsibiity for not testing thoroughly enough.

 

However, the issues I have experienced have not been eradicated, except the resolution issue at KLAX. However the odd blue tiling continues, regardless of any measures I use to correct the issue, including reinstallation, new drivers, rebuilt cfg etc.

 

Reference to CYVR, the misaligned tiling that I reported is something that you agreed was within the scenery and something you could not fix. The issue I have mentioned in my post here relates to some kind of GPU overload or similar. It is not the scenery that appears with graphical flashes, but the entire screen. It's the same kind of issue that we sometimes find when using the Bufferpools tweak without setting a higher water slider setting. My point is that it only happens at CYVR and nowhere else. So?

 

Again, I really don't want to be seen as bashing your scenery, as I respect you as a developer... but, when we are talking opinions and exchanging feedback it's only fair I pass on my opinions, good or bad.

 

BTW: I'd be grateful if you could expand on this statement as I don't understand it, thanks... this problem is more visible if you LOWER your settings so, by running "conservative" settings and low res textures, you are only making it more visible

I love FSDT and Flightbeam add on airports, but the one common denominator of both is that darn "Add On Manager". I don't like the way it fiddles with your FSX .cfg file whether you ask it to or not.

Doesn't change my fsx. cfg at all

Hi Umberto,

 

I just stumbled upon this thread, and since your great CYVR scenery is one that I use fairly often, I would like to mention something that has bothered me for a very long time.

 

I'm fortunate enough to have an i7-3930K CPU coupled with a GTX Titan GPU, but regardless of my settings, when I get within a certain distance of CYVR and the airport textures load, the entire simulation comes to a complete standstill for a second or two, both in DX9 and DX10. There is no other complex scenery that I have that has a similar issue, even FlyTampa's complex Dubai scenery does not ever show such a drastic pause. As the bulk of the CYVR scenery doesn't load from the root structure or add-on scenery directory, but instead installs itself in the SimObjects directory, I'm wondering if this is part of the performance issue, as the SimObjects directory tree was perhaps never intended to contain scenery files.

 

Is there anything that can be done to alleviate the very annoying complete pause that happens when CYVR loads?

 

Best regards,

 

Jerome

In laymans terms, simply don't use the Addon Manager. My FSX.cfg is always how I've left it.

In the past I have done exactly that. This has not happened because I had the sudden urge to go play with the Add On Manager, I have just done a major hardware upgrade on my machine due to a failing Mobo and consequently had to completely fresh install everything from my o/s to all my FS software. I had spent many hours setting up W7 before even touching FSX, then very slowly and meticulously set "it" up, following all the advice of the gurus and their guides. I installed one by one my ad ons, followed each time a reboot. Everything ran smoothly and reasonably fast as per my freshly tweaked .cfg (I do not over tweak by the way), then suddenly after installing the add ons that use the add on mgr, my performance went south. I spent many hours trying to figure out the problem, until finally I noticed in my .cfg file, that added to my single BP=0 tweak, BP=1 & BP=####### (forget the value). Having removed these entries, I then loaded my plane at EHAM and got very acceptable performance, considering the reputation of that add on. Then I loaded CYVR ( bare in mind that I know what I was getting before I reinstalled) and again my performance went south. I then went into the A O M and low and behold, the BP slider was all the way over to the right (BP=1).

 

Anyhow, just for everybody's info, I uninstalled my airports (all from backup) and reinstalled from all fresh downloads from FSDT & FB and the problem has gone away.

 

I might not be the brightest bulb on the tree, but I know the basics of editing .cfg files and installing software and what was happening was not in my imagination.

 

Regards,

The issue I have mentioned in my post here relates to some kind of GPU overload or similar. It is not the scenery that appears with graphical flashes, but the entire screen.

You should have posted on the FSDT forum, which would be a proper place to walk you through some troubleshooting steps.

 

It's the same kind of issue that we sometimes find when using the Bufferpools tweak without setting a higher water slider setting. My point is that it only happens at CYVR and nowhere else. So?

As I've said, CYVR DOES put your GPU to more use. You surely must have heard the usual complain "FSX is outdated technology, how nice would be if the engine could use more of my $$$$-powerful GPU, like a modern game".

 

Well, CYVR, within the limitation of the FSX engine, DOES use your GPU more than any other scenery out there. This has been verified in many test, it's intended, and it's a *good* thing, because updating the GPU is easy and more power keeps coming, while updating the CPU is hard, complex and CPU power increase way slower over the years ( we already had 3.0 Ghz CPUs 10 years ago )

 

But there's the other side of the coin: because of this, CYVR is more dependent by a correct video card installation, by drivers, and by FSX.CFG tweaks and settings so, if any of these is not right, you will have problems and will be mislead thinking they are "CYVR problems", just because you don't seem them everywhere else, but just because old sceneries made with legacy code are so much more dependent by the CPU, that you can afford the luxury of running them even with bugged video drivers or wrong tweaks, and you won't see a problem. But this has an high cost on fps AND it doesn't offer room for growth.

 

This to EXPLAIN the issue.

 

To FIX the issue, please come to the FSDT forum.

 

 

BTW: I'd be grateful if you could expand on this statement as I don't understand it, thanks... this problem is more visible if you LOWER your settings so, by running "conservative" settings and low res textures, you are only making it more visible

I'm referring only to the "tiling" problem, the boundary is more visible if the texture resolution is low.

You should have posted on the FSDT forum, which would be a proper place to walk you through some troubleshooting steps.

 

 

As I've said, CYVR DOES put your GPU to more use. You surely must have heard the usual complain "FSX is outdated technology, how nice would be if the engine could use more of my $$$$-powerful GPU, like a modern game".

 

Well, CYVR, within the limitation of the FSX engine, DOES use your GPU more than any other scenery out there. This has been verified in many test, it's intended, and it's a *good* thing, because updating the GPU is easy and more power keeps coming, while updating the CPU is hard, complex and CPU power increase way slower over the years ( we already had 3.0 Ghz CPUs 10 years ago )

 

But there's the other side of the coin: because of this, CYVR is more dependent by a correct video card installation, by drivers, and by FSX.CFG tweaks and settings so, if any of these is not right, you will have problems and will be mislead thinking they are "CYVR problems", just because you don't seem them everywhere else, but just because old sceneries made with legacy code are so much more dependent by the CPU, that you can afford the luxury of running them even with bugged video drivers or wrong tweaks, and you won't see a problem. But this has an high cost on fps AND it doesn't offer room for growth.

 

This to EXPLAIN the issue.

 

To FIX the issue, please come to the FSDT forum.

 

 

 

I'm referring only to the "tiling" problem, the boundary is more visible if the texture resolution is low.

 

OK Umberto, I'll drop by the  FSDT forum, cheers...

Howard, 

 

I still completely agree, there is something about this scenery which I just cannot run. It's my biggest FSX headache and has been on different machines and installs.

 

Frankly it's the worse performing scenery that I have used sorry to say  

Well Alex, at least I know it's not me. I've posted over on the FSDT forum and I'll wait and see what Umberto comes up with. But with respect to the guy, to be frank, I really don't think he'll be able to offer a solution.

Howard, you and Alex don't have the same problems at YVR though do you?

Seems  strange that some people have  trouble  with cyvr  and others  don't  like me, havnt had  any problems  at all as of  yet.  So must be  some pcs  can handle  it  and others  that cant