May 24, 20242 yr Hi, As stated, beta 4 is out. If you get a Vulkan / Zlink error when loading XP12b4, a reboot of the computer may be all that's needed to fix the problem. Edited May 24, 20242 yr by Mike_CFII_MEL Former Beta Tester - (for a few companies) - As well as provide Regional Voice Set Recordings Two: AMD-9950X | One: AMD-7950X3D | Three: Asus TUF 4090s | Three: 64GB DDR5 RAM 6000mhz | Three: Cosair 1300 P/S | Three: 990Pro 2TB NVME One: Eugenius ECS2512 - 2.5 GHz Switch | Three: Ice Giant Elite CPU Coolers | Three: 75" 4K UHDTVs | One: Boeing 737NG Flight Deck
May 24, 20242 yr Changelog from https://www.x-plane.com/kb/x-plane-12-1-0-release-notes/ Quote General New batch file in support folder to start X-Plane with aftermath on Microsoft Windows Updated translations for X-Plane Disabled Zink for NVIDIA graphic cards Bug fixes XPD-15396 – Crash after runway incursion if spoken taxi instructions are still pending. XPD-15472 – DSF-planet transition Broken. 7950X3D + 7900 XT + 64 GB + Linux | 4800H + RTX2060 + 32 GB + Linux My add-ons from my FS9/FSX days
May 25, 20242 yr I just opened my copy of Beta 3, disabled Zink, and closed it then restarted Beta 4 OK. YMMV
May 25, 20242 yr 3 hours ago, dolph98 said: I just opened my copy of Beta 3, disabled Zink, and closed it then restarted Beta 4 OK. YMMV didnt have to it only applies to Nvidia cards, and like last time, is automatically disabled buy xplane. AMD cards need it, NVIDA not yet, but they will.
May 25, 20242 yr Mine was disabled, but I still got the error message the first time I started XP12.1b4... Restarting worked fine. Maybe by default they simply don't check if it's already unchecked in the Graphic options... Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
May 25, 20242 yr Actually, after a bit more of testing, XP12's default weather shares a bug with MSFS 2020... Both sims, when in Real Weather (default) fail most of the time to reproduce the correct wind transition on approach... What I mean is that both sims appear to have a poor algorithm for blending of wind intensity from aloft GRIB data into METAR and, for instance, if you go searching and flying at airports with gusty and high winds you'll find that most of the time there's a sudden and rather unrealistic transition between the wind vectors at 6000' AGL (specially where MSA is low, like in most of the Europe) and the reported METAR wind. Say you have 18021G35KT reported... As you takeoff and climb past MSA (even before reaching MSA) the wind intensity will drop significantly, under most circumstances. Then as you come for landing you'll be in tame winds down to past MSA, and only as you get to around 2000' AGL the METAR winds will start to kick in... This "wind data blend bug" plagues both XP12 and MSFS default "real world weather". Edited May 25, 20242 yr by jcomm Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
May 26, 20242 yr @jcomm I agree with you. i just reported a few bugs because of that. Not based on the transition part but on the wind conditions on ground. My first tests a few days ago were quite good but with the beta 4 I noticed some very annoying differences compared to the actual metars. I am not expecting a perfect match since in real it also changes a bit. But I observed some extreme differences. Some airports were reporting winds of for example 15kts gusting 20kts or similar strong and the sim-weather on ground reported winds calm. And a few other times there were clear winds of let’s say 8kts from 280deg and during the take off I had a tail wind from the opposite direction like 100deg. Of course this completely messes up the take off calculations. Other than that the visbility and cloud coverage are very good now and also the upper weather seems way more accurate. It really must be a difficult task to blend these 2 weather sources but I think it should still be possible to priorise the local winds below let’s say 2000ft so that the transition happens before during the approach, although this may also not be always 100% realistic. Could you also make some reports to LR? i9 12900k, RTX 3090, 32GB RAM
May 26, 20242 yr 1 hour ago, Franz007 said: Could you also make some reports to LR? Good idea ! Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
May 27, 20242 yr Done a couple of flights in B4 (using latest Zibo). My take: 1. Better performance 2. Better clouds 3. Less shimmering. Really nice! Richard 7950x3d | 32Gb 6000mHz RAM | 8Tb NVme | RTX 4090 | MSFS | P3D | XP12
May 27, 20242 yr Are blurry cockpit displays still an issue or is there fixes / workarounds for this now? Vote to fix transparent sun visors having no effect on the sun glare effect in MSFS at: https://forums.flightsimulator.com/t/sun-shades-sun-visors-not-influencing-light-in-cockpit/691565/
May 27, 20242 yr 5 hours ago, Swe_Richard said: Done a couple of flights in B4 (using latest Zibo). My take: 1. Better performance 2. Better clouds 3. Less shimmering. Really nice! Agree fully, but in my case using different aircraft. Three 2-hour flights so far and all is good so far. Trying different things like AO and other stuff. Noticed the cloud types are not varied anymore but it may just be me.
May 30, 20242 yr On 5/27/2024 at 8:32 PM, Zangoose said: Are blurry cockpit displays still an issue or is there fixes / workarounds for this now? Nothing changed as far as I can tell
Archived
This topic is now archived and is closed to further replies.