Matrix Games Forums

ORIGINAL: n01487477

ORIGINAL: asdicus

michaelm several of us have reported problems running 1108m5 beta with tracker. Can I ask is this an issue with the beta or is it a problem the tracker team need to look at ? Up to 1108m2 I had no problems but this is the error I get running a new tracker install with 1108m5 save.

Answered in the Tracker thread... (change the dll in the tracker folder)

Michael - there are 2 different dlls one for the M4 and one the M5 with differing dates - the M5 has a later date ... Is this by design?

Sorry it does not work for either dll. I used the dll from the m4 and m5 beta - 2 different dll files - same error message each time. New tracker install.

No longer able to withdraw ships in the off map areas around Cape Horn until the ship really gets to Cape Horn..This is true of this patch and the last patch..

I was also not able to withdraw from Manila, in supply, I own the air, lots of brass hats and support..Size 9 port.

I'm using Tracker with 1108m5 without changing the Tracker DLL since that AE version that first required the change (I forget which Beta that was).

ORIGINAL: michaelm

ORIGINAL: BigDuke66

That the refuel setting in the TF screen also used at the home port to set how much is fueled when using the manual option is new to me, did that come with on of the latest version?
But the setting normally just sets how much is refueled at the destination hex aka none-home or waypoint port, correct? Or does it now also work differently?

Not sure what you are referring to?

Well I tried to refuel a TF at its home port but the button was greyed out, so I thought it should than fuel at its destination hex so I changed the setting for that and when I changed it from "Do not refuel" the manual refuel button wasn't greyed out anymore, not only this but setting it ti minimal didn't make them refuel as the TF had enough fuel and as I set it to Full refuel the TF refuel, so altogether the setting for refuel seems not only to work at the destination hex but also at the port where the TF is at the moment.
Maybe I don't remember this correctly but I don't think it was this way in earlier beta versions, don't get me wrong I like it they way it is as the TF can be refueled like I think it needs to, I just wonder because I haven't seen this in earlier versions(or maybe I overlooked it).

ORIGINAL: witpqs

I'm using Tracker with 1108m5 without changing the Tracker DLL since that AE version that first required the change (I forget which Beta that was).

I get a different error message when I try running tracker with original dll and 1108m5 beta. New tracker install.

Thank you Sir for your time and effort, it is very much appreciated. [&o]

ORIGINAL: BigDuke66

ORIGINAL: michaelm

ORIGINAL: BigDuke66

That the refuel setting in the TF screen also used at the home port to set how much is fueled when using the manual option is new to me, did that come with on of the latest version?
But the setting normally just sets how much is refueled at the destination hex aka none-home or waypoint port, correct? Or does it now also work differently?

Not sure what you are referring to?

Well I tried to refuel a TF at its home port but the button was greyed out, so I thought it should than fuel at its destination hex so I changed the setting for that and when I changed it from "Do not refuel" the manual refuel button wasn't greyed out anymore, not only this but setting it ti minimal didn't make them refuel as the TF had enough fuel and as I set it to Full refuel the TF refuel, so altogether the setting for refuel seems not only to work at the destination hex but also at the port where the TF is at the moment.
Maybe I don't remember this correctly but I don't think it was this way in earlier beta versions, don't get me wrong I like it they way it is as the TF can be refueled like I think it needs to, I just wonder because I haven't seen this in earlier versions(or maybe I overlooked it).

Duke, it has been working as you now observe at any port at least as far back as the last official patch, 1106i. I'm pretty sure the Do Not Refuel setting would prevent Refuel From Port in earlier versions than that, also.

ORIGINAL: n01487477

ORIGINAL: asdicus

michaelm several of us have reported problems running 1108m5 beta with tracker. Can I ask is this an issue with the beta or is it a problem the tracker team need to look at ? Up to 1108m2 I had no problems but this is the error I get running a new tracker install with 1108m5 save.

Answered in the Tracker thread... (change the dll in the tracker folder)

Michael - there are 2 different dlls one for the M4 and one the M5 with differing dates - the M5 has a later date ... Is this by design?

Doesn't work for me.

Doesn't work for me, either.
It did before when I tried it before packaging.

Memory issue, not the DLL.

The DLL in the Tracker directory should be dated 9 May

Where I can download DLL from 9 May?

It should be in the Beta2 directory where the new EXE for m5 is located.

I got this ERROR with m5 BETA

ORIGINAL: Schorsch

I got this ERROR with m5 BETA

You didn't attach the file right - try again.

something got lost but here it is again


and tracker says
Error comparing bases (comparebase_unequalsize)

Hi... I also have lost the use of Tracker, after I upgraded to Build 1108m5 yesterday. Please help, as Tracker is a must in running the Japanese economy.

Here is the error messages I now get when I run Tracker-

java.lang.UnsatisfiedLinkError: C:\Matrix Games\WitPTracker AE Release 1.8\pwsdll.dll: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at JNIpws.JNIpws.<clinit>(JNIpws.java:20)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:94)
at witptracker.Main.main(Main.java:135)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)

Guys,

I am running that 1108m5a version of the patch and Tracker is working fine for me. Here is the date and time of the DLL that I am using (note that the date and time of the .zip or .exe that installed the patch might be different).




I should add that this is a DLL from one of the patches that Michael posted. On his and Damian's advice I copied it into the Tracker folder and that got Tracker working again for me.

Thanks witpqs, is working now with the .dll, and I also had to updated my C+++ library. [&o]

Only problem is I lost my old data, but never mind having tracker back is gold anyway.

ORIGINAL: witpqs

Guys,

I am running that 1108m5a version of the patch and Tracker is working fine for me. Here is the date and time of the DLL that I am using (note that the date and time of the .zip or .exe that installed the patch might be different).




I should add that this is a DLL from one of the patches that Michael posted. On his and Damian's advice I copied it into the Tracker folder and that got Tracker working again for me.

I'm happy for you, doesn't work for me.

ORIGINAL: DivePac88
Here is the error messages I now get when I run Tracker-
java.lang.UnsatisfiedLinkError: C:\Matrix Games\WitPTracker AE Release 1.8\pwsdll.dll: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at JNIpws.JNIpws.<clinit>(JNIpws.java:20)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:94)
at witptracker.Main.main(Main.java:135)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)

I am getting this same error message. I wonder what a "side-to-side" configuration error might mean and how to fix it. ???