Bunchy

I'm using V3 mesh without issue on beta 3. I'm on Win 10, though Stu

As the title says. List of fixes: The following is a list of additions/fixes included: What's New / Changed: Minor mesh fixes on front fuselage to patch up model holes Fixed high levels of gloss on ailerons Fixed texture artefacts on deice panel screws Artificial horizon light scatter fixed New datarefs on spill lights for glareshield Automatic switching from GPS to LOC guidance on a programmed approach wasn't engaging LOC mode properly Weight-on-wheels sensors should be on all gear legs OFV should begin modulating on the takeoff roll Switched state timer from microclock to unixtime due to potential problem with microsecond rollover on Windows vrconfig with hotspots for walkaround Fixed sudden pitch change when AP was engaged with the aircraft out of trim Retuned steering constants to make crosswind takeoffs easier Lowered minimum PAX weight to allow for children Lightened overhead panel textures to look better Implemented aircraft reset to Cold & Dark when selecting 'No' in flight recovery or when a new airframe is created Increased cloud cover sun radiation decrease factor to not overheat the cabin so easily on cold weather Increased cabin surface heat flow rate to cool the cabin a bit in colder weather Implemented hard crash detection Refactored panel overlay drawing code to avoid hard-coding panel viewport offsets to help with rendering on multi-monitor setups Made negative-G effect of fuel instability less pronounced FMS keyboard box joystick move UP should tilt radar down on radar page Fuel indicator should display proper inop indication instead of amber XXX Added code to detect left-most monitor and display drawer there Fixed UI scaling support issues - all windows should now rescale & behave properly with UI size > 100% Fixed windows not properly centering on multi-monitor setups Smartcopilot compatibility fixes - very early work Pushing CWS shouldn't emit the AP disconnection sound Flipped default CB light position to be off Very short runways could cause a div-by-zero in the runway segment number determination Added xEnviro integration to read rain rate. High-elevation VORs and ILSes could sometimes fail being received due to signal propagation computation errors Enjoy Stu

It used to be ctrl J to get the jetways moving but since GSX v2, I have to use the GSX menu itself. Stu

My experience with a 1080 GTX, which is obviously more powerful than a 1060 is this: If you use DL, then 8 x MSAA at night but only a max of 4xSSAA in the day. You will rid yourself of shimmering ONLY at the SSAA settings. Stu

That sounds interesting. Thanks for the heads up Stu

Thanks for your advice, guys. Second monitor not an option. Just need to get laptop talking to desktop. Will try as you suggest pete. Away from home at present, so can't try now 😢 Stu

I like the look of this software. I downloaded the free trial and ran the client and server on my desktop, very nice indeed. However, I want to run the client on my laptop and there lies the problem for me. I cannot get the the win 7 laptop to see my win 10 1803 desktop. So, without network connection, I would have to run an extra monitor with client/server on same PC. I am not IT savvy and having read many forums on how to connect my laptop and desktop together, I have to say that before I read the forums I knew nothing, after reading the forums, I know slightly less than that! If anyone knows how I can get my 2 computers configured, I would buy this in a flash. What I need is clear instruction on the network configuring and the install instructions lack that information. Happy to persevere, if someone could help? Thanks and regards Stu

As far as autogen not loading, have any of you tried removing any and all nvidia control panel or inspector settings, locking you frames to 30 internally and maybe setting a FFTF of 0.1? I find this works for me. Running unlimited frames, I see the same as everyone else, slow autogen load. The only reason I set FFTF to 0.1 is that I find at its default setting of 0.33, results in too low a frame rate whilst on, or close to the ground. I can provide my settings but can't seem to easily upload images at present. No harm in trying Stu

Do you use Navigraph charts and simlink, by any chance? If so, download and install the very latest simlink. I had this issue myself but only after flying for a few hours. Otherwise, make sure your sim is excluded from antivirus scans, or disable antivirus all together for test purposes. Stu

All the best for your treatment, Gary. I work in the radiotherapy field as an engineer, so I know you'll be well looked after. Get well soon Regards Stu

I had blurries back in 4.2, so I don't think it is a 4.3 issue per se. I'm not sure the exact run of events I used to fix the blurries but I do remember that I deleted the FTX-AA ORBX lib.txt file in C:\Program Files\Lockheed Martin\Prepar3D v4\ORBX\User Documents\Versions folder and let FTX central reinstall libraries. I also forced a migration of the lclookup via the settings menu of FTX central. I also followed advice about rebuilding scenery cfg and terrain cfg, too. Though I don't suffer from blurries anymore, I do suffer from slow loading autogen, especially with the fslabs a320. (Not surprised, as all 4 cores are at 98-100%) To remedy that, I find that adding an FFTF of 0.15 to the p3d.cfg and locking my frame rate to 30 internally overcomes slow autogen loading. The sacrifice is low 20'sFPS at busy addon airports but reducing FFTF to lower values improves FPS but re introduces slow autogen loading. I hope this has been at least a partly useful post. Regards Stu

Have you guys/girls seen this? https://orbxsystems.com/forum/topic/152274-orbx-england-trueearth-and-egcb-barton-for-x-plane-11-teaser-trailer-video/ It looks pretty amazing...... really, it does! Stu

Have you deleted your config.txt and shaders folder? They will renew themselves when you open the sim again. It's quite normal that the first time you load a scenario after a shader delete, it will take a few seconds to draw the scene. This should only happen the first time however.

I use navigraph navdata and still have this problem

Hi all, I had this problem too but I managed to fix it. My error was an ntldll.dll error. Here were the conditions: P3Dv4.1 PMDG 777-200 flying northeast of Labrador, heading west/southwest. Addons: FSDT CYYZ, FB KSFO, Orbx KSAN, Imaginesim KATL, FB KDEN, FB KIAD, UTL live, ORBX global, vector, NA landclass ASP4 with ASCA and Envtex only textures. All of these at there latest builds. Sim crashes with ntldll.dll as the faulting module. I reviewed the Avsim CTD document https://www.avsim.com/files/file/65-avsim-crash-to-desktop-guide-for-fsx-p3d-fs9/and followed its advice. I eventually cured these crashes by downloading Driver Booster and letting it update my drivers, apart from the nvidia driver. (I like to do a clean install of that manually but I have the latest driver 390.65.) Driver Booster found many intel drivers and motherboard drivers out of date, about 19 in all, even though I had downloaded the latest ones from the Gigabyte site. Not had the ntldll.dll errors since. My computer specs are my sig. Hopefully this will help some of you resolve this PITA. Refards Stu