DX9 Common App Framework

Could you be a little more specific? What part of the framework could use some improvement?

I think he means the AppWizard Dx9 Setup.

I''m also wondering how slow it is to use, because it comes with tons of MFC crap and other stuff.

But on the plus side it has everything initialized, supports dynamic window sizing and fullscreen switching, everything is enumerated and the device gets reset. You also have your main .cpp file which has a D3DApp class with vertual functions, game loop ready...


There must be a performance hit for that though.? I''m guessing it would be better to write everything from the ground up, but alot of the gruntwork is done for you with the MS classes,?

Dima

It says in the SDK that the sample framework should not be used personally, hence the title - it''s a sample. It is built to enable you to make small demo''s quick - not as a full engine.

Yes, it is very, very nice for things like switching modes and fullscreen device enumeration. However, it is difficult to expand it, and if you look at the code, it''s very complicated and bulky for what it does.

I think it''s better, for beginners especially, to write their own from the ground up to gain a better understanding of DirectX itself - I know I did

hmm.. thanx i''m sure now that i will work from the ground up... now, i think it''s easier to use the first tutorial (device creation) and expand it than anything else given in the sdk (summer update + extras)

is there no more than one god or no less than one god?

Where I found the common framework to be very good was in the structure setup to restore, invalidate and delete the DX resources.

www.jeremypardon.com

[edited by - jpardon on January 9, 2004 8:02:41 AM]

hmm... i find the whole dx structure to be rather slow... all these message stuff and the like... when i was younger and did not know about dx i though that it is great.. fast... reliable... easy... not so microsoftish... and don''t tell me to use opengl if i don''t like dx )