Usually this problem comes up when using the 1.8.0_66 JRE bundled with the current stable TripleA installer. So installing the latest version of Java on the OS doesn't actually do anything because TripleA will always use the bundled JRE. This topic is a walkthrough for troubleshooting the issue and uninstalling the bundled JRE if that is indeed the problem.
Posts made by ssoloff
RE: First TripleA Game Test
RE: [Closed] Are you running Windows 32 bit? The developers would like to know!
The 32-bit installer creates a different .vmoptions file than the 64-bit installer (see #4336) :
<action name="" id="458" customizedId="" beanClass="com.install4j.runtime.beans.actions.control.SetVariableAction" enabled="true" commentSet="false" comment="" actionElevationType="inherit" rollbackBarrier="false" rollbackBarrierExitCode="0" multiExec="false" failureStrategy="2" errorMessage=""> <serializedBean> <java class="java.beans.XMLDecoder"> <object class="com.install4j.runtime.beans.actions.control.SetVariableAction"> <void property="script"> <object class="com.install4j.api.beans.ScriptProperty"> <void property="value"> <string>final boolean is32BitJavaRuntime = "x86".equals(System.getProperty("os.arch")); final long halfMemoryMiB = Math.round(SystemInfo.getPhysicalMemory() * 0.5 / 1024L / 1024L); return Math.min(is32BitJavaRuntime ? 1024L : 2048L, halfMemoryMiB);</string> </void> </object> </void> <void property="variableName"> <string>heapSizeMiB</string> </void> </object> </java> </serializedBean> <condition /> </action>
RE: Error starting PBEM game...
is 32 and 64 conflicting ?
Good eye, but probably not. In this case, it appears a bundled JRE is being used (see the value of the
java.homeproperty), so it doesn't matter what other JREs the user has installed on the system--the TripleA launcher will always use that bundled JRE. (As has been observed by others, this tends to be a Bad Thing, and is being discussed in https://github.com/triplea-game/triplea/issues/4358.
RE: Error starting PBEM game...
@RoiEX Could be a TLS proxy causing issues, as we've seen in the past. Although I would have expected that to cause the dice server test to fail, as well.
According to this SO answer, several people reported Avast prevented TLS-enabled JavaMail from working. Temporarily disabling A/V while running the email test may be a good thing to try.
RE: The Future of Triplea
- Will Triplea ever be mercenary?
Do you mean that if someone were willing to pay for the development of a feature, would that feature get higher priority or a guaranteed addition in a future release? I don't think I have the authority to answer that question, but I just want to clarify what you mean when you use the term mercenary in this context.
- Are people able to copy some Triplea features then implement them to their games?
TripleA is licensed under version 3 of the GNU General Public License (GPLv3). In a nutshell, this license permits you to redistribute or make changes to TripleA code (including copying the code into your own program) as long as you abide by the terms of the GPLv3. These terms typically require you to make your modified work also available under the terms of the GPLv3.
Let's say, for example, you have a great idea for a new set of rules that the TripleA devs cannot or will not support. You are free to fork the TripleA code and make whatever changes you like. However, if you ever decide to release your new-and-improved version to anyone but yourself, you have to follow the terms of the GPLv3. The big deal there is that you have to make the modified source code available--at no charge--to anyone who wants it. Note that "at no charge" doesn't mean you can't charge people to buy a compiled version of your game or to pay a fee to play your game online. It simply means you can't charge for access to the source code.