After following your suggestion I change my setting in fms2020,my frame limit is setup in nvidia control panel to 35fps. Attaching screenshot I don't see any deferent.
Your screenshot is cut, so it's not possible to see if you changed the only setting that might affect this, that is the object LOD slider. I had it set in my video to 100, BTW.
this is only happen in your product.
No, it's only happening in your system. Why you think I took the time to make a video, other then proving how the product is supposed to look like ?
Pls. don't blame something else for your bad pay product, Some how let say free product like Gatwick EGKK has no problem at all and if free. I expecting full refund. Thx
And where, exactly, you can see ANY trace of "blame" in anything I posted. What I posted was:
- A video proving the problem doesn't happen
- Several suggestions about which settings can possibly affect this, that is the Object LOD and the Field of View.
Were is the "blame", my reference you might TRY removing other addons to see if there might a possible conflict or it was just an issue with VRAM consumption ? I'm trying to understand why a scenery that obviously works, is not working for YOU and it's a possible conflict with another addon IS possible, that doesn't obviously mean I'm "blaming" anybody, I'm just trying to HELP YOU.
Instead, the only blame I see is coming from you, who are very quickly calling this "a bad product", before even getting all the facts straight. If you took the time to look at the forum, you would have noticed only ONE other user had the same problem a few months ago:
http://www.fsdreamteam.com/forum/index.php/topic,25894.0.htmlIn that case, the user didn't know we had an update, which was required after SU5 changed all the LOD working and caused jetways in almost ALL add-on sceneries to disappear. We obviously fixed this long ago and, of course, as soon the user got the update, the jetways came back.
But you said you already updated, which is why, I suggest the other things, that is checking the LOD settings, the Field of View or trying with the Community empty of other add-ons. There's the Addon Linker, which I'm sure you must know, which makes extremely quick to disable everything to eliminate the chance of a conflict, that should be the first thing to try.
Another thing you can try, is to remove the CONTENT.XML here:
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\CONTENT.XML
On the next startup, the sim will create a new one, sometimes this fixes disappearing things, due to a known bug in the sim DeleteAllJetways command which is required for any scenery to replace jetways with custom models. The bug manifests in a strange way, everything works normally, but only in the same session in which the CONTENT.XML is being recreated, if it already exists, the replacement jetways won't appear, but this would only happen if there's ANOTHER add-on that has other "Delete" commands in its .BGLs.
And before you say I'm "blaming" the sim for a bug I made up to justify a "bad product", check it here, on the official Microsoft Devevelopers forum, I reported myself in January:
https://devsupport.flightsimulator.com/questions/5082/possible-bug-with-deletealljetways.htmlAs you can see Sylvain ( FlyingRacoon ) is one of the Asobo devlopers, CONFIRMED THE BUG, and later on, he confirmed is still not fixed in SU9, but it's likely planned to be fixed in SU10.
Again, this bug would appear only if there are multiple add-ons Deleting things at the same airports,
that's why I told you to try with no other add-ons, NOT for "blaming" anybody, but because it's the PROPER way of troubleshoot this, since I obviously KNOW about this confirmed bug in the sim, and if you get it fixed, temporarily at least, for the session in which you remove the CONTENT.XML, it means we found the cause, and you triggered this bug.
If it's not that, we can still proceed other troubleshooting steps, like checking if you really go the current version of the files ( antivirus / firewalls can block this ), every problem has a solution, and we won't stop until is found.
Lastly, if you are referring to the THIS free Gatwick, as far I can see this screenshot:
https://cdn.flightsim.to/images/08/NIXV6YiQ.jpg?width=1400&auto_optimize=mediumIt uses
DEFAULT Jetways, so it won't ever be affected by the aforementioned bug, since this would only affect products that have custom jetway models.