We can still perhaps present this as an option for users to be able to turn on if the benefit is really large, we'd need to be careful to clearly note that there could be rendering problems. We do not know which conditions are necessary yet for a game to be able to offer this flag. Without deeply knowing the root cause, removing the flag is right. This does not seem to be necessarily OS related, perhaps video card, graphics driver, or even java version related. On one hand I did not want to infer the blast radius of this problem was larger than what I concretely knew, on the other hand assuming the problem is related to the one OS of the person reporting the problem was a mistake. One comment, I noted that we saw this in Ubuntu and I think that biased things a bit to think the problem was OS specific. I wish I had the time to rewrite the rendering in JavaFX for better performance and quality at the same time, but it looks like this will stay a dream until I have a little bit more free time. TL DR having a switch that might or might not default to a value based on the OS is probably the best short term solution. I mean most of the time is spent in menus buying troops and other stuff, moving troops around, watching battles happen and observing other players movement, but I'm that especially on systems with a slow CPU, people will notice a serious drop in performance.
Install4j gpu option update#
With OpenGL, the screen update feels near instantly and 60FPS smooth, and without it it seems like the rendering can't really keep up with the fast scrolling, so it skips some frames which makes the movement feel choppy.īut at the same time the non GL version is definitely playable.
Install4j gpu option code#
There's also a catch to this approach I haven't thought of before:Ĭurrently javafx is only a game-headed dependency, so we'd have to create it in game-headed code (or have at least the code there and pass a supplier) and pass the object through the window model.Īlso I removed the flag on my machine to get the direct comparison: Once the new size is fixed though, everything works normal again. There are some limitations to this (it looks like JavaFX really doesn't like the swing event model) so that resizing the surrounding swing window really slows everything down. JFXPanel does indeed skip swing rendering so that it uses the 3D capabilities of the GPU to do some rendering (fortunately windows task manager finally allows users to see how much load the GPU has). Ok, did some testing and I have good news:
0 kommentar(er)
