| 1 |
[quote]If ZK is suspected of being a cause of the reduced performance it should be fairly easy to identify code changes likely to be responsible between March's stable and this one[/quote]
|
1 |
[quote]If ZK is suspected of being a cause of the reduced performance it should be fairly easy to identify code changes likely to be responsible between March's stable and this one[/quote]
|
| 2 |
That is only one half of what my post implied. The other half is lack of changes that would/could be required by a new engine release.
|
2 |
That is only one half of what my post implied. The other half is lack of changes that would/could be required by a new engine release.
|
| 3 |
\n
|
3 |
\n
|
| 4 |
I didn't bother to check commit history because everytime zk changes the engine it relies on, commit history just becomes an even bigger farce. The problem with huge CPU use by both healthbars and metal features widgets seem clearly linked to ZK... now, is it caused by recent changes to these widgets or is it caused by changes to the engine that are expected to be acted upon by mod devs (who may just be expecting to get all kind of new features with no work to do)?
|
4 |
I didn't bother to check commit history because everytime zk changes the engine it relies on, commit history just becomes an even bigger farce. The problem with huge CPU use by both healthbars and metal features widgets seem clearly linked to ZK... now, is it caused by recent changes to these widgets or is it caused by changes to the engine that are expected to be acted upon by mod devs (who may just be expecting to get all kind of new features with no work to do)?
|
| 5 |
\n
|
5 |
\n
|
| 6 |
Hypothetical question: If some hack was working fine with a previous version of the engine, and this hack now just sucks your CPU with newer engine, is it engine devs fault or should the hack be revised by mod devs? Lets say, mod devs made something horribly inefficient which was working fine until engine started to report much more items (whatever that is, events, units, features, ...), should the engine devs be blamed because they provide you with more control ability or should the mod be revised to be more efficient?
|
6 |
Hypothetical question: If some hack was working fine with a previous version of the engine, and this hack now just sucks your CPU with newer engine, is it engine devs fault or should the hack be revised by mod devs? Lets say, mod devs made something horribly inefficient which was working fine until engine started to report much more items (whatever that is, events, units, features, ...), should the engine devs be blamed because they provide you with more control ability or should the mod be revised to be more efficient?
|
| 7 |
\n
|
7 |
\n
|
| 8 |
It
may
be
a
mix
of
everything.
.
.
but
the
poll
is
written
in
a
way
that
leave
no
doubt
about
who
is
supposed
to
be
blamed.
.
.
|
8 |
It
may
be
a
mix
of
everything.
.
.
but
the
poll
is
written
in
a
way
that
leave
no
doubt
about
who
is
supposed
to
be
blamed.
Sorry,
but
I'm
not
playing
an
engine,
I'm
playing
a
game
relying
on
an
engine.
|
| 9 |
\n
|
|
|
Current poll - 94.1 vs 91.0