Crash - Airfield Attack

I reported one of these long ago. I found another while flying for RFC No 46 in late October 1917. Using v2.02.

Got the following error when the campaign mission was loading:






It sent me back to the squadron campaign screen instead of loading in.

Interesting.
I am going to guess the airfield you were attacking had DFW's assigned to it?
Since they also fly in the campaign itself I wonder why you don't always get that message on any campaign mission.
Unless... static aircraft at a field are different than the ones that do the flying?

Nefaro I had that same error yesterday, I didn't get screenshot at the time. It was also an airfield attack. My mission was with 11 RFC in June 1917.

I had a similar one months ago that I posted.

IIRC, a Dev said it was just a bug in part of the random mission generator code for a certain period, or something of the sort. They got it sorted pretty quickly before in the next update.

Guys rather than simply post the error screen here - it does not help us much - send the logs and the screen shot to us on support.

This is likely a database issue and easily fixed but I need the logs.
The problem with the WOFF database is its huuuge so potential for simple errors like this is high as we cannot test every squad and every craft and every period for every mission type despite months of testing.

Finally make sure you are not running 3rd party mission types.

Ta

WM

AI flights of DFW may or may not fly each time obviously, they may also not always be doing a particular mission/action.
If other craft are in squadrons in your region/date they may be used instead too sometimes.

WOFF is so incredible, and has many factors leading to millions of variations on AI flights alone. We try to get across the enormity of the campaign - I bet no other sim does this to this level.

That's why we need the logs and mission right after any error like this, please exit the manager and send the logs.
It is very hard to reproduce or even see some of them so we need those logs to fix.

Thanks for the information Pol.
Figures it wouldn't be something easy!
Don't. change a thing though - the campaign is obviously awesome.

Well... I'll see if the logs are still valid for that mission when I get back to my desktop computer (where they're at).

Hopefully it wasn't replaced by a newer crash that I had not long afterward. I believe the second one was related to some screen tearing or display issue when I was moving my TrackIR view around. That one may not have left any logs since the process straight died, but I'll try to find the stuff from the earlier mission.

Alas if you have run the Manager again they are gone - grab them and send then directly after the issue...directly after exiting the manager

Then I can easily fix the data error.

To give you guys an idea of the immensity of the database....and possibilities of mission gen

~400 squads with on average 100 records per squad file with 65 aircraft types on average 2000 targets per war period slice and 13 mission types with at least 2 sub types per mission type - simplistically one can multiply those all out (in a linear fashion) and you get an idea of how many tests need to be done....

400 x 100 x 65 x 2000 x 13 x 2 - yeah.... 135200000000



HTH

WM

Will do.

I often fly campaigns in or through late 1917 so I'll probably run into it again and get the Logs sent off before restarting.

I had the same problem and I sent the log files to OBD Team yesterday so it is a chance that this problem will be solved soon.

Thanks very much manfras yes its fixed already for 2.03 - item 12)

http://simhq.com/forum/ubbthreads.php/topics/4046945/WOFF_2.03_fixes_and_improvemen#Post4046945

WM