SimeonWilbury

That is more or less what I expected unfortunately. As other users have already noted, I expect there will ultimately end up being other avenues for sufficiently determined simmers to acquire these.

As a Concorde flier - I noticed there seemed to be virtually no sceneries available for GOOY (the old Dakar airport). Maybe a bit of a more niche one and there is a FSDG Lite scenery for GOBD providing an alternative, so not necessarily a one for the top of the list but perhaps one that would be nice to have a 'better than default' option for. There are a few other airports in more far-out places on the earth that occasionally get visited on cargo flights (Almaty, Bishkek etc.) that don't seem to have much more to offer than ones merely altering the default scenery (which I personally can't stand). Otherwise, there are plenty of third-party sceneries (some of which requiring various amounts of TLC to get working properly), though the big issue will be the tendency for these to get increasingly out of date as the real life airports develop.

Brought forward until 26 May? I'm about to leave for a holiday until then! I can fully appreciate the costs of keeping the ops-centre running - but I hope there would at least be an alternative method for obtaining liveries - otherwise this smacks overly of forced obsolescence... In the absence of such then I presume that PMDG will have no objections to said liveries being rehosted elswhere so they can continue to be enjoyed by their paying customers (presumably in non-ptp form if that is being disabled for good).

Sunday's return flight was also successful, with settings bumped up slighty (density up form 'normal' to 'dense'. I might try and go up to 'very dense', though I think draw distance will definitely stay down. Hopefully that will be the end of issues for now!

Today's run was successful (albeit with a slightly different route, as I took the marconi route into JFK due to 22L/R being in use) - this time with draw distance down to high and autogen density down to normal (along with a few other settings knocked down). I think I will keep the draw distance as it is as it does give a noticeable FPS boost. Next flight I will maybe try autogen density back up to dense and it that works when I will maybe keep as is.

Ray - your last post doesn't seem to be visible to me for some reason (edit: it is now, appears posting this helped!). I have however tried the Microsoft Visual C++ repair and will see if that makes a difference. Also, may be a long-shot, but I also wasn't having these CTDs when I had FSUIPC autosave disabled. I don't know if that was a factor, but is another change I will try reverting in case it somehow introduced a problem. I did at one point also change the dynamic reflection settings mid-flight at one point, don't know if that somehow messed things up. Alas I have had to abandon the current flight and have work for the rest of the week, so I won't be able to repeat the flight again until Saturday. Hopefully with a few more tweaks I might be able to get all the way across the atlantic without a CTD.

Not currently, I might give a try possibly, although again FPS isn't much of a concern for me currently. I may possibly try FSR which I understand has a similar overall effect. Unfortunately I have now had another CTD at what seems to be exactly the same position (near Halifax), which is worrying - this time the faulting module is VCRUNTIME140.dll.

I don't use AI traffic (less queuing!), so I may have a bit more wriggle-room in that respect hopefully. I do like autogen to be as high as I can get away with - I did turn it down a lot with my old GPU to try and keep my framerate up around Heathrow. On my current card FPS is less of an issue - but it seems it does seem to need some more balancing for stability potentially.

I do suspect I overestimated what my current card can do (albeit it can definitely do more than the old one). Hopefully it will just be a case of gradually adjusting over time until I get a good balance between graphical fidelity and performance/ stability.

I knocked them up to high & extremely dense when I was experimenting with my settings - kept it as I was still getting pretty decent FPS (at 1080p), in retrospect that was probably a mistake. From what I read it is one of more more common causes of the terrain.dll CTDs so it is possible I was flying too close to the sun with my current settings. For the current fight I have knocked them down to high & very dense. If still a CTD then I'll go back to Medium & Very Dense, which is roughly what I had before - if I still have crashes after that then it may not be an autogen issue.

Another terrain.dll CTD this evening. This time over the Atlantic near Halifax. This has been happening since I raised the amount of autogen in my settings, so perhaps I need to knock that down again - that is all I can really think of at present, as it appears to be completely unrelated to where the aircraft actually is

The terrain.dll CTD is probably one of the only non-VRAM related CTDs I've had for some time, so for now I will leave things as they are for now and hopefully will just have been an intermittent issue.

I switched to a second hand Radeon RX6700XT recently - 12gb VRAM but as it turns out, LVFR KMIA is still rather demanding! Turns out my settings were not particularly optimal however - dropping my texture resolution to Medium seems to have resolved the issue (seemingly without too much lost in graphical fidelity). So I think as long as I keep it there I won't have any VRAM issues going forward. I did however then get a Terrain.dll CTD today on hitting the acceleration point out of IAD on the return leg to London - may be that I've been fiddling with my settings too much and will need to rebuild my p3d.cfg, but thankfully having turned on FSUIPC autosave I was able to reload to a few minutes earlier and carry on the flight without any further issues (so far).

Can confirm this was just a VRAM exhaustion issue - managed the landing this time though!

Hi All, First CTD since I came back from my sim hiatus, I have done a google and can't seem to find many instances of this particular error code, so I thought I would post in case it rings a bell to anyone: Faulting application name: Prepar3D.exe, version: 5.4.9.28482, time stamp: 0x6463925f Faulting module name: mso20win32client.dll, version: 16.0.5023.1000, time stamp: 0x69e51f53 Exception code: 0x01483052 Fault offset: 0x000000000043a82d Faulting process id: 0x5078 Faulting application start time: 0x1DCDBA6930D324B Faulting application path: E:\Lockheed Martin\Prepar3D v5\Prepar3D.exe Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll Report Id: efabe954-9310-407a-bbff-d903111c75d7 Faulting package full name: Faulting package-relative application ID: Happened when I was around 20nm from MIA and the scenery was loading in - it may well be a VRAM issue given the LVFR scenery is rather intensive, though previously I did not get any error message at all when I had VRAM-related CTDs. Also that the fauling module is connected to MS Office makes me wonder if it is connected to something else (I previously had a series of CTDs caused by this module that traced back to a demo-module of FS2Crew). Previously my sim has been rock-solid aside from previous VRAM issues, but I wouldn't put it past Microsoft managing to break something again... Unfortunately I did not have FSUIPC autosave turned on, so I will need to repeat the entire flight to reproduce (which I don't have much free time for these days). Give a shout if any ideas!