FSDreamTeam forum
Products Support => Vancouver CYVR support FSX/P3D => Topic started by: Dicko on January 06, 2013, 07:18:06 am
-
Pre CYVR install FSX working perfectly, after install no buildings when approaching destination airport but jetways visible. No runway markings no taxiwat markings. This was departing CYVR and arriving KLAX. Not a happy camper!!!!!!! Couatl and addon manager present in the drop down menu and taskmanager indicates couatl.exe is running. Restart FSX again and all buildings are visible.
I would appreciate some advice.
Thanks
Andrew
-
Since nobody has reported this problem, it's difficult to see what can cause this. As a general rule, you should never, ever, "downgrade" anything in the Addon Manager. Install the Stand-Alone Addon Manager, to replace the correct versions, and try again.
Since GSX it's free to use at all our airports, there's no reason not to install it. From the GSX menu, you can enable logging of errors in the GSX Troubleshooting page, do that and, the next time it happens, post your Couatl.err log.
-
Seems strange that older version works and the new version seems to fail after a long flight and not allow the buildings, runways and taxiways to show only the jetways.
Can you please try doing what I've asked ?
-
I flew from CYVR without any issues, such a lovely job you guys have done, but on arrival to KSFO all the airport's buildings were gone, relocated myself to KLAX, no buildings either. Restarted the FSX, there they are, all fine. I tried manually restart Couatl from the menu nothing happened, tried clicking the Update, nothing either. I just enabled the error reporting so will report if and when it happens again.
-
Could you please check if it happens only if you departed (or landed) at CYVR or, if it happens even if you start a flight on another FSDT airport and land on another FSDT airport, without ever loading CYVR ?
-
After already spending a far amount of time trouble shooting the issue before the restore I will not reinstall CYVR untill a reason for this occurring is identified.
You can test this just as effectively even without reinstalling CYVR, but it's of paramount importance you have everything else from FSDT is current. Which usually boils down to installing all the sceneries, then GSX or the Stand-Alone Addon Manager as last.
If, under the most current configuration, you don't see the problem when departing from an FSDT airport and another FSDT airport (but you did noticed when departing or arriving at CYVR when you have it installed), that information it's useful enough to know for us, in order to at least figuring out what could cause it.
-
When I installed CYVR it updated the Addon Manger to the latest version so why is there a need to install it again after the scenery is installed?
There's obviously not need to.
But you said yourself you REMOVED CYVR and don't want to install it again so, in order to make a meaningful test with the OTHER FSDT sceneries, you should at lest be sure that everything related to the Addon Manager is updated.
You shouldn't try to figure out *what* is causing the problem, that would be our job. And, the information we need right now, is exactly what I've asked:
- Install all the other FSDT sceneries, except CYVR, if you don't want to (which is what you said)
- Then install the latest Addon Manager, just to be sure.
- Then try to make a flight from an FSDT airport to another FSDT airport, and see if you still have the problem.
This is what I've asked you to do, because this is what I need to know. If you were willing to reinstall CYVR (you said you weren't) it would have been enough to install it and make the "other FSDT-airport TO other FSDT-airport" test just the same.
But since you said you didn't wanted to reinstall CYVR, I've told you to install the latest Addon Manager, in order to be able to do that test without installing CYVR.
Regardless if you think the problem is the Addon Manager update as it is, it might not, because what it *does* changes depending if you go to CYVR or not, which is why I've asked to do THAT test in THAT way: it's because I might have a clue, but I need confirmation.
-
I then took a flight from KSFO to KLAX and the buildings were there on arrival! So the addon manager by itself (as you pointed out) didn't cause the issues but CYVR did.
I was quite sure of that.
Now, since you installed the latest Addon Manager, you have everything updated just as you had CYVR installed. I believe you should be able to install CYVR without any problem, because the problem was likely *going* there, is not the installer "broken" the other sceneries in any way. If you do that, I could send you some modified files to test at CYVR that might make some difference.
-
I then took a flight from KSFO to KLAX and the buildings were there on arrival! So the addon manager by itself (as you pointed out) didn't cause the issues but CYVR did.
I was quite sure of that.
Now, since you installed the latest Addon Manager, you have everything updated just as you had CYVR installed. I believe you should be able to install CYVR without any problem, because the problem was likely *going* there, is not the installer "broken" the other sceneries in any way. If you do that, I could send you some modified files to test at CYVR that might make some difference.
At the moment I have it only for FSDT airports but am seriously considering purchasing for use at all airports.
Thanks
Andrew
It's available at all airports as it is now. Nothing else to purchase or install. That's what makes it so great.
-
I don't really know what you are trying to say but I am a little hesitant to install CYVR as it is as finally my system is all OK again.
Your system has always been ok.
I departed CYVR and arrived at the other FSDT airports to find no buildings, I actually never approached Vancouver. By installing CYVR again would the same process happen as before with the same result? What is going to be different?
As I've said, the problem was probably *being* at CYVR, regardless if you started from there or landed there.
Can't you just BELIEVE what I'm telling you, and do what being asked ?
I obviously know what's inside the CYVR installer and what's inside the Addon Manager installer, and there's no difference whatsoever, except the actual scenery files, whatever is causing the problem, doesn't happen unless you GO to CYVR. Installing CYVR wasn't the issue in the first place, being there probably was, your latest test is giving me already confirmation of this, if you install CYVR I could send you some possible fixes to test, so the problem would not appear, but they obviously require having CYVR installed and going there, otherwise there's no point even trying.
-
bump
Don't you find a bit excessive bumping a message only an hour after your last one ? You know, people sometimes do silly things like eating, answering the phone or similar...
-
Being at CYVR means you started your flight there or landed there or flew in the vicinity of CYVR. So, being at CYVR may have somehow caused a glitch when you were at KSFO or another FSDT airport.
If I were in your shoes I would move your fsx.cfg file to another folder, then start FSX and let it create a new fsx.cfg file. Load FSX at CYVR and the aircraft you were flying. Don't change any settings within FSX.
It may look ugly but hey. My first guess is maybe there is a bad entry in your fsx.cfg file. You will have to reinstall your FSDT CYVR before you do this of course. So, if the buildings are all there then we can assume something in the fsx.cfg was bad. If the problem still exists we will have eliminated the FSX.cfg file as the culprit. And try something else.
-
Dicko, try the attached file, to be put into the FSX\fsdreamteam\Couatl\common folder, and see if it makes any difference. You'll notice the scenery will be build up a bit slower than usual when starting a flight or changing season, but that's normal.
-
I should note that I do NOT have CYVR, and this problem started after the release. I can depart any airport (including FSDT) and everything is fine, and when I get to an FSDT airport, no buildings. Happened yesterday PHNL to KLAX. I assume the problem lies somewhere in the addon manager, which I have installed the latest.
-
The problem is never the Addon Manager, because it doesn't handle the creation of buildings. You should instead check if the Couatl menu is still there when this happens and report back.
-
I too have had this happen, only at CYVR though. It almost always happens when starting at CYVR in the NGX, landing at CYVR in the NGX from another FSDT scenery the problem doesn't exist. Starting there with less memory intensive or default planes the buildings are there 8 or 9 out of 10 times.
-
Couatl stops responding on a long flight, it is in the menu but is non responsive. My question is why is couatl non responsive after a long flight with CYVR installed and responsive without CYVR installed??????
We are trying to understand it. It's hard to replicate, because it might depends on other addons installed, as if Simconnect itself was clobbered with data and couldn't keep trace with everything, so it stops talking with it.
-
I have other addons that use simconnect and they don't stop talking
That's not what I've said, I've said because it's stopping to talk with *Couatl* without any reason and without any error. It's not stopping to talk with the Addon Manager either.
The facts are simple, install CYVR couatl/addon manager becomes unresponsive but are present in the drop down menu, restore computer to before CYVR was installed but still with the latest couatl and addon manager and all sceneries work fantastic-that is the buildings and ground textures are present on arrival. I have done everything you have asked and as I said the issue remains because it hasn't been addressed.
You forget to say the most important thing: on YOUR system. The issue has been obviously addressed, and has been fixed for everyone, right now you are amongst a couple of users that still reporting it.
That doesn't mean we consider it closed, but in order to work on it and find a definitive fix that will work even on YOUR system, we must to be able to replicate it first.
-
Why would every FSDT airport plus gsx work flawlessly without CYVR and not with CYVR on my system?
If we knew exactly *why* it doesn't work on your system only, we would have fixed it already. What makes it different than *other* FSDT products, is the dynamic shadows, that none of them has, and that requires more traffic on Simconnect, which normally WORKS for everybody else.
Every single payware scenery works without issue apart from this particular scenery
Not a single payware scenery (including our own) has that feature.
.What have you obviously done to address the issue?
I've sent you a file to test:
http://www.fsdreamteam.com/forum/index.php?topic=7875.msg65241#msg65241
Which fixed the problem for everyone else (since it's now included as standard with the update) so the issue HAS obviously obviously addressed, fact that this hasn't *fixed* the issue on YOUR particular system, doesn't mean it hasn't been addressed.
As I've said, I don't consider the case to be entirely closed, but it's impossible for us to fix something we don't can't replicate in any way. If we at least get many other reports, we could at least see a pattern and start asking users what ELSE they have installed, and maybe find a source of conflict even without being able to replicate it.
But with no such reports, there's no much we can do. I can probably send you another file to test, but undertand that is just a blind shot, since there's no way I can replicate it.
-
I am having this issue as well. Buildings at fsdt airports disappearing with only gates visible. Started after installing cyvr. Downloaded and reinstalled latest addon manager and it fixed it until again now getting it at other fsdt airports. Think I May have to uninstall cyvr until this gets sorted.
As well I have not installed anything else as of late. This problem only started after installing cyvr. I also do not have any other scenery for this area.
Just saw that test fix file. Will try that on Wednesday when I am back home. Does this address coualt issue where it stops working?
Sent from my Samsung Galaxy Note 2
-
ìJust saw that test fix file. Will try that on Wednesday when I am back home. Does this address coualt issue where it stops working?
Unlikely, because it has been already included in the 1.1 update, I'll have you test a newer one.
-
I repeat I have DONE everything you have asked. I dont give a toss
Outrageous!!!
-
I repeat I have DONE everything you have asked. I dont give a toss if others work, mine doesn't. If a fix isn't available I respectfully ask for a refund, frusrated is an understatement
We'll keep sending you new fixes to test. We want to solve the issue, even if it affects just you another user right now. Refund is not an option, because it won't help anyone understanding the problem.
-
my gosh!...even if this product didin't work well for me, and very well for others, i would be totally happy to have contributed to those who created it, and say keep up the good work!
-
Try this updated file (put into the FSX\fsdreamteam\Couatl\common folder ) and please note if there's any difference.
-
ìJust saw that test fix file. Will try that on Wednesday when I am back home. Does this address coualt issue where it stops working?
Unlikely, because it has been already included in the 1.1 update, I'll have you test a newer one.
I did not have the 1.1 update installed yet. I just now installed it and will be flying to CYVR in a few from Salt Lake. Will let you know.
-
It happened to me,after I messed around with fsx config I just reinstalled add on manager
-
Try this updated file (put into the FSX\fsdreamteam\Couatl\common folder ) and please note if there's any difference.
Still the same, would you suggest uninstalling and reinstalling all of my FSDT sceneries?
Andrew
-
Still the same, would you suggest uninstalling and reinstalling all of my FSDT sceneries?
Don't do anything that I haven't explicitly said to do. To be sure you haven't made a mess, do exactly the following:
- Download and install the current Stand-Alone Addon Manager
- Replace ONLY the file posted above, don't do anything more.
-
As stated in the post above I tried that file and nothing changed. In the post you deleted I explained that couatl stopped responding after about 5 minutes from leaving CYVR. I downloaded the latest addon manager also.
The post was deleted because of the foul language you used. This was highly uncalled for.
You are not listening.........couatl stops working but only after CYVR install. Thank god for Acronis and a backup without CYVR!
I'm obviously listening. There's no need to revert to such extreme measures like Acronis backup. The problem is most likely that file I've posted, which is NOT used by any other scenery than CYVR which means, if you uninstall CYVR with its normal uninstaller, it should be more than enough.
However, that doesn't help anybody so, even if you are still the only one (maybe there are two users in total) with this problem, that doesn't mean we will not keep trying again, but you MUST keep CYVR installed, otherwise it's not use trying, because that file doesn't do anything without CYVR.
I'll send you another one soon, and another one too, until we find what is causing this on YOUR system only.
-
Check this updated file, and report of any changes (for better or worse...)
-
guess this update is for dicko only....?
-
Yes, the COUATL menu is still present. Seems the issue is not just limited to FSDT airport buildings, but GSX as well. When I departed KBUF(FlyTampa), everything was normal and visible. When I arrived at KBOS(FlyTampa), the covered stairways, as well as the marshaller's flashlights, were invisible. As stated before, I DO NOT own CYVR, nor do I have the demo version, BUT this did not start happening until CYVR was released.
http://i419.photobucket.com/albums/pp272/iforrage/-2013-jan-25-043_zps2a1a9a77.jpg (http://i419.photobucket.com/albums/pp272/iforrage/-2013-jan-25-043_zps2a1a9a77.jpg)
http://i419.photobucket.com/albums/pp272/iforrage/-2013-jan-25-061_zps8129c4b3.jpg (http://i419.photobucket.com/albums/pp272/iforrage/-2013-jan-25-061_zps8129c4b3.jpg)
http://i419.photobucket.com/albums/pp272/iforrage/-2013-jan-25-062_zps65a3f316.jpg (http://i419.photobucket.com/albums/pp272/iforrage/-2013-jan-25-062_zps65a3f316.jpg)
http://i419.photobucket.com/albums/pp272/iforrage/-2013-jan-25-063_zpsb5924569.jpg (http://i419.photobucket.com/albums/pp272/iforrage/-2013-jan-25-063_zpsb5924569.jpg)
The problem is never the Addon Manager, because it doesn't handle the creation of buildings. You should instead check if the Couatl menu is still there when this happens and report back.
-
However, that doesn't help anybody so, even if you are still the only one (maybe there are two users in total) with this problem, that doesn't mean we will not keep trying again, but you MUST keep CYVR installed, otherwise it's not use trying, because that file doesn't do anything without CYVR.!
That's three in total.
-
guess this update is for dicko only....?
It's obviously for anyone else (3 in total, as another user said) that has the same problem. With "the same problem", I mean exactly this and nothing else: products that stops working, but with the Couatl menu still visible.
-
Flew to SFO from YVR and no buildings, COUATL menu present, but I was unable to restart Couatl, call GSX or check for updates
-
Make it 4.......... sorry 6, wasn't allowing for the couple posting in the GSX forum of couatl not responding.
Whether they are 4 or 6 doesn't make the slightest difference, out of the total number of users. I would be more interested to know if the updated file made any difference for you.
-
Reinstalled Addon Manager and replaced the updated file provided earlier in the posts. Will report the outcome
edit - no issues this time, flew from yvr to lax
-
Were is this file? I flew from CYVR tonight..had buildings, quickly loaded up KLAX...had buildings, went back to YVR and flew the NGX to LAX, on approach ZERO buildings. Makes me upset, this Coluita engine or whatever is suppose to make it hard for people to pirate the software right, yet the people that actually purchased it get into trouble. All the Addon Menus and stuff was present, and after messing around with the Update and Restart engine I then got a CTD.
-
Were is this file?
In this thread, attached on a post I made, in the previous page. There are several post with that file attached, download only the most recent one.
-
Were is this file? I flew from CYVR tonight..had buildings, quickly loaded up KLAX...had buildings, went back to YVR and flew the NGX to LAX, on approach ZERO buildings. Makes me upset, this Coluita engine or whatever is suppose to make it hard for people to pirate the software right, yet the people that actually purchased it get into trouble. All the Addon Menus and stuff was present, and after messing around with the Update and Restart engine I then got a CTD.
I fully understand your frustration! Try the file and report back. I will try the file on the weekend when I get back.
Andrew
-
I'm having the same problems with CYVR buildings disappearing,
I'm thinking it's not CYVR but GSX is failing somehow, with GSX included for CYVR, with GSX fails it fails CYVR.
It's like CYVR goes into DEMO Mode.
I still have the GSX menus under FSX but they do nothing.
-
Same problem here. Did a a flight from CYVR to KSFO and there was no buildings at destination
-
I was using the file supplied by Umberto.
-
File is no good, this needs to be fixed. Starting to get beyond a joke...........
As you can see, another user (johnny_gitara) had this problem fixed with the new file. And I'veasked to you to report if this file made any DIFFERENCE, because maybe he had a problem, which is now obviously fixed, but you are having an entirely different one, so keep working on that file is useless in YOUR case.
You must have noticed something obviously different with the new file, but it seems you haven't. I'm asking this, to be sure you installed it correctly. Haven't you noticed *anything* different at CYVR with the updated file ?
-
I have been using CYVR since I bought it a couple of weeks or so ago. I have never had any issues with it and have always been impressed by the negligible demand on frame rate.
However, this morning I did a short run from Boundary Bay, about 10 minutes away from YVR and on arrival there were no buildings. I was on VATSIM at the time and luckily the runways were visible. When I exited and restarted FSX everything was back to normal. I then did another run from boundary Bay and this time the buildings stayed there or rather reappeared.
I am not sure if I have the update or not. How do I check that? Also, is there a way to force the scenery to update if you do not see it on approach? Without exiting and restarting obviously.
-
You can always click on "restart couatl". I flew yesterday from YVR to SFO and SFO airport was there, so no issues on dissapearing buildings at the destinations. Only thing that happened was the terminal building left of Westjet terminal was missing when i loaded the flight standing at the gate 4, but when i clicked on restart couatl everything went back to normal.
-
I have done 4 trips from CYYC to CYVR and 1 CYVR to CYYC and return to CYVR after using GSX for turn around, here is the results with the new file.
1. OOM warning beep at about 9.2 from CYVR then CTD
2. OOM warning beep at GATE 73, scenery was there. GSX worked.
3. 3 miles from CYVR 26R and scenery disappeared, at 2.2 miles it reappeared, GSX worked.
4. 2 miles, warning box computer has run out of available memory. scenery was there but GSX didn't work.
5. Orbx off, CYVR to CYYC then CYYC to CYVR, Approaching CYVR 9.3 DME airport appears lots of flickering,
3.9 DME no flickering, everything worked great, GSX worked good also, no stuttering when CYVR loaded.
Turning FTX back to default scenery seemed to work. In my opinion CYVR doesn't seem compatable with Orbx PNW.
I'll try a few more flights and see if there is any changes.
I have a 3.4 Ghz with 12 gigs of ram, and a Geforce 560 video card. I also have KLAX KJFK KDFW KLAS installed and never had these problems at any of the others,
LAX would drop the frames rates a bit but I expected that. CYVR has a lot of flashing of the scenery approaching the airport and at the airport.
-
Turning FTX back to default scenery seemed to work. In my opinion CYVR doesn't seem compatable with Orbx PNW.
Your test only proves that you have OOM with OrbX PNW and you don't have them without it, that doesn't obviously mean CYVR is not "compatible" with it. It only means that you already were at the limit of exhausting your memory, so you can't add OrbX PNW without casing an OOM, or you can't add CYVR if PNW is already installed, which is the same.
As explained, countless of times, there's no SINGLE addon causing OOMs, it's the COMBINATION of all of them and you settings which are probably too high, that cause OOMs. Fact that FSX will never use more than 4GB because it's a 32 bit application, is something we can't change. The only things you can change are:
- Lower your settings in the most dense areas
- Switch to DX10, which saves quite a bit or memory
- Don't use 4096x4096 textures.
- Use the CYVR 1.1 installation options to lower the texture resolution
-
I have never had to lower my settings for any of your other scenerys but CYVR was already lowered, No AI, No AS2012, No Autogen,
DX10 is out, I fly the PMDG MD11 and won't work in DX10
4096 textures worked before CYVR on KLAX, KDFW, KLAS, EHAM, PANC, now lowered.
already had the lower textures installed.
I have never had an "Out of Memory" warning before CYVR and have had my setting a lot higher than they are now.
The way I see it, No Orbx PNW, No AI, No AS2012, No Autogen, and poor textures everywhere but CYVR, or No CYVR.
I guess I'll never learn to stop wasting my money, Your other scenerys are great but this one has bombed.
hopefully in the future there will be a fix.....
CYVR deleted.
-
The way I see it, No Orbx PNW, No AI, No AS2012, No Autogen, and poor textures everywhere but CYVR, or No CYVR.
This is what you said before:
Orbx off, CYVR to CYYC then CYYC to CYVR, Approaching CYVR 9.3 DME airport appears lots of flickering, 3.9 DME no flickering, everything worked great, GSX worked good also, no stuttering when CYVR loaded.
That clearly proves that CYVR, by itself, is not a problem. I'm not saying PNW is a problem in itself too. It's just that you can't expect to stuff FSX without any limitations. SOMETHING you have to compromise. We gave you plenty of options in the 1.1 installer to lower CYVR memory footprint. Does all your other addons in this area offer such options ?
but this one has bombed.hopefully in the future there will be a fix.....
You really don't seem to understand. There's nothing to "fix" in CYVR, and if you use the 1.1 Texture resolution options, which you haven't said you have, to INSTALL it with lower resolution textures, for example 2048 for the scenery and 1024 for the dynamic shadows, it will result in CYVR taking LESS memory than KLAX.
However, "taking less memory", doesn't mean you it's guaranteed that you will never, ever, see an OOM, the KLAX area is way less stuffed of 3rd party addons before you would notice any problems at KLAX. But here, you must be more careful.
As I've said, try to lower CYVR textures at 2048 and 1024 for shadows.
-
Isn't it possible to make a dummy, "foolproof" setting in the add-on manager for CYVR, , I mean, a (scalable?) setting that will guarantee no OOMS or other mayhem etc., irrespective whether you run thousand add-ons or none? Kind of low-end system setting?
Then we could start analyze things from there.
BTW.:
1.Only few customers are reporting their sys specs. Is this irrelevant??
2. During installation about halfway, to my surprise, my screen turned black and installation slowed down. Later things got back to normal.
I'm running Windows XP on a high-end system.
3. I acknowledge your dedication and support but you react kind of irritated to your customers. As a professional software developer, which I assume you are, get yourself a spokesman!
I love your products!
Regards,
Charlie N.
p.s. unfortunately I have no time to test.
-
Isn't it possible to make a dummy, "foolproof" setting in the add-on manager for CYVR, , I mean, a (scalable?) setting that will guarantee no OOMS or other mayhem etc., irrespective whether you run thousand add-ons or none? Kind of low-end system setting?
It's not possible to "guarantee" anything. If an user is already fairly close to exhausting the memory limit in the CYVR area, even installing CYVR at its lowest settings will cause an OOM.
And of course, the installer can't possibly know how much memory a certain user is going to consume at a certain location, the only possible way would be testing it in game but this keeps changing, depending on the airplane used, even the weather coverage changes memory allocation, since fair weather it's one thing, 3-overcast layers with hi-res clouds is entirely different.
There's no other choice than letting the user configure CYVR at installation time, and I can't see how easier to understand the current options could be made.
1.Only few customers are reporting their sys specs. Is this irrelevant??
It is, but just in the general term of trying to suggest what might appear to be really a problem, not so much in relationship about how CYVR is. Is nothing special, it's just that it COULD take more memory than, let's say, KLAX, but it CAN be configured to take even LESS.
But being in an area fully stuffed with other add-ons, even when configured to take less memory than KLAX, OOMs can still happen, just because of the area.
. During installation about halfway, to my surprise, my screen turned black and installation slowed down. Later things got back to normal.
There's nothing in the installation that could cause that.
It's might simply due to the installation that took some time (rebuilding all textures takes time, especially if you choose 4096x4096 for everything), and so your power management turned off the screen to save power.
I'm running Windows XP on a high-end system.
I hope you use the 64 bit version (which is fairly uncommon, I have to say) because, on a 32 bit OS your problems would surely be amplified, especially on an high-end system, assuming with "high-end" you include an high-end video card too, because that is what is stealing most of your memory.
If you use a 32 bit OS, everything, including OS, FSX AND VRAM, will have to *share* the same 4GB address space, so you really have a bit more than 2GB available, while under a 64 bit OS, you would at least have up to 4GB reserved to FSX.
3. I acknowledge your dedication and support but you react kind of irritated to your customers. As a professional software developer, which I assume you are, get yourself a spokesman!
I don't think that having someone saying "I'll ask the developer", then disappear for some days, and then returning back saying "the developer has said he'll look into it", would do much good for users.
The only thing good about the Flight sim market, is that you CAN usually talk with the actual developers so they can do things for you and reply in the most effective way, do you really miss the "larger company" style of customer support, that doesn't have any other function of being a firewall between users and the developers ?
-
It appears that I owe Umberto a huge apology. The disappering buildings and the non responsive COUATL menu seems to be caused by a duplicate CYVR AFCAD in my addon scenery folder and this is why the issue occurred on my system when CYVR was installed. I have since removed that AFCAD and so far so good.
Umberto was good enough the refund my purchase. I have since re purchased the CYVR scenery.
This issue WAS my system so I have a bit of egg on my face!
Thanks
Andrew Dixon
Confirmed, the AFCAD was the issue not the scenery :-[
-
3.
The only thing good about the Flight sim market, is that you CAN usually talk with the actual developers so they can do things for you and reply in the most effective way, do you really miss the "larger company" style of customer support, that doesn't have any other function of being a firewall between users and the developers ?
Uhh...no.
On the other hand, we flightsimmers, whether customer or developer, are quite a bunch of passionate guys. So maybe not a firewall, but one made out of ice could come in handy... ::)
-
You can always click on "restart couatl". I flew yesterday from YVR to SFO and SFO airport was there, so no issues on dissapearing buildings at the destinations. Only thing that happened was the terminal building left of Westjet terminal was missing when i loaded the flight standing at the gate 4, but when i clicked on restart couatl everything went back to normal.
I did that but nothing happened. It seemed to have been a random incident (I hope) because it hasn't repeated.
-
Unfortunately I have to report the same problem. I read this thread completely but am not sure what to do.
Recently I purchased CYVR (v1.1) because I was very happy with KLAX, Honolulu´s and Vegas.
GSX loaded my NGX at CYVR; I enjoyed the scenery and flew to KLAX. Upon arrival I found the airport completely empty except for jetways. Just like the demo after some time. I tried to restart Couatl, no luck. Addon manager showed both airports installed and registered.
Two days later I started at KLAX for my NGX flight to CYVR. Exactly the same happened: great departure airport, lousy arrival.
I have a high end W7/64 system running without problems. I do have Orbx installed.
I understand that a file was offered but that it is already included in version 1.1
What do you recommend? Thanks in advance.
Ronald
-
I understand that a file was offered but that it is already included in version 1.1
What do you recommend? Thanks in advance.
No, that file is not included in the 1.1 so, please try it and see if it makes any difference for you, it's attached to a message of mine in the previous page, use the most recent post (there are a couple of version)
-
I am very pleased to let you know that your solution worked. I replaced the 7.8 kB dot pye file by the 8 kB one and enjoyed a good flight from KLAX to CYVR.
Vancouver looked great upon arrival and everything worked (except for the returning message to cut engines while following the FM car).
Thanks for your help.
-
Today I flew the other way around: CYVR - KLAX.
Everything worked fine. So whatever you changed, it did the trick.
Thanks a lot.
-
Hello,
Got the Vancouver Scenery + Honolulu both at the same time last month, at the bigining I had to reinstall both sceneries to get them working (no buildings) it was working for a while, noe since a week I didnt fly there, today tried to do so I had no buidlings again in both sceneries, tried to reinstall more than 5 times nut no way.
As soon as FS loads in both sceneries calt.exe crashes & in addition to this FS is blocking for a sec or 2 each 4 or 5 seconds looks like its trying to load I dont know what & this is happening only in YVR & HNL. Noting that I followed all possible solutions in this topic.
Please any help?.
Thanks
Arslan
-
Could you please try with the file attached in this post:
http://www.fsdreamteam.com/forum/index.php?topic=7875.msg66247#msg66247
Put into the FSX\fsdreamteam\Couatl\common folder, overwriting the one with the same name that should be already there.
-
Already tried that, absolutly no change.
Thanks
Arslan
-
Try to enable Logging in the "Troubleshooting" page of the GSX Settings page. And check both the Couatl.log and Couatl.err files which are (hopefully) created after a crash. Then post the files here.
-
I wish you can tell me the steps in how to do that.
Thanks.
-
There are no "steps", just enable Logging in the "Troubleshooting" page of the "GSX Settings" page.
Then wait for a crash, and check the Couatl.log files and Couatl.err files which should have been created. The Troubleshooting page will tell you exactly where they are located on your system.
-
Here is the log for the crash
Problem signature:
Problem Event Name: APPCRASH
Application Name: couatl.exe
Application Version: 2.0.0.2348
Application Timestamp: 511a6b6c
Fault Module Name: couatl.exe
Fault Module Version: 2.0.0.2348
Fault Module Timestamp: 511a6b6c
Exception Code: c0000005
Exception Offset: 00002916
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Can you tell me where is this GSX Settings" page.
Thanks
-
Here is the log for the crash
That's the Windows Event Viewer crash log, not the Couatl log.
Can you tell me where is this GSX Settings" page.
In the "Couatl powered products" menu, under the FSX "Addons" menu.
-
I had to reinstall GSX to be able to see that menu, as soon as it loads it crashes.
.log
https://www.box.com/s/30g3gclf6x189ul001ee
.err
https://www.box.com/s/rdu46sf37menlkgsjags
-
Your logs shows you don't have the current version of Couatl.exe. Or, more precisely, your .err file shows an error from last week with a NEWER version of the Couatl.exe that what you are running the in LOG file which is from today.
Since it's not normally possible to get an older version when reinstalling (you said you just reinstalled), since the installers automatically downloads the most current version online, the only possible explanation is that your antivirus has mistakenly blocked the download of the current version of the Couatl.exe, so you are stuck with an older version which might not work when everything else is updated.
As explained in many other threads, you should:
- Download AND install with the antivirus TURNED OFF ENTIRELY
- BEFORE launching FSX for the first time, you have to configure the antivirus to NOT scan those files:
FSX\fsdreamteam\couatl\Couatl.exe
FSX\bglmanx.dll
Or, even better, configure it to ignore the whole FSX folder.
-
Actually, I followed all instructions that were given to other users before posting, I had unistalled completely my AV & win firewall was off when downloaded & installed.
-
Actually, I followed all instructions that were given to other users before posting, I had unistalled completely my AV & win firewall was off when downloaded & installed.
But since the log clearly shows you are running an older build (2337), while the current one, which is the only one we have available online is 2348, there's no other explanation that either you did something wrong configuring the antivirus OR something ELSE in your system has blocked the download. Could be an anti-spyware or a firewall too.
-
I didnt have no firewall no antivirus & no antispyware, I will try to install the latest coualt later & let you know.
Thank very much for assistance.
-
I will try to install the latest coualt later & let you know
You said you just reinstalled GSX. This would get the latest Couatl.exe automatically, unless something is blocking the download for some reason.
-
So what you can suggest to me?
-
Again reinstalled the latest Addon Manager, still not having airport buidings.
here are the updated files.
https://www.box.com/s/tbxgx91os818pocei1pz (https://www.box.com/s/tbxgx91os818pocei1pz)
https://www.box.com/s/jg8c9vq0jhftszt673k1 (https://www.box.com/s/jg8c9vq0jhftszt673k1)
-
Finally worked, I had to regenerate a new FSX.CFG
-
And again the problem is back, really anooying when ever we want to fly to or from YVR we are not sure if the sim will make it or not.
Coualt started crashing again, as soon as I select FSDT scenery it crashes.
Again here are my files with the cfg:
https://www.box.com/s/o8u8sma6yh3dcdei1qmu (https://www.box.com/s/o8u8sma6yh3dcdei1qmu)
Please help.
-
Again, the log clearly shows you are running an older build (2346), while the current one, which is the only one we have available online is 2348, I don't know what you did because your *previous* log show you finally had the 2348 installed, now you went back to the 2346 for some reason, the program surely doesn't go back one version by itself.
-
This was the same version that worked yesterday, dont know whats making coualt crashing again.
-
This was the same version that worked yesterday, dont know whats making coualt crashing again.
Ok, looked it better, the Couatl.ERR is from previous version, but it shows 23 February as a date, which means you never had any errors since then.
Are you sure you are still getting the SAME crash ? What, exactly, are you seeing on screen ?
-
Hi Umberto,
Got it finally, in my CFG if you can see I was isolating the Rotorcraft for a reason I dont know loll.
[Main]
User Objects=Airplane
SimObjectPaths.0=SimObjects\Airplanes
\\SimObjectPaths.1=SimObjects\Rotorcraft <<<<
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
ProcSpeed=10112
PerfBucket=7
HideMenuNormal=0
HideMenuFullscreen=1
Location=440,130,1480,908,\\.\DISPLAY1
Maximized=2
FIBER_FRAME_TIME_FRACTION=0.18
DisablePreload=1
Thank you very much & apologize for the inconvenience.
Arslan
-
Got it finally, in my CFG if you can see I was isolating the Rotorcraft for a reason I dont know loll.
You haven't isolated it, you introduced an error in the FSX.CFG, because you used two *backslashes* when C++ style comments are two *forward slashes* like this: //
Well, the net effect was the same, because FSX ignored the line with the error, so the Rotocraft WAS disabled just the same...
But in fact, the most standard way to add a comment in an .INI file (the FSX.CFG it's an .INI file), is to use a semicolon ; the double forward slashes // as used in C++ are not considered legal commenting command for INI files, even if FSX itself tolerates them anyway, but you might have problems with other utilities that works on the FSX.CFG using the standard .INI parsing functions, that might not be so tolerant with syntax errors.
-
All is clear thank very much Umberto.
-
had the same problems as above, after installed that pye. files departed and landed fine.
but, no terminal during "instant replay from FSX" wonder if this caused?
Thanks, amazing scenery got every single airport purchased from FSDT
Virtual China Airlines
Brandon
-
but, no terminal during "instant replay from FSX" wonder if this caused?
See this thread for an answer:
http://www.fsdreamteam.com/forum/index.php?topic=8299.msg67993#msg67993
-
Part of this problem might have to do with the PMDG 737 becasue I only have this issue of no terminal buildings when arriving at KORD in the PMDG 737.