Posted by gouessej on
URL: https://forum.jogamp.org/Java3D-1-6-0-Released-tp4037525p4037951.html

The problem isn't serialization, it's rather binary serialization. You can override writeObject(ObjectOutputStream) and readObject(ObjectInputStream) in your own code and call defaultWriteObject() and defaultReadObject() when no special treatment is required. If you want to control everything with no default mechanism, Externalizable is the way to go:
http://www.oracle.com/technetwork/articles/java/javaserial-1536170.html

Another solution consists in reading those files as text files, replacing the class names and then reading the resulting files with the source code taking into account the latest versions of the class.

If you use XML encoders and decoders, rather use some persistence delegates or XSLT.

Numerous bugs have been fixed since Java3D 1.6_pre 9.

runiter wrote

My main hope for Java3D 1.7 was that maybe you guys solved the problem with some users having old video card drivers or Microsoft video cards and getting this exception: Java 3D ERROR : OpenGL 1.2 or better is required (GL_VERSION=1.1). But I doubt that's a solvable issue unless I downgrade to Java3D 1.5 before directx pipeline support was removed from Java3D.

This problem cannot be solved because the main root cause comes from Intel who chose to provide half broken drivers for Windows 10 just not to prevent the migration but decided not to maintain some of them, Phil and me talked about that in a bug report. The only workaround consists in using an old JRE so that Windows 10 believes that your software isn't ready for Windows 10 but then, you might fall on unfixed bugs in those drivers and Intel stopped maintaining the corresponding Direct3D drivers on this hardware too, which means that using Java3D 1.5.2 or 1.5.1 wouldn't solve your problem and you would have to undergo all bugs fixed by Harvey, Phil, numerous other contributors and me. Moreover, I remind you that the native Direct3D renderer of Java3D was very buggy, that's why its removal was planned since Java3D 1.3. If you decide to package your software with an outdated and unmaintained version of Java3D, we won't be able to help you and this subsection of the forum is about Java3D >= 1.6.0.