🚀 go-pugleaf

if you have a thread that all it does is execute a function, and it is 
competing with another thread with does more (your VCL thread), and they 
have the same priority, yeah, things are going to go slowly in that 
other thread (the VCL in your case).  When you have a timer happening, 
there is a delay between renderings, during which the computers sources 
are free.  You either need to use a timer, render in a frames per second 
scheme in the thread or turn the priority down.  Turning the priority 
down may not really work.

charlie

Bogdan wrote:
> I have a function that renders a Direct3D scene.If I call this function
> periodically through a timer everything works ok.But if I put the same
> function in a thread the application stops responding, or responds with
> a lot of delay, to its own messages(mouse clicks, movement).The thread
> has TP_NORMAL priority, and the function is called using the Synchronize
> method.
> 
> Here's some sample code:
> In the thread:
> 
> void __fastcall TRenderThread::Execute()
> {
>  while(!Terminated)
>  {
>   Synchronize(f);
>  };
> };
> 
> where f  is:
> 
> void __fastcall TRenderThread::f(void)
> {
>  Render();
> };
> 
> And, using a timer:
> 
> void __fastcall TMainForm::TimerTimer(TObject *Sender)
> {
>  Render();
> }
> 
> Render is the function that renders the Direct3D scene.
> 
> Bogdan.
> 
> 
> 
> 
> 
>