First of all: thanks for the great jMonkeyEngine! It was a piece of cake to get started.
However, I’m trying to run a game that I last coded on in 2015, or so. I haven’t started it since February 2016. It seems. When I run this now some graphics are missing, as well as the sound effects. The music is still there.
As far as I remember this was running on macOS back then, but it might have been made in Windows, originally. It’s been a while.
I’m running:
masOS Mojave 10.14.6
java 15.0.1 2020-10-20
Java™ SE Runtime Environment (build 15.0.1+9-18)
Java HotSpot™ 64-Bit Server VM (build 15.0.1+9-18, mixed mode, sharing)
This is not going well and I’ve tried a few versions. Any ideas?
The reason I’m running Mojave is mostly because my Cubase-version (paid etc.) stopped working in Catalina, and overall I didn’t like Catalina (Planned obsolescence?) and had to reinstall this iMac.
EDIT: It may have been made in Windows 7, originally. I can’t recall really.
Thanks for the like. But it doesn’t help me a whole lot. I’m going back in. The main problem is that some sound effects, background effects and the resolution/full screen selections are missing. I don’t have a clue what’s going on but it seems like there could be some static file issues.
Slow progress here. I’m getting a java/util/jar/pack200 error when running the installer. Currently I’m so sick of the internets that I can barely search on these results, and Google seems to be seriously messed up this time.
NetBeans have problems with the jdk-14, because I suppose that you have install the jdk-14 so uninstall it and try it with the jdk-13.0.2.
I can sense a couple of days with Java-issues here. I have no idea what will break if i change Java-version, and I haven’t programmed any Java in 4-5 years, or so.
The most sensible solution could perhaps be running Catalina on an external drive? Or a Virtual Box-thingy?
Note, you need to provide the full stack trace of error in details so others can help.
And note, pack200 is removed since Java 14 (see JEP 367). Maybe >you should try with Java 8 or 11.
NOTE: I don’t get it, how you quote correctly here? And I got some kind of bug while editing. Neverheless…
I don’t want to “downgrade” Java on my main OS. Who knows what will break? Isn’t my solution above with Catalina or running a virtual something a more sensible solution? If not, why? How would it be possible to know what might/will go kaputt Java-wise on my Mojave if i downgrade Java?
Running multiple versions, probably not. I have PSTD-experiences of similar things.
I have no idea what-so-ever regarding different Java-versions. I haven’t worked with Java professionally since 2016. And most of it were getting old at that time.
So my idea is: running the Latest - Latest. But I do have a jMonkeyEngine-project that hasn’t been touched since 2016. As far as I remember it was originally made on Windows 7, and the first Java 3D-version (eeeh… I had to - university) was made in 2005.
FYI : If you donot want to downgrade java , but you wanna run a game(must be in a jar file or .desktop form ) download the java version you want to try , then run the game using a specific version using java executable (jre) bundled with the jdk tar file :
Java 11 is the current LTS. Users should not be running non-lts versons of java with the expectation that there will be no differences in how the versions run. Downgrading to java 11 will almost certainly still work just fine, as jdk 14 does not add anything major that would cause backwards compatibility issues unless you or the code you are running are using jdk 14 specific features. Using them is highly unlikely for third parties at this time, and if you are using them, perhaps you should rethink that approach as those features are in flux until jdk 17.
Until jdk 17, which is the next LTS, version specific features are generally not set in stone. A good example of this is the new JEP 361, which even has multiple syntax variants within jdk 12, and was changed again for jdk 13 (I think this one is fairly concrete now?)
To summarize, there should be little to no consequence to downgrade to jdk 11, which is the current LTS. I am running 11 on all of my machines, and setup specific dev environments for anything requiring newer versions.