Of course if there is nothing but Cloud9 ENBR it should be normal - but we talk about FSX a software what is very aged and default is more then outdated in 2013/14. Therefore I need help to find the problem. I already brought it back to default. and did the reinstall again. But it was not possible to find the solution this way. So I disabled ENBR to see if the problem is still there without Cloud9 ENBR. And it was gone.
You still haven't replied to my question: does ENBR works WITHOUT such other add-ons ?
My logic (not necessary FSX logic) tells me that there must something in ENBR which is interfering with FTX Global and UTX.
If the above answer (which likely is) is Yes, then the logic is, instead, that something in FTX or the other addons is interfering with Cloud9 ENBR, not the other way around.
There are countless of forum threads about FTX causing issues to other sceneries, you surely can't expect that every scenery developer out there would revisit his sceneries, especially those dating back 7 years ago, just because a new terrain add-on has been released. FTX is the new product, it's *their* responsibility to check and eventually fix compatibility with existing products.
Again, assuming ENBR works with FTX disabled (assuming FTX is the problem), you could easily see it this way:
- You have a scenery installed ( Cloud9 ENBR ), which obviously worked since 2007
- You installed a new scenery, this creates problems to your previously working Cloud9 ENBR
- If you disable this new scenery, the problem goes away
Logic would dictate you should report this on that developer forum. When we release a new scenery, if we create issues with other EXISTING products, users expects we check compatibility and fix them from our side, I hope the same logic is valid the other way around, when our scenery is the existing and established one.
