July 20, 20187 yr 14 hours ago, ZKOKQ said: You omitted that from your original post 🙂 Hence my answer. I back up my Sode folder, just in case. Saves a lot of hassle later. Good point, Z. I did have my intact SODE folder (which was working fine with FSX), but after moving to P3d v4.3 from FSX, and re-installing FB airports, SODE no longer worked. After much back and forth with the good folks at 12bpilot, they had me move to SODE v1.6.3. Bottom-line, a SODE issue not a Flightbeam issue.
Archived
This topic is now archived and is closed to further replies.