1
TopoFusion on other OS - Mac / Linux / Delay Initialization Direct3D - OS X and Linux
« on: September 29, 2007, 07:40:25 PM »
Hi,
I'm a long time TopoFusion user that has switched from PC to Mac OS X, and quite like the Mac. But I miss TF.
I had it working under Parallels, but their latest update made it stop working, now it dies with the error "Fatal Error: Couldn't create memory pool surface".
Of course, this is all due to Parallels' (and VMWare Fusion's) limited and flaky support for Direct3D.
This got me wondering if the 2D aspects of TF wouldn't work just fine if the 3D weren't initialized.
Is it possible to delay the initialization of TF? Or possibly have a shortcut in the Start Menu that starts TF in "2D Only Mode".
I don't understand the inner workings of TF, of course, but if Direct3D isn't used for anything but the actual 3D functions, adding a $without_3d variable (or whatever) that prevents the initialization of Direct3D and hides the 3D related buttons and file options seems like it would work.
I have seen other people searching the net for the same solution, for TF specifically. In fact, one had it installed under Linux and it ran, but died at the Direct3D initialization. I wouldn't be surprised if the 2D things worked quite well under OS X and Linux with the 3D parts disabled.
Thanks,
Metzen
P.S. If anyone else would find this useful, speak up... :}
I'm a long time TopoFusion user that has switched from PC to Mac OS X, and quite like the Mac. But I miss TF.
I had it working under Parallels, but their latest update made it stop working, now it dies with the error "Fatal Error: Couldn't create memory pool surface".
Of course, this is all due to Parallels' (and VMWare Fusion's) limited and flaky support for Direct3D.
This got me wondering if the 2D aspects of TF wouldn't work just fine if the 3D weren't initialized.
Is it possible to delay the initialization of TF? Or possibly have a shortcut in the Start Menu that starts TF in "2D Only Mode".
I don't understand the inner workings of TF, of course, but if Direct3D isn't used for anything but the actual 3D functions, adding a $without_3d variable (or whatever) that prevents the initialization of Direct3D and hides the 3D related buttons and file options seems like it would work.
I have seen other people searching the net for the same solution, for TF specifically. In fact, one had it installed under Linux and it ran, but died at the Direct3D initialization. I wouldn't be surprised if the 2D things worked quite well under OS X and Linux with the 3D parts disabled.
Thanks,
Metzen
P.S. If anyone else would find this useful, speak up... :}