Non-conobject class

#1 Did you properly use the DECLARE_XXXObject() and IMPLEMENT_XXXObject() macros?

#2 Probably not ; ) could you give me a reference to where I can learn about doing this? (sorry, I'm still really new to the engine) Thanks!

#3 @Brian:

Doing a " f" project wide search for 'declare' or 'implement' from VS should give you a number of great examples to look at.

#4 Probably not ; ) could you give me a reference to where I can learn about doing this? (sorry, I'm still really new to the engine) Thanks!

#5 Sorry about the double post there (out of date page went and refreshed and reposted the data ; )

I'll take a look at that, thanks

#6 Hi, I encountered the same problem even after DECLARE_CONOBJECT(Myobject) and IMPLEMENT_CONOBJECT(Myobject. Is there any other possible mistakes ?
We do not need to put Class Constructor as Console method, right ?
Thanks

#7 As long as you declare_conobject in your object definition header and implement_conobject it somewhere in your code file, you should be fine - though there are different declaration and implementation functions for different sorts of objects. What class is your custom object derived from?

#8 Hi Daniel, I tried to implement a UDPObject (cos Torque only has TCPObject which needs a connection). So basically, I try to copy the template from TCPObject. So as TCPObj, my UDPObject derived from Simbase
Here are the first part of my object
Header file: UDPSocket.h

#include "platform/platformNet.h"
#ifndef _UDPSOCKET_H_
#define _UDPSOCKET_H_

#ifndef _SIMBASE_H_
#include "console/simBase.h"
#endif

//======================================
// sockets
class UDPSocket : public SimObject
{
	//public:
	   //enum State {Disconnected, DNSResolved, Connected, Listening };
	public:
		typedef SimObject Parent;
		[b]DECLARE_CONOBJECT(UDPSocket);[/b]

C++ file: UDPSocket.cpp

#include <iostream>
#include <fstream>
#include <string>
#include <vector>

#include "platform/platform.h"
#include "platform/event.h"
#include "app/net/UDPsocket.h"
#include "console/consoleInternal.h"

[b]IMPLEMENT_CONOBJECT(UDPSocket);[/b]

UDPSocket::UDPSocket()
{
	socket = 0;
}

UDPSocket::~UDPSocket()
{
	Close();
}



bool UDPSocket::InitializeSockets()
{
	#if PLATFORM == PLATFORM_WINDOWS
	WSADATA WsaData;
	return WSAStartup( MAKEWORD(2,2), &WsaData) == NO_ERROR;
	#else
	return true;
	#endif
}
//======================================

void UDPSocket::ShutdownSockets()
{
	#if PLATFORM == PLATFORM_WINDOWS
	WSACleanup();
	#endif
}

All the console methods also defined. What makes me confused is the program keeps generate this error:

c:\torque\torque 3d 2009 pro 1.1 alpha\engine\source\console\consoleobject.cpp(101) : Warning - Couldn't find class rep for dynamic class: UDPSocket
90: Unable to instantiate non-conobject class UDPSocket.
scripts/client/TCPconnection.cs (91): Unable to find object: '0' attempting to call function 'InitializeSockets'
scripts/client/TCPconnection.cs (92): Unable to find object: '0' attempting to call function 'open'

#9 Did you include UDPSocket.cpp in your project? I don't know if Visual Studio has a special way of handling that or if it's the same now in newer versions of Torque, but there used to be a "targets.torque.mk" file in the "engine" directory that specified the files to be included in the engine build.

#10 @Scott: I think both are included, because before that, I got couples of error messages on these files when building engine.

#11 I have the same problem with 3 classes I've created and am now trying to use in script. All 3 have DECLARE_CONOBJECT AND IMPLEMENT_CO_NETOBJECT_V1. Their related datablocks have DECLARE_CONOBJECT and IMPLEMENT_CO_DATABLOCK_V1.

Everything builds fine, but I get a "Warning - Couldn't find class rep for dynamic class:" and "Unable to instantiate non-conobject class ___." assert in the console for each of the 3 classes.

I've successfully added similar classes without any issue, but did not use them in script, other than adding them in the worldeditor.

#12 Debugging from the engine side, the objects are all instantiated, but the datablocks coming in are filled with garbage instead of the values set in the script. So the classes appear to be fine, just not hooked in to the script correctly.

Which is odd because the changes to the script for these classes was pretty much copy/paste/changename from the Player class. Anything worth reading about hooking new conobjects into the script?

#13 Updating...

Running in VS2005, in AbstractClassRep::create, which contains the assert "Couldn't find class rep...", the rep is actually being found and returned and instantiated (duh, that's why it was hitting the ctor and onNewDatablock :-P).

i.e. this is executing correctly

const AbstractClassRep *rep = AbstractClassRep::findClassRep(in_pClassName);
   if(rep)
      return rep->create();

So, from this I get:

(1) Running from Torsion, the rep must be coming back NULL, hence the assert being thrown
(2) Regardless of the nonsense Torsion is doing, the real problem is that the datablocks aren't being initialized with the values that are in the script.

So my new question is

How do datablocks get initialized? If I look at PlayerData for instance, the only place I see values coming in is in unpackData. As far as I can tell, this never gets called.