netconnection.cc error
by Tyler Turner · in Torque Game Engine · 05/18/2002 (10:05 pm) · 6 replies
Hey,
I have slightly modified my head version of torque and continously get an error when i try to load a mission. The error is...
Fatal:(f:\torque\head\engine\sim\netconnection.cc @671
invalid connection objectID
When i compile i get this warning. this is in the 5/18/02 HEAD version.
netConnection.cc
f:\torque_head\engine\sim\netconnection.cc(194) : warning C4355: 'this' : used in base member initializer list
I don't know whats going on. even someone posting they get the same error will be helpfull
I have slightly modified my head version of torque and continously get an error when i try to load a mission. The error is...
Fatal:(f:\torque\head\engine\sim\netconnection.cc @671
invalid connection objectID
When i compile i get this warning. this is in the 5/18/02 HEAD version.
netConnection.cc
f:\torque_head\engine\sim\netconnection.cc(194) : warning C4355: 'this' : used in base member initializer list
I don't know whats going on. even someone posting they get the same error will be helpfull
#2
05/19/2002 (3:03 pm)
I'm sorry, i'm verry new to c++ coding so don't know a whole lot. Could you explain it a little more so i could figure it out? thanks
#3
Fafhrd
05/19/2002 (3:07 pm)
I've recieved this error, or at least one darn similar many times. So far, it's always been due to an invalid path in my .cs files. ie, I add a new script file containing a few new datablocks, and a path to one of the textures or sounds is wrong. It's never been an actual source code error.Fafhrd
#4
05/19/2002 (3:12 pm)
Thanks Erik, i think that may be what it is. i did add a file to be exec and that could be my problem. I can't test it right now but i'll post here to see if that was the problem.
#5
05/20/2002 (12:57 pm)
this happened to me when I didn't add some skies from one build to a new build but had copied over the missions that requested them.
#6
05/20/2002 (4:18 pm)
It actualy was a bad mission file. its weird though, the mission was a strait new mission just with a different name. hmm
Torque Owner Badguy
and the best way to find out what object is causing it.
is to go ahead and retry the assert, debug and step back in your debugger checking the callstack.
this will lead you to at least an object error.
(by showing you the name)
now you can resolve it as user error and fix the problem with your new object :)
a suggestion is your adding something to the mission not properly initialized.
Or you have maybe busted the serialization somehow, i've done that too :)