FSDreamTeam forum
Products Support => Vancouver CYVR support MSFS => Topic started by: Kai-Uwe on October 16, 2020, 11:35:45 pm
-
Hm, it's a little bit strange: I can't fullfill a landing in Vancouver with your scenery is being active. I tried it several times, coming from KSEA, CYYJ or from the north. Even a great turn flying out via 26, turning over Vancouver town and back crashes the sim. About five miles from the runways away. Checking flying without CYVR from FSDT, means only with the stock one is sucessfull. Before this question is coming: no, there is no addon beside, the nearest ones are CYLW from FSimstudios and KPAE as freeware or KPDX from Flightbeam.
Maybe other ones are sharing this too? What can I do here?
Kai
-
I CTD Around KSEA. Its nothing to do with CYVR on my setup.
Even when I fly ILS from KBVS to KSEA I get CTD just when the ATC transitions me to KSEA tower or somewhere close like that. and KSEA is default airport. I have no addons for KSEA.
-
I can't see no connection to my posted problem ::).
-
Those airports are close enough that, since KSEA is a known crashy area ( it crashes on me too, even with nothing installed ) so you might be mislead it's caused by CYVR.
-
KSEA is an default airport, so everybody should have it. Should I deactivate it? Should that be a solution?
-
KSEA is an default airport, so everybody should have it. Should I deactivate it? Should that be a solution?
Maybe the problem is not the airport itself ( neither KSEA or CYVR ), but some AI with issues, possibly a missing texture or corrupted file. Do you have 3rd party AI additions, like livery packs, etc ?
-
Yes, I have some liveries installed. I will try it after deactivating them.
-
Even if I uninstall everything except the 3 FSDT sceneries I do CTD when I try to approach 08R in the default C172 EVERY time. No matter if I use the autopilot which would send me into the water or if I handfly the needles.
If I just remove CYVR I have no issue, not even if I use of my other >100 sceneries.
-
I'm sorry but, we cannot reproduce the problem in any way, and right now there are just two people reporting this.
-
Just tried the update with the A320NX mod, no CTD anymore.
Just one oddity, if I select 26R for the departure I still get placed at 26L.
-
Just tried the update with the A320NX mod, no CTD anymore.
Was quite sure the scenery didn't had anything to do with this.
-
I hesitate to say it's the latest update to CYVR, but since updating this morning I've experienced two CTDs, one of which was taking off from CYVR (shortly after initial climb on a C172). The other one earlier this morning I was nowhere near CYVR (en route from KEWR-KATL midflight in a King Air) but...again, the FSDT update is all I've done to FS today and I RARELY get any CTDs. Just letting you know...again, not assigning blame because I have no idea what's causing it. If it's possibly the update, may wanna check it out. I've sent the file dumps to MS/Asobo letting them know as well.
Thanks!
-
The other one earlier this morning I was nowhere near CYVR (en route from KEWR-KATL midflight in a King Air)
Not sure how this can possibly be related in any way to CYVR. It's just a plain scenery, there's no software we install in the sim that could possibly cause a crash.
-
Just tried the update with the A320NX mod, no CTD anymore.
Was quite sure the scenery didn't had anything to do with this.
Not sure I would say that. I permanently crashed when approaching 08R before the update. Now the one and only approach I did after the update was without a CTD, we will see, finger crossed.
-
2nd approach after the update, with the default C172 with analogue gages, autopilot ILS08R approach and a CTD so it's not fixed for me.
Let me know how to proceed, are there any log files I can send you ?
And BTW, again, I select 26R for the departure but got placed onto 26L, this also only happens when CYVR is installed.
PS: 3rd approach, 2nd CTD so no, it's not fixed yet ! Also this time I selected 26L but got placed on 13 !
-
The other one earlier this morning I was nowhere near CYVR (en route from KEWR-KATL midflight in a King Air)
Not sure how this can possibly be related in any way to CYVR. It's just a plain scenery, there's no software we install in the sim that could possibly cause a crash.
Update: For me, I reran the FSDT Live Update. The updater seemed to think I had not yet updated CYVR as it re-did all of the update. I made sure both times that it completed as expected, so I dunno. Either way, I entered the sim, emptied my rolling cache and then have flown several flights successfully since with no issues (including one into and one out of CYVR). Maybe something just didn't completely go right on the first install of the update...oh well...all good now. EXCELLENT scenery as always! Thanks! ;D
-
I had the same CTD issues with version 1, haven't bothered updating, since removing the scenery stopped any CTD in the area.
-
I too got another update today, at least now I get placed on 26R when I select 26R, at least there is progress !
For me there would be no logic reason why the rolling cache would have any effect to a CTD. I have done around 6 approaches to 08R today, only the first one after the update resulted in no CTD, all other still resulted in a CTD at around the same place on the approach phase, i.e. I can reproduce it on will. And there is still no CTD at all when I remove the scenery.
Not sure how my rolling cache should have any affect to it but I gave it a try and deleted my rolling cache ... but I still CTD when approaching 08R.
As there seems to be no interest from the developer to fix it I'm about to permanently remove the scenery too.
-
Let me know how to proceed, are there any log files I can send you ?
There are none, of course. I think you are misunderstanding a bit how different a scenery for MSFS is, compared to our FSX/P3D products. There's NO software we install in the sim. There's no "FSDT code" that could eventually provides some log we could check, it's JUST a scenery, so no, it cannot be the cause of your crash, unless there's a problem with the simulator itself.
And BTW, again, I select 26R for the departure but got placed onto 26L, this also only happens when CYVR is installed.
You don't have the current update, we fixed the runway start positions a few hours after release.
-
Just wanted to let you know that after Asobos update from yesterday and your latest update from yesterday I now was able to successfully complete 3 flights (with the default C172) without any CTD.
-
Just wanted to let you know that after Asobos update from yesterday and your latest update from yesterday I now was able to successfully complete 3 flights (with the default C172) without any CTD.
Our latest update surely didn't do anything to fix CTDs ( since they weren't caused by the airport, there's nothing we did or could do to fix them ) so, if they are fixed now, it was the Asobo update.
-
I have CTD's occasionally when approaching CYVR with this scenery. I was approaching 26L, short final, then CTD. Another time was approaching the airport from the south-southeast and when I got within 10 miles CTD.
-
I have CTD's occasionally when approaching CYVR with this scenery. I was approaching 26L, short final, then CTD. Another time was approaching the airport from the south-southeast and when I got within 10 miles CTD.
I don't know you are getting CTD with "this scenery".
You are getting CTD *at* CYVR, but that doesn't mean the problem is the scenery because, as you can see from last user post before yours, the user thought we fixed something because he stopped getting CTD, after an update of the simulator itself, which he assumed was something we fixed, but we haven't. This is just a plain standard scenery made only with 100% SDK methods so, it's either show up, or it doesn't, and in MSFS is basically impossible to have issues like CTD due to missing textures or invalid models ( which where possible with FSX/P3D ), because the SDK verifies every file and gives clear errors if, for example, a texture is missing or a model is not valid. In addition to that, sceneries sold on the MS Marketplace are ALSO verified by Microsoft before being approved.
What other add-ons are you using ? Do you have add-on AI airplanes, for example ?
-
I'm also getting CTD with 8R in my case. Several times I landed OK, but when I taxi to parking it will CTD. I know when this is going to happen because the sound starts to stutter and then the screen freezes...then the CTD. Happens the same way every time.
In my case, I wonder if my settings are too high for my 3080 card...I am running in 4K, with many settings set to ULTRA. I did set objects LOD to 125 (was 200) in an effort to figure this out.
I do think I'm overloading the memory and is the reason for the CTD.
Are there recommended GENERAL settings in MSFS 2020 for this scenery?
-
Just wanted to provide some positive feedback.
I have flown three flights now without a CTD. They were with three different planes, the 172, the TBM 930, and the Carenado Mooney. Here's what I did to get to a good starting point:
1. I turned OFF AI of any kind.
2. I turned OFF LIVE weather and used SCATTERED clouds.
3. I deleted my ROLLING CACHE and then increased it to 16 GB.
4. I set my LOD to 100.
5. I removed the G1000, G3000, and GX mods.
After these settings, I flew three flights, with the three different planes noted above, from KFHR to FSDT CYVR 8R. I did not have any CTD's and after landing, I was able to taxi to the South Parking and shut down.
I'm not sure which setting helped me and I plan to add one of the steps above, one by one, to try and figure it out. But, I do have a good starting point now.
-
Of course the problem didn't had anything to do with CYVR. There's a many pages long thread on Avsim about CTDs with the latest update:
https://www.avsim.com/forums/topic/592833-i-am-so-sick-of-this/
And reading the thread, it's clear that:
- Users are getting CTDs almost everywhere, there isn't a single scenery that can be seen as a constant
- Deleting the Rolling cache seems to be one of the most effective fixes
-
So sorry to say i am in the Boot but i am, and not only since yesterday this happens from the beginning i using CYVR ( Crash somehow )
Yesterday before i started a flight i deleted my floating cache and built a new on, mine is 100 GB, started the sim allover after that
and made a flight from KDEN to CYVR with an a320. (Flybywire ) But i think this mod isn`t the case.
Landing at 8R went fine ( didn`t work before on 8R always crashed short before touchdown ) so i got to the gates and the gates come in, ordered the Caterring Truck and Bagage Truck
all OK, at some time the Trucks moved away and BOOM Crash - could not understand what happens..
So i closed MSFS started again, pickt up 787-10 with no mod, setted the plane to runway 8R for start, than i had to go out of my computerroom in the kitchen
and this took around 5 mins or so than i come back and go sitting in my chair and BOOM Crash, i did nothing just sitting and can`t understand.. :o
I love this airport but i can`t us em, if i bin there since beginning with the first FSDT Version of CYVR i get this kind of crashes that i can not replicate..
I would i am not in the boat but i am - unfortynality; and i have no clou how i can go over that - real anoying !
regards ;)
-
See my above reply, with a link on Avsim indicating MSFS possibly crashing for no apparent reason basically everywhere, and see the last reply from flyblueskies, who said he completed several flights at CYVR without any crashes.
The scenery has been also approved by Microsoft, and I assure you they DO check thinks like crashes. Of course, they don't use any addons, which is the only safe way to be sure a single one is fine.
-
I had the same CTD problem as the last fellow. Started out at gate 21 with the A320 and after a few minutes CTD. Tried again after a re-boot, CTD. Tried again, quick start, taxi to 26L, CTD. Removed the scenery and no more CTD. Did not touch anything. It was like a timer was counting down and the CTD happened.
-
Started out at gate 21 with the A320 and after a few minutes CTD.
Tried to replicate your flight just now, here's a 20 minutes long video showing pushback from gate 21, taxi to 26L, takeoff, short circuit and manual landing on 26R, no problems whatsoever, other than some default ground vehicles not waiting during pushback, and silly atc clearing me for takeoff with a car on the runway but, other than that, I can see it proves CYVR doesn't cause any crashes.
I'm not using any add-ons, except for all other FSDT sceneries installed, and 2 UPS liveries for AI.
-
Is this the Asobos NEO or Flybywire ?
Mine is still crashing ,the only thing now i could try is to complitly move everything out the community Folder
except CYVR and try with standard Installation.
This is the only thing i didn't Test yet..
But so far ( only with your CYVR ) i got no probs at all and my Rig works superstable !
cheers ;)
-
By the way: I see a lot postings about CTD at CYVR, so are this still alive or do you guys fixed the problem/issue with some kind of a solution ?
Please reply !
cheers ;)
-
Is this the Asobos NEO or Flybywire ?
It's default, when testing if a scenery has a problem, it should always be tested with everything default.
Another common cause of users assuming a scenery has a problem, it's a problem with AI.
Due to different parking codes ( default scenery doesn't have any airline code, ours do ) compared to default, the kind of AI you see will change depending if you use default or the add-on airport. So, if one of your AI has a problem, and that AI doesn't appear in the default airport, or appears in different time/dates, you can be easily mislead assuming the airport has a problem, because if you remove the add-on airport, the problem might go away, so you can say "it happens only on that airport, I removed it and goes away, so it must be the airport", but it might be an AI with missing/corrupted/wrong textures for a specific livery.
I'll repeat it again, in case the 20 minutes long video I posted wasn't enough: this scenery has been released months ago in the MS Marketplace and, I can assure you if it really caused a crash on its own, it won't be approved because, while MS doesn't really question if a scenery is "nice" or not, they surely test from crashes.
-
OK i want to report back so i don`t make any bad blood here..
Maybe i am a lucky man but it isn`t 100% tested yet but looks good so far, the testing of last hours looking very promising 8)
I decided for me to focus on the AI Aircraft and i have a lot A320, 747-8 and 787-10`s in my community folder, so what to do ?
I leave the AI settings in the Sim to on because what is a Sim witout AI Aircraft so to have all emty Airports that couldn`t be the thing.
So i beginn with the A320 and took all my A320 out of the community so i have only the other leave inside.
So the first Test shows ( i setted my plane, an 787 ) to Runway 8R to start and drive it from there over the taxiways to the Gates docked on and ordered the bagage car and the catering truck
waiting they doeing her job and this all takes around 25 mins and therefore i got the crahes most off the time before.
OK i shut off the Sim checked around 15 off my A320 and found at 2 some anomalies in the ac.cfg file what i corrected.
This tested A320 liveries i than copied back for another start from the Sim and everything went OK - so looks good.
Now i have to check my other lets say 30 A320 liverys and copy them back over again also.
Now as i said not 100% shure but hopefully i get over it, will see but have a good feeling :D
cheers ;)
-
@Metrosz:
Seems to me that Vancouver has this problem with the ai. Not even other FSDT airports have this problem with the liveries. I even tried the Vancouver airport with the original livery (having no extra liveries in the sim) using the flybywire A32NX and it still exited without error every time between 3 minutes and 7 minutes after loading the scenery and being parked in the gate. I did the same at FSDT's KORD and it all worked well.
I believe FSDT should look into the scenery code and see what can it do to fix it as again, it's the ONLY scenery that does that.
I agree that as ASOBO updates their simulator, things can change. But as all the other scenery developers do fixes for their airports (i.e. Flightbeam just took out a fix for their Denver airport because of the latest Asobo update), FSDT should look int it as well. Again, KORD works perfectly with the flybywire A32NX with all the liveries I have, as do other payware airports I own for MSFS.
-
Seems to me that Vancouver has this problem with the ai.
A scenery cannot have a "problem with AI". If an AI is causing a CTD, the problem is the AI ONLY, it doesn't anything to do with the scenery, unless you are trying to say the scenery shouldn't have real world airline code assigned to gates ( the default scenery doesn't have them ), which will attract different AI with matching codes that MIGHT have a problem which, of course, is not the scenery fault.
Not even other FSDT airports have this problem with the liveries
This sentence doesn't mean anything for the reasons explained above. There's no such thing as a scenery with "problems with liveries".
I even tried the Vancouver airport with the original livery (having no extra liveries in the sim) using the flybywire A32NX and it still exited without error every time between 3 minutes and 7 minutes after loading the scenery and being parked in the gate.
Clearly proving the scenery doesn't have anything to do with it, but it's an AI that entered in the area after a while. If the scenery was a problem, the crash would have happened immediately, because the whole scenery loads immediately, only AIs appears after minutes.
I believe FSDT should look into the scenery code and see what can it do to fix it as again, it's the ONLY scenery that does that.
There's nothing we can do if your AI ( or something else ) is causing a crash in the Vancover area.
I agree that as ASOBO updates their simulator, things can change. But as all the other scenery developers do fixes for their airports (i.e. Flightbeam just took out a fix for their Denver airport because of the latest Asobo update), FSDT should look int it as well
Fact that other sceneries had to be updated because changes in the sim, doesn't mean every scenery requires updates, and CYVR surely doesn't require any changes, since the only problem the PREVIOUS update caused to it, which were the taxiway lights spread around randomly, was clearly a simulator bug that has been fixed in the current update.
So, please, stop saying FSDT CYVR has a CTD issue, because it hasn't, and your report of it happening only after several minutes clearly proves that, if my previous 20-minutes long video wasn't enough already.
-
Hi Umberto,
So you're saying the default MSFS 2020 AI is the problem?
Thanks for clarifying that.
Could you also tell me if it's possible to move my Vancouver license from the MSFS Marketplace to your FSDT store?
Thanks for clarifying!
Have a great Sunday.
-
So you're saying the default MSFS 2020 AI is the problem?
I'm saying what I already proven with my video ( 20 minutes long, takeoff and landing at CYVR ), that FSDT CYVR doesn't crash on its own. I can't be sure YOUR problem is caused by AI, both because I cannot be absolutely sure you really removed any airplane that, as an AI, might crash, but even if you had, I cannot possibly say if in YOUR case, the cause might be something else, not AI related.
AI is only the most common case, but it's not the only one, another possible cause for CTD which has also been discussed here in this thread, is a problem with Rolling cache, that is usually fixed by deleting it.
Could you also tell me if it's possible to move my Vancouver license from the MSFS Marketplace to your FSDT store?
We can't do that, since Microsoft doesn't share customer data with developers.
-
In my experience the CTDs are definitely caused by ai livery addons. I also had CTDs at CYVR not only with FSDT CYVR, but also a competitors payware of CYVR. For both payware versions of CYVR the CTDs happened approximately 5 miles away from CYVR on any approach. Deleting the ai livery addons fixed the CTDs for both payware versions of the CYVR airports.
-
In my experience the CTDs are definitely caused by ai livery addons. I also had CTDs at CYVR not only with FSDT CYVR, but also a competitors payware of CYVR.
I think we provided ample evidence of that. I really hope nobody bought another CYVR just to fix CTDs which were mistakenly assumed to be caused by our version.
-
I am minimum spec and ran CYVR without problems, but then it would CTD logging into or approaching the airport. Having temporarily removed the airfield replicated the problem, so I'm sure it's not the addon itself.
Broader issues with the KSEA traffic area seems to be a thing, would the next prudent step would be to temporarily remove all addons, then gradually re-install them testing against YVR performance?
Are there settings or apps I should shoul down. For example... disable developer mode? Lower or disable traffic density settings?
Thanks!
-
I am minimum spec and ran CYVR without problems, but then it would CTD logging into or approaching the airport. Having temporarily removed the airfield replicated the problem, so I'm sure it's not the addon itself.
"Having removed the airfield replicated the problem" is further proof what we have been trying to explain so many times: the problem is NOT the scenery. The most likely cause is some AI with a missing/corrupted texture. In some cases, even a multiplayer airplane with a livery or a model you don't have MIGHT cause a CTD, anywyere.
-
I replicated the exact flight. Flew it with default planes, no YVR addon (or any addons) and AI off. Still CTD during the downwind leg just before turning base.
I'm 100% sure it's not the addon insomuch as trying to figure what's corrupted on the subsequent scenery load. I suspect near YVR in the native code base. Why? Two reasons. I cannot load the sim from any airports near YVR. This includes, Boundary Bay, Abbotsford and Pitt Meadows as departures. However. I can depart from Nanaimo, fly into the zone and arrive anywhere except YVR.
I'll try teleporting around next and see how that works.
-
I suspect near YVR in the native code base
It might be possible but, when trying, I was never able to replicate it, surely not with 0% AI ( which also means no Multiplayer, because other users airplane are handled very similar to AI )
-
I had a few problems with SU6 and it was reported the hotfix would address some CTD issues.
Once I got the Xbox login issue resolved, I was able to fly near, start into or SDK teleport to YVR with no issues.
The addon runs and looks great. It takes a bit of time to load fully, but I expected that given I'm minimum spec.