|
About:
Plasma EBG is an empire building game with an isometric view. It runs in multiple resolutions with graphics being displayed better for higher resolutions; hence, lower resolutions do not suffer from being too large, etc. In the future several viewing engines will be available, such as EBG-opengl and EBG-2d. There is a separate module called EBG-dev which features the latest AI-development, as well as a separate server module.
Author:
Konstanty Bialkowski <thekon __at__ plasma __dot__ worldgroup __dot__ net __dot__ au>
[contact developer]
Homepage:
http://plasma.alphadimensions.net/projects/ebg/
Tar/GZ:
http://celab21.students.csee.uq.edu.au/[..]bg/linux/EBG-main-release-0.26.21.tar.gz
Changelog:
http://celab21.students.csee.uq.edu.au/~kon/ebg/releasenotes.html
Mirror site:
http://celab21.students.csee.uq.edu.au/~kon/ebg/
Trove categories:
[change]
Dependencies:
[change]
Allegro (Stable branch) (recommended)
XFree86 4.1.0 (recommended)
[download links]
|
|
» Rating:
8.31/10.00
(Rank N/A)
» Vitality: 0.00% (Rank 8613)
» Popularity: 1.25% (Rank 4529)
 
(click to enlarge graphs)
Record hits: 18,004
URL hits: 15,077
Subscribers: 17
|
|
Branches
Comments
[»]
a contructive complaint? ;)
by Dublet - Feb 16th 2002 17:00:39
I've been trying to get it to work, so I downloaded it and trying to
compile it first, but after realizing it was a binairy I tried to run it,
which would work, I'd get an application, full windowed with some red cloud
pictures or some sort (about the first and only things it loaded), then it
would exit. It gave the following output:
Final Options:
Colour depth: 32
Screen resolution: 1280 x 1024
Graphics driver: 0
Initilizing Graphics...
./isotest: error while loading shared libraries: /usr/lib/libpng.so.2:
undefined symbol: inflateInit_
I tried to upgrade to libpng 1.2.1, but to no avail, which I tried several
times, but it wouldn't help. finally I also removed the symlinks from the
old librairy named to the new ones, and then it wouldn't run at all. So
probably your binairy has been compiled for an old libpng version, and I am
not one to downgrade the system, so I would either appeciate the source, or
a binairy for the new libpng
[reply]
[top]
[»]
Re: a contructive complaint? ;)
by Konstanty - Mar 27th 2002 00:20:28
It seems that our binaries have become quite outdated during the
(Australian) summer.
I appologize for the inconvenience caused from this.
I plan to rebuild binaries for both libpng 1.0.12 and the new and
improved libpng 1.2.1. Also the allegro library has had an update - so this
shall also be included.
Large delays in updates have been caused by plasma.worldgroup.net.au being
down throughout January and February (2002).
Konstanty.
> ./isotest: error while loading shared
> libraries: /usr/lib/libpng.so.2:
> undefined symbol: inflateInit_
>
-- I assume this is with libpng 1.2.x with the .so.2 linked to it?
> downgrade the system, so I would either
> appeciate the source, or a binairy for
> the new libpng
[reply]
[top]
[»]
Bug Tracking
by Jon/Azure - Sep 18th 2001 09:00:31
Just a quick comment to let everyone who was thinking of installing or
running this project that I am now onboard as of around realease 0.26.15 as
software tester. Presently I am only testing the win32 releases, although
a large proportion of the code is shared across all releases (in fact the
main section of code is identical).
So far Konstanty and I have discovered and patched a large number of the
"critical" bugs, such as memory leaks, busy waiting, and
'crashes' (both serious and non-serious).
The current release (0.26.20) is fixed for a lot of the serious bugs and
is generally a lot more stable than previous versions. If EBG crashes on
you (and lets face it, it's alpha, and will) it shouldn't take down the
whole system (although previous posts seem to indicate that SVGALib is a
problem! I think that was at about release 0.26.01 or something).
I know that my win2k testing no longer crashes explorer.exe, and I am yet
to bring win2k down at all during testing of EBG.
EBG is coming nicely along the road to a mature product, and I urge anyone
that is interested to run it, test it out, and submit bug reports to us!
[reply]
[top]
[»]
PoS
by Nero - Mar 25th 2001 00:52:46
This POS managed to crash my system in both X and
SVGAlib - Don't use it.
[reply]
[top]
[»]
Re: PoS
by Konstanty - Mar 25th 2001 08:52:31
Thanks for your constructive comment.
What do you mean by "crash your system"? Did it
actually bring your whle system down?
Looking at the SVGAlib support - it doesn't work -
as ModeX support is only for 8-bit modes [This
will be fixed for the next release in the rare
occurance that someone would actually want to use
SVGAlib].
Also you don't want to run ./isotest - as you
probably are missing the allegro library from your
system - hence there is a wrapper ./run-ebg.sh -
which will make sure the allegro library is
included in the linker path.
If what you say is correct.. then why not submit a
bug report in bugzilla? [paste the contents of
your log.txt as well]
> This POS managed to crash my system in
> both X and
> SVGAlib - Don't use it.
[reply]
[top]
[»]
Re: PoS
by Nero - Mar 25th 2001 10:07:31
In svga mouse didnt work (no matter what i changed
in libvga.conf settings), it took mouse/keyboard
(so.. mouse cant quit it, and i couldnt go to
another console to kill the process)
X did about the same thing, except it took
mouse/keyboard, opened a small window (with
nothing in it) and then died.
[I dont have the log.. rm -rf'd the thing after
the second "crash"]
I did run it with the shell script btw.
Sorry if the original comment was a little harsh.
One tends to get ticked off after crashing twice..
> Thanks for your constructive comment.
>
> What do you mean by "crash your
> system"? Did it
> actually bring your whle system down?
>
>
> Looking at the SVGAlib support - it
> doesn't work -
> as ModeX support is only for 8-bit
> modes [This
> will be fixed for the next release in
> the rare
> occurance that someone would actually
> want to use
> SVGAlib].
>
> Also you don't want to run ./isotest -
> as you
> probably are missing the allegro
> library from your
> system - hence there is a wrapper
> ./run-ebg.sh -
> which will make sure the allegro
> library is
> included in the linker path.
>
> If what you say is correct.. then why
> not submit a
> bug report in bugzilla? [paste the
> contents of
> your log.txt as well]
>
>
> % This POS managed to crash my system
> in
> % both X and
> % SVGAlib - Don't use it.
>
>
>
[reply]
[top]
[»]
Re: PoS
by Jon/Azure - Dec 29th 2001 07:32:13
> One tends to get ticked off after
> crashing twice..
HAHAHAH!!! Sorry, I only just noticed that!! Imagine that - it must have
been a while since you used windows!!! I only start to get ticked off after
the 38th crash!!! :)
[reply]
[top]
[»]
Licensing question...
by J. Maynard Gelinas - Apr 5th 2001 14:44:45
Konstantly,
Could you elaborate on the licensing terms for
this project? I don't see a specific license
available on your web page, and I'm confused about
what "freely distributable" means with a
binary only release. Do you expect to release source
with this project, or will it remain binary only?
A link to the actual text of the license off your
web page would help.
Cheers,
--Maynard
[reply]
[top]
[»]
Re: Licensing question...
by Konstanty - Apr 6th 2001 21:30:35
Maynard,
This is a good point.. and I am sorry for
putting up a license on the website for these
releases. I will remedy this soon.
But FYI (and others):
Until the game is playable we do not expect to
release source code to the general public. (Trying
to keep the foundations of this project within
Plasma). [I know some people might debate this
descision.]
However, we do want to open up devopment in the
not so distant future. The binaries can be
distributed 'as-you-wish', however the source code
itself is under a "plasma private license". So
'Freely distributable' seems to fit the binary
releases... [I didn't notice a more appropriate
one]
--Konstanty.
[reply]
[top]
|
