Hello,
In the SimpleClientListener, there is a method which returns a PasswordAuthentication object.  Clearly the user name becomes the user name which is accessible in the ClientSession object on the server side.  However, what happens to the password?  I can't seem to find any methods in the server-side code to get access to it.  Does it dissappear or am I missing something?

Thanks,
--brendan

My experience is that the game server doesn't synchronize the references.  e.g. it serializes two copies of the same object.    So when you deserialize, I pretty sure you actually get two different object instances.  This is almost certainly guaranteed to break things if you trely on referring to the same object in multiple places in your code.

As I see it, the rule is:
If the objects in the List are instance variables (or contained in instance variables) in multiple ManagedObjects, it should be a List of their ManagedReference objects.  If the objects in the List are only in that one ManagedObject, then its okay to have a list of the objects themselves.

Hope that helps.
--brendan

The startup script supports Linux-x86, but the native db libraries are missing.  On Fedora Core, you can install them with:


Note that this is version 4.3 and includes its own db.jar, thus change sgs.sh  to read:

Hey Ken,
I tried the Feb 17th release with a backport of your DRIHack.java patch and it works correctly with accelerated graphics.
If I can be of any help figuring out what is broken in the CVS version, let me know (I'm a reasonably adept programmer...)
Thanks!
--brendan

Thanks,
I'll look forward to the more strict locking.  FYI, I'm not using mustang, here's my java version:

[bburns@localhost ~]$ java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

In the meantime, I will also backport your DRIHack modifications to the Feb 17th source release and see if that fixes things. I'll let you know what happens.

Thanks!
--brendan

Thanks,
I built from CVS, and it now loads and renders.  However the minute there is any window activity (mouse over, moving the window, etc.) I get the XLib async error (see below).  Here's the complete output:

[bburns@localhost build]$ java -classpath ./jogl.jar:/home/bburns/Desktop/jogl-demos.jar demos.gears.Gears
libGL: XF86DRIGetClientDriverName: 4.1.0 unichrome (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/unichrome_dri.so
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
__driCreateNewScreen - succeeded
libGL: XF86DRIGetClientDriverName: 4.1.0 unichrome (screen 0)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
__driCreateNewScreen - succeeded
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.
libGL error:
Can't open configuration file /home/bburns/.drirc: No such file or directory.
INIT GL IS: com.sun.opengl.impl.GLImpl
GL_VENDOR: VIA Technology
GL_RENDERER: Mesa DRI UniChrome (KM400) 20050526 x86/MMX+/3DNow!+/SSE
GL_VERSION: 1.2 Mesa 6.3
Xlib: unexpected async reply (sequence 0xd39)!

Thanks
--brendan

When I try to run HelloUniverse I get the following (with LIBGL_DEBUG set to verbose)

libGL: XF86DRIGetClientDriverName: 4.1.0 unichrome (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/unichrome_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/unichrome_dri.so failed (/usr/X11R6/lib/modules/dri/unichrome_dri.so: undefined symbol: _glapi_add_entrypoint)
libGL error: unable to find driver: unichrome_dri.so
Java 3D WARNING : reported GLX version = 1.2
    GLX version 1.3 or higher is required
    The reported version number may be incorrect.  There is a known
    ATI driver bug in glXQueryVersion that incorrectly reports the GLX
    version as 1.2 when it really is 1.3, so Java 3D will attempt to
    run anyway.
Java 3D WARNING : OpenGL 1.3 will be required in the near future (GL_VERSION=1.2)

and a window which simply displays a black screen.

Thanks!
--brendan

Thanks for the respons, here's the output from demos.gears.Gears

[bburns@localhost Desktop]$ java -classpath ./jogl.jar:./jogl-demos.jar demos.gears.Gears
libGL: XF86DRIGetClientDriverName: 4.1.0 unichrome (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/unichrome_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/unichrome_dri.so failed (/usr/X11R6/lib/modules/dri/unichrome_dri.so: undefined symbol: _glapi_add_entrypoint)
libGL error: unable to find driver: unichrome_dri.so
libGL: XF86DRIGetClientDriverName: 4.1.0 unichrome (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/unichrome_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/unichrome_dri.so failed (/usr/X11R6/lib/modules/dri/unichrome_dri.so: undefined symbol: _glapi_add_entrypoint)
libGL error: unable to find driver: unichrome_dri.so
INIT GL IS: com.sun.opengl.impl.GLImpl
GL_VENDOR: Mesa project: www.mesa3d.org
GL_RENDERER: Mesa GLX Indirect
GL_VERSION: 1.2 (1.5 Mesa 6.2.1)

and glxgears.

[bburns@localhost Desktop]$ glxgears
libGL: XF86DRIGetClientDriverName: 4.1.0 unichrome (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/unichrome_dri.so
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
__driCreateNewScreen - succeeded
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.
libGL error:
Can't open configuration file /home/bburns/.drirc: No such file or directory.
2323 frames in 5.0 seconds = 464.600 FPS

/usr/X11R6/lib/modules/dri/unichrome_dri.so exists...

Thanks!
--brendan

I'm also seeing this on VIA UniChrome (KM400), when I run the latest snapshot I get a Gray Screen:

[bburns@localhost Desktop]$ java -classpath ./tmp/jogl.jar:jogl-demos.jar demos.gears.Gears
INIT GL IS: com.sun.opengl.impl.GLImpl
Xlib: unexpected async reply (sequence 0x13d)!

[bburns@localhost Desktop]$ java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

The Feb. 17th release works (well it uses the indirect renderer, see my earlier message)

Any ideas?
--brendan

Hello,
I'm using the Via UniChrome (KM400) chipset for graphics acceleration.  Using c/c++ graphics acceleration works, glxinfo reports:

OpenGL vendor string: VIA Technology
OpenGL renderer string: Mesa DRI UniChrome (KM400) 20050526 x86/MMX+/3DNow!+/SSEOpenGL version string: 1.2 Mesa 6.3

However when I run jogl (demos.gears.Gears), it reports:

INIT GL IS: com.sun.opengl.impl.GLImpl
GL_VENDOR: Mesa project: www.mesa3d.org
GL_RENDERER: Mesa GLX Indirect
GL_VERSION: 1.2 (1.5 Mesa 6.2.1)

And from the framerate difference between demos.gears.Gears and glxgears shows that it is definitely doing software rendering.  Any ideas as to what the problem is?

I'm running the Feb. 17th release.  (the latest snapshot breaks w/ an XLib async error)
Thanks!
--brendan