Which fog? I couldn't see any fog at all...(Core i7 2600K@4Ghz, 16GB, Java 7.something, GeForce 680, Windows 7 64bit)... I agree on the sliding thing...once you hit a wall, you get stuck, which is very annoying and not what you would expect.

Yes it is really annoying. I implemented collisions with the walls very quickly, I will have to rewrite them, it is crappy and not accurate enough.

I have not yet updated the demo of the pre-beta version. I will do so when the source code is more beautiful.

Thank you for the feedbacks and sorry for the late reply. I didn't notice your posts. There are obviously tons of wrong things in my game and it is still under development, I will take into account your comments.

I won't do that because a fat JAR is less reliable than Java Web Start (I already explained it several times in other threads), a zip archive is not satisfying because my script would not work in some particular cases (Java installed but not in the path, 32 bits vm on a 64 bits machine, etc...). I prefer helping you to fix your problem.

I use OpenJDK and Icedtea for several years now. I can try to solve your problem. Please let me know which distro you use, which version of OpenJDK and which version of Icedtea. What do you mean by "JNLP's don't work for me"? If you don't succeed in using them from your web browser, try to do it in command line:

So I have played your game now. Couldn't play it tough... I still have problems with XRandr and fullscreen applications. If LWJGL's XRandr stuff is disabled, all the DisplayModes other than the 2-monitor wide display mode fail, and cause the application to stop immediatly. That alone is not too bad: I SHOULD still be able to play it in 2 screens, but the game is only showing on one screen. I really don't know why... Unplayable right now

You really should take the like 5 mins to write a launcher for the 3 big OSes and make this a desktop app. No one wants to wait 10 mins to download a web-game. Also, JWS and applets suck, but that's out of scope of this topic.

How goes development? You really should display a screenshot or video of what you got so far. :3

So I have played your game now. Couldn't play it tough... I still have problems with XRandr and fullscreen applications. If LWJGL's XRandr stuff is disabled, all the DisplayModes other than the 2-monitor wide display mode fail, and cause the application to stop immediatly.

I don't use LWJGL but NEWT (JOGL) uses XRandr too, like LWJGL native windowing system. If I don't use NEWT, I cannot use the full screen mode under GNU Linux because of an AWT bug (the task bar is drawn above the window).

That alone is not too bad: I SHOULD still be able to play it in 2 screens, but the game is only showing on one screen. I really don't know why... Unplayable right now

Why is it unplayable right now? It is intentional, I ask NEWT to use only the primary screen by default to work around some (native) bugs with the support of multiple monitors when its order has been changed.

You do know Chrome downloads the JNLP now instead of launching it. You have to launch the JNLP file directly

That's Google's fault, I provided them a patch to fix that, one of its employees prefered suggesting a weaker patch. When you come here, you can see that I show a nice message to explain the situation:

Quote

Google Chrome is not supported. Launch the game with your file browser or install it with another web browser.You can find more information about this bug of Google Chrome here.

Google is still trying to kill Java, it still shows a scary warning when I try to run my game with Chrome:

You really should take the like 5 mins to write a launcher for the 3 big OSes and make this a desktop app. No one wants to wait 10 mins to download a web-game. Also, JWS and applets suck, but that's out of scope of this topic.

There is no automatic update in native installers and IzPack. It means that if I use one of them, when a player runs my game, an obsolete version will be used instead of the latest one whereas my game is far from finished. Your suggestion would be interesting for a polished and stable game, TUER is neither polished nor fully stable. TUER is seen as a "web" game but it is rather a desktop application that can be launched from the web. Java Web Start does not suck, I can work around some of its broken features and actually, Google sucks. Anyway, your suggestion would not reduce the time spent to download the game, the very first versions of TUER (available as zip archives) took ages to download. TUER will use more and more sound samples (ogg) and models, it will take much time to run. I don't intend to make a very casual game with a very few artworks and tiny levels, therefore people will have to spend some time in installing it or give up and rather play with "smaller" games.

Wanted to tryhowever major problem is, all my desktop setups have multiple screens. TUER splits the game onto both screensyou cant play like that =D

TUER attempts to use only the primary screen. If your operating system shows your both screens as a single wide screen, it will use it as is. I will try to fix that, maybe I misuse NEWT but I'm not sure I will succeed.

Wanted to tryhowever major problem is, all my desktop setups have multiple screens. TUER splits the game onto both screensyou cant play like that =D

TUER attempts to use only the primary screen. If your operating system shows your both screens as a single wide screen, it will use it as is. I will try to fix that, maybe I misuse NEWT but I'm not sure I will succeed.

Which is just the problem I had. Maybe I haven't pointed out clearly...

Wanted to tryhowever major problem is, all my desktop setups have multiple screens. TUER splits the game onto both screensyou cant play like that =D

TUER attempts to use only the primary screen. If your operating system shows your both screens as a single wide screen, it will use it as is. I will try to fix that, maybe I misuse NEWT but I'm not sure I will succeed.

Which is just the problem I had. Maybe I haven't pointed out clearly...

I see what you meant, don't worry. I use the wrong instance of com.jogamp.newt.Screen (the default one) when creating an instance of com.jogamp.newt.opengl.GLWindow. If NEWT (through XRandR) doesn't report only 2-monitor screens, I will be able to find a way to get 1-monitor screens, otherwise I won't be able to fix this bug.

when I get the screens via lwjgl or anything else, it shows 3 screen with their own resolution; or 2 depending on where I test =D

so imo there shouldnt be any reason why any program would think its one big screen

I use the default "screen", the screen that you use before launching my game, the 2-monitor wide screen. That's why you have this problem. I have only one screen and no Microsoft Windows operating system, I will fix that but not as fast as I would like to do it. If choosing the single primary screen was absolutely trivial, I would already have done it. Blindly fixing bugs without being able to reproduce them is not easy.

Awesome... Still updating right now, but I hope these also fix the Applet bugs !!!

Actually, I'm disappointed, something is missing in these fixes, it won't solve the problem. There is not yet any support of applets using JNLP with OpenJDK (plain applets still work), another contributor of JogAmp has been trying to fix that.

I have just updated the source code. The enemies can suffer a bit before dying, several frame sets are used. I will add some sound samples for their pain and I will update the demo of the pre-beta version tomorrow.

I would like to remove the limitation mentioned by EgonOlsen, I don't know what I broke when porting the code to Ardor3D.

I'm currently working on the (minimal) artificial intelligence and I plan to update the road map very soon

I need your help to measure the frame rate of my game on different computers. I will resume my work on my biggest optimizations and I would like to know the actual performance of several versions of my game before modifying the spatial subdivisions. Please run the alpha version and the prebeta version, tell me the frame rate you get (it is displayed in the game, please don't use Fraps), give me some information about your hardware (operating system, CPU frequency, number of cores, graphics card, driver version especially if you're under GNU Linux, etc). I will make some tries to evaluate the impact of my improvements before fully implementing them by manually modifying the map.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org