TacView files not recorded since last update. Edit: fixed it myself

[AndyJWest]

I've just noticed that I'm no longer getting TacView .acmi files with my track recordings. I got a failed update, and had to delete the 'updates' folder to get IL-2 GB working, which might possibly be related.

 

I have the latest version of TacView, though I don't think that would affect recordings anyway.

 

Edit: Never mind, fixed it. My startup.cfg file had been 'updated' and was set to 'tacviewrecord = 0'. Changing it to 'tacviewrecord = 1' got it working again. Not sure this qualifies as a bug now, but leaving this post here may help anyone else with the same issue.

Edited July 30, 2019 by AndyJWest

[56RAF_Roblex]

I *think* your startup would have remained the same if you had not deleted the Update folder.  The advice on what to do if your update jams is to first make a backup of startup and your views folder before delete the Update folder.  I have not seen anyone say that you needed to backup startup.cfg and put it back after a successful update.

[AndyJWest]

1 hour ago, 56RAF_Roblex said:

I *think* your startup would have remained the same if you had not deleted the Update folder.  The advice on what to do if your update jams is to first make a backup of startup and your views folder before delete the Update folder.  I have not seen anyone say that you needed to backup startup.cfg and put it back after a successful update.

 

You may be right, though given that startup.cfg isn't in the update folder, I can't think of an obvious reason why deleting 'updates' should result in it being rewritten. Not unless it needs to be changed anyway, e.g. to add new parameters. And that would be necessary for a 'normal' update too. The updater does seem to have its quirks though, and trying to figure out why it does what it does is beyond me. Fortunately, I rarely have issues with updating.

[56RAF_Roblex]

18 minutes ago, AndyJWest said:

 

You may be right, though given that startup.cfg isn't in the update folder, I can't think of an obvious reason why deleting 'updates' should result in it being rewritten. Not unless it needs to be changed anyway, e.g. to add new parameters. And that would be necessary for a 'normal' update too. The updater does seem to have its quirks though, and trying to figure out why it does what it does is beyond me. Fortunately, I rarely have issues with updating.

 

Perhaps it moves your old startup.cfg into the update folder while it does the update so it can put it back after? So when you delete the folder and start a new update it can't find your old one and just builds a new default one.

[Dagwoodyt]

thx for info

Edited July 30, 2019 by Dagwoodyt