FTX Trees is now available. I downloaded and installed it. Looks beautifull in boht FSX and P3D V2.5... but on my sytem with a decent trees density (just normal or dense, no extreme) it really kills my FPS below20 fps and partly below 16-18. Tried on a forest environement from Misty place airfield. Of course in the desert it does not have such an impact !
Wih my system (Intel core i 7 3770s @ 3.10 ghz and relatively low range graphic card Nvidia Gforce 740a) these new trees really kill the performance and force me to decrease all settings up to a point where the quality of the new trees does not compensate (for me!) the lost of quality of the general scenery. Be aware that this is just an opinion mostly based on the "state of the art" of my own computer. Furthermore, when reading the documentation supplied with the ORBX trees program, it is clearly stated that it has been built with future computer development in mind and seemingly without care for those (like me) who cannot afford to change their machine every 12 months.
Added:
After further test I noticed that the impact was not as heavy in FSX and in my case it is mostly P3D V. 2.5 which is really affected by an important fall in fps.
On my sytem the Graphic Card is certainly the weak point and I suppose that P3D use more capacity of this element and thus it is more concerned with this fps drop.
Thanks to ORBX, this trees scenery can be neutralized by just one click in the new FTX Central 2 dashboard.
Finally forgive my somewhat ectic use of the English language. My own language is French!
I just made new test with P3D V. 2.5 and I supressed the tesselation which put a heavy load on the Graphic Card, and with this setting I can get a very decent fps rating with the ORBX trees installed, roughly 30 fps which is quite satisfactory. And all this with Level of detail... MAX - Mesh coml. HIGH - MESH Resol 5m. - Texture resol. 30 cm - Scenery compl. Extremely dense - Autogen VEG. and Autogen Build. Very dense.
The problem is that some times ago, without tessalation operational I awas had the famous Runtime Error R6025 hapening. But this was before P3D V 2.5, and during my new tests right now it did not happen. Will see...
