Game Development Community

Differences between Mac and PC torque

by Peter Robinson · in Torque Game Builder · 03/01/2007 (3:38 pm) · 5 replies

I've been making my game on the Mac for years now and just recently had someone testing it on the PC. Everything works great except for this one very strange error. The bad guys completely left the battle field. They should be kept from doing this by the setWorldBounds (or something) set to clamp. Is there any subtle differences in the way the Mac build works from the way the PC build works that I should be aware of? It's almost like the baddies go toward something when they collide with it instead of away. Is the coordinate system different somehow between Mac and PC?

-Peter

About the author

A programmer who has been using the Torque2D game engine since the early adopter days. My game is Pirate Code and it can be found at www.circuithive.com. It will be arriving on Steam in 2016.


#1
03/02/2007 (12:08 pm)
I would check that you packaged the PC build with the same exact version that you are using on the Mac. Also, make sure you are comparing build to build, in other words not comparing the build PC .exe to your Mac version running from within the level editor. There are no large differences of the type you mention between OS versions, that I have come across.

Greg
#2
03/03/2007 (1:43 pm)
I think the Mac version is 1.1.1 where as the PC version is 1.1.3. I don't really see why the bad guys could leave their world bounds on the PC but not the Mac though. Also, I'm one of people who started with the Early Adopter release so I don't use the level editor. It probably is something missing in the build though. Thanks!

-Peter
#3
03/03/2007 (2:06 pm)
Did you clear all DSO before trying? (just to make sure)
Because old DSO potentially could cause some problems.
#4
03/03/2007 (2:47 pm)
No, but I'll try that. Thanks!

-Peter
#5
03/06/2007 (7:45 pm)
Good news! Well, actually its not that good. I just upgraded my mac version to 1.1.3 and now the bug is in both. Which means something changed between 1.1.3 and 1.1.1 that caused the bug. So where can I find a list of complete changes?

-Peter