There are not many VB.NET GDK developers here and this has been pointed out before in the case of meshes
. As a reminder and warning, you have to keep an eye on your object identities when referencing them using the GDK commands.
Normally, in DBPRO, moving an object by the ID of zero will throw up an 'object number illegal' error message.
make object cube 1,1
move object 0,1 ` Error
But in Visual Basic 2008, I am able to run the following code with no obvious problem.
odb3d.moveObject(0,1) ` No error
But doing so will cause problems after a few sync calls ahead, during the sync call. You get a 'Exception of type 'System.ExecutionEngineException' error. No inner exception or any useful information of what is causing the problem; at first you'd test and eliminate the possible causes function by function, assuming it is something major, but it turns out to be a trivial matter of validating the object ID.
I strongly recommend checking the IDs using property or if blocks when working with 3d objects, meshes and perhaps other assets when using VB.