2016.2.1 random trees fps hog

[KL-666]

I switched to 2016.2.1, and immediately had huge fps problems compared to 2016.1.1. So i started eliminating options, until i got at random trees. Turning that of suddenly made the 15 fps jump above 30 fps again.

Just a tip to try random trees first if you have horrible fps on 2016.2.1.

Kind regards, Vincent

[IAHM-COL]

oh wow!
Yes. Random trees have always been a resource hog. But AFAIK these were off by default and turned on at the users discretion.

I believe this is Dr. Jekyll's work, and maybe they want to push some sort of FG default with this now?

[KL-666]

No, i had it on in the previous version and then it comes to the new version. This is just for the ones who have it on. And i had no problems with the trees in the previous version (at low density setting 1.0), so something must have changed for the bad in the new woods.

Kind regards, Vincent

[legoboyvdlp]

With my Intel graphics, random trees has no effects on fps until I turn them up above 2.5 or so.

[KL-666]

is that on 2016.2.1 Lego?

Kind regards, Vincent

[IAHM-COL]

With my Intel graphics, random trees has no effects on fps until I turn them up above 2.5 or so.

Nice hint.
I'll try this out.
I have kept them off for always, due to the loss in performance, but if there's a magick number, I better use this.

[legoboyvdlp]

Well, the nightly builds are broken right now, so it's 2016.2.0.

[KL-666]

Let's wait till you have 2016.2.1 then, Lego, and let us know what happens.

Kind regards, Vincent

[OPFOR77]

2016.1.1 was terrible in the frame rate category for me, and 2016.2.1 is much better. Trees at 4.5 or thereabouts.

[KL-666]

Strange, those different effects with different versions and users.

Kind regards, Vincent