Latest blender2ogre and Tundra revisions cannot update dynamically

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use the latest blender2ogre and Tundra revisions
2. Open Blender and enable the blender2ogre functionality
3. Open Tundra from Blender and move an object around

What is the expected output? What do you see instead?
The object you try to move around in Blender does not get updated in Tundra.  
It outputs 'send data error'.  The exception being thrown is a socket error.  
The exception says "(111, 'Connection refused')".

What version of the product are you using? On what operating system?
Gentoo Linux
blender2ogre revision 0dc0748d7fee 
Tundra revision d3d237e5a8fcb53413debeab2a1307c89f01460e

Please provide any additional information below.

Original issue reported on code.google.com by vax...@gmail.com on 27 Mar 2012 at 9:13

[GoogleCodeExporter]

The port number was wrong.  After fixing the right port number, it now outputs:
"
UDPMessageConnection::QueueInboundDatagram: Discarding received over-sized 
datagram (2048 bytes)!
"

When decreasing the buffer size, it outputs:
"
2.30079, 0x3b825c0: Queued new connection attempt from 127.0.0.1:43464.
2.32776, 0x1230e00: New inbound connection attempt from 127.0.0.1:43464 with 
datagram of size 1024.
2.32784, 0x1230e00: Network::CreateUDPSlaveSocket: Connected an UDP socket to 
127.0.0.1:43464 (UDP Slave, connected=true, readOpen: true, writeOpen: true, 
maxSendSize=1400, sock: 0.0.0.0:2345, peer: (-), socket: 32, this: 0x3f24cc0).
User connected from 127.0.0.1:43464, connection ID 1
2.35108, 0x1230e00: Accepted new UDP connection.
2.42579, 0x3b825c0: Malformed UDP packet! Byteofs 61, Packet length 1024. 
Expected 1792 bytes of message content, but only 963 bytes left!
2.42599, 0x3b825c0: kNet::NetException thrown when processing 
UpdateConnection() for client connection: Malformed UDP packet received! 
Message payload missing.
2.42604, 0x3b825c0: Socket::Close(): Closing socket 127.0.0.1:43464 (UDP Slave, 
connected=true, readOpen: true, writeOpen: true, maxSendSize=1400, sock: 
0.0.0.0:2345, peer: (-), socket: 32, this: 0x3f24cc0).
2.43433, 0x1230e00: MessageConnection::Close: Closed connection to :0 (UDP, 
connected=false, readOpen: false, writeOpen: false, maxSendSize=1400, sock: 
(-), peer: (-), socket: 0, this: 0x3f24cc0).
2.47623, 0x1230e00: Network::DeleteSocket: Closed socket 0x3f24cc0.
2.4945, 0x1230e00: Client (Not connected) disconnected.
User disconnected, connection ID 1
"

Original comment by vax...@gmail.com on 28 Mar 2012 at 2:03

[GoogleCodeExporter]

http://code.google.com/p/blender2ogre/source/browse/io_export_ogreDotScene.py#51
21

Turns out the only thing I had to do was uncomment this line

Original comment by vax...@gmail.com on 30 Mar 2012 at 10:54

[GoogleCodeExporter]

if you uncomment that line, as noted: tundra2.1.2 will ignore entity id's, and 
that breaks streaming.  Can you confirm that entity ids remain intact?  You 
should be able to test this by creating new objects, texture them, change their 
materials, and if all looks ok then entity ids are in sync.

Original comment by goatman.py@gmail.com on 3 Apr 2012 at 4:56

• Changed state: Accepted