What happened to the autogen?

[Blackdog_kt]

Once again, too many assumptions in this thread.

Nobody knows if this is an intentional thing, a bug or a limitation.

It's the same thing we had in the previous alpha patch all over again.

People wanted a patch so we got an interim one that was DX10 only. Since the effects are done in DX9 they were not included in the patch. Then people assumed that cutting effects was a "trick" to boost FPS and not something that was brought about by our own desire to get a patch at whatever cost. Then they didn't want DX9 support, even though they wanted the effects.

Now we get effects back and people say they like it, despite the fact that they didn't want to support the API that effects were coded on.

Apparently all that is not irrational and self-contradicting enough, so we get the same thing this week as well with another feature/bug/whatever

As for what is a beta, it's a test. It doesn't promise to improve anything, it promises to test if the improvements work and if they don't, find out what doesn't work so that it can be fixed.

If we want to debate whether speedtree was a good choice or not, we can. But assuming too much while knowing too little will only result in us contradicting ourselves and looking like fools. Why don't we just do what the beta is supposed to be? Download if we want to test, then test and report?

[addman]

Originally Posted by Blackdog_kt

Once again, too many assumptions in this thread.

Nobody knows if this is an intentional thing, a bug or a limitation.

It's the same thing we had in the previous alpha patch all over again.

People wanted a patch so we got an interim one that was DX10 only. Since the effects are done in DX9 they were not included in the patch. Then people assumed that cutting effects was a "trick" to boost FPS and not something that was brought about by our own desire to get a patch at whatever cost. Then they didn't want DX9 support, even though they wanted the effects.

Now we get effects back and people say they like it, despite the fact that they didn't want to support the API that effects were coded on.

Apparently all that is not irrational and self-contradicting enough, so we get the same thing this week as well with another feature/bug/whatever

As for what is a beta, it's a test. It doesn't promise to improve anything, it promises to test if the improvements work and if they don't, find out what doesn't work so that it can be fixed.

If we want to debate whether speedtree was a good choice or not, we can. But assuming too much while knowing too little will only result in us contradicting ourselves and looking like fools. Why don't we just do what the beta is supposed to be? Download if we want to test, then test and report?

I would bet money on that the auto-gen box is an intentional thing, a quick performance fix if you will and in all fairness I think it's the only thing the devs can do to really improve performance for the vast majority out there. I'm not complaining at all, it just confirms what luthier has mentioned quite a few times, the Speedtree trees are in fact, a problem. Who's talking about effects and directx versions BTW? I thought this thread was about the limited auto-gen box. Nobody's trying to look like a fool here, people are correctly reporting their observations found in the latest beta patch, in this case the limited auto-gen box. You are not giving the devs any credits here, insinuating that they are doing "tricks" to improve performance. Try to be a bit more respectful towards the intellect of the devs and exchange the word "tricks" to "temporary fixes that makes the game playable for everyone, even those that can't afford a nuclear power plant PC rig".

[SlipBall]

Originally Posted by addman

I would bet money on that the auto-gen box is an intentional thing, a quick performance fix if you will and in all fairness I think it's the only thing the devs can do to really improve performance for the vast majority out there. I'm not complaining at all, it just confirms what luthier has mentioned quite a few times, the Speedtree trees are in fact, a problem. Who's talking about effects and directx versions BTW? I thought this thread was about the limited auto-gen box. Nobody's trying to look like a fool here, people are correctly reporting their observations found in the latest beta patch, in this case the limited auto-gen box. You are not giving the devs any credits here, insinuating that they are doing "tricks" to improve performance. Try to be a bit more respectful towards the intellect of the devs and exchange the word "tricks" to "temporary fixes that makes the game playable for everyone, even those that can't afford a nuclear power plant PC rig".

Good post there

[Dano]

Originally Posted by addman

I would bet money on that the auto-gen box is an intentional thing, a quick performance fix if you will and in all fairness I think it's the only thing the devs can do to really improve performance for the vast majority out there. I'm not complaining at all, it just confirms what luthier has mentioned quite a few times, the Speedtree trees are in fact, a problem. Who's talking about effects and directx versions BTW? I thought this thread was about the limited auto-gen box. Nobody's trying to look like a fool here, people are correctly reporting their observations found in the latest beta patch, in this case the limited auto-gen box. You are not giving the devs any credits here, insinuating that they are doing "tricks" to improve performance. Try to be a bit more respectful towards the intellect of the devs and exchange the word "tricks" to "temporary fixes that makes the game playable for everyone, even those that can't afford a nuclear power plant PC rig".

If it is intended as a quick performance fix it's failed miserably on my system.

[PotNoodles]

If this is an intended fix for the trees will the Readme file confirm this next week? I actually sent returned FlightSim X because this was such an irritation when flying, and it looked alot better in that Sim then it does in this one. I really hope they are not going with this as a fix for the trees because I agree it looks horrendous.

[_YoYo_]

Originally Posted by PotNoodles

If this is an intended fix for the trees will the Readme file confirm this next week? I actually sent returned FlightSim X because this was such an irritation when flying, and it looked alot better in that Sim then it does in this one. I really hope they are not going with this as a fix for the trees because I agree it looks horrendous.

+ 1
I returned to Rise of Flight now with weapon mods, I bought all mods, nice to see many good changes in this beta patch, but this flashing trees are very annoying. Sure, know its a "beta", but looks like broke beta with autogen subject and step back.