kev4242

https://forums.flightsimulator.com/t/diamond-da40ng-main-pfd-surround-missing/340315?u=wingdxplore20

Glad it's not just me. I'll add to zendesk today so ASOBO are aware. Hopefully will be an easy fix. Seems fine in other planes.

Hi all, Has anyone noticed the surround on the left G1000 display on the Diamond 40NG since the last patch? All other aircraft seem fine, and I the buttons still work around the screen, but the surround mounting seems to have gone. Wondered if it is just my system or a bug introduced by the last patch. Thanks and merry xmas/happy holidays to all. Stay safe, be merry.

Love it so far. Performance great, visuals great and yes a few bugs but had a better immersive experience in msfs 2020 so far. Just done a quick IFR circuit over the UK with real weather. Big weather front over us at the moment so ils with about 3nm of visibility and gusty wind in the c172 and it was great. Well done ASOBO and MS. With a few patches and fixes this will be even better. No regret in purchasing at all.

I wonder if this is linked to whether you are using yoke or joystick. I've only 2 or 3 hours in the new Sim so far mostly with the c172. Compared to the a2a c172 from p3d if have found the controls from my yoke very similar in the new Sim. In fact the 'feel' of the plane seems better in the new Sim especially in ground effect when landing. Maybe the more realistic air effects are making the controls more sensitive on controllers with a smaller range of travel such as a joystick?

Think I've found the problem. Imagine this will only apply to those of us outside the USA. You need to install the following free voice pack. https://support.microsoft.com/en-us/help/14236/windows-language-packs Hope that helps.

I have ch throttle quadrant. Although fs2020 didn't recognise it as a ch throttle it did show throttles attached, I had to calibrate the range of the throttle travel via the windows game controller settings as the range in game was 20-80% throttle. Hope you get yours working.

Blown away by out of the box performance. Yes, there are a couple of bugs, but compared to FSX launch flying is smooth (not checked FPS but it feels buttery smooth so far after an hour of UK flying) rather than a slideshow. Flying on i8700k @4.8 and RTX2700 16GB RAM. Does anyone have some missing ATC voices? I hear some radio transmissions, but for others I just hear the mike click but no voice. Presuming I'm missing some windows voice packs? Also, does anyone know where the logbook entries are stored and if we can delete flights? FS2020 is going to be a great base/platform to build on for many years to come. Happy flying.

Thanks John. I've already exhausted all the fs9 ntdll.dll search results. I think my next steps are: Reinstall vanilla windows and fs9 on a different hard drive. At least this will rule out a hardware problem since all other programs seem to be running normally. Try putting my old graphics card back in, but I think this is unlikely to solve anything since I cannot find any other fs9 users having a similar problem with the 970gtx. Thanks again for your help. Any suggestions greatly appreciated!

Thanks Ghiom. It seems strange as the sim has run flawlessly for years with lots of complex scenery, aircraft and ai add ons. I've reinstalled FS9 and with the basic vanilla programme I am still getting the ntdll.dll crash. Thanks for your suggestion anyway. This is a very frustrating problem!

Hi Ronzie. I have run the dxdiag.exe. It says there are no problems found. The current dx version being used is direct x 11.

Hi, I've been going around the houses for some time trying to find the cause of an ntdll.dll error. It happens on FS9 usually between 15mins to one hour after loading a flight (but sometimes longer). It can take place at any location or time of day. I've tried disabling add ons, ai traffic and most recently a clean reinstall of FS9 using the late Opa Marshall's reinstallation guide to ensure there are no remnants of my previous install. I've run chkdsk, reg checkers and checked BIOS settings but nothing seems to work. I have previously run FS9 on this system for about 4 years flawlessly. The only hardware change in a graphics card upgrade to a 970gtx. This is the only thing I can think of that has changed that could be causing the crash. I've tried the latest drivers, and older drivers with no success (using the guru3d driver uninstall tool). All other applications and games are working fine so I'm thinking it has to be something to do with how fs9 is interacting with my machine rather than a hardware problem. The exception code on the ntdll.dll crash is 0x4000001f. This seems different from the more common c000005 code that I've seen reported on many FS forums. I have no idea what these codes mean or represent but I'm hoping someone here could shed some light and possible give me some clues to solving this frustrating problem. I'm considering putting the old graphics card back in and seeing if the ntdll.dll crash remains. Thanks for any help.

Thanks John and Ronzie. Reflections are off. I bit the bullet and reinstalled FS9 and the problem remains. I'm therefore thinking it is graphic card/driver related. I might try putting my old graphics card back in to see if I can further narrow down the cause. My system seems stable with all other programmes/games/applications so I'm thinking the new nvidia drivers aren't keen with FS9.

Thanks A32xx. I've already done this. I've tried FS9 running with and without nvidia inspector additional settings and still get the crash. Thanks anyway for the suggestion.

Hi all, I'm currently having a major headache with FS9. After a few months of no simming I returned to FS9. I am now having freezes. Through task manager it appears to be a ntdll.dll error. It seems like this error has happened to other users but I cannot find a solution that has worked. If anyone has any ideas that I haven't tried to prevent me having to reinstall that would be great. The only hardware change I have made since FS9 ran fine is a graphics card update to EVGA 970. The drivers are updated and from searching forums I cannot find anyone else who is having issues with this card. So far I have tried the following: - removing all AI (was using WOAI successfully for many years). - disabling add on scenery. - changing locations in FS. - Ran DSK Check. - Ran a driver uninstaller to check there were no bits of an old driver left that were causing a conflict. - HD defrag Any help greatly appreciated! Thanks, Kev