Quote:

Original post by deffer Quote: Original post by gorogoro So I changed the Update code to something like this: *** Source Snippet Removed *** But that if is really really ugly. And things are kept hard coded. :s I didn't mean to clamp it in here, but immediately when you're geting the value from the timer (possibly in the main loop). This kind of hardcoding is well known - it enforces slowdown of the gameplay when desired frame rate cannot be achieved. Quote: Original post by gorogoro By the way with this if statment the thing works just fine. Good for you! Now go fix that mass/force issue I was bugging you about before. ~def

	static double lastTime = Core::GetTimer().GetTimeSec();			double curDeltaTime = Core::GetTimer().GetTimeSec() - lastTime;						// update last time			lastTime += curDeltaTime;

Quote:

Original post by gorogoro Quote: Original post by deffer Quote: Original post by gorogoro So I changed the Update code to something like this: *** Source Snippet Removed *** But that if is really really ugly. And things are kept hard coded. :s I didn't mean to clamp it in here, but immediately when you're geting the value from the timer (possibly in the main loop). This kind of hardcoding is well known - it enforces slowdown of the gameplay when desired frame rate cannot be achieved. Quote: Original post by gorogoro By the way with this if statment the thing works just fine. Good for you! Now go fix that mass/force issue I was bugging you about before. ~def ARGH! I'm freaking out and running out of time! I don't now how to fix this stuff :p. Because the value 0.0065 (if(elapsedTime > 0.0099)elapsedTime = 0.0065) is working on my computer. But who garanties that it is still going to work on other computer or even at XBox360?? :S DAmned. I'm looking to the files, with lot of values, and I don't now what to do. This elapsedTime is messing me a lot. Here is the code I'm using to calculate the elapsedTime: *** Source Snippet Removed *** Wich is done at every rendering step! The elapsedTime is the lastTime variable.

Quote:

Original post by gorogoro Here is the code I'm using to calculate the elapsedTime: *** Source Snippet Removed *** Wich is done at every rendering step! The elapsedTime is the lastTime variable.

static double lastTime = Core::GetTimer().GetTimeSec();double curDeltaTime = Core::GetTimer().GetTimeSec() - lastTime;			// update last timelastTime += curDeltaTime;const double timeDiffToUpdate = clampMinMax(curDeltaTime, 0, 1.0/g_MinFrameRate);// do various updates using only "timeDiffToUpdate" variablemyAgent.Update(timeDiffToUpdate);myCamera.Update(timeDiffToUpdate);// ...

Quote:

Original post by gorogoro One thing I just remembered now. I'm always using the World cordinate system. Could it be wrong? Should I use the local coordinate systems?

Quote:

Original post by deffer Quote: Original post by gorogoro Here is the code I'm using to calculate the elapsedTime: *** Source Snippet Removed *** Wich is done at every rendering step! The elapsedTime is the lastTime variable. You should definitely use "curDeltaTime" variable. *** Source Snippet Removed *** Actually, you should check if this actually is the problem you were facing and "you think" you've resolved. Is "curDeltaTime" happen to be negative sometimes? Is it exceeding some high treshold value? If both answers are: no - the problem lies totally elsewhere. Quote: Original post by gorogoro One thing I just remembered now. I'm always using the World cordinate system. Could it be wrong? Should I use the local coordinate systems? It hardly matters, so you ought to use the one that more intuitively fits the concept. In other words, nope, you should stick to World Coordinates.

Quote:

Original post by gorogoro And is that procedure OK? Is it usual to do in games? I should say that this game is going to be plattform independent (should work on PC and Xbox for now, but later it is going to work on ps3 and other consoles).