[quote]Creating a lwjgl lib as a bundle should fix this
[/quote]
Do yo mean creating a LWJGL App as a bundle should fix it? I wonder because AlienFlux works fine on the Mac… but I made an App bundle for it.
I made some updates:
- When you run out of fuel, you fall down until you crash
- Replaced an Unreal texture in level 1 with my own
- Made the textures of the city appear twice as big, which makes the city look better IMO
- little update in the music
This is the version I submitted to be shown at GDC (I hope it will make it this time :-)).
Erik
Could a linux user please try
http://www.movegaga.nl/CosmicTrip_LINUX.jar ?
Just extract the jar and run ./run_linux.sh
I’m wondering if the offline linux version has the same problem as we’re having now with the mac (see the Mac Distribution thread in newless clubies).
Erik
It works here, after changing the script to:
java -Djava.library.path=. -cp GLGame1.jar:Graphics.jar:Sound1.jar:Music1.jar:lwjgl.jar net.movegaga.GameWindow
e
- elias
What’s the last ‘e’ for?
Thanks,
Erik
It’s the secret “copy-paste” bug that shows up once in a while…
- elias
ah
no ./ necessary before ‘java’?
</another_linux_n00b_question>
Erik
no, the ./ thing just makes it search for java in the local dir only, and that’s bound to fail.
- elias
pffft, of course. Stupid me :
It says missing apache… ???
eh? ???
what does?
I just checked and it still works here… :-/
Erik
Just tried the demo - superb! Loved the soundtrack too. Very smooth on my P3 1Ghz/512MB/GeFTi4200. Very inspiring.
20thCB
[quote]There is a 3 level demo available at
http://www.mycgiserver.com/~movegaga/cosmictrip.jnlp
It supports windows, linux and mac.
[/quote]
Black for a long time (about 30 seconds).
Then the logo and the four circles appear in the corners.
Nothing happens for another 30 seconds (top shows that it’s got almost 100% CPU though)
Pressing keys has no effect
Eventually, menu appears and logo is smaller above menu. Some highlight effect behind the word “start” takes 10 seconds to change from white to sort-of-red.
There is a little “1” in the bottom-right-hand-corner.
I’m guessing I’m experiencing some kind of “0.001 FPS” problem here.
linux 1.4.2_04 1Ghz P3. No exceptions in log, but I do get
Failed to choose preferred display mode, falling back to any mode:1400 x 1050 x 24 @0Hz
Which is correct (that means “laptop monitor running at full res and it’s normal refresh rate” - as I’ve pointed out before elsewhere, LWJGL seems to always report 0 as the refresh rate for this LCD). As noted previously, linux reports “24” for 32, IIRC because of the way X11’s config works - e.g. if you specify “32 bpp” in the config, your machine will crash and not load X :(. Apparently, its not that they think 32 == 24, it’s that they have their own unique definition of the meaning of the term “ColorDepth” which is not equivalent to what everyone else in the world uses…
JNLP link works great on Suse9.0, jre1.5.0b1, NVIDIA. All of it works; fullscreen, sound, controls and no GC pauses. But only first run, heh! That “apache” bug mentioned earlier is actually:
java.lang.NoClassDefFoundError: org/apache/xpath/XPathAPI
at net.movegaga.Config.load(Config.java:90)
at net.movegaga.Config.init(Config.java:65)
and has something to do with .cosmictrip/config.xml file, that gets written in home directory every time one starts a game. When that file is removed/renamed, all works great again.
Nice game, btw.
Heh, weird bug,.
Anyway, there’s no need whatsoever for using xml for just a config file. I’ll just use a Properties file instead.
I think it still works in 1.4.2 though, so I blame 1.5 being in beta.
As for blahblah’s error, I regard 24 bit modes as ‘undesired’ since on many cards (on windows) they are very slow. Maybe I have to check if we’re dealing with linux and then allow 24 bit so that it won’t fall back to the 1st mode it can find and do a more sensible selection.
Thanks for the reports
I know exactly what you mean! I too have plenty of experience of the serious problems if you run a windows desktop in 24-bit and try to run hw-accelerated apps (historically has enough problems with enough drivers to be something you always avoid if at all possible :)).
PS the statement about how setting it to 32 in X can kill X is from personal experience - I saw the 24 and thought “Argh! No!” and tried to “fix” it ;D.
PPS I think we could really do with either a neat-o class/jar that handled mode-selection for LWJGL (there seem to be quite a lot of quirks, and quite a lot of bits people get wrong because their system is not sensitive to the quirks), or a mini-tutorial on it, giving explanations for accepting/rejecting certain combos.
For instance, IIRC someone’s code (quite understandably) rejected my GeForce2 as being non-accelerated because it said it could only do “0Hz” refresh rate…sigh.