Open ApfelWurmer opened 6 years ago
Shpw app's logs -- black window screenshot or last logs from logs file ..\xmage\mage-client\mageclient.log
-- it's will contain errors and warnings from last launch. Also open launcher window, settings and show client launch commands field.
INFO 2016-09-16 19:34:45,932 Starting MAGE client version 1.4.15v1 =>[main] MageFrame.main
INFO 2016-09-16 19:34:45,935 Logging level: INFO =>[main] MageFrame.main
INFO 2016-09-16 19:34:47,810 Loading plugins... =>[AWT-EventQueue-0] Plugins.loadPlugins
INFO 2016-09-16 19:34:47,852 [Game counter plugin, version 0.1] has been loaded. =>[AWT-EventQueue-0] CounterPluginImpl.newPlugin
INFO 2016-09-16 19:34:47,859 Done. =>[AWT-EventQueue-0] Plugins.loadPlugins
INFO 2016-09-16 19:34:49,478 Card pool load time: 0 seconds =>[AWT-EventQueue-0] MageFrame.checkForNewImages
INFO 2016-09-16 19:34:50,098 Card images checking time: 0 seconds =>[AWT-EventQueue-0] MageFrame.checkForNewImages
INFO 2016-09-16 19:35:01,178 Client start up time: 15 seconds =>[AWT-EventQueue-0] MageFrame$7.run
INFO 2016-09-16 19:35:01,184 Trying to connect to XMAGE server at localhost:17171 =>[AWT-EventQueue-0] SessionImpl$5.run
WARN 2016-09-16 19:35:02,286 Cannot connect =>[AWT-EventQueue-0] SessionImpl.handleCannotConnectException
org.jboss.remoting.CannotConnectException: Error setting up client lease upon performing connect.
at org.jboss.remoting.Client.connect(Client.java:1928)
at org.jboss.remoting.Client.connect(Client.java:737)
at mage.remote.SessionImpl$5.run(SessionImpl.java:403)
at mage.remote.SessionImpl.handleRemotingTaskExceptions(SessionImpl.java:136)
at mage.remote.SessionImpl.establishJBossRemotingConnection(SessionImpl.java:281)
at mage.remote.SessionImpl.connect(SessionImpl.java:239)
at mage.client.MageFrame.connect(MageFrame.java:823)
at mage.client.MageFrame.performConnect(MageFrame.java:867)
at mage.client.MageFrame.autoConnect(MageFrame.java:836)
at mage.client.MageFrame$7.run(MageFrame.java:427)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.lang.Exception: Error setting up client lease
at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:563)
at org.jboss.remoting.Client.setupClientLease(Client.java:2070)
at org.jboss.remoting.Client.connect(Client.java:1924)
... 23 more
Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://192.168.1.72:17171/?serializationtype=jboss]
at
You've got image file corruption.
..\xmage\mage-client\plugins\
and delete images
folder;I had already deleted all xmage files, and uninstalled java and began from the start. But with the normal xmage launcher downloaded from xmage.de I can't run it, the launcher stays black forever and the physical memory rises anyways.
Also, if I try to download the zip file and run directly from it I encounter the same physical memory problem. I allocated the files on a simple path folder but it doesn't run in any manner.
It's can be a graphic card problem. Try to update drivers. If not helped then disable Direct3D for java apps -- use fixes from here:
-Dsun.java2d.d3d=false
to command line (for launcher or/and for client).E.g. create run.cmd
file in launcher folder and add text to it:
java.exe -Dsun.java2d.d3d=false -jar XMageLauncher-0.3.8.jar
Updating graphic card apparently helped. Also running xmage from command prompt with the command line works (although it takes a lot of work), but running it directly from launcher (easier way) doesn't work. Did I put the command line in the right place at launcher? (red area)
I suspect it's a java problem, because everytime I open the java control panel it freezes when after I try to close it (I can change the settings normally, it freezes only at closing act). Also tried to put this command line inside java control panel (advanced>user tab>runtime column).
Yes, that's must help (command line from launcher). Try add it at the end of line. And restart launcher.
Nope... launcher doesn't seem to work even with this command ate the end... Can only launch from command prompt so far
I was trying to disable direct 3D directly from nvidia panel, but can't find it where to do it.
I have been playing xmage for a long time in my pc (Windows 7). Recently it doesn't launch anymore. Whenever I try to launch, the physical memory starts to rise and xmage never launches. I've already tried uninstalling java and xmage, and then reinstalling both; also tried download the zip file and launch it directly from the executable (without the launcher). Sometimes it launches a few times before it stops launching and never launching again. Someone having #a similar problem?