Paradroid3D

WIP games, tools & toy projects Archived Projects
#21

Doesn’t work on my laptop when I choose OpenGL; the dialog disappears and nothing happens.
The log says it initialized software (?) mode and it says it chose 72 Hz although I selected 60Hz.
Software rendering still works fine.


Java Web Start 1.4.2_05 Console, started Tue Oct 12 11:15:02 CEST 2004
Java 2 Runtime Environment: Version 1.4.2_05 by Sun Microsystems Inc.
Logging to file: C:\webstart.log
Loading Texture...from InputStream
Loading Texture...from InputStream
Loading Texture...from InputStream
Loading Texture...from InputStream
Loading Texture...from InputStream
Loading Texture...from InputStream
Loading Texture...from InputStream
Java version is: 1.4.2_05
-> support for BufferedImage
-> using BufferedImage
Software renderer (legacy mode) initialized
Current mode:1024 x 768 x 16 @72Hz
#22

Works fine here.

Please everyone stop putting LWJGL dlls all over the bloody place!!! You are NOT supposed to put it in jre\bin or System32!!!

Cas :slight_smile:

#23

doesn’t help that the wiki sugests installing into the jre folder :wink:
I have modified the wiki. Sorry for hijacking - please carry on, nothing to see here…

#24

[quote]please everyone stop putting LWJGL dlls all over the bloody place!!! You are NOT supposed to put it in jre\bin or System32!!!
[/quote]
Well, I don’t and never did. Still doesn’t work here. :-/

#25

[quote]Doesn’t work on my laptop when I choose OpenGL; the dialog disappears and nothing happens.
The log says it initialized software (?) mode and it says it chose 72 Hz although I selected 60Hz.
Software rendering still works fine.
[/quote]
Software mode is ok at this stage of the initialization, because the framebuffer defaults to software when created.
However, after choosing the OpenGL mode, something like “OpenGL-renderer initialized” should be printed out. If this doesn’t happen and no exception occurs, it’s somehow stuck in the Display’s initialization…strange. About the refresh rate: If i remember correctly, i’m ignoring the refresh rate for windowed mode and will take the first mode that matches resolution and color-depth. Maybe i should change that…

#26

Actually I think it has something to do with me having installed SP2 for WinXP. No LWJGL or JOGL programs work anymore on my machine! Might be the video driver which stopped working though…

#27

[quote]Actually I think it has something to do with me having installed SP2 for WinXP. No LWJGL or JOGL programs work anymore on my machine! Might be the video driver which stopped working though…
[/quote]
Hehe… read that story twice today. Yea, installing the drivers again (or a newer one) should fix that.

#28

Hm, just installed new ATI mobility radeon drivers, but still no luck… :frowning:

#29

[quote]Hm, just installed new ATI mobility radeon drivers, but still no luck… :frowning:
[/quote]
No luck at all or just with this particular demo? Are you forcing AA and/or AF in the driver settings? ATI’s latest drivers have a bug that causes some Java applications to hang/blank the screen when doing so.

#30

Hm. That’s bad :-/

Well, you could try uninstalling the driver (eventually through the software control panel)… reboot… and then install the new ones. Doing so helps… sometimes.

#31

No java-app using OpenGL (either JOGL or LWJGL, I don’t have anything non-java using opengl on my laptop) works, so I guess it has nothing to do with your demo. I’ll check AA/AF settings when I’m at work again, but iirc they are not forced and everything used to work fine before installing SP2.
I’ll also try uninstalling/reinstalling the drivers although I have the feeling it won’t make a difference, but it’s worth a shot anyway.

Just tried at home, where it works beautifully, getting up to 300 fps :slight_smile: (GF4, no SP2)
But could you please add vsync? :slight_smile:

#32

An update! The new version includes some (i.e.10) enemy robots that are running around in the level. They don’t do anything usefull for now, but you can already kill them. They have a very basic “AI”, i.e. they try to reach a target position somewhere in the level. If they managed to do so or they think that they can’t reach this position with reasonable afford, they’ll chose a new one. Movement is real 3D (incl. collision detection) when a robot is in view and a grid based 2D movement when it’s not.
I also tried to implement the classic Paradroid’s line of sight, so robots will disappear if something blocks the view of the 001 unit.

#33

Cool, I’ll check it out when I’m at home.
On my laptop, it doesn’t work. OpenGL on my machine is broken since SP2 (not only java programs).

#34

@1024x768x24 == 50-60 FPS (GF2) (modulo some fluctuations)
@320x240 == 25 fps (software) (modulo some fluctuations)

EDIT: @1024, == 5 fps (software, no fluctuation ever). Ahem. I thought your jPCT did much better (faster) software rendering than tthis before? (same machine, q3-style FPS map?)

Suggestion/request: “shade” the areas your droid cannot see. For instance, apply a slight darkning of the textures (if your textures were less grey, I’d suggest simply converting them to BW). Otherwise it’s going to be confusing, at least in 3D mode - where you can “see” a long distance)

#35

Yup. that was the problem. Works fine now.

#36

Grrr. Running this has disabled keyboard-auto-repeat on linux >:(.

Since I don’t know how to reset the OS’s keyboard stuff any other way :frowning: I now have to reboot just to be able to get basic KB functionality.

I don’t suppose you’re using any particular input API’s or anything that might have clobbered linux’s KB stuff? It definitely happened after quitting paradroid (using alt-f4 (did nothing) then escape), but I guess it might just be a co-incidental linux/jvm bug?

#37

Erm… LWJGL might do that… ask Elias.

Cas :slight_smile:

#38

[quote]I don’t suppose you’re using any particular input API’s or anything that might have clobbered linux’s KB stuff? It definitely happened after quitting paradroid (using alt-f4 (did nothing) then escape), but I guess it might just be a co-incidental linux/jvm bug?
[/quote]
I’m using Java’s build in keyboard stuff for the software renderer and LWJGL’s Keyboard API for the OpenGL renderer and it works fine for me under Linux. However, i’ve the same problem from time to time, but it’s definitly not related to Paradroid or even Java in my case. About the software renderer’s performance: It hasn’t changed since that quake-demo. I get 6fps@1024*768 on this crappy Athlon 1000MHz (non-XP) with SDRAM here @work, which sounds reasonable.

#39

run’s just fine for me! However I did notice that in 3D view when a robot would round a corner, and I should have been able to see the top of him, he’d just disappear. This was in OpenGL mode

#40

[quote]run’s just fine for me! However I did notice that in 3D view when a robot would round a corner, and I should have been able to see the top of him, he’d just disappear. This was in OpenGL mode
[/quote]
That’s the line of sight implementation. It calculates the line of sight from the 001-unit to each robot and not from the camera. The 001-unit can’t see such robots behind a corner (while the camera potentially can) and so they disappear. The same happens in “2D” mode.