I just discovered I had the same issue with Everett. This time the same fix didn't work, but disabling UTX.
After re-enabling TOPOSIM and UTX except for two entries which are obviously directed to FSX everything is fine.
Strange - I hope this is a permanent fix!
Thanks & regards, Mark
Search found 3 matches
- Tuesday 21 Aug 2018, 11:20
- Forum: Products - FSX, FSX:SE, FSW, P3Dv1/v2/v3
- Topic: Seattle Airports X
- Replies: 1032
- Views: 739099
- Tuesday 21 Aug 2018, 07:37
- Forum: Products - FSX, FSX:SE, FSW, P3Dv1/v2/v3
- Topic: Seattle Airports X
- Replies: 1032
- Views: 739099
Re: Seattle Airports X
Hello Stanislaw Yes, there is only one entry named Seattle X and it is on top between the grey shaded entries (I don't know what that means). After deactivating TOPOSIM USA the field elevation was perfect. I then reactivated TOPOSIM again, same result. It seems that the problem has been resolved by ...
- Sunday 19 Aug 2018, 08:41
- Forum: Products - FSX, FSX:SE, FSW, P3Dv1/v2/v3
- Topic: Seattle Airports X
- Replies: 1032
- Views: 739099
Re: Seattle Airports X
Hello
Not sure if I'm posting in the right place here ...
I have Seattle X installed in P3DV4. Everything is fine, except KBFI. All taxiways, runways etc. are positioned about 10 m below terrain. I'm also using UTX USA and TOPOSIM mesh.
Anything I can do about that?
Thanks for help!
Not sure if I'm posting in the right place here ...
I have Seattle X installed in P3DV4. Everything is fine, except KBFI. All taxiways, runways etc. are positioned about 10 m below terrain. I'm also using UTX USA and TOPOSIM mesh.
Anything I can do about that?
Thanks for help!