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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

WTF is this???????? Unhandled exception during init: System.NullReferenceException:

alien98

New Member
Joined
Mar 4, 2010
Messages
198
Unhandled exception during init: System.NullReferenceException: Object reference not set to an instance of an object.
Anyone figured out how to avoid this error? I have stopped and restarted the bot, rebooted my computer and reinstalling buddywing is sometimes all that will get it to stop on startup of the bot. I get this error more times than the bot running correctly and I am getting sick and tired of fighting the bot for 15minutes everytime I try to use it so I wanna figure out how to solve this problem. Sure the bot randomly crashes from time to time but for the most part it runs really good for me other than this startup issue that plagues me. Any help you can offer would be great. I have the same issue on multiple computers all running windows7 64bit. I have attatched a log for what its worth.
 

Attachments

in case it helps here are the c+= and net frameworks I have installed
 

Attachments

  • frameworks.webp
    frameworks.webp
    23.4 KB · Views: 128
It happens when it tries to connect to the other swtor.exe... I get it all the time i asked for a parameter of -pid but they haven't gotten back to me.
 
restart both swtor and BW
This happens when starting up SWTOR and Buddywing for the first time and sometimes for the first 4 or 5 times until I reboot and reinstall BW. Restarting bw and swtor is hardly a fix
 
This happens when starting up SWTOR and Buddywing for the first time and sometimes for the first 4 or 5 times until I reboot and reinstall BW. Restarting bw and swtor is hardly a fix


it works after restarting them?
 
In an effort to help you avoid reinstalling anything, try the following (if a BW restart fails to do the trick):

  • Restart SWToR (not just from character select - quit the game and restart it)
  • Delete the BuddyWing/CompiledAssemblies folder
  • Delete the BuddyWing/Settings folder
  • Restart Buddy Wing (have your Buddy Wing key ready to paste when prompted)
  • Reload your working profile
  • Say a prayer and press Start

That's all I've got. :confused:

Good luck!
-D
 
It happens when it tries to connect to the other swtor.exe... I get it all the time i asked for a parameter of -pid but they haven't gotten back to me.

What do you base that on? We exclude the rendering process completely.
 
What do you base that on? We exclude the rendering process completely.
I base this on buddywings logs trying to attach to a PID then buddywing then tells me said pid is already attached to something.

So if i open only 2 buddy wings and 2 swtor.exe's it says 3 swtor.exe PIDS are already attached.

I honestly open and close buddywing about 10-20 times before it shuts up about attaching to another PID and finally initializes to the right PID.

Im not trying to talk shit and i love buddywing im just pointing out from what i can see and programming knowledge that buddywing is either..

Attaching to the wrong PID or the initialization when it tries to read the first memory block it fucks up. I really don't care because the bot works when it does attach to the right PID.

I just would like a -pid parameter and -key parameter like demonbuddy had because it would atleast solve my problem.
 
Last edited:
I base this on buddywings logs trying to attach to a PID then buddywing then tells me said pid is already attached to something.

So if i open only 2 buddy wings and 2 swtor.exe's it says 3 swtor.exe PIDS are already attached.

I honestly open and close buddywing about 10-20 times before it shuts up about attaching to another PID and finally initializes to the right PID.

Im not trying to talk shit and i love buddywing im just pointing out from what i can see and programming knowledge that buddywing is either..

Attaching to the wrong PID or the initialization when it tries to read the first memory block it fucks up. I really don't care because the bot works when it does attach to the right PID.

I just would like a -pid parameter and -key parameter like demonbuddy had because it would atleast solve my problem.

I didn't mean to sound like a dick, sorry. Anyway, it's probably because of an abandoned mutex, does shutting down both BW and SWTOR solve the issue?
 
I didn't mean to sound like a dick, sorry. Anyway, it's probably because of an abandoned mutex, does shutting down both BW and SWTOR solve the issue?
Nope. Not when running in it inside isboxer. If you want I can Teamviewer it to you or give you access to my comp and you can debug/test it all you want.

It just loops through all the swtor.exe's says they are all in use when i have 2 buddywings opened and none get attached they all throw the read memory error.
 
In an effort to help you avoid reinstalling anything, try the following (if a BW restart fails to do the trick):

  • Restart SWToR (not just from character select - quit the game and restart it)
  • Delete the BuddyWing/CompiledAssemblies folder
  • Delete the BuddyWing/Settings folder
  • Restart Buddy Wing (have your Buddy Wing key ready to paste when prompted)
  • Reload your working profile
  • Say a prayer and press Start

That's all I've got. :confused:

Good luck!
-D

Thanks for this Im sure thats what reinstalling Bw was doing for me to get it to work. Restarting the game from scratch and BW didnt work but this does

  • Delete the BuddyWing/CompiledAssemblies folder
 
Nope. Not when running in it inside isboxer. If you want I can Teamviewer it to you or give you access to my comp and you can debug/test it all you want.

It just loops through all the swtor.exe's says they are all in use when i have 2 buddywings opened and none get attached they all throw the read memory error.

Yeah so that has to do with a mutex. I'll look into what could be causing this, thanks.
 
Back
Top