[Magn0733]

Hey guys.

I've been programming in directX for some days now, and things start to make sense to me now
But one things do seems to pass my mind.

The thing is when I prepare the Instantiate D3D etc. I call my InitD3D function in WinMain.
As far as i understod WinMain worked as the normal Main method? (Updating each frame?)
So i wonder do i intialize my D3D each frame and why call it in WinMain and not make a class and call it once with a constructor?

Hope you can anwser my question.

Thanks in adavance!

[anonymous26]

WinMain() is the operating system entry point for your program, so the OS effectively only knows what is either directly or indirectly called within WinMain().

No you do not initialize D3D each frame, you initialize on startup and clean up on program shutdown. You should be seeing this in the SDK example that come with the DirectX distribution.

[Magn0733]

ButchDean, on 03 May 2013 - 02:19 PM, said:

WinMain() is the operating system entry point for your program, so the OS effectively only knows what is either directly or indirectly called within WinMain().

No you do not initialize D3D each frame, you initialize on startup and clean up on program shutdown. You should be seeing this in the SDK example that come with the DirectX distribution.

But WinMain is called each frame right?
So how is it that the Initialize function where i set up D3D is only called once?

Sorry if i'm a bit slow on this but it seems a bit conffusing

[anonymous26]

No, WinMain() is not called each frame.

[aaron1178]

Hello,

WinMain is the applications entry point. Without this method, your compiler will chuck an Unresolved External Symbol error at you. As said, WinMain() is not called each frame. In your WinMain() method, you will have a 'while' loop that keeps the 'game' looping, hence, each frame, is when the while loop repeats.

In the 'while' loop, you call all the necessary functions that you need to call, such as BeginScene, EndScene(for your DirectX renderer), and such assortments as AI calls, Animation calls, GUI/HUD calls and even Physics calls.

I strongly suggest that you learn some more on C++, the WinApi and DirectX.

I've found some tutorials here on Dream.In.Code that may help you:

Dream.In.Code C++ Basics Tutorials
Introduction to the Windows API
Introduction to DirectX and C++
DirectX Tutorial Series

Hope it helps

Aaron1178

[Magn0733]

aaron1178, on 03 May 2013 - 05:08 PM, said:

Hello,

WinMain is the applications entry point. Without this method, your compiler will chuck an Unresolved External Symbol error at you. As said, WinMain() is not called each frame. In your WinMain() method, you will have a 'while' loop that keeps the 'game' looping, hence, each frame, is when the while loop repeats.

In the 'while' loop, you call all the necessary functions that you need to call, such as BeginScene, EndScene(for your DirectX renderer), and such assortments as AI calls, Animation calls, GUI/HUD calls and even Physics calls.

I strongly suggest that you learn some more on C++, the WinApi and DirectX.

I've found some tutorials here on Dream.In.Code that may help you:

Dream.In.Code C++ Basics Tutorials
Introduction to the Windows API
Introduction to DirectX and C++
DirectX Tutorial Series

Hope it helps />

Aaron1178

Ahh, thanks.
Don't think i need to study more c++ (of course you can never learn enough). But i don't seem to find myself questioning what thing does. Only the WinMain was a bit unclear for me cause the thing i read about it kinda made me belive that it was a every frame call. which didn't make much sense to me. And that was why i posted!
Anyways thanks it's much more clear now

[stayscrisp]

MSDN is awesome