Bug in cross-platform game
by J "hplus" W · in Torque Game Engine · 10/08/2006 (11:47 am) · 4 replies
I built Torque on Linux, and am hosting there. Then I try to connect from a client, running the same code, built on Windows. Here's the error I get:
Mapping string: MissionStartPhase1 to index: 8
*** New Mission: FHO/data/missions/loginmission.mis
*** Phase 1: Download Datablocks & Targets
Warning: (c:\torque\sdk\engine\core\bitstream.cc @ 258) Out of range read
... Shape with old version.
ShapeBaseData::preload: Invalid packet, bad datablockId(explosion): 0x253
ShapeBaseData::preload: Invalid packet, bad datablockId(underwaterExplosion): 0x125
Something seems to be different between Windows and UNIX in object marshaling? Does this work for anyone else? Is GarageGames actually running a daily build-and-test cycle that verifies that this works?
Mapping string: MissionStartPhase1 to index: 8
*** New Mission: FHO/data/missions/loginmission.mis
*** Phase 1: Download Datablocks & Targets
Warning: (c:\torque\sdk\engine\core\bitstream.cc @ 258) Out of range read
... Shape with old version.
ShapeBaseData::preload: Invalid packet, bad datablockId(explosion): 0x253
ShapeBaseData::preload: Invalid packet, bad datablockId(underwaterExplosion): 0x125
Something seems to be different between Windows and UNIX in object marshaling? Does this work for anyone else? Is GarageGames actually running a daily build-and-test cycle that verifies that this works?
#2
That's not what their web site is saying:
However, given that Linux didn't even build correctly, maybe it's too much to expect that they test what they're selling?
10/08/2006 (4:07 pm)
Quote:GarageGames do not directly support Linux.
That's not what their web site is saying:
However, given that Linux didn't even build correctly, maybe it's too much to expect that they test what they're selling?
#4
I see that they haven't quite gotten around to doing that yet. After all, it's been less than a year... barely.
All I'm saying is: if they do nightly automated builds of CVS, and run some simple regression that runs some scripts on a troika of Linux, Windows and MacOS machines, they'd catch these problems early, and they'd be easy to fix (because you'd know which check-ins broke something). It doesn't seem to me as if they're quite at that level of maturity, though.
I agree Linux development is harder than Windows. The graphical debugger shells, especially, all kind-of suck, crash, hang, and generally mis-behave. However, if they don't want to support Linux, they should drop the icon from the front page.
10/08/2006 (5:42 pm)
Quote from that blog:Quote:1. Torque is cross platform, but Linux support will lag behind a point release or two. We can manage expectations by saying this upfront in our product pages.
2. In all product pages we should say that using Linux on Torque requires an advanced programmer that understands Linux and the build process in depth, i.e. the build process is unsupported.
I see that they haven't quite gotten around to doing that yet. After all, it's been less than a year... barely.
All I'm saying is: if they do nightly automated builds of CVS, and run some simple regression that runs some scripts on a troika of Linux, Windows and MacOS machines, they'd catch these problems early, and they'd be easy to fix (because you'd know which check-ins broke something). It doesn't seem to me as if they're quite at that level of maturity, though.
I agree Linux development is harder than Windows. The graphical debugger shells, especially, all kind-of suck, crash, hang, and generally mis-behave. However, if they don't want to support Linux, they should drop the icon from the front page.
Torque Owner Stefan Lundmark