XPD-7295 Fixed dark lightning bolts in storms with high visual effects settings.XPD-6959 Fixed rainbow swirling patterns under wheels at highest visual effects setting.XPD-7841 Fixed bright light on cockpit ceiling at night with high visual effects settings.GPS fixes: we allow setting of GPS relative bearing when override_gps is on, & the magnetic bearing points to the terminator.
Default C172 fixes: OAT gauge & 41″ MP at max throttle.Fixed plugins changing UI units and resulting in out of range values.XPD-7864 Fixed mouse fly not working with two monitors and large UI.XPD-7861 New hint text without extraneous line breaks.XPD-7850 Fixed crash when selecting approach at LGML.XPD-7363, XPD-7508 Fix for planet showing up in near view in low vis.XPD-7283 Spill lights not fogged in HDR mode.XPD-7259 ATC taxi guidelines too faint.XPD-5349 Fixed lights visible when above heavy (overcast setting & above) clouds.XPD-7163 Crash when reporting field in sight.XPD-6618 Ability to handle more than 1 hat switch.
#X PLANE UPDATE 11.21 WINDOWS#
XPD-6808 Some windows not re-skinned to match new UI. XPD-6812 Editing the Rendering settings for Visual Effects is SLOW. XPD-6849 Issue with power lines & base mesh. Also, you’ve said before that only one LOD is generated for ALL of the geometry in an OBJ - not individual LODs for individual TRIS commands. I guess that this LOD is generated based on the size of the bounding box of the OBJ geometry. Should I use ATTR_shiny_rat or GLOBAL_specular in this situation? Which is better for performance?Ģ) If an artist doesn’t assign an LOD to a scenery OBJ, X-Plane automatically generates an LOD for it. If you are worried that your preferred home airport is so unique that it is personal data, again, simply don’t opt-in.ġ) I have a scenery OBJ that uses an RGBA normal map for normals+metalness+roughness, but it is not instanced (i.e., it is only referenced once in the DSF). That means we know how many people use a type of aircraft, which airports are popular as start locations or which start type people like. If you actively given consent, we will know that a computer with some hardware stats and some joystick hardware starts a flight with the name of the aircraft, the identifier of the airport it starts at, and the start type (on the ramp, in the air, on approach, glider winch, oil-rig approach, space shuttle re-entry, etc…). So unless you have a home-built monitor with a unique 2781×1462 pixel resolution, or a home-built joystick with a unique USB device ID, there’s no way to identify you or you computer in the analytics data. No IP address (anonymized by Google analytics before we even see it) and no hardware-identifying data like MAC-addresses or Volume identifiers. If you have actively given consent in the opt-in process, we will know your operating system, monitor resolution, number of CPU cores, amount of RAM, your graphics card type and the type of joysticks you have. This is not new with GDPR – it has been this way since analytics were introduced in X-Plane 10. 
It is NOT required to opt-in to analytics in order to use X-Plane.
No data is transmitted unless you have actively allowed (opt-in) analytics data collection in the installer, or in X-Plane under Settings -> General.
0 kommentar(er)
