1 |
Due to complaints about decreased performance, we asked Valve to disable Steam Overlay for ZK by default.
|
1 |
Due to complaints about decreased performance, we asked Valve to disable Steam Overlay for ZK by default.
|
2 |
Unfortunately
this
takes
out
the
invite
functionality.
|
2 |
Unfortunately
this
takes
out
parts
of
the
invite
functionality.
|
3 |
\n
|
3 |
\n
|
4 |
The
crux
of
the
problem
is
that
for
the
Overlay
to
work
properly,
the
Steam
API
thing
needs
to
be
called
by
the
same
process
that
does
the
heavy
graphics
work
-
in
this
case,
Spring.
However,
Spring
can't
do
this
as-is,
so
instead,
in
case
of
ZK,
the
Steam
API
is
called
by
the
Chobby's
.
NET
based
wrapper
program.
|
4 |
(
erroneous
info
below
compacted)
|
|
|
5 |
[spoiler]The crux of the problem is that for the Overlay to work properly, the Steam API thing needs to be called by the same process that does the heavy graphics work - in this case, Spring. However, Spring can't do this as-is, so instead, in case of ZK, the Steam API is called by the Chobby's .NET based wrapper program.
|
5 |
\n
|
6 |
\n
|
6 |
A proper fix will require an engine update, and the last time a new engine was tested for ZK it had issues (broken terraform, etc).
|
7 |
A proper fix will require an engine update, and the last time a new engine was tested for ZK it had issues (broken terraform, etc).
|
7 |
\n
|
8 |
\n
|
8 |
So three things need to be done to solve [b]both[/b] the overlay performance regression problem and broken invites:
|
9 |
So three things need to be done to solve [b]both[/b] the overlay performance regression problem and broken invites:
|
9 |
\n
|
10 |
\n
|
10 |
1) Implement a way for Spring to call the SteamAPI directly rather than via wrapper program. While somehow dodging all the kinds of nasty that the infectious GPL license and engine developers' sense of squeamishness may say about [i]linking proprietary code[/i], then get it merged into the maintanance branch.
|
11 |
1) Implement a way for Spring to call the SteamAPI directly rather than via wrapper program. While somehow dodging all the kinds of nasty that the infectious GPL license and engine developers' sense of squeamishness may say about [i]linking proprietary code[/i], then get it merged into the maintanance branch.
|
11 |
\n
|
12 |
\n
|
12 |
2) Test the resulting build that contains the fix for presence of unrelated regressions and general fitness to run ZK, and obtain fixes to issues that are found.
|
13 |
2) Test the resulting build that contains the fix for presence of unrelated regressions and general fitness to run ZK, and obtain fixes to issues that are found.
|
13 |
\n
|
14 |
\n
|
14 |
3)
Apply
new
engine
to
ZK
and
modify
the
game
and
its
lobby
to
use
the
new
way
of
accessing
Steam
API.
|
15 |
3)
Apply
new
engine
to
ZK
and
modify
the
game
and
its
lobby
to
use
the
new
way
of
accessing
Steam
API.
[/spoiler]
|