Game Development Community

Torque 3D Pro 1.1 Mac Preview - What should I expect?

by Steve Ganem · in Torque 3D Professional · 12/22/2011 (3:36 pm) · 4 replies

I am running Torque 3D Pro 1.1 Mac Preview, and have noticed that Basic Lighting is turned on and enforced by default. I have tried enabling Advanced lighting by uncommenting $pref::machax::enableAdvancedLighting = true; in core/main.cs and by updating client/prefs.cs to use Advanced Lighting, but once my Application launches, and it's trying to render my scene, the screen goes red and my computer locks up (in fact, Torque applications seem to lock up my machine constantly, but that's a different subject).

I have seen many threads that lead me to believe that Advanced Lighting is not supported on the Mac at this point, but I did read some posts which led me to believe that it was at least partially working in 1.1 Preview for the Mac. What is the actual case, and what should I expect?

For reference, I am on a Macbook Pro on OS X 10.6.8 and here are my specs :

Processor : 2.16 GHz Intel Core Duo
Memory : 2 HB 667 MHz DDR2 SDRAM
GPU : ATI Radeon X1600

Thanks in advance,

Steve

About the author

Recent Threads


#1
12/22/2011 (4:22 pm)
As a practical matter, only Basic Lighting works in 1.1. There was work done towards an implementation of AL for the Mac in 1.1, but it's not complete and doesn't really work.

I would stick with BL for now if you're developing for Mac. Better Mac support is coming, but it will be a little while still.
#2
12/23/2011 (9:59 am)
So, assuming we stick with Basic Lighting, is Torque 3D Pro 1.1 Mac Preview suitable for the release of professional applications? As I mentioned, my Torque application seems to crash my machine pretty consistently.

Also, what versions of OS X does this release support?
#3
12/23/2011 (10:23 am)
Quote:So, assuming we stick with Basic Lighting, is Torque 3D Pro 1.1 Mac Preview suitable for the release of professional applications?

Basically, no.

You can work on the development of your game/app with the knowledge that most, if not all, of what you do will still work (better) when it's finally updated. But it would not be robust or stable enough for production use with the current Mac support.
#4
12/23/2011 (10:26 am)
Do you have an idea for the timeframe of the eventual update?