You’ve read the document? If so, for determining the value to use within the range allowed you’d use trial and error to select a temperature and review the takeoff data to see if you have enough runway and obstacle clearance.
Very odd indeed.
This is typical of X-Plane’s Vulkan engine, particularly on the ground, in my experience.
Can you provide the detail requested here please? And also a recent Log.txt file? Thanks.
Also have you tried the following?
P.S. It’s a 60 Hz 4K panel but only drivable at 60 Hz via DisplayPort. That explains the “30 Hz” question. Not that unusual after all, due to HDMI limitations of past.
This is likely just X-Plane’s lack of any occlusion/shadowing by the fuselage when the sun in low. But maybe @Goran_Mcan do something with materials to tone it down. Otherwise we’ll just have to hope X-Plane 12 improves the situation.
It uses either the default nav data that comes with X-Plane or optional nav data from Custom Data directory. Have you read the provided FMS Primer document that explains how to select the correct nav data?
Just to clear the ice simulation does not use real temperatures and weather from the past, it extrapolates from the current OAT and weather conditions only. Could it be tuned? Of course, and your feedback will be helpful. There is an algorithm, it isn’t random as some have alluded to.
Please don’t confuse matters with +1s, crashes can be very specific to each user. Please post your own threads with your own Log.txt, description of simulator state when crash occurred, and reproduction steps, if possible.