[ Beginners] 2 question [ fullscreen + mini app ]
by Lecourtier Benoit · in Torque Game Engine · 04/04/2005 (12:04 am) · 2 replies
Hello !
I'm a beginners and sorry for mon poor language, but i am a french guy and i am not strong in english . . . ;-)
I have two question :
1) First, i want to start my projet... MY projet .... so start with mini app is a good idea ? ( then add script according to my needs... ) . It will not be too difficult?
2) I want to the program start in fullscreen ( and in 1024/724 for example )... It is possible ? I must compliling the torque demo for have a good torquedemo.exe ? it is possible in script ?
Plizzzzz help me ! :-D
I'm a beginners and sorry for mon poor language, but i am a french guy and i am not strong in english . . . ;-)
I have two question :
1) First, i want to start my projet... MY projet .... so start with mini app is a good idea ? ( then add script according to my needs... ) . It will not be too difficult?
2) I want to the program start in fullscreen ( and in 1024/724 for example )... It is possible ? I must compliling the torque demo for have a good torquedemo.exe ? it is possible in script ?
Plizzzzz help me ! :-D
#2
You will then spend the next several months adding back in functionality that Torque has, continually coming back to the forums asking "why doesn't this work", and the answer will be "you took that out when you used the Min App" tutorials.
My strong suggestion to you would be:
1) Spend time with Torque as it is distributed, figuring out why each script does the things it does (as well as the underlying code). My project's team spent more than a year and a half combined between us doing exactly this, but that was our choice.
2) If you feel so strongly that certain parts of Torque don't apply to what you want to do, list them out, and most importantly explain to yourself (or us) why you don't want them, and more importantly what you will do to replace them.
Starting with Min App, and then re-writing script to do the things that you want will be wasting probably 20+ man-years of work that has already been done for you. If you have 20+ years to work on your game, then that is ok!
Otherwise, I would suggest identifying what exactly it is that you don't want, and then cutting that out, instead of cutting everything out and then re-coding what you took out.
Just my suggestion, but as Ben and others have mentioned in other threads, this is how things work when you are working with a game engine--Torque is not an SDK that is designed to offer up pieces of little things you can use.
04/04/2005 (6:13 am)
If you use the minApp tutorials, you will, once you have completed them, have a game environment that accomplishes just about nothing at all. For example, if I remember correctly, one of the steps in the Min App tutorials is to add back in the capability of using the console.You will then spend the next several months adding back in functionality that Torque has, continually coming back to the forums asking "why doesn't this work", and the answer will be "you took that out when you used the Min App" tutorials.
My strong suggestion to you would be:
1) Spend time with Torque as it is distributed, figuring out why each script does the things it does (as well as the underlying code). My project's team spent more than a year and a half combined between us doing exactly this, but that was our choice.
2) If you feel so strongly that certain parts of Torque don't apply to what you want to do, list them out, and most importantly explain to yourself (or us) why you don't want them, and more importantly what you will do to replace them.
Starting with Min App, and then re-writing script to do the things that you want will be wasting probably 20+ man-years of work that has already been done for you. If you have 20+ years to work on your game, then that is ok!
Otherwise, I would suggest identifying what exactly it is that you don't want, and then cutting that out, instead of cutting everything out and then re-coding what you took out.
Just my suggestion, but as Ben and others have mentioned in other threads, this is how things work when you are working with a game engine--Torque is not an SDK that is designed to offer up pieces of little things you can use.
Torque Owner Lecourtier Benoit
in prefs.cs :
$pref::Video::deleteContext = "1";
$pref::Video::disableVerticalSync = 1;
$pref::Video::displayDevice = "D3D";
$pref::Video::fullScreen = "1";
$pref::Video::monitorNum = 0;
$pref::Video::only16 = "0";
$pref::Video::preferOpenGL = "1";
$pref::Video::profiledRenderer = "Direct3D";
$pref::Video::profiledVendor = "Microsoft Corp.";
$pref::Video::resolution = "1024 768 32";
$pref::Video::safeModeOn = "1";
$pref::Video::screenShotFormat = "PNG";
$pref::Video::windowedRes = "800 600";
$pref::visibleDistanceMod = "1";