C2ISTAR tasks aren't persisting

[HeroesandvillainsOS]

I'd just like to report an issue where I believe auto-generated C2ISTAR tasks aren't persisting between sessions. This was initially reported by user Riksen using a vanilla ALiVE/CBA mission. I decided to test it on my end using a vanilla mission on Altis with the exception being Spyder Addons and saw the same behavior.

Here is a server rpt file where I tried to continue a mission. For the purposes of the test, the C2ISTAR module and Data module have debug turned on:

https://www.dropbox.com/s/pyy8r0tcxhx7w17/arma3server_2016-06-27_00-00-58.rpt?dl=0

[HeroesandvillainsOS]

@Friznnit @tupolov @Spyderblack723

I see you guys asked for a repro but I also see that the issue is closed (while this one is still open???)?

Is the rpt not enough? To repro, any vanilla mission with auto-tasking will suffice.

[DavisBrown723]

The other was closed due to duplication, one ticket per issue.

Not sure if anyone has actually looked at this issue, bit short staffed lately.

[tupolov]

Sorry, can you re run your test and post the RPT and the plugin log thanks!

We have hundreds of tasks saved in the DB, so we know it saves :) In your mission it doesn't appear to save anything though. Please ensure you wait until everything is loaded in/init'd before adding a new task.

Ensure data and c2istar have debug on.

Also check the tablet to see if it states it is saving anything.

[HeroesandvillainsOS]

@tupolov, I used the auto-tasking feature so if anything isn't being initialized or is being initialized too quickly, it's not due to me being trigger happy. :)

The tablet server saved and exited just fine in the repro. Everything persisted for the purposes of this test aside from the open task from the previous session.

I'll attempt to it again but I don't really think I could do anything differently. I started the mission. I waited for a task to appear. I server saved and exited. I closed the server. I opened the server and launched the mission. Once it was obvious the task wasn't going to load, I closed the mission and posted the rpt file.

Thanks for taking a look and I'll try again.

[1ncontinentia]

Yeah I can confirm this issue too, repro is pretty much just using auto-tasking. Haven't had any autotasking tasks persist yet I don't think. Cheers for looking into this!

On 19 Jul 2016, at 15:43, HeroesandvillainsOS notifications@github.com wrote:

@tupolov, I used the auto-tasking feature so if anything isn't being initialized or is being initialized too quickly, it's not due to me being trigger happy. :)

The tablet server saved and exited just fine in the repro. Everything persisted for the purposes of this test aside from the open task from the previous session.

I'll attempt to it again but I don't really think I could do anything differently. I started the mission. I waited for a task to appear. I server saved and exited. I closed the server. I opened the server and launched the mission. Once it was obvious the task wasn't going to load, I closed the mission and posted the rpt file.

Thanks for taking a look and I'll try again.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[tupolov]

ah ok auto tasks, not manually added tasks?

[1ncontinentia]

Yup, it's just autotasks as far as I’m aware.

On 19 July 2016 at 16:22:20, Tupolov (notifications@github.com) wrote:

ah ok auto tasks, not manually added tasks?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#37 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ATizBqDp0nwXiMYgrJzvdJAs5Db4vPQSks5qXOurgaJpZM4JARO2
.

[HeroesandvillainsOS]

Yes auto-tasks

[friznit]

This is by design. We do not intend to persist auto-tasks.