What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[RELEASE] TankLeader 2 (updated for 8.0.7)

Has anyone been able to get the TL2Beta working today?
My event viewer keeps saying - TankLeader.exe terminated because of unhandled exception. Also could we get rid of the "would you like to see the changelogs?" (if I did. I would look in the folder or online.)

More error trapping required that doesn't just hang the app.
get the error trapping perfect first then the app won't crash. It will just continue after logging an error.
I shouldnt have to use task manager everytime it crashes.

You have a great idea here and after decompiling it I can see that lots of work has been put in.
Unfortunately you are missing the basics. Solid platform with the basics.

This should be a one step at a time improvement on TankLeader1 not a complete rewrite.

DERV
 
there was a windows 7 64 bit - the bot working. tanks are added to the queue. and all was well. now replaced by another assembly 64 u all. perstal tanks added to the queue. read somewhere that you can manually add the tanks in place. can somebody explain to me how a complete nuba (preferably with pictures or vidio) how to add tanks to the queue manually.
 
Has anyone been able to get the TL2Beta working today?
My event viewer keeps saying - TankLeader.exe terminated because of unhandled exception. Also could we get rid of the "would you like to see the changelogs?" (if I did. I would look in the folder or online.)

More error trapping required that doesn't just hang the app.
get the error trapping perfect first then the app won't crash. It will just continue after logging an error.
I shouldnt have to use task manager everytime it crashes.

You have a great idea here and after decompiling it I can see that lots of work has been put in.
Unfortunately you are missing the basics. Solid platform with the basics.

This should be a one step at a time improvement on TankLeader1 not a complete rewrite.

DERV

The code base for TankLeader 1 is beyond salvation, and it's not worth the effort to bandaid every single issue that code base has only to cause other issues. Anyway, do you have a stack trace or any other sort of error description with that unhandled exception that's useful by chance? :)
 
Can't add tanks in queue priority, because + and - are grey (disabled). I have chosen the tank in WOT client and i see the name in the name bar.
What should i do? o_O
 
Can't add tanks in queue priority, because + and - are grey (disabled). I have chosen the tank in WOT client and i see the name in the name bar.
What should i do? o_O

Send me a PM on the forums and hit me up on Skype. We need much more information and people who are having this issue to resolve it fast, thanks!
 
When will be ready the main software?
We all pay for a simple interface not for programming interface and xml.
Will be fair for us to extend all the licenses with a few days.
Move please. Premium accounts costs money.
Regards,
R.
 
Aevitas
would you be able to add that if the tank is stuck somewhere it to cancel and then get around the obstacle or dodge.
 
Problem with aiming!
No custom profile found for map 33_fjord. Using default objective waypoints.
Poi set to Wait. Reason: Waiting for time 00:00:27 to pass...
Poi set to Objective. Reason: Moving to complete objective
Poi set to Kill. Reason: Aiming to kill enemy at <-55.70397, 14.38432, 26.87265>.
Poi set to Kill. Reason: Aiming to kill enemy at <161.717, 19.28248, 33.24043>.
Poi set to Kill. Reason: Aiming to kill enemy at <-45.77033, 9.780226, 18.47532>.
Poi set to Kill. Reason: Aiming to kill enemy at <157.8224, 19.65599, 39.04349>.
Poi set to Kill. Reason: Aiming to kill enemy at <151.9754, 20.18834, 47.80151>.
Poi set to Kill. Reason: Aiming to kill enemy at <23.26622, 0.6237386, -161.1752>.
Poi set to Kill. Reason: Aiming to kill enemy at <-63.17787, 4.639959, -350.2637>.

My bot tracking down all the targets in turn. Stops and does not move forward. Targeting even when the target is behind an obstacle (mountain, rock, etc.)
Next case. The BoT is not able to choose the appropriate objectives. BoT is not interested in that for me to shoot. BoT is not exposed to selected targets and targets located closer.

Im stupid or this bot is stupid. How can you ask money for something that does nothing. If it is busier turn honors. But at the moment BoT does not think about what to target ..
 
So atm i have only 2 major issues with the TL2 beta.
1. It runs in and out of cap zone when finishing objective. This is both with or without profiles and you surely get alot of flak from other players while doing this :p
2. Face hull towards enemy when shooting. If you get tracked or blocked it doesnt shoot untill hull is facing the enemy, which is extremely useless.
 
Problem with aiming!


My bot tracking down all the targets in turn. Stops and does not move forward. Targeting even when the target is behind an obstacle (mountain, rock, etc.)
Next case. The BoT is not able to choose the appropriate objectives. BoT is not interested in that for me to shoot. BoT is not exposed to selected targets and targets located closer.

Im stupid or this bot is stupid. How can you ask money for something that does nothing. If it is busier turn honors. But at the moment BoT does not think about what to target ..

Have you checked that you don't have artillery mode setup for your tanks ?
 
Anyone figure out why the client crashes instantly after the changelog prompt appears?
 
The code base for TankLeader 1 is beyond salvation, and it's not worth the effort to bandaid every single issue that code base has only to cause other issues. Anyway, do you have a stack trace or any other sort of error description with that unhandled exception that's useful by chance? :)

Hey I just got home from work and had a chance to review the notes.
Here is the scenario.

I start Wot Client, then I start the TankLeader2 Beta and it logs in. then it asks if I want to view the ChangeLog files. Once I answer it crashes the WotClient and the TL2 log shows that it was successful at initializing. but now I cant do anything because Wot is closed. So now I try to close TL2 and it just blackens out the window and hangs. The windows event log shows this error and stack trace.

Application: TankLeader.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
at System.Windows.Window.WmClose()
at System.Windows.Window.WindowFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at System.Windows.Application.Run()
at TankLeader.App.Main()

I hope that will be helpful. I think this just supports the idea that once the Wot client crashes the TL2 can't use the hooks anymore and crashes.

DERV
 
HELP ME. I deleted TankLeader 2.0.206.77 for update lastest version.
But the lastest version of TL2 don't work with my WOT 8.5, my server (VietNam) not update 8.6 right now.
Please give me the link of TankLeader 2.0.206.77, Aevitas or someone, help me, thanks!
 
I installed the card profiles, tanks added to the queue, hit start. And all of that does not happen. Help what to do?
And how to create tags on the map?
 
HELP ME. I deleted TankLeader 2.0.206.77 for update lastest version.
But the lastest version of TL2 don't work with my WOT 8.5, my server (VietNam) not update 8.6 right now.
Please give me the link of TankLeader 2.0.206.77, Aevitas or someone, help me, thanks!


Not sure how to help on this one? Most players are on the 8.6
 
Yeah, N.America Server player here, still on 8.5. 2.0.206.77 still works fine, but the new 2.0.218.81 fails on every occasion. It automatically closes the WoT window whenever it logs in.

Anyhow, I'm not complaining or anything, the old version still works fine, and the update is coming in a few short days.
 
Hey there!

Still not able to use TL2 since patch.

Europe/Switzerland
Started both, WOT and TL2 as Admin.
Always crashes upon start.

Log File
[13:11:18.511 D] Reloading AssemblyLoader<Scylla.CommonBot.ITargetingProvider> - Initializing
[13:11:22.559 N] Logging in...
[13:11:22.819 N] Login Success!
[13:11:22.821 N] Welcome to TankLeader 2. Please wait until initialisation finishes.
[13:11:22.822 N] Windows NT 6.1.7600.0
[13:11:23.974 N] Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
[13:11:25.678 N] [ProfileManager] Reloading profiles from disk.
[13:11:25.679 N] Finished loading profiles; found 0 profiles in total.
[13:11:25.683 D] Custom Python types set up successfully.
[13:11:25.775 D] Ekans set up successfully.
[13:11:25.778 D] Garage set up successully.
[13:11:25.779 D] Player object set up successfully.
[13:11:25.780 N] ScyllaWot initialisation has completed.
[13:11:25.782 D] BotMain initialisation completed.
[13:11:25.785 D] Reloading AssemblyLoader<Scylla.Common.Plugins.IPlugin> - Initializing
[13:11:26.116 D] Reloading AssemblyLoader<Scylla.CommonBot.ITankRoutine> - Initializing
[13:11:26.185 D] System.IO.FileNotFoundException: Die Datei oder Assembly "file:///C:\Users\Bora\Desktop\t2\CompiledAssemblies\HotspotLogger_635074170857851563.dll" oder eine Abh?ngigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
Dateiname: "file:///C:\Users\Bora\Desktop\t2\CompiledAssemblies\HotspotLogger_635074170857851563.dll"
bei System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
bei System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
bei System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
bei System.Reflection.Assembly.Load(AssemblyName assemblyRef, Evidence assemblySecurity)
bei System.CodeDom.Compiler.CompilerResults.get_CompiledAssembly()
bei Scylla.Common.Compiler.CodeCompiler.Compile()
bei Scylla.Common.AssemblyLoader`1.Reload(String reason)
bei Scylla.Common.AssemblyLoader`1..ctor(String directory, Boolean detectFileChanges)
bei Scylla.Common.Plugins.PluginManager.ReloadAllPlugins(String pluginsDirectory, Boolean reloadOnFileChange)
bei TankLeader.MainWindow.Initialise()

WRN: Protokollierung der Assemblybindung ist AUS.
Sie k?nnen die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) auf 1 festlegen.
Hinweis: Die Protokollierung der Assemblybindungsfehler f?hrt zu einer gewissen Leistungseinbu?e.
Sie k?nnen dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] entfernen.

[13:11:26.185 N] Initialisation failed! See the above error messages.
 
WRN: Protokollierung der Assemblybindung ist AUS.
Sie k?nnen die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) auf 1 festlegen.
Hinweis: Die Protokollierung der Assemblybindungsfehler f?hrt zu einer gewissen Leistungseinbu?e.
Sie k?nnen dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] entfernen.

Stell mal die Sprache auf englisch ein sonst kann dir hier keiner helfen :) Hast du die Registry mal versucht zu ?ndern, wie es dort in der Meldung steht?
 
Back
Top