Bug #3437

skipTime and setDate freeze the game to 0 fps for a short while

Added by Sickboy over 5 years ago. Updated 5 months ago.

Status:Assigned Start date:08/07/2009
Priority:Low Due date:
Assignee:Dwarden % Done:

0%

Category:Scripting: Problem
Target version:-
Affected ArmA II version:1.63 Beta First affected build:
Reproduced by another DH user:Yes First affected ArmA II version:
I am using some Mods:No Single / Multi Player?:Both
I am using: BIForumURL:
Reproducible for you:Yes NGUrl:
Related to content of DLC: WIKIurl:

Description

e.g skiptime 0.1 or setDate date

FPS drops down to 0 for a short while.

Problem seems bigger on Chernarus than Utes.

Repro.Chernarus.zip (2.2 kB) kju, 12/29/2010 20:48


Related issues

related to ARMA2 Community Issue Tracker - Feature #2568: Add global weather and daytime Assigned 07/05/2009
duplicated by ARMA2 Community Issue Tracker - Bug #5896: Skiptime Lag Duplicate 11/17/2009 12/01/2009

History

Updated by Xeno over 5 years ago

Good find. I also wanted to check setDate when I get home from work, not necessary now anymore :) (am using it too)

Updated by Fireball over 5 years ago

  • Category set to Game freezes
  • Status changed from New to Assigned
  • Maxmem parameter deleted (Not set)

Updated by Fireball over 5 years ago

  • Due date set to 09/07/2009

Updated by sbsmac over 5 years ago

The severity of the effect also seems to depend on the weather/time of day. Perhaps it's something to do with changing the lighting conditions ?

Updated by Fireball over 5 years ago

  • Due date changed from 09/07/2009 to 09/27/2009

Updated by zGuba over 5 years ago

  • Status changed from Assigned to Feedback
  • Assignee set to Sickboy
  • Maxmem parameter set to Not set
  • Reproduced by another DH user set to No

Updated by zGuba over 5 years ago

  • Due date changed from 09/27/2009 to 10/10/2009

Updated by Fireball over 5 years ago

  • Due date changed from 10/10/2009 to 11/10/2009
  • CPU set to Please specify!

Updated by ceeeb over 5 years ago

Can confirm this bug using beta 59323. The game freezes for about 1 second with either command.

Updated by alef over 5 years ago

  • Due date changed from 11/10/2009 to 11/13/2009
  • Status changed from Feedback to Assigned
  • Assignee deleted (Sickboy)
  • Affected ArmA II version changed from 1.03.58627 to 1.05 BETA
  • Reproduced by another DH user changed from No to Yes
  • CPU changed from Please specify! to n/a

Updated by kju over 5 years ago

  • Due date changed from 11/13/2009 to 01/02/2010

Updated by Dwarden almost 5 years ago

  • Assignee set to Dwarden

Updated by Dwarden almost 5 years ago

  • Priority changed from Normal to Low

this is more likely as designed due amount of things which engine needs to recalculate ...
lowering priority unless proved it break something fatally

Updated by takbal almost 5 years ago

Looks like the engine is doing something in each 1-1.5 in-game minutes which blocks the entire rendering for a while. Somehow it can accumulate with larger skips.

One functionality what this lag makes uglier is FastTime in Warfare, where timeSkip or setDate is continuously applied. The problem is not so prominent if skipTime amount is quite small, like <0.02. SetDate is completely useless as it smallest skip (1 minute) is lagging as well.

As SetDate is the only way to avoid jumping clouds with overcast, this lag practically makes FastTime and weather exclusive. Please either fix this or make the clouds unaware of skipTime.

Strange is that I cannot remember this lag from earlier patches when I played with both functions, so probably it was introduced later.

Updated by kju almost 5 years ago

  • Due date changed from 01/02/2010 to 07/16/2010
  • Affected ArmA II version changed from 1.05 BETA to 1.06 BETA

Agreed. It should be analyzed as it was no issue in a1 nor in a2 to some patch.

Updated by takbal almost 5 years ago

Probably set bug priority back to normal? It will never get dealt with if it stays on low. And we will never see nights again in Warfare...

Updated by kju almost 5 years ago

Well you can read the argument above your post by Dwarden.
Prove or with arguments make him think otherwise. Ok?

Updated by takbal almost 5 years ago

My argument is stated above: it breaks weather and fasttime together. With fasttime you also need frequent time updates to make a sensible time compression, which is ugly (jumpy shadows and backgrounds). I hope Dwarden is reading it.

I have tried the following with different STEPTIME values:

[] spawn {for [{_x=1},{_x<=10},{_x=_x+1}] do {sleep 1; skiptime STEPTIME;};}

The lag exactly kicks in at STEPTIME=0.0333, which is skipping 2 minutes in game time. Anything larger will freeze the game for more than a second at each update, anything lower will run smooth without any problems, at least in my case. So it is not a continuous issue which gets worse with larger skips, rather some hardcoded limit. It can be a bug as well, as it is improbable that with 0.0334 the engine cannot do something what it could with 0.0332.

With SetDate, even 1 minute skips lag:

[] spawn {for [{_x=1},{_x<=10},{_x=_x+1}] do {sleep 1; setdate[date select 0,date select 1, date select 2, date select 3, (date select 4)+1];};}

So it is not even consistent between skipTime and SetDate. If SetDate worked with 1 minute time skips, that would be somewhat better.

Updated by Dwarden almost 5 years ago

  • Priority changed from Low to Trivial
  • Target version set to NextGen
  • Audio card set to Please specify!
  • Size of OS swap file set to Please specify!
  • I am using some Mods set to No
  • Reproducible for you set to No

Updated by kju almost 5 years ago

  • Due date changed from 07/16/2010 to 08/01/2010
  • Target version deleted (NextGen)

Updated by takbal over 4 years ago

Dwarden can you explain please why it got trivial priority? This bug breaks weather in all missions which use FastTime. I do seriously miss thunderstorms.

I do not believe a bug is trivial which makes day/night cycle and weather mutually exclusive.

It cannot have a serious technical reason because skipTime does not lag up to 2 minute changes, but setDate does. Just make setDate do the same as skipTime, and we will not have the jumping clouds anymore.

Updated by kju over 4 years ago

  • File Repro.Chernarus.zip added
  • Due date changed from 08/01/2010 to 03/01/2011
  • Priority changed from Trivial to Normal
  • Affected ArmA II version changed from 1.06 BETA to 1.58 BETA
  • I am using set to CO (A2+OA)
  • Reproducible for you changed from No to Yes

Would be good to see some optimization here.

Updated by Dwarden about 4 years ago

  • Priority changed from Normal to Low
  • I am using deleted (CO (A2+OA))
  • Language set to Please set for missions

Updated by kju over 3 years ago

  • Category changed from Game freezes to Scripting: Problem

Updated by looter over 2 years ago

Would be great for this bug to get some love, it pretty much makes any mission that slowly transitions the time (Day/Night for example) very annoying to play, FPS Drops to 0 for everyone every time skipTime is called.

Updated by kju over 2 years ago

  • Due date deleted (03/01/2011)
  • Affected ArmA II version changed from 1.58 BETA to 1.62.95248

Updated by Sa-Matra over 2 years ago

Problem is still actual and causes a lot of trouble with our Wasteland mission, the more you play the more freeze is being produced by skipTime command. Dear devs, please do something about it.

Updated by player2 5 months ago

  • Affected ArmA II version changed from 1.62.95248 to 1.63 Beta
  • Single / Multi Player? set to Both

Still happens, could write a lot of interesting code if it didn't.

Also available in: Atom PDF