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

Can't launch the bot

B

boynextdoor

Member
Joined
Feb 15, 2016
Messages
79
Reaction score
0
i've seen this error posted in the support section previously but I didn't have any luck following the steps in those posts:

[Trinity 2.14.39] Error in OnEnable: System.TypeInitializationException: The type initializer for 'Trinity.Combat.Abilities.CombatBase' threw an exception. ---> GreyMagic.InjectionDesyncException: Process must have frozen or gotten out of sync: Injection Finished Event was never fired

Problem: I can't get the bot to run with default trinity / adventurer or updated trinity / adventurer. when I log into a game, windowed mode - administrator etc - I go to plug ins and if I try to enable trinity it hangs. if i enable trinity after enabling adventurer, it hangs. The .PDF manual doesn't cover exactly what to do step by step with the latest version, the graphics seem outdated so I don't know.

steps I took:

1. uninstall bot
2. uninstall vcredit and .net framework
3. restart computer.
4. use the buddywizard.exe file to reinstall vcredit and .net framework
5. restart computer
6. check for windows updates
7. restart computer
8. Install the bot with the executable
9. run the bot without copying new trinity and adventurer plugins. Bot hangs at plugin tab.
10. Copy new trinity and adventurer plugins. run the bot again
11. bot hangs.

Running windows 7 x64. tried running diablo through b.net launcher and with the -launch command. out of ideas and have a lifetime license sitting in my inbox.

rip :(
 
Is there a log that you can post for the support team?

You have listed all of the things that I have done to fix my issues in the past.

I can confirm for you that the latest BETA and stable builds work smooth on Win7 x64.

Are you using the DB Installer or the ZIP file?
 
Just tried with beta. same issue.

2016-02-16 03:49:05,979 [1] INFO MainWindow (null) - DemonbuddyBETA v1.1.2923.599 started
2016-02-16 03:49:05,998 [1] INFO MainWindow (null) - This build may have bugs. Use at your own risk!
2016-02-16 03:49:05,997 [1] INFO MainWindow (null) - This is a BETA build of Demonbuddy. This is not meant for general usage. Please report any issues you may have in the beta thread on our forums.
2016-02-16 03:49:09,324 [1] INFO MainWindow (null) - Logging in...
2016-02-16 03:49:09,375 [5] DEBUG MainWindow (null) - Logging in to BestLatency (192.99.20.72)
2016-02-16 03:49:09,455 [5] INFO MainWindow (null) - T: 5247597931921187850 H: 1326901910
2016-02-16 03:49:09,750 [1] INFO MainWindow (null) - Attached to Diablo III with pid: 2172
2016-02-16 03:49:09,760 [1] INFO MainWindow (null) - Flashing window
2016-02-16 03:49:09,761 [1] DEBUG MainWindow (null) - Platform: Microsoft Windows NT 6.1.7601 Service Pack 1
2016-02-16 03:49:09,761 [1] DEBUG MainWindow (null) - Executable Path: D:\Bot\Demonbuddy.exe
2016-02-16 03:49:09,768 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Bot.IBot> - BotManager.Reload
2016-02-16 03:49:09,823 [1] DEBUG BotManager (null) - Bots were reloaded. New bot list:
2016-02-16 03:49:09,823 [1] DEBUG BotManager (null) - Combat Bot v1.1.2923.599
2016-02-16 03:49:09,825 [1] DEBUG BotManager (null) - Script Runner v1.1.2923.599
2016-02-16 03:49:09,825 [1] DEBUG BotManager (null) - Order Bot v1.1.2923.599
2016-02-16 03:49:10,474 [1] DEBUG AssemblyLoader`1 (null) - Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing plugins
2016-02-16 03:49:15,360 [1] INFO Logger (null) - [Trinity 2.14.39] Combat routine is not installed or is not latest version, installing! // VERSION 1.2.0
2016-02-16 03:49:15,368 [1] INFO Logger (null) - Setting up Trinity Logging
22:49:15.373 DEBUG TrinityDebug [Trinity 2.14.39] Copying file D:\Bot\Plugins\Trinity\Combat\Routine\TrinityRoutine.cs to D:\Bot\Routines\TrinityRoutine\TrinityRoutine.cs
22:49:15.375 DEBUG AssemblyLoader`1 Reloading AssemblyLoader<Zeta.Bot.ICombat> - RoutineManager.Reload
22:49:19.043 INFO RoutineManager Chose Trinity as your combat routine
22:49:19.046 DEBUG TreeHooks Replaced hook [RoutineCombat] e17bbe09-d3f6-4ffe-9cbb-085b313e188a
22:49:19.047 DEBUG RoutineManager Routines were reloaded. New routine list:
22:49:19.048 DEBUG RoutineManager Trinity v0.0.0.0
22:49:19.048 DEBUG RoutineManager Generic v1.1.2923.599
22:49:19.312 INFO Logger [Adventurer] (1.3.4.18) initialized.
22:49:19.320 INFO Logger [Trinity 2.14.39] Initialized v2.14.39
22:49:19.656 DEBUG MainWindow There are 3 plugins
22:49:21.752 INFO Logger [Adventurer] Plugin is up-to-date.
22:49:33.206 INFO Logger [Adventurer] (1.3.4.18) enabled.
22:49:34.861 INFO Logger [Trinity 2.14.39] OnEnable start
22:49:34.873 INFO Logger [Trinity 2.14.39] Loading Avoidance Data
22:50:04.931 ERROR Logger [Trinity 2.14.39] Error in OnEnable: System.TypeInitializationException: The type initializer for 'Trinity.Combat.Abilities.CombatBase' threw an exception. ---> GreyMagic.InjectionDesyncException: Process must have frozen or gotten out of sync: Injection Finished Event was never fired
at GreyMagic.Executor.?????????????????????????????????????????(Int32 )
at GreyMagic.Executor.?????????????????????????????????????????(Int32 )
at GreyMagic.Executor.Execute(Int32 timeout)
at GreyMagic.ExternalProcessMemory.CallInjected[T](IntPtr address, CallingConvention callingConvention, Object[] args)
at Zeta.Game.ZetaDia.get_TlsVal()
at Zeta.Game.ZetaDia.?????????????????????????????????????????.?????????????????????????????????????????()
at Zeta.Game.Internals.DynamicPointer`1.get_Value()
at Zeta.Game.ZetaDia.get_ActorCommonData()
at Zeta.Game.Internals.ActorManager.?????????????????????????????????????????()
at Zeta.Game.Internals.ActorManager.Update()
at Trinity.Helpers.MemoryHelper..ctor() in d:\Bot\Plugins\Trinity\Helpers\MemoryHelper.cs:line 34
at Trinity.CacheData.InventoryCache..ctor() in d:\Bot\Plugins\Trinity\Cache\CacheData.Inventory.cs:line 34
at Trinity.CacheData.InventoryCache.get_Instance() in d:\Bot\Plugins\Trinity\Cache\CacheData.Inventory.cs:line 43
at Trinity.CacheData.get_Inventory() in d:\Bot\Plugins\Trinity\Cache\CacheData.cs:line 164
at Trinity.Objects.Item.get_IsEquipped() in d:\Bot\Plugins\Trinity\Objects\Item.cs:line 56
at Trinity.Objects.Set.IsBonusActive(Int32 requiredItemCountForBonus) in d:\Bot\Plugins\Trinity\Objects\Set.cs:line 96
at Trinity.Objects.Set.get_IsThirdBonusActive() in d:\Bot\Plugins\Trinity\Objects\Set.cs:line 91
at Trinity.Objects.Set.get_IsFullyEquipped() in d:\Bot\Plugins\Trinity\Objects\Set.cs:line 153
at Trinity.Combat.Abilities.CombatBase.LoadCombatSettings() in d:\Bot\Plugins\Trinity\Combat\Abilities\CombatBase.cs:line 114
at Trinity.Combat.Abilities.CombatBase..cctor() in d:\Bot\Plugins\Trinity\Combat\Abilities\CombatBase.cs:line 33
--- End of inner exception stack trace ---
at Trinity.Combat.Abilities.CombatBase.LoadCombatSettings()
at Trinity.Trinity.LoadConfiguration() in d:\Bot\Plugins\Trinity\Settings\Settings.cs:line 21
at Trinity.Trinity.OnEnabled() in d:\Bot\Plugins\Trinity\Plugin.cs:line 193
22:50:26.384 DEBUG Logger [Adventurer] Load XAML file : D:\Bot\Plugins\Adventurer\UI\Config.xaml
 
so I uninstalled DB, and diablo.

Reinstalled both on my ssd.

I'm able to run DB and compile everything stock. I ran enditall2 to close all my applications and only ran DB and Diablo. nothing else running. previously I had msi afterburner and riva tuner and random stuff

Once I update try to update trinity and adventurer I get a different error.

Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\BuyItemsFromVendor.cs(16,7) : warning CS0105: The using directive for 'Zeta.Common' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\BuyItemsFromVendor.cs(17,7) : warning CS0105: The using directive for 'Zeta.Bot' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\PutItemsInStash.cs(12,7) : warning CS0105: The using directive for 'Zeta.Common' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\PutItemsInStash.cs(13,7) : warning CS0105: The using directive for 'Zeta.Bot' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\TakeItemsFromStash.cs(12,7) : warning CS0105: The using directive for 'Zeta.Common' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\TakeItemsFromStash.cs(13,7) : warning CS0105: The using directive for 'Zeta.Bot' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Movement\StuckHandler.cs(11,7) : warning CS0105: The using directive for 'System.Threading.Tasks' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Settings\Loot\ItemListSettings.cs(27,7) : warning CS0105: The using directive for 'System.Text' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Settings\Loot\ItemListSettings.cs(28,7) : warning CS0105: The using directive for 'System.IO' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\UI\UIComponents\BindingMember.cs(17,7) : warning CS0105: The using directive for 'Trinity.Technicals' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\UI\UIComponents\MarkupExtensions\WidthToColumnCountExtension.cs(6,7) : warning CS0105: The using directive for 'System' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\UI\Visualizer\RadarCanvas\RadarHitTestUtility.cs(2,7) : warning CS0105: The using directive for 'System' appeared previously in this namespace
Compiler Error: c:\Bot\Plugins\Trinity\Framework\Grid\GridPoint.cs(5,19) : warning CS0660: 'Trinity.Bot.Providers.Grid.GridPoint' defines operator == or operator != but does not override Object.Equals(object o)
Compiler Error: c:\Bot\Plugins\Trinity\Framework\Grid\GridPoint.cs(5,19) : warning CS0661: 'Trinity.Bot.Providers.Grid.GridPoint' defines operator == or operator != but does not override Object.GetHashCode()
Compiler Error: c:\Bot\Plugins\Trinity\Items\ItemWrapper.cs(12,18) : warning CS0660: 'Trinity.Items.ItemWrapper' defines operator == or operator != but does not override Object.Equals(object o)
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\ExtractLegendaryPowers.cs(185,40) : warning CS0028: 'TrinityCoroutines.ExtractLegendaryPowers.Main()' has the wrong signature to be an entry point
Compiler Error: c:\Bot\Plugins\Trinity\Settings\AvoidanceSetting.cs(95,50) : warning CS0108: 'Trinity.Config.AvoidanceSetting.PropertyChanged' hides inherited member 'Trinity.Helpers.NotifyBase.PropertyChanged'. Use the new keyword if hiding was intended.
Compiler Error: c:\Bot\Plugins\Trinity\UI\UIComponents\BindingMember.cs(40,50) : warning CS0108: 'Trinity.UI.UIComponents.BindingMember.PropertyChanged' hides inherited member 'Trinity.Objects.BaseObject.PropertyChanged'. Use the new keyword if hiding was intended.
Compiler Error: c:\Bot\Plugins\Trinity\UI\Visualizer\VisualizerViewModel.cs(674,50) : warning CS0108: 'Trinity.UI.RadarUI.VisualizerViewModel.PropertyChanged' hides inherited member 'Zeta.Common.Xml.XmlSettings.PropertyChanged'. Use the new keyword if hiding was intended.
Compiler Error: c:\Bot\Plugins\Trinity\UI\Visualizer\VisualizerViewModel.cs(677,29) : warning CS0114: 'Trinity.UI.RadarUI.VisualizerViewModel.OnPropertyChanged(string)' hides inherited member 'Zeta.Common.Xml.XmlSettings.OnPropertyChanged(string)'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\AutoEquipItems.cs(172,34) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\AutoEquipItems.cs(205,34) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\CoroutineHelper.cs(168,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\Gamble.cs(136,41) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\Overrides.cs(18,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: c:\Bot\Plugins\Trinity\Coroutines\Resources\CoroutineHelper.cs(168,40) : warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Compiler Error: c:\Bot\Plugins\Trinity\Framework\Avoidance\AvoidanceDataFactory.cs(536,37) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: c:\Bot\Plugins\Trinity\Framework\Grid\TrinityGrid.cs(110,41) : error CS0117: 'Trinity.MathUtil' does not contain a definition for 'GetHeadingFromCardinal'
Compiler Error: c:\Bot\Plugins\Trinity\Framework\Grid\TrinityGrid.cs(558,27) : error CS1061: 'Trinity.Framework.Avoidance.Avoidance' does not contain a definition for 'Handler' and no extension method 'Handler' accepting a first argument of type 'Trinity.Framework.Avoidance.Avoidance' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Bot\Plugins\Trinity\Helpers\IPluginCommunicator.cs(78,30) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: c:\Bot\Plugins\Trinity\Helpers\IPluginCommunicator.cs(115,34) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: c:\Bot\Plugins\Trinity\Helpers\MemoryHelper.cs(65,34) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: c:\Bot\Plugins\Trinity\Helpers\MemoryHelper.cs(75,34) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: c:\Bot\Plugins\Trinity\Helpers\Rotator.cs(122,19) : warning CS0168: The variable 'newAngle' is declared but never used
Compiler Error: c:\Bot\Plugins\Trinity\Helpers\ToStringReflector.cs(16,32) : warning CS0168: The variable 'properties' is declared but never used
Compiler Error: c:\Bot\Plugins\Trinity\UI\UIComponents\Converters\DisplayNameAttributeConverter.cs(43,30) : warning CS0168: The variable 'ex' is declared but never used
Compiler Error: c:\Bot\Plugins\Trinity\UI\UIComponents\Converters\EnumVisibilityConverter.cs(33,30) : warning CS0168: The variable 'ex' is declared but never used
[Adventurer] (1.3.4.18) initialized.
[Adventurer] (1.3.4.18) enabled.
[Adventurer] Plugin is up-to-date.

Going to try again, this time I will delete the trinity folder instead of copying over it.
 
[Adventurer][Rift] Time to kill some scary monsters. Chop chop!
[Adventurer] Opening Greater Rift

finally.

So, to help people in the future, this is what I call the "nuke it from orbit" approach to getting DB to work.

1. uninstall the bot, uninstall d3, uninstall dot net framework and vcredit c++ stuff.
2. restart computer
3. run the buddy wizard exe file that updates your c++ and dot net framework.
4. Restart computer.
5. install d3 and demon buddy. for me I put both on the same drive, my ssd.
6. run windows updates then restart
7. CLOSE ALL PROGRAMS USING SOMETHING LIKE ENDITALL2 OR JUST MANUALLY MAKE SURE NOTHING IS RUNNING - fire up diablo and sit in town, launch db, have DB do an initial compile with stock settings, enable adventurer in plugins first, then enable trinity.
8. shut down bot and diablo
9. copy updated adventurer zip to your bot directory and unzip the file in its entirety directly into the root folder of the bot (i.e. c:/bot or whatever you chose).
10. delete the trinity folder under c:\bot\plugins
11. extract the trinity folder from the zip file for updated trinity into c:\bot\plugins
12. run diablo and sit in town, launch DB, make sure everything compiles, under plugins tab enable adventurer first then enable trinity.
 
You must log in or register to reply here.
Back
Top